- From: Timothy Lebo <lebot@rpi.edu>
- Date: Wed, 23 Nov 2011 11:34:06 -0500
- To: Provenance Working Group WG <public-prov-wg@w3.org>
- Message-Id: <1384FBFB-1520-47F1-A537-A050524EFC51@rpi.edu>
Graham and Paul, I'm finally sitting down with the PAQ, and I'm pretty excited about the technique described in "Resource accessed by HTTP" [1]. The nice part about this is that HTTP can be used regardless of what type of content or format is being transferred. Further, one could "poll back" to see if any new provenance URIs show up. Very similar representational techniques are described in "Resource presented as HTML" [2], and the need for this is also clear because we want to "bake in" the provenance URIs so that they "go along for the ride" when copied and manipulated. Given the similar (identical?) rel link techniques across these two sections, I was curious about their association: 1) If the rel links are returned in HTTP, should they also appear in the HTML? 2) Should the rel links provided be equivalent in the HTML and HTTP? I recognize that I'm exposing some naivety with some of the HTTP fundamentals, but I'm guessing (hoping?) that others could benefit from some description of the association between appearance in HTTP and appearance in HTML <head>. For example, stating that the HTML <head> _is_ a recording of the headers returned when the HTTP request was made (but is this _true_? From my experience, it seems to be a signifiant subset of those returned from HTTP). If this is already discussed in the document (I'm still working through it), could you provide a pointer to it at the end of "Resource presented as HTML"? Thanks for your consideration. Regards, Tim [1] http://dvcs.w3.org/hg/prov/raw-file/default/paq/provenance-access.html#resource-accessed-by-http [2] http://dvcs.w3.org/hg/prov/raw-file/default/paq/provenance-access.html#resource-presented-as-html
Received on Wednesday, 23 November 2011 16:34:48 UTC