ISSUE-79: what is the contract associated with provenance-uris
provenance-uri-contract
what is the contract associated with provenance-uris
- State:
- CLOSED
- Product:
- Accessing and Querying Provenance
- Raised by:
- Luc Moreau
- Opened on:
- 2011-08-23
- Description:
- The PAQ document indicates that provenance information (sometimes referred to as provenance resource) may change over time. What's the implication for the provenance-uri? Is the provenance-uri a cool URI? I think it is not, but this should be made explicit. There are also further issues.
Generally, what is the "contract" associated with this provenance-URI? How long should the server be able to serve this URI? It's particularly important for dynamically generated pages.
Let us consider a provenance store, in which provenance assertions gets accumulated. Let us consider a static resource, r, but over time, what we know about r changes, so it may have different provenance information p1 and p2.
If r is accessed, and a provenance-uri is returned, and dereferenced a first time, we obtain p1.
If r is accessed again, are we expecting to get the same provenance-uri, or a different one if provenance has changed?
Now, let us consider r as a dynamic resource. If r changes between the first and second access, is the same provenance-uri supposed to be returned?
If it does not change, how do we ever have a guarantee that the provenance information obtained corresponds to the resource representation we obtained?
- Related Actions Items:
- No related actions
- Related emails:
- addressing issues in prov-aq (from p.t.groth@vu.nl on 2012-04-05)
- Plan for Prov-aq going forward (from p.t.groth@vu.nl on 2011-12-20)
- Re: PROV-WG Reminder: Review PAQ before FPWD vote (from GK@ninebynine.org on 2011-11-16)
- Re: PROV-WG Reminder: Review PAQ before FPWD vote (from L.Moreau@ecs.soton.ac.uk on 2011-11-15)
- Re: PROV-WG Reminder: Review PAQ before FPWD vote (from p.t.groth@vu.nl on 2011-11-15)
- Re: PROV-WG Reminder: Review PAQ before FPWD vote (from L.Moreau@ecs.soton.ac.uk on 2011-11-15)
- Reviewing outstanding issues on PAQ document. (from GK@ninebynine.org on 2011-09-15)
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-09-01)
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance] (from L.Moreau@ecs.soton.ac.uk on 2011-08-26)
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-08-26)
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance] (from p.t.groth@vu.nl on 2011-08-25)
- Re: PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-08-25)
- PROV-ISSUE-79 (provenance-uri-contract): what is the contract associated with provenance-uris [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2011-08-23)
Related notes:
I believe the key issue here is addressed by text in section 2 of FPWD.
Graham Klyne, 5 Jan 2012, 11:24:43Display change log