--- a/paq/prov-aq.html Thu Nov 08 22:20:59 2012 +0000
+++ b/paq/prov-aq.html Thu Nov 08 22:24:15 2012 +0000
@@ -318,9 +318,6 @@
<section>
<h2>Locating provenance information</h2>
- <p class="TODO">
- @@TODO: introduce producer/consumer roles to cover cases of HTTP and non-HTTP transfer of provenance discovery information.
- </p>
<p>
If <a class="internalDFN">provenance information</a> is a resource that can be accessed using web retrieval, one needs to know its <a class="internalDFN">provenance-URI</a> to dereference. If this is known in advance, there is nothing more to specify. If a provenance-URI is not known then a mechanism to discover one must be based on information that is available to the would-be accessor. Likewise, provenance information may be exposed by a service, in which case, the <a class="internalDFN">service-URI</a> needs to be known.
</p>
@@ -363,6 +360,9 @@
<section>
<h2>Resource accessed by HTTP</h2>
+ <p class="TODO">
+ @@TODO: Use URIs for link relations (?)
+ </p>
<p>
For a resource accessible using HTTP, provenance information may be indicated using an HTTP <code>Link</code> header field, as defined by <a href="http://tools.ietf.org/html/rfc5988">Web Linking (RFC 5988)</a> [[LINK-REL]]. The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
</p>
@@ -402,6 +402,9 @@
<section>
<h2>Resource represented as HTML</h2>
+ <p class="TODO">
+ @@TODO: Use URIs for link relations (?)
+ </p>
<div>
For a document presented as HTML or XHTML, without regard for how it has been obtained, provenance information may be associated with a resource by adding a <code><link></code> element to the HTML <code><head></code> section.
Two new link relation types for referencing provenance information are registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>, and may be used as shown: