--- a/paq/WD-PROV-AQ-20111201.html Thu Dec 01 17:33:25 2011 +0000
+++ b/paq/WD-PROV-AQ-20111201.html Thu Dec 01 17:49:17 2011 +0000
@@ -1,20 +1,15 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
-<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml">
+<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
+<html lang="en" dir="ltr">
<head>
<title>PROV-AQ: Provenance Access and Query</title>
- <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:
- -->
-
+ <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:
+-->
-
-<!-- Use local version of ReSpec.js for debugging:
+<!-- Use local version of ReSpec.js for debugging:
<script src="js/respec.js" class="remove"></script>
- -->
-
+-->
<style type="text/css">
/*****************************************************************
@@ -62,6 +57,212 @@
}
+/* --- WEB IDL --- */
+pre.idl {
+ border-top: 1px solid #90b8de;
+ border-bottom: 1px solid #90b8de;
+ padding: 1em;
+ line-height: 120%;
+}
+
+pre.idl::before {
+ content: "WebIDL";
+ display: block;
+ width: 150px;
+ background: #90b8de;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+.idlType {
+ color: #ff4500;
+ font-weight: bold;
+ text-decoration: none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID {
+ font-weight: bold;
+ color: #005a9c;
+}
+
+.idlSuperclass {
+ font-style: italic;
+ color: #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+ color: #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+ color: #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+ color: #005a9c;
+}
+.idlMethName {
+ color: #ff4500;
+}
+.idlMethName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+ color: #005a9c;
+}
+.idlParamName {
+ font-style: italic;
+}
+
+.extAttr {
+ color: #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+ color: #005a9c;
+}
+.idlConstName {
+ color: #ff4500;
+}
+.idlConstName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+ font-weight: bold;
+ color: #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+ color: #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+ color: #c00;
+ font-weight: normal;
+}
+
+.excName a {
+ font-family: monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+ border-bottom: 1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+ width: 45px;
+ text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
+
+.idlImplements a {
+ font-weight: bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+ margin-left: 2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+ font-weight: normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+ font-weight: bold;
+ color: #000;
+ font-family: monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+ background: #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+ color: #005a9c;
+ background: transparent;
+ font-family: inherit;
+ font-weight: normal;
+ font-style: italic;
+}
+
+.methods dt code {
+ background: #d9e6f8;
+}
+
+.constants dt code {
+ background: #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+ margin-bottom: 1em;
+}
+
+table.parameters, table.exceptions {
+ border-spacing: 0;
+ border-collapse: collapse;
+ margin: 0.5em 0;
+ width: 100%;
+}
+table.parameters { border-bottom: 1px solid #90b8de; }
+table.exceptions { border-bottom: 1px solid #deb890; }
+
+.parameters th, .exceptions th {
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+ font-family: initial;
+ font-weight: normal;
+ text-shadow: #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+ vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+ border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+ width: 100px;
+}
+
+.parameters td.prmType {
+ width: 120px;
+}
+
+table.exceptions table {
+ border-spacing: 0;
+ border-collapse: collapse;
+ width: 100%;
+}
+
/* --- TOC --- */
.toc a {
text-decoration: none;
@@ -96,11 +297,19 @@
border-top: 1px solid #ddd;
}
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
/* --- DL --- */
.section dd > p:first-child {
margin-top: 0;
}
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
.section dd {
margin-bottom: 1em;
}
@@ -117,7 +326,7 @@
margin-top: 1em;
}
-pre.example:before {
+pre.example::before {
content: "Example";
display: block;
width: 150px;
@@ -137,7 +346,7 @@
background: #ffc;
}
-.issue:before {
+.issue::before {
content: "Issue";
display: block;
width: 150px;
@@ -155,7 +364,7 @@
background: #e2fff0;
}
-.note:before {
+.note::before {
content: "Note";
display: block;
width: 150px;
@@ -267,10 +476,10 @@
pre.sh_sourceCode .sh_paren { color: red; }
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" 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>
+</style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head>
+ <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></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>
+<dt>Authors:</dt><dd><a href="http://www.ecs.soton.ac.uk/%7Elavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><span>Olaf Hartig</span></dd>
<dd><span>Yogesh Simmhan</span></dd>
<dd><a href="http://www.rpi.edu/research/ccni/">James Myers</a>, Rensselaer Polytechnic Institute</dd>
@@ -278,34 +487,30 @@
<dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
<dd><span>Stephen Cresswell</span>, legislation.gov.uk</dd>
<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, Invited Expert</dd>
-</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011-2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr /></div>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011-2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
- <div id="abstract" class="introductory section"><h2>Abstract</h2>
+ <div class="introductory section" id="abstract"><h2>Abstract</h2>
This document describes the use of existing mechanisms for accessing and querying provenance data about resources on the web.
</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>
- <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>
- <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>
+ 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 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 class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#concepts"><span class="secno">1.1 </span>Concepts</a></li><li class="tocline"><a class="tocxref" href="#provenance--entities-and-resources"><span class="secno">1.2 </span>Provenance, entities and resources</a></li><li class="tocline"><a class="tocxref" href="#interpreting-provenance-information"><span class="secno">1.3 </span>Interpreting provenance information</a></li></ul></li><li class="tocline"><a class="tocxref" href="#accessing-provenance-information"><span class="secno">2. </span>Accessing provenance information</a></li><li class="tocline"><a class="tocxref" href="#locating-provenance-information"><span class="secno">3. </span>Locating provenance information</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#resource-accessed-by-http"><span class="secno">3.1 </span>Resource accessed by HTTP</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#specifying-provenance-services"><span class="secno">3.1.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a class="tocxref" href="#resource-represented-as-html"><span class="secno">3.2 </span>Resource represented as HTML</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#specifying-provenance-services-1"><span class="secno">3.2.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a class="tocxref" href="#resource-represented-as-rdf"><span class="secno">3.3 </span>Resource represented as RDF</a></li><li class="tocline"><a class="tocxref" href="#arbitrary-data"><span class="secno">3.4 </span>Arbitrary data</a></li></ul></li><li class="tocline"><a class="tocxref" href="#provenance-services"><span class="secno">4. </span>Provenance services</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#using-the-provenance-service-api"><span class="secno">4.1 </span>Using the provenance service API</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#retrieve-provenance-uris-for-a-resource"><span class="secno">4.1.1 </span>Retrieve Provenance-URIs for a resource</a></li><li class="tocline"><a class="tocxref" href="#retrieve-provenance-information-for-a-resource"><span class="secno">4.1.2 </span>Retrieve Provenance information for a resource</a></li></ul></li><li class="tocline"><a class="tocxref" href="#resources-presented-and-representations-used"><span class="secno">4.2 </span>Resources presented and representations used</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#service-description"><span class="secno">4.2.1 </span>Service description</a></li><li class="tocline"><a class="tocxref" href="#provenance-locations"><span class="secno">4.2.2 </span>Provenance locations</a></li><li class="tocline"><a class="tocxref" href="#provenance-information"><span class="secno">4.2.3 </span>Provenance information</a></li></ul></li><li class="tocline"><a class="tocxref" href="#provenance-service-discovery"><span class="secno">4.3 </span>Provenance service discovery</a></li></ul></li><li class="tocline"><a class="tocxref" href="#querying-provenance-information"><span class="secno">5. </span>Querying provenance information</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#find-provenance-uri-given-entity-uri-of-resource"><span class="secno">5.1 </span>Find provenance-URI given entity-URI of resource</a></li><li class="tocline"><a class="tocxref" href="#find-provenance-uri-given-identifying-information-about-a-resource"><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</a></li><li class="tocline"><a class="tocxref" href="#obtain-provenance-information-directly-given-an-entity-uri-of-a-resource"><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 class="tocxref" href="#incremental-provenance-retrieval"><span class="secno">6. </span>Incremental Provenance Retrieval</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#via-web-retrieval"><span class="secno">6.1 </span>Via Web Retrieval</a></li><li class="tocline"><a class="tocxref" href="#via-queries"><span class="secno">6.2 </span>Via Queries</a></li></ul></li><li class="tocline"><a class="tocxref" href="#iana-considerations"><span class="secno">7. </span>IANA considerations</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#registration-template-for-link-relation---provenance"><span class="secno">7.1 </span>Registration template for link relation: "provenance"</a></li><li class="tocline"><a class="tocxref" href="#registration-template-for-link-relation---anchor"><span class="secno">7.2 </span>Registration template for link relation: "anchor"</a></li><li class="tocline"><a class="tocxref" href="#registration-template-for-link-relation---provenance-service"><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</a></li></ul></li><li class="tocline"><a class="tocxref" href="#security-considerations"><span class="secno">8. </span>Security considerations</a></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#provenance-service-format-examples"><span class="secno">B. </span>Provenance service format examples</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#rdf-turtle-example-of-service-description"><span class="secno">B.1 </span>RDF Turtle example of service description</a></li><li class="tocline"><a class="tocxref" href="#rdf-xml-example-of-service-description"><span class="secno">B.2 </span>RDF/XML example of service description</a></li><li class="tocline"><a class="tocxref" href="#plain-xml-example-of-service-description"><span class="secno">B.3 </span>Plain XML example of service description</a></li><li class="tocline"><a class="tocxref" href="#rdf-turtle-example-of-provenance-locations"><span class="secno">B.4 </span>RDF Turtle example of provenance locations</a></li><li class="tocline"><a class="tocxref" href="#rdf-xml-example-of-provenance-locations"><span class="secno">B.5 </span>RDF/XML example of provenance locations</a></li><li class="tocline"><a class="tocxref" href="#plain-xml-example-of-provenance-locations"><span class="secno">B.6 </span>Plain XML example of provenance locations</a></li></ul></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
-
-<!-- == Sect 1 =================================================================================== -->
-
+<!-- == Sect 1 =================================================================================== -->
- <div id="introduction" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">1. </span>Introduction</h2>
+ <div class="section" id="introduction">
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
<p>
- The Provenance Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] and Provenance Ontology [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-O">PROV-O</a></cite>] specifications define how to represent provenance information in the World Wide Web.
+ The Provenance Data Model [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] and Provenance Ontology [<cite><a href="#bib-PROV-O" rel="biblioentry" class="bibref">PROV-O</a></cite>] specifications define how to represent provenance information in the World Wide Web.
</p>
<p>
This note describes how existing web mechanisms may be used to locate, retrieve and query provenance information.
</p>
- <div id="concepts" class="section">
+ <div class="section" id="concepts">
<h3><span class="secno">1.1 </span>Concepts</h3>
<p>
In defining the specification below, we make use of the following concepts.
@@ -313,41 +518,41 @@
<dt><dfn id="dfn-provenance-information">Provenance information</dfn></dt>
<dd>refers to provenance represented in some fashion.</dd>
<dt><dfn id="dfn-provenance-uri">Provenance-URI</dfn></dt>
- <dd>a URI denoting some <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>.</dd>
+ <dd>a URI denoting some <a href="#dfn-provenance-information" class="internalDFN">provenance information</a>.</dd>
<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>
+ <dd>an aspect of a <a href="#dfn-resource" class="internalDFN">resource</a>, about which one wishes to present some <a href="#dfn-provenance-information" class="internalDFN">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 href="#dfn-resource" class="internalDFN">resource</a>. See also [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>], and [<cite><a href="#bib-WEBARCH" rel="biblioentry" class="bibref">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 href="#provenance-context" class="sectionRef">section 1.2 </a> for discussion)</dd>
+ <dd>a URI denoting an <a href="#dfn-entity" class="internalDFN">entity</a>, which allows that entity to be identified for the purpose of finding and expressing <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> (see <a href="#provenance-entities-resources" 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>
+ <dd>a service that provides a <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a> or <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> given a <a href="#dfn-resource" class="internalDFN">resource</a> URI or an <a href="#dfn-entity-uri" class="internalDFN">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>
+ <dd>the URI of a <a href="#dfn-provenance-service" class="internalDFN">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 title="Entity" class="internalDFN" href="#dfn-entity">entities</a> (see <a href="#provenance-context" class="sectionRef">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 href="#bib-WEBARCH" rel="biblioentry" class="bibref">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 href="#dfn-entity" title="Entity" class="internalDFN">entities</a> (see <a href="#provenance-entities-resources" class="sectionRef">section 1.2 </a> for discussion)</dd>
</dl>
<p></p>
</div>
- <div id="provenance--entities-and-resources" class="section">
- <h3 id="provenance-context"><span class="secno">1.2 </span>Provenance, entities and resources</h3>
+ <div class="section" id="provenance--entities-and-resources">
+ <h3 id="provenance-entities-resources"><span class="secno">1.2 </span>Provenance, entities and resources</h3>
<p>
- Fundamentally, <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> is <em>about</em> <a class="internalDFN">resources</a>. In general, resources may vary over time and context. E.g., a resource describing the weather in London changes from day-to-day, or one listing restaurants near you will vary depending on your location. Provenance information, to be useful, must be persistent and not itself dependent on context. Yet we may still want to make provenance assertions about dynamic or context-dependent web resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
+ Fundamentally, <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resources</a>. In general, resources may vary over time and context. E.g., a resource describing the weather in London changes from day-to-day, or one listing restaurants near you will vary depending on your location. Provenance information, to be useful, must be persistent and not itself dependent on context. Yet we may still want to make provenance assertions about dynamic or context-dependent web resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
</p>
<p>
- Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities. An <a class="internalDFN" href="#dfn-entity">entity</a> is simply a web resource that is a contextualized view or instance of an original web resource. For example, a <acronym title="World Wide Web Consortium">W3C</acronym> specification typically undergoes several public revisions before it is finalized. A URI that refers to the "current" revision might be thought of as denoting the specification through its lifetime. Separate URIs for each individual revision would then be <a class="internalDFN">entity-URIs</a>, denoting the specification at a particular stage in its development. Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor. Entity-URIs may use any URI scheme, and are not required to be dereferencable.
+ Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities. An <a href="#dfn-entity" class="internalDFN">entity</a> is simply a web resource that is a contextualized view or instance of an original web resource. For example, a <acronym title="World Wide Web Consortium">W3C</acronym> specification typically undergoes several public revisions before it is finalized. A URI that refers to the "current" revision might be thought of as denoting the specification through its lifetime. Separate URIs for each individual revision would then be <a class="internalDFN">entity-URIs</a>, denoting the specification at a particular stage in its development. Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor. Entity-URIs may use any URI scheme, and are not required to be dereferencable.
</p>
<p>
Requests for provenance about a resource may return provenance information that uses one or more entity-URIs to refer to versions of that resource. Some given provenance information may use multiple entity-URIs if there are assertions referring to the same underlying resource in different contexts. For example, provenance information describing a <acronym title="World Wide Web Consortium">W3C</acronym> document might include information about all revisions of the document using statements that use the different entity-URIs of the various revisions.
</p>
<p>
- In summary, a key notion within the concepts outlined above is that <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> may be not universally applicable to a <a class="internalDFN" href="#dfn-resource">resource</a>, but may be expressed with respect to that resource in a restricted context (e.g. at a particular time). This restricted view is called an <a class="internalDFN" href="#dfn-entity">entity</a>, and an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a> is used to refer to it within provenance information.
+ In summary, a key notion within the concepts outlined above is that <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> may be not universally applicable to a <a href="#dfn-resource" class="internalDFN">resource</a>, but may be expressed with respect to that resource in a restricted context (e.g. at a particular time). This restricted view is called an <a href="#dfn-entity" class="internalDFN">entity</a>, and an <a href="#dfn-entity-uri" class="internalDFN">entity-URI</a> is used to refer to it within provenance information.
</p>
</div>
- <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 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.
+ <div class="section" id="interpreting-provenance-information">
+ <h3><span class="secno">1.3 </span>Interpreting provenance information</h3>
+ <p><a href="#dfn-provenance-information" class="internalDFN">Provenance information</a> describes relationships between entities, activities and agents. As such, any given provenance information may contain information about several <a href="#dfn-entity" title="Entity" class="internalDFN">entities</a>. Within some provenance information, the entities thus described are identified by their <a href="#dfn-entity-uri" class="internalDFN">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>
@@ -355,15 +560,11 @@
</div>
-
-<!-- == Sect 2 =================================================================================== -->
-
+<!-- == Sect 2 =================================================================================== -->
- <div id="accessing-provenance-information" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">2. </span>Accessing provenance information</h2>
- <p>Web applications may access <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> in the same way as any web resource, by dereferencing its URI. Typically, this will be by performing an HTTP GET operation. Thus, any provenance information may be associated with a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>, and may be accessed by dereferencing that URI using normal web mechanisms.
+ <div class="section" id="accessing-provenance-information">
+ <!--OddPage--><h2><span class="secno">2. </span>Accessing provenance information</h2>
+ <p>Web applications may access <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> in the same way as any web resource, by dereferencing its URI. Typically, this will be by performing an HTTP GET operation. Thus, any provenance information may be associated with a <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a>, and may be accessed by dereferencing that URI using normal web mechanisms.
</p>
<p>
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.
@@ -372,31 +573,27 @@
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 href="#locating-provenance-information" class="sectionRef">section 3. Locating provenance information</a>.
+ When publishing provenance as a web resource, the <a href="#dfn-provenance-uri" class="internalDFN">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 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>
-
-<!-- == Sect 3 =================================================================================== -->
-
+<!-- == Sect 3 =================================================================================== -->
- <div id="locating-provenance-information" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">3. </span>Locating provenance information</h2>
+ <div class="section" id="locating-provenance-information">
+ <!--OddPage--><h2><span class="secno">3. </span>Locating provenance information</h2>
<p>
- When <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> is a resource that can be accessed using normal web retrieval, one needs to know a <a class="internalDFN" href="#dfn-provenance-uri">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.
+ When <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> is a resource that can be accessed using normal web retrieval, one needs to know a <a href="#dfn-provenance-uri" 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.
</p>
<p>Provenance information may be provided by several parties other than the provider of the original resource, each using different provenance-URIs, and each with different concerns. (It is possible that these different parties may provide contradictory provenance information.)
</p>
<p>
- 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>.
+ 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 href="#dfn-entity" class="internalDFN">entity</a> and is identified by an <a href="#dfn-entity-uri" class="internalDFN">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 href="#provenance-services" class="sectionRef">section 4. Provenance services</a>). Three mechanisms are described here:
+ We start by considering mechanisms for the resource provider to indicate a <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a> along with a <a href="#dfn-entity-uri" class="internalDFN">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>
@@ -405,18 +602,18 @@
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>).
+ The mechanisms specified for use with HTTP and HTML are similar to those proposed by POWDER [<cite><a href="#bib-POWDER-DR" rel="biblioentry" class="bibref">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>).
</p>
- <div id="resource-accessed-by-http" class="section">
+ <div class="section" id="resource-accessed-by-http">
<h3><span class="secno">3.1 </span>Resource accessed by HTTP</h3>
<p>
- 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).
+ 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 href="#bib-LINK-REL" rel="biblioentry" class="bibref">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 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></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 href="#interpreting-provenance-information" class="sectionRef">section 1.3 Interpreting provenance information</a>.)
<p></p>
@@ -427,7 +624,7 @@
At this time, the meaning of these links returned with other HTTP response codes is not defined: future revisions of this specification may define interpretations for these.
</p>
<p>
- 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.
+ An HTTP response <em title="may" class="rfc2119">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 href="#provenance-services" class="sectionRef">section 4. Provenance services</a>).
@@ -436,20 +633,20 @@
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">
+ <div class="section" id="specifying-provenance-services">
<h4><span class="secno">3.1.1 </span>Specifying Provenance Services</h4>
<p class="pending">
This is a new proposal. It needs to be checked as to whether it is useful. GK/PG to review nature of provenance-service-URI.
</p>
<p>
- The document provider may indicate that provenance information about the document is provided by a <a class="internalDFN" href="#dfn-provenance-service">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
+ The document provider may indicate that provenance information about the document is provided by a <a href="#dfn-provenance-service" class="internalDFN">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
</p>
<code>
- <pre class="pattern"> Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
+ <pre class="pattern"> Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
</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 href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
+ The <code>provenance-service</code> link identifies the <a href="#dfn-service-uri" class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a> or retrieve <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> for an <a href="#dfn-entity" class="internalDFN">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).
@@ -458,16 +655,16 @@
</div>
- <div id="resource-represented-as-html" class="section">
+ <div class="section" id="resource-represented-as-html">
<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 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">
+ </code></p><pre class="pattern"><code> <html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <link rel="provenance" href="<cite>provenance-URI</cite>">
- <link rel="anchor" href="<cite>entity-URI</cite>">
+ <link rel="provenance" href="<cite>provenance-URI</cite>">
+ <link rel="anchor" href="<cite>entity-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -484,25 +681,25 @@
The <code><cite>entity-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the presented document view, and which may be used within the provenance information when referring to this document.
</p>
<p>
- An HTML document header <em class="rfc2119" title="may">may</em> include multiple "provenance" link elements, indicating a number of different provenance resources that are known to the creator of the document, each of which may provide provenance information about the document.
+ An HTML document header <em title="may" class="rfc2119">may</em> include multiple "provenance" link elements, indicating a number of different provenance resources that are known to the creator of the document, each of which may provide provenance information about the document.
</p>
<p>
- Likewise, the header <em class="rfc2119" title="may">may</em> include multiple "anchor" link elements indicating that, e.g., different revisions of the document can be identified in the provenance information using the different <code><cite>entity-URIs</cite></code>.
+ Likewise, the header <em title="may" class="rfc2119">may</em> include multiple "anchor" link elements indicating that, e.g., different revisions of the document can be identified in the provenance information using the different <code><cite>entity-URIs</cite></code>.
</p>
<p>
- If no "anchor" link element is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the document. It is <em class="rfc2119" title="recommended">recommended</em> that this convention be used only when the document is static.
+ If no "anchor" link element is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the document. It is <em title="recommended" class="rfc2119">recommended</em> that this convention be used only when the document is static.
</p>
- <div id="specifying-provenance-services-1" class="section">
+ <div class="section" id="specifying-provenance-services-1">
<h4><span class="secno">3.2.1 </span>Specifying Provenance Services</h4>
<p>
- The document creator may specify that the provenance information about the document is provided by a <a class="internalDFN" href="#dfn-provenance-service">provenance service</a>. This is done through the use of a third link relation type following the same pattern as above:
+ The document creator may specify that the provenance information about the document is provided by a <a href="#dfn-provenance-service" class="internalDFN">provenance service</a>. 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">
+ <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
<head>
- <link rel="provenance-service" href="<cite>service-URI</cite>">
- <link rel="anchor" href="<cite>entity-URI</cite>">
+ <link rel="provenance-service" href="<cite>service-URI</cite>">
+ <link rel="anchor" href="<cite>entity-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -512,15 +709,15 @@
</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 href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
+ The <code>provenance-service</code> link element identifies the <a href="#dfn-service-uri" class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> for an <a href="#dfn-entity" class="internalDFN">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).
+ There may be multiple <code>provenance-service</code> link elements, and these <em title="may" class="rfc2119">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).
</p>
</div>
</div>
- <div id="resource-represented-as-rdf" class="section">
+ <div class="section" id="resource-represented-as-rdf">
<h3><span class="secno">3.3 </span>Resource represented as RDF</h3>
<p>
If a resource is represented as RDF (in any of its recognized syntaxes, including RDFa), it may contain references to its own provenance using additional RDF statements.
@@ -529,15 +726,15 @@
For this purpose a new RDF property, <code>prov:hasProvenance</code>, is defined as a relation between two resources, where the object of the property is a resource that provides provenance information about the subject resource. Multiple <code>prov:hasProvenance</code> assertions may be made about a subject resource.
</p>
<p>
- Another new RDF property, <code>prov:hasAnchor</code>, is defined to allow the RDF content to specify one or more <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>s of the RDF document for the purpose of provenance information (similar to the use of the "anchor" link relation in HTML).
+ Another new RDF property, <code>prov:hasAnchor</code>, is defined to allow the RDF content to specify one or more <a href="#dfn-entity-uri" class="internalDFN">entity-URI</a>s of the RDF document for the purpose of provenance information (similar to the use of the "anchor" link relation in HTML).
</p>
<p class="TODO">
- @@TODO: document namespace. Check naming style. Use provenance model namespace? Define as part of model?<br />
+ @@TODO: document namespace. Check naming style. Use provenance model namespace? Define as part of model?<br>
@@TODO: example, when vocabulary issues are settled.
</p>
</div>
- <div id="arbitrary-data" class="section">
+ <div class="section" id="arbitrary-data">
<h3><span class="secno">3.4 </span>Arbitrary data</h3>
<p class="pending">
We have so far decided not to try and define a common mechanism for arbitrary data, because it's not clear to us what the correct choice would be. Is this a reasonable position, or is there a real need for a generic solution for provenance discovery for arbitrary, non-web-accessible data objects?
@@ -546,12 +743,12 @@
If a resource is represented using a data format other than HTML or RDF, and no URI for the resource is known, provenance discovery becomes trickier to achieve. This specification does not define a specific mechanism for such arbitrary resources, but this section discusses some of the options that might be considered.
</p>
<p>
- For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>, <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> and/or <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Format-specific metadata provision might also be used to include <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> directly in the resource.
+ For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a <a href="#dfn-entity-uri" class="internalDFN">entity-URI</a>, <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a> and/or <a href="#dfn-service-uri" class="internalDFN">service-URI</a>. Format-specific metadata provision might also be used to include <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> directly in the resource.
</p>
<p>
Use a generic packaging format that can combine an arbitrary data file with a separate metadata file in a known format, such as RDF. At this time, it is not clear what format that should be, but some possible candidates are:
</p><ul>
- <li>MIME multipart/related [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2387">RFC2387</a></cite>]: both email and HTTP are based on MIME or MIME-derivatives, so this has the advantage of working well with the network transfer mechanisms discussed in the motivating scenarios considered.
+ <li>MIME multipart/related [<cite><a href="#bib-RFC2387" rel="biblioentry" class="bibref">RFC2387</a></cite>]: both email and HTTP are based on MIME or MIME-derivatives, so this has the advantage of working well with the network transfer mechanisms discussed in the motivating scenarios considered.
</li>
<li>
Composite object-packaging work from the digital library community, of which there are several (ORE, MPEG-21, BagIt @@refs) to name a handful. Practical implementations of these seem to commonly be based on the ZIP file format.
@@ -571,16 +768,12 @@
</div>
-
-<!-- == Sect 4 =================================================================================== -->
-
+<!-- == Sect 4 =================================================================================== -->
- <div id="provenance-services" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">4. </span>Provenance services</h2>
+ <div class="section" id="provenance-services">
+ <!--OddPage--><h2><span class="secno">4. </span>Provenance services</h2>
<p>
- 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).
+ This section describes a REST API [<cite><a href="#bib-REST-APIs" rel="biblioentry" class="bibref">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 href="#service-description" class="sectionRef">section 4.2.1 Service description</a>) when the service URI is dereferenced.
@@ -593,21 +786,21 @@
The provenance retrieval service returns provenance information directly. This mechanism may be preferred when the provenance information is not already presented directly to the web, or is stored in a database with a complex query protocol, or when the provenance service can control the URI from which provenance information is served and avoid the intermediate step of URI discovery.
</p>
- <div id="using-the-provenance-service-api" class="section">
+ <div class="section" id="using-the-provenance-service-api">
<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 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">
+ <div class="section" id="retrieve-provenance-uris-for-a-resource">
<h4><span class="secno">4.1.1 </span>Retrieve Provenance-URIs for a resource</h4>
<p>
To use the provenance service to retrieve a list of provenance-URIs for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or entity (<code>entity-URI</code>):
</p><ol>
- <li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN" href="#dfn-service-description">service description</a>.</li>
+ <li>Dereference <code>service-URI</code> to obtain a representation of the <a href="#dfn-service-description" class="internalDFN">service description</a>.</li>
<li>Extract the provenance locations template from the service description.</li>
<li>Use the provenance locations template with <code>entity-URI</code> for template variable <code>uri</code> to form <code>provenance-locations-URI</code>.</li>
- <li>Dereference <code>provenance-locations-URI</code> to obtain a <a class="internalDFN" href="#dfn-provenance-locations-resource">provenance locations resource</a> in one of the formats described below.</li>
+ <li>Dereference <code>provenance-locations-URI</code> to obtain a <a href="#dfn-provenance-locations-resource" class="internalDFN">provenance locations resource</a> in one of the formats described below.</li>
</ol>
<p></p>
<p>
@@ -615,38 +808,38 @@
</p>
</div>
- <div id="retrieve-provenance-information-for-a-resource" class="section">
+ <div class="section" id="retrieve-provenance-information-for-a-resource">
<h4><span class="secno">4.1.2 </span>Retrieve Provenance information for a resource</h4>
<p>
To use the provenance service to directly retrieve provenance information for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or context (<code>entity-URI</code>):
</p><ol>
- <li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN" href="#dfn-service-description">service description</a>.</li>
+ <li>Dereference <code>service-URI</code> to obtain a representation of the <a href="#dfn-service-description" class="internalDFN">service description</a>.</li>
<li>Extract the provenance information template from the service description.</li>
<li>Use the provenance information template with <code>entity-URI</code> for template variable <code>uri</code> to form <code>provenance-URI</code>.</li>
- <li>Dereference <code>provenance-URI</code> to obtain <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>.</li>
+ <li>Dereference <code>provenance-URI</code> to obtain <a href="#dfn-provenance-information" class="internalDFN">provenance information</a>.</li>
</ol>
<p></p>
</div>
</div>
- <div id="resources-presented-and-representations-used" class="section">
+ <div class="section" id="resources-presented-and-representations-used">
<h3><span class="secno">4.2 </span>Resources presented and representations used</h3>
- <div id="service-description" class="section">
+ <div class="section" id="service-description">
<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 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.
+ 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 href="#bib-URI-template" rel="biblioentry" class="bibref">URI-template</a></cite>] for URIs to access <a href="#dfn-provenance-locations-resource" title="provenance locations resource" class="internalDFN">provenance locations resources</a> and/or <a href="#dfn-provenance-information" class="internalDFN">provenance information</a>. Dereferencing the service URI returns a representation of this service description. The service description <em title="may" class="rfc2119">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>.
+ This example shows a provenance service description using JSON format [<cite><a href="#bib-RFC4627" rel="biblioentry" class="bibref">RFC4627</a></cite>], which is presented as MIME content-type <code>application/json</code>.
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">{
- "provenance_service_uri": "http://example.org/provenance_service/",
- "provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
- "provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
+ "provenance_service_uri": "http://example.org/provenance_service/",
+ "provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
+ "provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
}</pre>
</code>
<p class="issue">
@@ -654,25 +847,25 @@
</p>
</div>
- <div id="provenance-locations" class="section">
+ <div class="section" id="provenance-locations">
<h4><span class="secno">4.2.2 </span>Provenance locations</h4>
<p>
- 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.
+ A <dfn id="dfn-provenance-locations-resource">provenance locations resource</dfn> enumerates one or more <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a>s identifying <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> associated with a given resource.
</p>
<p>
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>.
+ This example uses JSON format [<cite><a href="#bib-RFC4627" rel="biblioentry" class="bibref">RFC4627</a></cite>], presented as MIME content type <code>application/json</code>.
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">{
- "uri": "http://example.org/qdata/",
- "provenance": [
- "http://source1.example.org/provenance/qdata/",
- "http://source2.example.org/prov/qdata/",
- "http://source3.example.com/prov?id=qdata"
+ "uri": "http://example.org/qdata/",
+ "provenance": [
+ "http://source1.example.org/provenance/qdata/",
+ "http://source2.example.org/prov/qdata/",
+ "http://source3.example.com/prov?id=qdata"
]
}</pre>
</code>
@@ -681,10 +874,10 @@
</p>
</div>
- <div id="provenance-information" class="section">
+ <div class="section" id="provenance-information">
<h4><span class="secno">4.2.3 </span>Provenance information</h4>
<p>
- Provenance information about a resource or resources may be returned in any format. It is recommended that the format be one defined by the Provenance Model specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].
+ Provenance information about a resource or resources may be returned in any format. It is recommended that the format be one defined by the Provenance Model specification [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>].
</p>
<p>
Assuming a given resource URI <code>http://example.org/qdata/</code>, and
@@ -694,10 +887,8 @@
</div>
-
-<!-- <section class="informative"> -->
-
- <div id="provenance-service-discovery" class="section">
+ <!-- <section class="informative"> -->
+ <div class="section" id="provenance-service-discovery">
<h3><span class="secno">4.3 </span>Provenance service discovery</h3>
<p>
This specification does not define any specific mechanism for discovering provenance services. Applications may use any appropriate mechanism, including but not limited to: prior configuration, search engines, service registries, etc.
@@ -706,14 +897,10 @@
</div>
-
-<!-- ===================================================================================== -->
-
+<!-- ===================================================================================== -->
- <div id="querying-provenance-information" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">5. </span>Querying provenance information</h2>
+ <div class="section" id="querying-provenance-information">
+ <!--OddPage--><h2><span class="secno">5. </span>Querying provenance information</h2>
<p>
Simply identifying and retrieving provenance information as a web resource may not always meet the requirements of a particular application or service, e.g.:
</p><ul>
@@ -727,13 +914,13 @@
A provenance query service provides an alternative way to access provenance information and/or Provenance-URIs. An application will need a provenance query service URI, and some relevant information about the entity whose provenance is to be accessed.
</p>
<p>
- The details of a provenance query service is an implementation choice, but for interoperability between different providers and users we recommend use of SPARQL [<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>]. The query service URI would then be the URI of a SPARQL endpoint (or, to use the SPARQL specification language, a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>). The following subsections provide examples for what are considered to be some plausible common scenarios for using SPARQL, and are not intended to cover all possibilities.
+ The details of a provenance query service is an implementation choice, but for interoperability between different providers and users we recommend use of SPARQL [<cite><a href="#bib-RDF-SPARQL-PROTOCOL" rel="biblioentry" class="bibref">RDF-SPARQL-PROTOCOL</a></cite>] [<cite><a href="#bib-RDF-SPARQL-QUERY" rel="biblioentry" class="bibref">RDF-SPARQL-QUERY</a></cite>]. The query service URI would then be the URI of a SPARQL endpoint (or, to use the SPARQL specification language, a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>). The following subsections provide examples for what are considered to be some plausible common scenarios for using SPARQL, and are not intended to cover all possibilities.
</p>
- <div id="find-provenance-uri-given-entity-uri-of-resource" class="section">
+ <div class="section" id="find-provenance-uri-given-entity-uri-of-resource">
<h3><span class="secno">5.1 </span>Find provenance-URI given entity-URI of resource</h3>
<p>
- If the requester has an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>, a simple SPARQL query may be used to return the correpsonding <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>. E.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
+ If the requester has an <a href="#dfn-entity-uri" class="internalDFN">entity-URI</a>, a simple SPARQL query may be used to return the corresponding <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a>. E.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
<code>
</code></p><pre class="example"><code> @prefix prov: <@@TBD>
SELECT ?provenance_uri WHERE
@@ -748,16 +935,16 @@
</p>
</div>
- <div id="find-provenance-uri-given-identifying-information-about-a-resource" class="section">
+ <div class="section" id="find-provenance-uri-given-identifying-information-about-a-resource">
<h3><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</h3>
<p>
- If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate an entity description and obtain its provenance-URI(s). The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification. For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [<cite><a class="bibref" rel="biblioentry" href="#bib-PRISM">PRISM</a></cite>] recommended by FaBio [<cite><a class="bibref" rel="biblioentry" href="#bib-FABIO">FABIO</a></cite>], might look like this:
+ If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate an entity description and obtain its provenance-URI(s). The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification. For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [<cite><a href="#bib-PRISM" rel="biblioentry" class="bibref">PRISM</a></cite>] recommended by FaBio [<cite><a href="#bib-FABIO" rel="biblioentry" class="bibref">FABIO</a></cite>], might look like this:
<code>
</code></p><pre class="example"><code> @prefix prov: <@@TBD>
@prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
SELECT ?provenance_uri WHERE
{
- [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
+ [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
}
</code></pre><code>
</code>
@@ -767,7 +954,7 @@
</p>
</div>
- <div id="obtain-provenance-information-directly-given-an-entity-uri-of-a-resource" class="section">
+ <div class="section" id="obtain-provenance-information-directly-given-an-entity-uri-of-a-resource">
<h3><span class="secno">5.3 </span>Obtain provenance information directly given an entity-URI of a resource</h3>
<p>
This scenario retrieves provenance information directly given the URI of a resource or entity, and may be useful where the provenance information has not been assigned a specific URI, or when the calling application is interested only in specific elements of provenance information.
@@ -795,20 +982,16 @@
</div>
-
-<!-- ===================================================================================== -->
-
+<!-- ===================================================================================== -->
- <div id="incremental-provenance-retrieval" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">6. </span>Incremental Provenance Retrieval</h2>
- <p><a class="internalDFN" href="#dfn-provenance-information">Provenance information</a> may be large. While this specification does not define how to implement scalable provenance systems, it does allow for publishers to make available provenance in an incremental fashion. We now discuss two possibilities for incremental provenance retrieval.
+ <div class="section" id="incremental-provenance-retrieval">
+ <!--OddPage--><h2><span class="secno">6. </span>Incremental Provenance Retrieval</h2>
+ <p><a href="#dfn-provenance-information" class="internalDFN">Provenance information</a> may be large. While this specification does not define how to implement scalable provenance systems, it does allow for publishers to make available provenance in an incremental fashion. We now discuss two possibilities for incremental provenance retrieval.
</p>
- <div id="via-web-retrieval" class="section">
+ <div class="section" id="via-web-retrieval">
<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>Publishers are not required to publish all the provenance information associated with a given entity at a particular <a href="#dfn-provenance-uri" class="internalDFN">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 href="#resource-accessed-by-http" class="sectionRef">section 3.1 Resource accessed by HTTP</a>)</li>
<li>Dereference <code>provenance-uri-1</code></li>
@@ -818,33 +1001,29 @@
<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 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>The same approach can be adopted when using the <a href="#dfn-provenance-service" class="internalDFN">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 href="#dfn-entity-uri" class="internalDFN">entity-uri</a>.
</p>
</div>
- <div id="via-queries" class="section">
+ <div class="section" id="via-queries">
<h3><span class="secno">6.2 </span>Via Queries</h3>
- <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>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 href="#bib-RDF-SPARQL-PROTOCOL" rel="biblioentry" class="bibref">RDF-SPARQL-PROTOCOL</a></cite>] [<cite><a href="#bib-RDF-SPARQL-QUERY" rel="biblioentry" class="bibref">RDF-SPARQL-QUERY</a></cite>]. Using SPARQL queries, provenance can be selectively retrieved using combinations of filters and or path queries.
</p>
</div>
</div>
-
-<!-- ===================================================================================== -->
-
+<!-- ===================================================================================== -->
- <div id="iana-considerations" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">7. </span>IANA considerations</h2>
+ <div class="section" id="iana-considerations">
+ <!--OddPage--><h2><span class="secno">7. </span>IANA considerations</h2>
<p>This document requests registration of new link relations, per <a href="http://tools.ietf.org/html/rfc5988#section-6.2.1">section-6.2.1 of RFC 5988</a>.
</p>
<p class="TODO">
@@TODO The following templates should be completed and submitted to link-relations@ietf.org:
</p>
- <div id="registration-template-for-link-relation---provenance" class="section">
- <h3><span class="secno">7.1 </span>Registration template for link relation: "provenance"</h3>
+ <div class="section" id="registration-template-for-link-relation---provenance">
+ <h3><span class="secno">7.1 </span>Registration template for link relation: "provenance"</h3>
<p>
</p><dl>
<dt>Relation Name:</dt>
@@ -870,10 +1049,10 @@
</dl>
<p></p>
</div>
- <div id="registration-template-for-link-relation---anchor" class="section">
- <h3><span class="secno">7.2 </span>Registration template for link relation: "anchor"</h3>
+ <div class="section" id="registration-template-for-link-relation---anchor">
+ <h3><span class="secno">7.2 </span>Registration template for link relation: "anchor"</h3>
<p class="pending">
- The name "anchor" has been used for the link relation name, despite the corresponding URI being described as an entity-URI. This terminology has been chosen to align with usage in the description of the HTTP <code>Link</code> header field, per <a href="http://tools.ietf.org/html/rfc5988#section-5.2">RFC 5988</a>.
+ The name "anchor" has been used for the link relation name, despite the corresponding URI being described as an entity-URI. This terminology has been chosen to align with usage in the description of the HTTP <code>Link</code> header field, per <a href="http://tools.ietf.org/html/rfc5988#section-5.2">RFC 5988</a>.
</p>
<p>
</p><dl>
@@ -883,7 +1062,7 @@
</dd>
<dt>Description:</dt>
<dd>
- when used in conjunction with a "provenance" link, the resource identified by target IRI of the link is an entity for which provenance information may be provided. This may be used, for example, to isolate relevant information from a referenced document that contains provenance information for several entities.
+ when used in conjunction with a "provenance" link, the resource identified by target IRI of the link is an entity for which provenance information may be provided. This may be used, for example, to isolate relevant information from a referenced document that contains provenance information for several entities.
</dd>
<dt>Reference:</dt>
<dd>
@@ -900,8 +1079,8 @@
</dl>
<p></p>
</div>
- <div id="registration-template-for-link-relation---provenance-service" class="section">
- <h3><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</h3>
+ <div class="section" id="registration-template-for-link-relation---provenance-service">
+ <h3><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</h3>
<p>
</p><dl>
<dt>Relation Name:</dt>
@@ -929,36 +1108,28 @@
</div>
</div>
-
-<!-- ===================================================================================== -->
-
+<!-- ===================================================================================== -->
- <div id="security-considerations" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">8. </span>Security considerations</h2>
+ <div class="section" id="security-considerations">
+ <!--OddPage--><h2><span class="secno">8. </span>Security considerations</h2>
<p>
Provenance is central to establishing trust in data. If provenance information is corrupted, it may lead agents (human or software) to draw inappropriate and possibly harmful conclusions. Therefore, care is needed to ensure that the integrity of provenance data is maintained.
</p>
<p>
- When using HTTP to access provenance information, or to determine a provenance URI, secure HTTP (https) <em class="rfc2119" title="should">should</em> be used.
+ When using HTTP to access provenance information, or to determine a provenance URI, secure HTTP (https) <em title="should" class="rfc2119">should</em> be used.
</p>
<p>
- When retrieving a provenance URI from a document, steps <em class="rfc2119" title="should">should</em> be taken to ensure the document itself is an accurate copy of the original whose author is being trusted (e.g. signature checking, or verifying its checksum against an author-provided secure web service).
+ When retrieving a provenance URI from a document, steps <em title="should" class="rfc2119">should</em> be taken to ensure the document itself is an accurate copy of the original whose author is being trusted (e.g. signature checking, or verifying its checksum against an author-provided secure web service).
</p>
<p class="TODO">
@@TODO ... privacy, access control to provenance (note to self: discussed in Edinburgh linked data provenance workshop). In particular, note that the fact that a resource is openly accessible does not mean that its provenance information should also be.
</p>
</div>
-
-<!-- ===================================================================================== -->
-
+<!-- ===================================================================================== -->
- <div class="appendix section" id="acknowledgements">
-
-<!-- OddPage -->
-<h2><span class="secno">A. </span>Acknowledgements</h2>
+ <div id="acknowledgements" class="appendix section">
+ <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
The editors acknowledge the contribution and review from members of the provenance working group.
</p>
@@ -967,28 +1138,24 @@
</p>
</div>
-
-<!-- ===================================================================================== -->
-
+<!-- ===================================================================================== -->
- <div class="appendix section" id="provenance-service-format-examples">
-
-<!-- OddPage -->
-<h2><span class="secno">B. </span>Provenance service format examples</h2>
+ <div id="provenance-service-format-examples" class="appendix section">
+ <!--OddPage--><h2><span class="secno">B. </span>Provenance service format examples</h2>
<p>
- 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.
+ 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 title="may" class="rfc2119">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">
+ <div class="section" id="rdf-turtle-example-of-service-description">
<h3><span class="secno">B.1 </span>RDF Turtle example of service description</h3>
<p>
- 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>.
+ This example uses the RDF Turtle format [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>], presented as MIME content-type <code>text/turtle</code>.
</p>
<code>
<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}"
+ provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
+ provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
.</pre>
</code>
<p class="note">
@@ -999,16 +1166,16 @@
</p>
</div>
- <div id="rdf-xml-example-of-service-description" class="section">
+ <div class="section" id="rdf-xml-example-of-service-description">
<h3><span class="secno">B.2 </span>RDF/XML example of service description</h3>
- <p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
+ <p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a href="#bib-RDF-SYNTAX-GRAMMAR" rel="biblioentry" class="bibref">RDF-SYNTAX-GRAMMAR</a></cite>], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
<code>
<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 = "@@TBD@@#"
+ xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:provds = "@@TBD@@#"
>
- <provds:Service_description rdf:about="http://example.org/provenance_service/">
+ <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> ;
<provds:provenance_content_template>http://example.org/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
</provds:Service_description>
@@ -1019,17 +1186,17 @@
</p>
</div>
- <div id="plain-xml-example-of-service-description" class="section">
+ <div class="section" id="plain-xml-example-of-service-description">
<h3><span class="secno">B.3 </span>Plain XML example of service description</h3>
<p class="TODO">
@@TODO: provide example and schema
</p>
</div>
- <div id="rdf-turtle-example-of-provenance-locations" class="section">
+ <div class="section" id="rdf-turtle-example-of-provenance-locations">
<h3><span class="secno">B.4 </span>RDF Turtle example of provenance locations</h3>
<p>
- 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>.
+ This example uses the RDF Turtle format [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>], presented as MIME content type <code>text/turtle</code>.
</p>
<code>
<pre class="example">@prefix prov: <@@TBD@@#> .
@@ -1045,28 +1212,28 @@
<p class="TODO">@@TODO: revise to conform with Provenance Model vocabulary; review URIs</p>
</div>
- <div id="rdf-xml-example-of-provenance-locations" class="section">
+ <div class="section" id="rdf-xml-example-of-provenance-locations">
<h3><span class="secno">B.5 </span>RDF/XML example of provenance locations</h3>
<p>
- This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>], and presented with MIME content type <code>application/rdf+xml</code>.
+ This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a href="#bib-RDF-SYNTAX-GRAMMAR" rel="biblioentry" class="bibref">RDF-SYNTAX-GRAMMAR</a></cite>], and presented with MIME content type <code>application/rdf+xml</code>.
</p>
<code>
<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 = "@@TBD@@#"
+ xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:prov = "@@TBD@@#"
>
- <prov:Entity rdf:about="http://example.org/qdata/">
- <prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;
- <prov:hasProvenance rdf:resource="http://source2.example.org/prov/qdata/" /> ;
- <prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
+ <prov:Entity rdf:about="http://example.org/qdata/">
+ <prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source2.example.org/prov/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
</prov:Entity>
</rdf:RDF></pre>
</code>
<p class="issue">@@TODO: revise to conform with Provenance Model vocabulary</p>
</div>
- <div id="plain-xml-example-of-provenance-locations" class="section">
+ <div class="section" id="plain-xml-example-of-provenance-locations">
<h3><span class="secno">B.6 </span>Plain XML example of provenance locations</h3>
<p class="TODO">
@@TODO: provide example and schema
@@ -1075,12 +1242,9 @@
</div>
-
-<!-- ===================================================================================== -->
+<!-- ===================================================================================== -->
-
-
-<!--
+<!--
<section class="appendix">
<h2>Motivating scenario</h2>
<p class="pending">
@@ -1126,14 +1290,11 @@
</section>
</section>
- -->
-
+-->
-<div id="references" class="appendix section">
-<!-- OddPage -->
-<h2><span class="secno">C. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><p>No normative references.</p></div><div id="informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-FABIO">[FABIO]</dt><dd>D. Shotton; S. Peroni. <a href="http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations"><cite>FaBiO, the FRBR-aligned Bibliographic Ontology.</cite></a> June 2011. URL: <a href="http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations">http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations</a>
+<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">C. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">C.1 </span>Normative references</h3><p>No normative references.</p></div><div class="section" id="informative-references"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-FABIO">[FABIO]</dt><dd>D. Shotton; S. Peroni. <a href="http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations"><cite>FaBiO, the FRBR-aligned Bibliographic Ontology.</cite></a> June 2011. URL: <a href="http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations">http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations</a>
</dd><dt id="bib-LINK-REL">[LINK-REL]</dt><dd>M. Nottingham, <a href="http://www.ietf.org/rfc/rfc5988.txt"><cite>Web Linking</cite></a>, October 2010, Internet RFC 5988. URL: <a href="http://www.ietf.org/rfc/rfc5988.txt">http://www.ietf.org/rfc/rfc5988.txt</a>
</dd><dt id="bib-POWDER-DR">[POWDER-DR]</dt><dd>Kevin Smith; Phil Archer; Andrea Perego. <a href="http://www.w3.org/TR/2008/WD-powder-dr-20081114"><cite>Protocol for Web Description Resources (POWDER): Description Resources.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2008/WD-powder-dr-20081114">http://www.w3.org/TR/2008/WD-powder-dr-20081114</a>
</dd><dt id="bib-PRISM">[PRISM]</dt><dd>International Digital Enterprise Alliance, Inc. <a href="http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf"><cite>PRISM: Publishing Requirements for Industry Standard Metadata</cite></a>. February 2008. URL: <a href="http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf">http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf</a>