ISSUE-112: provenance information in GET message
prov-in-get
provenance information in GET message
- State:
- CLOSED
- Product:
- Accessing and Querying Provenance
- Raised by:
- Luc Moreau
- Opened on:
- 2011-10-04
- Description:
- The document says:
For a document accessible using HTTP, provenance information may be indicated using an HTTP Link header field, as defined by Web Linking (RFC 5988) [LINK-REL]. The Link header field is included in the HTTP response to a GET or HEAD operation.
However, the resource serialization may be generated on demand, following a GET request. Hence, its provenance may need to make a reference to the GET request itself.
We should allow for provenance information to be included in HTTP Get messages also. - Related Actions Items:
- No related actions
- Related emails:
- addressing issues in prov-aq (from p.t.groth@vu.nl on 2012-04-05)
- Re: PROV-ISSUE-112 (prov-in-get): provenance information in GET message [Accessing and Querying Provenance] (from GK@ninebynine.org on 2011-10-19)
- Re: PROV-ISSUE-112 (prov-in-get): provenance information in GET message [Accessing and Querying Provenance] (from l.moreau@ecs.soton.ac.uk on 2011-10-17)
- Re: PROV-ISSUE-112 (prov-in-get): provenance information in GET message [Accessing and Querying Provenance] (from graham.klyne@zoo.ox.ac.uk on 2011-10-17)
- PROV-ISSUE-112 (prov-in-get): provenance information in GET message [Accessing and Querying Provenance] (from sysbot+tracker@w3.org on 2011-10-04)
Related notes:
Per my last message from October 2011, and lacking any further response, I am proposing to close this issue without further change. I think we need to keep the details of protocol exchange modeling distinct from provenance modeling.
The possible outstanding issue is the association of provenance information with HTTP POST requests, but lacking a clear and present use-case need for this I think we do better to defer consideration of this and stick to our knitting.
Display change log
