ISSUE-165: Enforcing non-contradictory provenance.


Enforcing non-contradictory provenance.

Accessing and Querying Provenance
Raised by:
Timothy Lebo
Opened on:

2. Accessing provenance information

"... the availability of provenance information about a resource may vary ... provided that such change does not contradict any previously retrieved information."

I could imagine a service that reports the creation date of a file, but "forgot" to handle a daylight savings transition and reported a time that is incorrect by one hour. Once this bug was identified and corrected, must an entirely NEW provenance URI be used to offer the corrected provenance information? According to the "non-contradictory" requirement stated in PAQ, one could not just tweak the true modification time and offer it at the original provenance URI.

Is this the desired intent?

Related Actions Items:
No related actions
Related emails:
  1. Re: PROV-ISSUE-165 (TLebo): Enforcing non-contradictory provenance. [Accessing and Querying Provenance] (from on 2011-11-24)
  2. PROV-ISSUE-165 (TLebo): Enforcing non-contradictory provenance. [Accessing and Querying Provenance] (from on 2011-11-23)

Related notes:

I've added a note in section 2 to try to clarify this.

Graham Klyne, 5 Jan 2012, 12:42:01

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 165.html,v 1.1 2013-06-20 07:37:25 vivien Exp $