--- a/paq/WD-PROV-AQ-20111201.html Thu Dec 01 16:02:24 2011 +0000
+++ b/paq/WD-PROV-AQ-20111201.html Thu Dec 01 16:09:21 2011 +0000
@@ -3,8 +3,8 @@
<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>PROV-AQ: Provenance Access and Query</title>
- <link href="css/prov-aq.css" type="text/css" rel="stylesheet" />
- <meta content="text/html;charset=utf-8" http-equiv="Content-Type" />
+ <link rel="stylesheet" type="text/css" href="css/prov-aq.css" />
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<!-- Use common W3C-hosted version of ReSpec.js:
-->
@@ -482,7 +482,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8" /></head>
- <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p><h1 id="title" class="title">PROV-AQ: Provenance Access and Query</h1><h2 id="w3c-working-draft-01-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 01 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-AQ-20111201/">http://www.w3.org/TR/2011/WD-PROV-AQ-20111201/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/PROV-AQ/">http://www.w3.org/TR/PROV-AQ/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html">http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html</a></dd><dt>Editors:</dt><dd><span>Graham Klyne</span>, <a href="http://www.ox.ac.uk/">University of Oxford</a></dd>
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a></p><h1 class="title" id="title">PROV-AQ: Provenance Access and Query</h1><h2 id="w3c-working-draft-01-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 01 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-AQ-20111201/">http://www.w3.org/TR/2011/WD-PROV-AQ-20111201/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/PROV-AQ/">http://www.w3.org/TR/PROV-AQ/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html">http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html</a></dd><dt>Editors:</dt><dd><span>Graham Klyne</span>, <a href="http://www.ox.ac.uk/">University of Oxford</a></dd>
<dd><span>Paul Groth</span>, <a href="http://www.vu.nl/">VU University Amsterdam</a></dd>
<dt>Authors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><span>Olaf Hartig</span></dd>
@@ -497,10 +497,10 @@
<div id="abstract" class="introductory section"><h2>Abstract</h2>
This document describes the use of existing mechanisms for accessing and querying provenance data about resources on the web.
- </div><div class="introductory section" id="sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
- Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
+ </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
+ Publication as a Working Group Note does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document is part of a set of specifications produced by the <acronym title="World Wide Web Consortium">W3C</acronym> provenance working group aiming to define interoperable interchange of provenance information in heterogeneous environments such as the Web. It describes the use of existing web mechanisms for discovery and retrieval of provenance information.
- <p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a rel="disclosure" href="">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#concepts" class="tocxref"><span class="secno">1.1 </span>Concepts</a></li><li class="tocline"><a href="#provenance--entities-and-resources" class="tocxref"><span class="secno">1.2 </span>Provenance, entities and resources</a></li><li class="tocline"><a href="#interpreting-provenance-information" class="tocxref"><span class="secno">1.3 </span>Interpreting provenance information</a></li></ul></li><li class="tocline"><a href="#accessing-provenance-information" class="tocxref"><span class="secno">2. </span>Accessing provenance information</a></li><li class="tocline"><a href="#locating-provenance-information" class="tocxref"><span class="secno">3. </span>Locating provenance information</a><ul class="toc"><li class="tocline"><a href="#resource-accessed-by-http" class="tocxref"><span class="secno">3.1 </span>Resource accessed by HTTP</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-services" class="tocxref"><span class="secno">3.1.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-html" class="tocxref"><span class="secno">3.2 </span>Resource represented as HTML</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-services-1" class="tocxref"><span class="secno">3.2.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-rdf" class="tocxref"><span class="secno">3.3 </span>Resource represented as RDF</a></li><li class="tocline"><a href="#arbitrary-data" class="tocxref"><span class="secno">3.4 </span>Arbitrary data</a></li></ul></li><li class="tocline"><a href="#provenance-services" class="tocxref"><span class="secno">4. </span>Provenance services</a><ul class="toc"><li class="tocline"><a href="#using-the-provenance-service-api" class="tocxref"><span class="secno">4.1 </span>Using the provenance service API</a><ul class="toc"><li class="tocline"><a href="#retrieve-provenance-uris-for-a-resource" class="tocxref"><span class="secno">4.1.1 </span>Retrieve Provenance-URIs for a resource</a></li><li class="tocline"><a href="#retrieve-provenance-information-for-a-resource" class="tocxref"><span class="secno">4.1.2 </span>Retrieve Provenance information for a resource</a></li></ul></li><li class="tocline"><a href="#resources-presented-and-representations-used" class="tocxref"><span class="secno">4.2 </span>Resources presented and representations used</a><ul class="toc"><li class="tocline"><a href="#service-description" class="tocxref"><span class="secno">4.2.1 </span>Service description</a></li><li class="tocline"><a href="#provenance-locations" class="tocxref"><span class="secno">4.2.2 </span>Provenance locations</a></li><li class="tocline"><a href="#provenance-information" class="tocxref"><span class="secno">4.2.3 </span>Provenance information</a></li></ul></li><li class="tocline"><a href="#provenance-service-discovery" class="tocxref"><span class="secno">4.3 </span>Provenance service discovery</a></li></ul></li><li class="tocline"><a href="#querying-provenance-information" class="tocxref"><span class="secno">5. </span>Querying provenance information</a><ul class="toc"><li class="tocline"><a href="#find-provenance-uri-given-entity-uri-of-resource" class="tocxref"><span class="secno">5.1 </span>Find provenance-URI given entity-URI of resource</a></li><li class="tocline"><a href="#find-provenance-uri-given-identifying-information-about-a-resource" class="tocxref"><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</a></li><li class="tocline"><a href="#obtain-provenance-information-directly-given-an-entity-uri-of-a-resource" class="tocxref"><span class="secno">5.3 </span>Obtain provenance information directly given an entity-URI of a resource</a></li></ul></li><li class="tocline"><a href="#incremental-provenance-retrieval" class="tocxref"><span class="secno">6. </span>Incremental Provenance Retrieval</a><ul class="toc"><li class="tocline"><a href="#via-web-retrieval" class="tocxref"><span class="secno">6.1 </span>Via Web Retrieval</a></li><li class="tocline"><a href="#via-queries" class="tocxref"><span class="secno">6.2 </span>Via Queries</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">7. </span>IANA considerations</a><ul class="toc"><li class="tocline"><a href="#registration-template-for-link-relation---provenance" class="tocxref"><span class="secno">7.1 </span>Registration template for link relation: "provenance"</a></li><li class="tocline"><a href="#registration-template-for-link-relation---anchor" class="tocxref"><span class="secno">7.2 </span>Registration template for link relation: "anchor"</a></li><li class="tocline"><a href="#registration-template-for-link-relation---provenance-service" class="tocxref"><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</a></li></ul></li><li class="tocline"><a href="#security-considerations" class="tocxref"><span class="secno">8. </span>Security considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#provenance-service-format-examples" class="tocxref"><span class="secno">B. </span>Provenance service format examples</a><ul class="toc"><li class="tocline"><a href="#rdf-turtle-example-of-service-description" class="tocxref"><span class="secno">B.1 </span>RDF Turtle example of service description</a></li><li class="tocline"><a href="#rdf-xml-example-of-service-description" class="tocxref"><span class="secno">B.2 </span>RDF/XML example of service description</a></li><li class="tocline"><a href="#plain-xml-example-of-service-description" class="tocxref"><span class="secno">B.3 </span>Plain XML example of service description</a></li><li class="tocline"><a href="#rdf-turtle-example-of-provenance-locations" class="tocxref"><span class="secno">B.4 </span>RDF Turtle example of provenance locations</a></li><li class="tocline"><a href="#rdf-xml-example-of-provenance-locations" class="tocxref"><span class="secno">B.5 </span>RDF/XML example of provenance locations</a></li><li class="tocline"><a href="#plain-xml-example-of-provenance-locations" class="tocxref"><span class="secno">B.6 </span>Plain XML example of provenance locations</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
+ <p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#concepts" class="tocxref"><span class="secno">1.1 </span>Concepts</a></li><li class="tocline"><a href="#provenance--entities-and-resources" class="tocxref"><span class="secno">1.2 </span>Provenance, entities and resources</a></li><li class="tocline"><a href="#interpreting-provenance-information" class="tocxref"><span class="secno">1.3 </span>Interpreting provenance information</a></li></ul></li><li class="tocline"><a href="#accessing-provenance-information" class="tocxref"><span class="secno">2. </span>Accessing provenance information</a></li><li class="tocline"><a href="#locating-provenance-information" class="tocxref"><span class="secno">3. </span>Locating provenance information</a><ul class="toc"><li class="tocline"><a href="#resource-accessed-by-http" class="tocxref"><span class="secno">3.1 </span>Resource accessed by HTTP</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-services" class="tocxref"><span class="secno">3.1.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-html" class="tocxref"><span class="secno">3.2 </span>Resource represented as HTML</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-services-1" class="tocxref"><span class="secno">3.2.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-rdf" class="tocxref"><span class="secno">3.3 </span>Resource represented as RDF</a></li><li class="tocline"><a href="#arbitrary-data" class="tocxref"><span class="secno">3.4 </span>Arbitrary data</a></li></ul></li><li class="tocline"><a href="#provenance-services" class="tocxref"><span class="secno">4. </span>Provenance services</a><ul class="toc"><li class="tocline"><a href="#using-the-provenance-service-api" class="tocxref"><span class="secno">4.1 </span>Using the provenance service API</a><ul class="toc"><li class="tocline"><a href="#retrieve-provenance-uris-for-a-resource" class="tocxref"><span class="secno">4.1.1 </span>Retrieve Provenance-URIs for a resource</a></li><li class="tocline"><a href="#retrieve-provenance-information-for-a-resource" class="tocxref"><span class="secno">4.1.2 </span>Retrieve Provenance information for a resource</a></li></ul></li><li class="tocline"><a href="#resources-presented-and-representations-used" class="tocxref"><span class="secno">4.2 </span>Resources presented and representations used</a><ul class="toc"><li class="tocline"><a href="#service-description" class="tocxref"><span class="secno">4.2.1 </span>Service description</a></li><li class="tocline"><a href="#provenance-locations" class="tocxref"><span class="secno">4.2.2 </span>Provenance locations</a></li><li class="tocline"><a href="#provenance-information" class="tocxref"><span class="secno">4.2.3 </span>Provenance information</a></li></ul></li><li class="tocline"><a href="#provenance-service-discovery" class="tocxref"><span class="secno">4.3 </span>Provenance service discovery</a></li></ul></li><li class="tocline"><a href="#querying-provenance-information" class="tocxref"><span class="secno">5. </span>Querying provenance information</a><ul class="toc"><li class="tocline"><a href="#find-provenance-uri-given-entity-uri-of-resource" class="tocxref"><span class="secno">5.1 </span>Find provenance-URI given entity-URI of resource</a></li><li class="tocline"><a href="#find-provenance-uri-given-identifying-information-about-a-resource" class="tocxref"><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</a></li><li class="tocline"><a href="#obtain-provenance-information-directly-given-an-entity-uri-of-a-resource" class="tocxref"><span class="secno">5.3 </span>Obtain provenance information directly given an entity-URI of a resource</a></li></ul></li><li class="tocline"><a href="#incremental-provenance-retrieval" class="tocxref"><span class="secno">6. </span>Incremental Provenance Retrieval</a><ul class="toc"><li class="tocline"><a href="#via-web-retrieval" class="tocxref"><span class="secno">6.1 </span>Via Web Retrieval</a></li><li class="tocline"><a href="#via-queries" class="tocxref"><span class="secno">6.2 </span>Via Queries</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">7. </span>IANA considerations</a><ul class="toc"><li class="tocline"><a href="#registration-template-for-link-relation---provenance" class="tocxref"><span class="secno">7.1 </span>Registration template for link relation: "provenance"</a></li><li class="tocline"><a href="#registration-template-for-link-relation---anchor" class="tocxref"><span class="secno">7.2 </span>Registration template for link relation: "anchor"</a></li><li class="tocline"><a href="#registration-template-for-link-relation---provenance-service" class="tocxref"><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</a></li></ul></li><li class="tocline"><a href="#security-considerations" class="tocxref"><span class="secno">8. </span>Security considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#provenance-service-format-examples" class="tocxref"><span class="secno">B. </span>Provenance service format examples</a><ul class="toc"><li class="tocline"><a href="#rdf-turtle-example-of-service-description" class="tocxref"><span class="secno">B.1 </span>RDF Turtle example of service description</a></li><li class="tocline"><a href="#rdf-xml-example-of-service-description" class="tocxref"><span class="secno">B.2 </span>RDF/XML example of service description</a></li><li class="tocline"><a href="#plain-xml-example-of-service-description" class="tocxref"><span class="secno">B.3 </span>Plain XML example of service description</a></li><li class="tocline"><a href="#rdf-turtle-example-of-provenance-locations" class="tocxref"><span class="secno">B.4 </span>RDF Turtle example of provenance locations</a></li><li class="tocline"><a href="#rdf-xml-example-of-provenance-locations" class="tocxref"><span class="secno">B.5 </span>RDF/XML example of provenance locations</a></li><li class="tocline"><a href="#plain-xml-example-of-provenance-locations" class="tocxref"><span class="secno">B.6 </span>Plain XML example of provenance locations</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
@@ -531,13 +531,13 @@
<dt><dfn id="dfn-entity">Entity</dfn></dt>
<dd>an aspect of a <a class="internalDFN" href="#dfn-resource">resource</a>, about which one wishes to present some <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>. For example, a weather report for a given date may be an aspect of a resource that is maintained as the current weather report. An entity is itself a <a class="internalDFN" href="#dfn-resource">resource</a>. See also [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>], and [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
<dt><dfn id="dfn-entity-uri">Entity-URI</dfn></dt>
- <dd>a URI denoting an <a class="internalDFN" href="#dfn-entity">entity</a>, which allows that entity to be identified for the purpose of finding and expressing <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> (see <a class="sectionRef" href="#provenance-context">section 1.2 </a> for discussion)</dd>
+ <dd>a URI denoting an <a class="internalDFN" href="#dfn-entity">entity</a>, which allows that entity to be identified for the purpose of finding and expressing <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> (see <a href="#provenance-context" class="sectionRef">section 1.2 </a> for discussion)</dd>
<dt><dfn id="dfn-provenance-service">Provenance service</dfn></dt>
<dd>a service that provides a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> given a <a class="internalDFN" href="#dfn-resource">resource</a> URI or an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>.</dd>
<dt><dfn id="dfn-service-uri">Service-URI</dfn></dt>
<dd>the URI of a <a class="internalDFN" href="#dfn-provenance-service">provenance service</a>.</dd>
<dt><dfn id="dfn-resource">Resource</dfn></dt>
- <dd>also referred to as <dfn id="dfn-web-resource">web resource</dfn>: a resource as described by the Architecture of the World Wide Web [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple <a class="internalDFN" title="Entity" href="#dfn-entity">entities</a> (see <a class="sectionRef" href="#provenance-context">section 1.2 </a> for discussion)</dd>
+ <dd>also referred to as <dfn id="dfn-web-resource">web resource</dfn>: a resource as described by the Architecture of the World Wide Web [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple <a title="Entity" class="internalDFN" href="#dfn-entity">entities</a> (see <a href="#provenance-context" class="sectionRef">section 1.2 </a> for discussion)</dd>
</dl>
<p></p>
@@ -561,7 +561,7 @@
<div id="interpreting-provenance-information" class="section">
<h3 id="provenance-context"><span class="secno">1.3 </span>Interpreting provenance information</h3>
- <p><a class="internalDFN" href="#dfn-provenance-information">Provenance information</a> describes relationships between entities, activities and agents. As such, any given provenance information may contain information about several <a class="internalDFN" title="Entity" href="#dfn-entity">entities</a>. Within some provenance information, the entities thus described are identified by their <a class="internalDFN" href="#dfn-entity-uri">Entity-URI</a>s.
+ <p><a class="internalDFN" href="#dfn-provenance-information">Provenance information</a> describes relationships between entities, activities and agents. As such, any given provenance information may contain information about several <a title="Entity" class="internalDFN" href="#dfn-entity">entities</a>. Within some provenance information, the entities thus described are identified by their <a class="internalDFN" href="#dfn-entity-uri">Entity-URI</a>s.
</p>
<p>When interpreting provenance information, it is important to be aware that statements about several entities may be present, and to be accordingly selective when using the information provided. (In some exceptional cases, it may be that the provenance information returned does not contain any information relating to a specific associated entity.)
</p>
@@ -583,13 +583,13 @@
Provenance assertions are about pre-determined activities involving entities; as such, they are not dynamic. Thus, provenance information returned at a given provenance-URI may commonly be static. But the availability of provenance information about a resource may vary (e.g. if there is insufficient storage to keep it indefinitely, or new information becomes available at a later date), so the provenance information returned at a given URI may change, provided that such change does not contradict any previously retrieved information.
</p>
<p>
- How much or how little provenance information is returned in response to to a retrieval request is a matter for the provenance provider application. At a minimum, for as long as provenance information about an entity remains available, sufficient should be returned to enable a client application to walk the provenance graph per <a href="#incremental-provenance-retrieval" class="sectionRef">section 6. Incremental Provenance Retrieval</a>.
+ How much or how little provenance information is returned in response to to a retrieval request is a matter for the provenance provider application. At a minimum, for as long as provenance information about an entity remains available, sufficient should be returned to enable a client application to walk the provenance graph per <a class="sectionRef" href="#incremental-provenance-retrieval">section 6. Incremental Provenance Retrieval</a>.
</p>
<p>
- When publishing provenance as a web resource, the <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> should be discoverable using one or more of the mechanisms described in <a class="sectionRef" href="#locating-provenance-information">section 3. Locating provenance information</a>.
+ When publishing provenance as a web resource, the <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef">section 3. Locating provenance information</a>.
</p>
<p>
- If there is no URI for some particular provenance information, then alternative mechanisms may be needed. Possible mechanisms are suggested in <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a> and <a class="sectionRef" href="#querying-provenance-information">section 5. Querying provenance information</a>.
+ If there is no URI for some particular provenance information, then alternative mechanisms may be needed. Possible mechanisms are suggested in <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> and <a href="#querying-provenance-information" class="sectionRef">section 5. Querying provenance information</a>.
</p>
</div>
@@ -610,13 +610,13 @@
Once provenance information information is retrieved, one also needs to know how to locate the view of that resource within that provenance information. This view is an <a class="internalDFN" href="#dfn-entity">entity</a> and is identified by an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>.
</p>
<p>
- We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> along with a <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>. (Mechanisms that can be independent of the resource provision are discussed in <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a>). Three mechanisms are described here:
+ We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> along with a <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>. (Mechanisms that can be independent of the resource provision are discussed in <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>). Three mechanisms are described here:
</p><ul>
<li>The requester knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
<li>The requester has a copy of a resource represented as HTML or XHTML</li>
<li>The requester has a copy of a resource represented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
</ul>
- These particular cases are selected as corresponding to primary current web protocol and data formats. Finally, in <a class="sectionRef" href="#arbitrary-data">section 3.4 Arbitrary data</a>, we discuss the case of a resource in an unspecified format which has been provided by some means other than HTTP.
+ These particular cases are selected as corresponding to primary current web protocol and data formats. Finally, in <a href="#arbitrary-data" class="sectionRef">section 3.4 Arbitrary data</a>, we discuss the case of a resource in an unspecified format which has been provided by some means other than HTTP.
<p></p>
<p>
The mechanisms specified for use with HTTP and HTML are similar to those proposed by POWDER [<cite><a class="bibref" rel="biblioentry" href="#bib-POWDER-DR">POWDER-DR</a></cite>] (sections <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#assoc-markup">4.1.1</a> and <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink">4.1.3</a>).
@@ -628,11 +628,11 @@
For a document 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> [<cite><a class="bibref" rel="biblioentry" href="#bib-LINK-REL">LINK-REL</a></cite>]. 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>
<p>
- A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a class="sectionRef" href="#iana-considerations">section 7. IANA considerations</a>, and may be used as shown::
+ A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a href="#iana-considerations" class="sectionRef">section 7. IANA considerations</a>, and may be used as shown::
<code>
</code></p><pre class="pattern"><code> Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</code></pre><code>
</code>
- When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a class="sectionRef" href="#interpreting-provenance-information">section 1.3 Interpreting provenance information</a>.)
+ When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef">section 1.3 Interpreting provenance information</a>.)
<p></p>
<p>
If no <code>anchor</code> link is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the resource.
@@ -644,10 +644,10 @@
An HTTP response <em class="rfc2119" title="may">may</em> include multiple <code>provenance</code> link header fields, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource.
</p>
<p>
- The presence of a <code>provenance</code> link in an HTTP response does not preclude the possibility that other publishers may offer provenance information about the same resource. In such cases, discovery of the additional provenance information must use other means (e.g. see <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a>).
+ The presence of a <code>provenance</code> link in an HTTP response does not preclude the possibility that other publishers may offer provenance information about the same resource. In such cases, discovery of the additional provenance information must use other means (e.g. see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>).
</p>
<p>
- Provenance resources indicated in this way are not guaranteed to be authoritative. Trust in the linked provenance data must be determined separately from trust in the original resource, just as in the web at large, it is a users' responsibility to determine an appropriate level of trust in any other linked resource; e.g. based on the domain that serves it, or an associated digital signature. (Ssee also <a class="sectionRef" href="#security-considerations">section 8. Security considerations</a>.)
+ Provenance resources indicated in this way are not guaranteed to be authoritative. Trust in the linked provenance data must be determined separately from trust in the original resource, just as in the web at large, it is a users' responsibility to determine an appropriate level of trust in any other linked resource; e.g. based on the domain that serves it, or an associated digital signature. (Ssee also <a href="#security-considerations" class="sectionRef">section 8. Security considerations</a>.)
</p>
<div id="specifying-provenance-services" class="section">
@@ -663,7 +663,7 @@
</code>
<p>
- The <code>provenance-service</code> link identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or retrieve <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> for an <a class="internalDFN" href="#dfn-entity">entity</a>; see <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a> for more details.
+ The <code>provenance-service</code> link identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or retrieve <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> for an <a class="internalDFN" href="#dfn-entity">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
</p>
<p>
There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same document as <code>provenance</code> links (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
@@ -676,7 +676,7 @@
<h3><span class="secno">3.2 </span>Resource represented as HTML</h3>
<p>
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 class="sectionRef" href="#iana-considerations">section 7. IANA considerations</a>, and may be used as shown:
+ Two new link relation types for referencing provenance information are registered according to the template in <a href="#iana-considerations" class="sectionRef">section 7. IANA considerations</a>, and may be used as shown:
<code>
</code></p><pre class="pattern"><code> <html xmlns="http://www.w3.org/1999/xhtml">
<head>
@@ -726,7 +726,7 @@
</pre>
</code>
<p>
- The <code>provenance-service</code> link element identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> for an <a class="internalDFN" href="#dfn-entity">entity</a>; see <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a> for more details.
+ The <code>provenance-service</code> link element identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> for an <a class="internalDFN" href="#dfn-entity">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
</p>
<p>
There may be multiple <code>provenance-service</code> link elements, and these <em class="rfc2119" title="may">may</em> appear in the same document as <code>anchor</code> and <code>provenance</code> link elements (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations would not be used together).
@@ -797,7 +797,7 @@
This section describes a REST API [<cite><a class="bibref" rel="biblioentry" href="#bib-REST-APIs">REST-APIs</a></cite>] for a provenance service with facilities for discovery and/or retrieval of provenance information, which can be implemented independently of the original resource delivery channels (e.g. by a third party service).
</p>
<p>
- All service implementations must respond with a service description (<a class="sectionRef" href="#service-description">section 4.2.1 Service description</a>) when the service URI is dereferenced.
+ All service implementations must respond with a service description (<a href="#service-description" class="sectionRef">section 4.2.1 Service description</a>) when the service URI is dereferenced.
Service implementations may provide either discovery, retrieval or both of these services, indicated by presence of the corresponding service URI templates in the service description. Which of these services to provide is a choice for individual service implementations.
</p>
<p>
@@ -810,7 +810,7 @@
<div id="using-the-provenance-service-api" class="section">
<h3><span class="secno">4.1 </span>Using the provenance service API</h3>
<p>
- This section describes general procedures for using the provenance service API. Later sections describe the resources presented by the API, and their representation using JSON. <a class="sectionRef" href="#provenance-service-format-examples">section B. Provenance service format examples</a>gives examples of alternative representations. Normal HTTP content negotiation mechanisms may be used to retrieve representations using formats convenient for the client application.
+ This section describes general procedures for using the provenance service API. Later sections describe the resources presented by the API, and their representation using JSON. <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>gives examples of alternative representations. Normal HTTP content negotiation mechanisms may be used to retrieve representations using formats convenient for the client application.
</p>
<div id="retrieve-provenance-uris-for-a-resource" class="section">
@@ -825,7 +825,7 @@
</ol>
<p></p>
<p>
- Any or all of URIs in the returned provenance locations may be used to retrieve provenance information, per <a class="sectionRef" href="#accessing-provenance-information">section 2. Accessing provenance information</a>.
+ Any or all of URIs in the returned provenance locations may be used to retrieve provenance information, per <a href="#accessing-provenance-information" class="sectionRef">section 2. Accessing provenance information</a>.
</p>
</div>
@@ -850,11 +850,11 @@
<div id="service-description" class="section">
<h4><span class="secno">4.2.1 </span>Service description</h4>
<p>
- A provenance <dfn id="dfn-service-description">service description</dfn> describes the provenance discovery and retrieval service and, in particular, provides URI templates [<cite><a class="bibref" rel="biblioentry" href="#bib-URI-template">URI-template</a></cite>] for URIs to access <a class="internalDFN" title="provenance locations resource" href="#dfn-provenance-locations-resource">provenance locations resources</a> and/or <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>. Dereferencing the service URI returns a representation of this service description. The service description <em class="rfc2119" title="may">may</em> contain additional metadata about the service beyond that described here: API clients are expected to ignore any metadata elements they do not understand.
+ A provenance <dfn id="dfn-service-description">service description</dfn> describes the provenance discovery and retrieval service and, in particular, provides URI templates [<cite><a class="bibref" rel="biblioentry" href="#bib-URI-template">URI-template</a></cite>] for URIs to access <a title="provenance locations resource" class="internalDFN" href="#dfn-provenance-locations-resource">provenance locations resources</a> and/or <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>. Dereferencing the service URI returns a representation of this service description. The service description <em class="rfc2119" title="may">may</em> contain additional metadata about the service beyond that described here: API clients are expected to ignore any metadata elements they do not understand.
</p>
<p>
This example shows a provenance service description using JSON format [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>], which is presented as MIME content-type <code>application/json</code>.
- Other examples may be seen in <a class="sectionRef" href="#provenance-service-format-examples">section B. Provenance service format examples</a>.
+ Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>.
</p>
<code>
<pre class="example">{
@@ -874,11 +874,11 @@
A <dfn id="dfn-provenance-locations-resource">provenance locations resource</dfn> enumerates one or more <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>s identifying <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> associated with a given resource.
</p>
<p>
- The examples below and in <a class="sectionRef" href="#provenance-service-format-examples">section B. Provenance service format examples</a> are for a given resource URI <code>http://example.org/qdata/</code>, and using the service description example above, its URI would be <code>http://example.org/provenance_service/location/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
+ The examples below and in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a> are for a given resource URI <code>http://example.org/qdata/</code>, and using the service description example above, its URI would be <code>http://example.org/provenance_service/location/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
</p>
<p>
This example uses JSON format [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>], presented as MIME content type <code>application/json</code>.
- Other examples may be seen in <a class="sectionRef" href="#provenance-service-format-examples">section B. Provenance service format examples</a>.
+ Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>.
</p>
<code>
<pre class="example">{
@@ -1024,7 +1024,7 @@
<h3><span class="secno">6.1 </span>Via Web Retrieval</h3>
<p>Publishers are not required to publish all the provenance information associated with a given entity at a particular <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>. The amount of provenance information exposed is application dependent. However, it is possible to incrementally retrieve (i.e. walk the provenance graph) by progressively looking up provenance information using HTTP. The pattern is as follows:
</p><ol>
- <li>For a given entity (<code>entity-uri-1</code>) retrieve it's associated <code>provenance-uri-1</code> using the HTTP <code>Link</code> header (<a class="sectionRef" href="#resource-accessed-by-http">section 3.1 Resource accessed by HTTP</a>)</li>
+ <li>For a given entity (<code>entity-uri-1</code>) retrieve it's associated <code>provenance-uri-1</code> using the HTTP <code>Link</code> header (<a href="#resource-accessed-by-http" class="sectionRef">section 3.1 Resource accessed by HTTP</a>)</li>
<li>Dereference <code>provenance-uri-1</code></li>
<li>Navigate the provenance information</li>
<li>When reaching a dead-end during navigation, that is on encountering a reference to an entity (<code>entity-uri-2</code>) with no provided provenance information, find its provenance-URI and continue from Step 1. (Note: an HTTP HEAD operation may be used to obtain the Link headers without retrieving the entity content.)</li>
@@ -1032,13 +1032,13 @@
<p></p>
<p>To reduce the overhead of multiple HTTP requests, a provenance information publisher may link entities to their associated provenance information using the <code>prov:hasProvenance</code> predicate. Thus, the same pattern above applies, except instead of having to retrieve a new <code>Link</code> header field, one can immediately dereference the entity's associated provenance.
</p>
- <p>The same approach can be adopted when using the <a class="internalDFN" href="#dfn-provenance-service">provenance service</a> API (<a class="sectionRef" href="#provenance-services">section 4. Provenance services</a>). However, instead of performing an HTTP HEAD or GET against a resource one queries the provenance service using the given <a class="internalDFN" href="#dfn-entity-uri">entity-uri</a>.
+ <p>The same approach can be adopted when using the <a class="internalDFN" href="#dfn-provenance-service">provenance service</a> API (<a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>). However, instead of performing an HTTP HEAD or GET against a resource one queries the provenance service using the given <a class="internalDFN" href="#dfn-entity-uri">entity-uri</a>.
</p>
</div>
<div id="via-queries" class="section">
<h3><span class="secno">6.2 </span>Via Queries</h3>
- <p>Provenance information may be made available using a SPARQL endpoint (<a class="sectionRef" href="#querying-provenance-information">section 5. Querying provenance information</a>) [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-PROTOCOL">RDF-SPARQL-PROTOCOL</a></cite>] [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]. Using SPARQL queries, provenance can be selectively retrieved using combinations of filters and or path queries.
+ <p>Provenance information may be made available using a SPARQL endpoint (<a href="#querying-provenance-information" class="sectionRef">section 5. Querying provenance information</a>) [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-PROTOCOL">RDF-SPARQL-PROTOCOL</a></cite>] [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]. Using SPARQL queries, provenance can be selectively retrieved using combinations of filters and or path queries.
</p>
</div>
@@ -1124,7 +1124,7 @@
</dd>
<dt>Description:</dt>
<dd>
- the resource identified by target URI of the link is an provenance service per <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a> of this specification.
+ the resource identified by target URI of the link is an provenance service per <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> of this specification.
</dd>
<dt>Reference:</dt>
<dd>
@@ -1190,7 +1190,7 @@
<!-- OddPage -->
<h2><span class="secno">B. </span>Provenance service format examples</h2>
<p>
- In <a class="sectionRef" href="#provenance-services">section 4. Provenance services</a>, the provenance service description was represented as a JSON-formatted document. As noted, HTTP content negotiation <em class="rfc2119" title="may">may</em> be enabled to retrieve the document in alternative formats. This appendix provides examples of service description document represented using RDF Turtle and XML syntaxes, and XML.
+ In <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>, the provenance service description was represented as a JSON-formatted document. As noted, HTTP content negotiation <em class="rfc2119" title="may">may</em> be enabled to retrieve the document in alternative formats. This appendix provides examples of service description document represented using RDF Turtle and XML syntaxes, and XML.
</p>
<div id="rdf-turtle-example-of-service-description" class="section">
@@ -1199,7 +1199,7 @@
This example uses the RDF Turtle format [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE">TURTLE</a></cite>], presented as MIME content-type <code>text/turtle</code>.
</p>
<code>
- <pre class="example">@prefix provds: <http://www.w3.org/2011/provenance_discovery/@@TBD@@#> .
+ <pre class="example">@prefix provds: <@@TBD@@#> .
<http://example.org/provenance_service/> a provds:Service_description ;
provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
@@ -1220,7 +1220,7 @@
<pre class="example"><rdf:RDF
xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
- xmlns:provds = "http://www.w3.org/2011/provenance_discovery/@@TBD@@#"
+ xmlns:provds = "@@TBD@@#"
>
<provds:Service_description rdf:about="http://example.org/provenance_service/">
example.org <provds:provenance_locations_template>http://example.org/provenance_service/locations/?uri={uri}</provds:location_template> ;
@@ -1246,7 +1246,7 @@
This example uses the RDF Turtle format [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE">TURTLE</a></cite>], presented as MIME content type <code>text/turtle</code>.
</p>
<code>
- <pre class="example">@prefix prov: <http://www.w3.org/2011/provenance/@@TBD@@#> .
+ <pre class="example">@prefix prov: <@@TBD@@#> .
<http://example.org/qdata/> a prov:Entity ;
prov:hasProvenance <http://source1.example.org/provenance/qdata/> ;
prov:hasProvenance <http://source2.example.org/prov/qdata/> ;
@@ -1268,7 +1268,7 @@
<pre class="example"><rdf:RDF
xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
- xmlns:prov = "http://www.w3.org/2011/provenance/@@TBD@@#"
+ xmlns:prov = "@@TBD@@#"
>
<prov:Entity rdf:about="http://example.org/qdata/">
<prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;