--- a/paq/provenance-access.html Tue Aug 09 14:42:03 2011 +0200
+++ b/paq/provenance-access.html Tue Aug 09 15:47:01 2011 +0200
@@ -186,13 +186,14 @@
For a document presented as HTML or XHTML, without regard for how it has been obtained, POWDER [[POWDER-DR]] describes <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#assoc-markup">a mechanism</a> for associating metadata with a resource by adding a <code><Link></code> element to the HTML <code><head></code> section.
</p>
<p>
- The same basic mechanism can be used for referencing provence data, for which a new link relation type is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>:
+ The same basic mechanism can be used for referencing provence data, for which two new link relation types are registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>:
<code>
<pre class="pattern">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="wdr.issuedby" content="http://authority.example.org/company.rdf#me"/>
<link rel="provenance" href="<cite>provenance-URI</cite>">
+ <link rel="target" href="<cite>target-URI</cite>">
<title>Welcome to example.com </title>
</head>
<body>
@@ -201,12 +202,43 @@
</html>
</pre>
</code>
- This element indicates that <code><cite>provenance-URI</cite></code> is the URI of a provenance resource for the containing document.
+ The first link element provenanceidentifies the URI of provenance information for the document where the <code><cite>target-URI</cite></code> given by the target link element specifies identifier of the document within the provenance information.
</p>
<p>
- An HTML document header MAY include multiple provenance link elements, indicating a number of different resources that are known to the creator of the document, each providing provenance about the document resource.
+ An HTML document header MAY include multiple provenance link elements, indicating a number of different resources that are known to the creator of the document, each providing provenance about the document.
</p>
<p>
+ Likewise, the header MAY include multiple target link elements indicating that the document can be identified in the provenance information with multiple <code><cite>target-URIs</cite></code>.
+ </p>
+ <p>
+ If no target link element is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this only be done when the document is static.
+ </p>
+
+ <h4> Specifying Provenance Services </h4>
+ <p class="pending">
+ This is a new proposal. It needs to be checked as to whether it is useful.
+ </p>
+ <p>
+ The document creator may specify that the provenance information about the document is provided by a provenance service. This is done through the use of a third link relation type following the same pattern as above:
+ </p>
+ <code>
+ <pre class="pattern">
+ <html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta name="wdr.issuedby" content="http://authority.example.org/company.rdf#me"/>
+ <link rel="provenance-service" href="<cite>provenance-service-URI</cite>">
+ <title>Welcome to example.com </title>
+ </head>
+ <body>
+ ...
+ </body>
+ </html>
+ </pre>
+ </code>
+ <p> The provenance-service link element identifies both the service and the target using one URI. The <code><cite>provenance-service-uri</cite></code> follows the form of <a href="#request-uri" class="sectionRef"></a>. There may be multiple provenance-service link elements. provenance service link elements may appear in the same document as target and provenance linke elements.
+ </p>
+
+ <p>
See in particular <a href="http://tools.ietf.org/html/rfc5988#appendix-A">Appendix A. Notes on Using the Link Header with the HTML4 Format</a> of RFC5988 for further notes about using link relation types in HTML.
</p>
<p class="note">