Re: PROV-ISSUE-168 (TLebo): HTTP POSTing a provenance URI to an originating source [Accessing and Querying Provenance]

Tim,

This is a very interesting, nay exciting, idea, but I fear may be a bit out of 
scope for the current work.  I think it meshes nicely with Paul's section on 
using a "follow-your-nose" linked data style of interaction for incremental 
provenance retrieval.

I assume the idea is inspired in part by the Weblog ping-back idea?  I think 
there's also some work going on in other areas for publication and dataset 
citation track-backs, which it would be good to mesh with, if feasible.

I'd be interested to work with you to map out some mechanisms for this (but 
probably not this side of Christmas), and then consider whether or not they 
belong in the current document.  I think the fact that the present document is 
not normative somewhat lowers the bar for what might be included, as long as 
it's firmly grounded in existing web protocols.

#g
--

On 23/11/2011 16:43, Provenance Working Group Issue Tracker wrote:
>
> PROV-ISSUE-168 (TLebo): HTTP POSTing a provenance URI to an originating source [Accessing and Querying Provenance]
>
> http://www.w3.org/2011/prov/track/issues/168
>
> Raised by: Timothy Lebo
> On product: Accessing and Querying Provenance
>
> Permitting "downstream" activities to "report back" to originating sources would be an invaluable way to create a web of provenance.
>
> Would it be possible to add a section describing how third party clients can HTTP POST additional provenance URIs describing resources relevant to the server?
>
> This would allow data consumers to tell data providers, "Hey, I used your data!".
>
> Servers receiving these POSTs could choose to acknowledge them (or not) by including the additional provenance URIs in the HTTP GET described in http://dvcs.w3.org/hg/prov/raw-file/default/paq/provenance-access.html#resource-accessed-by-http
>
> Thanks!
> Tim
>
>
>
>

Received on Friday, 25 November 2011 10:11:35 UTC