--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/working/css/respec.css Tue Mar 27 18:00:51 2012 +0100
@@ -0,0 +1,464 @@
+
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: medium dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+code {
+ color: #224433;
+}
+
+
+/* --- 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: #224433;
+ font-weight: bold;
+ text-decoration: none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID {
+ font-weight: bold;
+ color: #005a9c;
+}
+
+.idlSuperclass {
+ font-style: italic;
+ color: #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType {
+ color: #005a9c;
+}
+.idlAttrName, .idlFieldName {
+ color: #224433;
+}
+.idlAttrName a, .idlFieldName a {
+ color: #224433;
+ border-bottom: 1px dotted #224433;
+ text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+ color: #005a9c;
+}
+.idlMethName {
+ color: #224433;
+}
+.idlMethName a {
+ color: #224433;
+ border-bottom: 1px dotted #224433;
+ text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+ color: #005a9c;
+}
+.idlParamName {
+ font-style: italic;
+}
+
+.extAttr {
+ color: #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+ color: #005a9c;
+}
+.idlConstName {
+ color: #224433;
+}
+.idlConstName a {
+ color: #224433;
+ border-bottom: 1px dotted #224433;
+ 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 {
+ margin-left: 2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt {
+ font-weight: normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
+ font-weight: bold;
+ color: #000;
+ font-family: monospace;
+}
+
+.attributes dt code, .fields dt code {
+ background: #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType 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 {
+ 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;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ 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;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+ border-top: 1px solid #224433;
+ border-bottom: 1px solid #224433;
+ padding: 1em;
+ margin-top: 1em;
+}
+
+pre.example::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ background: #224433;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.issue::before {
+ content: "Issue";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.note {
+ margin: 1em 0em 0em;
+ padding: 1em;
+ border: 2px solid #cff6d9;
+ background: #e2fff0;
+}
+
+.note::before {
+ content: "Note";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #cff6d9;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+ border: solid #bebebe 1px;
+ margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+ margin: 1.5em 0.5em 1em 1em;
+ font-weight: bold;
+ font-style: italic;
+}
+
+span.practicelab { background: #dfffff; }
+
+span.practicelab {
+ position: relative;
+ padding: 0 0.5em;
+ top: -1.5em;
+}
+
+p.practicedesc {
+ margin: 1.5em 0.5em 1em 1em;
+}
+
+@media screen {
+ p.practicedesc {
+ position: relative;
+ top: -2em;
+ padding: 0;
+ margin: 1.5em 0.5em -1em 1em;
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+ background-color: white;
+ color: black;
+ font-style: normal;
+ font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; } /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; } /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; } /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; } /* comments */
+pre.sh_sourceCode .sh_number { color: purple; } /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; } /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/working/prov-aq-gk-20120327.html Tue Mar 27 18:00:51 2012 +0100
@@ -0,0 +1,961 @@
+<!DOCTYPE html>
+
+<html>
+ <head>
+ <title>PROV-AQ: Provenance Access and Query</title>
+ <link rel="stylesheet" type="text/css" href="css/respec.css" />
+ <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:
+-->
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+<!-- Use local version of ReSpec.js for debugging:
+ <script src="js/respec.js" class="remove"></script>
+-->
+ <script class='remove'>
+ var addExtraReferences = function() {
+ for (var k in extraReferences)
+ berjon.biblio[k] = extraReferences[k];
+ };
+ var extraReferences = {
+
+ "LINK-REL" : "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>",
+
+ "RFC2387" : "E. Levinson. <a href=\"http://www.ietf.org/rfc/rfc2387.txt\"><cite>The MIME Multipart/Related Content-type.</cite></a> August 1998. Internet RFC 2387. URL: <a href=\"http://www.ietf.org/rfc/rfc2387.txt\">http://www.ietf.org/rfc/rfc2387.txt</a>",
+
+ "RFC3297" : "G. Klyne; R. Iwazaki; D. Crocker. <a href=\"http://www.ietf.org/rfc/rfc3297.txt\"><cite>Content Negotiation for Messaging Services based on Email.</cite></a> July 2002. Internet RFC 3297. URL: <a href=\"http://www.ietf.org/rfc/rfc3297.txt\">http://www.ietf.org/rfc/rfc3297.txt</a>",
+
+ "PRISM" : "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>",
+
+ "FABIO" : "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>",
+
+ "URI-template":
+ "J. Gregorio; R. Fielding, ed.; M. Hadley; M. Nottingham. "+
+ "<a href=\"https://datatracker.ietf.org/doc/draft-gregorio-uritemplate/\"><cite>URI Template</cite></a>. "+
+ "September 2011, Work in progress. "+
+ "URL: <a href=\"https://datatracker.ietf.org/doc/draft-gregorio-uritemplate/\"><cite>https://datatracker.ietf.org/doc/draft-gregorio-uritemplate/</cite></a>",
+
+ "REST-APIs":
+ "R. Fielding. "+
+ "<a href=\"http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven\">REST APIs must be hypertext driven</a>. "+
+ "October 2008 (blog post), "+
+ "URL: <a href=\"http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven\">http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</a>",
+
+ "PROV-DM":
+ "L. Moreau; P. Missier. "+
+ "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
+
+ "PROV-O":
+ "S. Sahoo; D. McGuinness. "+
+ "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html\"><cite>PROV Ontology Model</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html/\">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a>",
+
+ "SPARQL-SD":
+ "G. T. Williams. "+
+ "<a href=\"http://www.w3.org/TR/sparql11-service-description/\"><cite>SPARQL 1.1 Service Description</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://www.w3.org/TR/sparql11-service-description/\">http://www.w3.org/TR/sparql11-service-description/</a>",
+
+ "SPARQL-HTTP":
+ "Chimezie Ogbuji. "+
+ "<a href=\"http://www.w3.org/TR/sparql11-http-rdf-update/\"><cite>SPARQL 1.1 Service Description</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://www.w3.org/TR/sparql11-http-rdf-update/\">http://www.w3.org/TR/sparql11-http-rdf-update/</a>",
+
+ };
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "prov-aq",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ // subtitle : "an excellent document",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ copyrightStart: "2011",
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ // previousPublishDate: "1977-03-15",
+ // previousMaturity: "WD",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ //extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+ extraCSS: [],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Graham Klyne", url: "",
+ company: "University of Oxford", companyURL: "http://www.ox.ac.uk/" },
+
+ { name: "Paul Groth", url: "",
+ company: "VU University Amsterdam", companyURL: "http://www.vu.nl/" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [
+ // { name: "Your Name", url: "http://example.org/",
+ // company: "Your Company", companyURL: "http://example.com/" },
+ //],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ authors: [
+ { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
+ company: "University of Southampton" },
+ { name: "Olaf Hartig", url: "http://olafhartig.de/",
+ company: "Invited Expert"},
+ { name: "Yogesh Simmhan",
+ company: "Invited Expert"},
+ { name: "James Myers", url:"http://www.rpi.edu/research/ccni/",
+ company: "Rensselaer Polytechnic Institute"},
+ { name: "Timothy Lebo", url:"http://tw.rpi.edu/web/person/TimLebo",
+ company: "Rensselaer Polytechnic Institute"},
+ { name: "Khalid Belhajjame", url: "http://semanticweb.org/wiki/Khalid_Belhajjame",
+ company: "University of Manchester" },
+ { name: "Simon Miles",
+ company: "Invited Expert", url:"http://www.inf.kcl.ac.uk/staff/simonm/" },
+ ],
+
+ // name of the WG
+ wg: "Provenance Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/prov",
+
+ // name (with the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "public-prov-comments",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
+
+ // Add extraReferences to bibliography database
+ preProcess: [addExtraReferences],
+ };
+ </script>
+ </head>
+ <body>
+
+
+ <section id='abstract'>
+This document specifies how to use standard Web protocols,
+including HTTP, to obtain information about the provenance of Web
+resources. We describe both simple access mechanisms for
+locating provenance information associated with web pages or resources, and
+provenance query services for more complex deployments. This is
+part of the larger W3C Prov provenance framework.
+ </section>
+
+ <section id="sotd">
+ This document is part of a set of specifications produced by the W3C 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.
+ </section>
+
+<!-- == Sect 1 =================================================================================== -->
+
+ <section>
+ <h2>Introduction</h2>
+ <p>
+ The Provenance Data Model [[PROV-DM]] and Provenance Ontology [[PROV-O]] specifications define how to represent provenance information in the World Wide Web.
+ </p>
+ <p>
+ This note describes how standard web protocols may be used to locate, retrieve and query provenance information:
+ <ul>
+ <li>
+ Simple mechanisms for retrieving and discovering provenance information are described in <a href="#accessing-provenance-information" class="sectionRef"></a> and <a href="#locating-provenance-information" class="sectionRef"></a> .
+ </li>
+ <li>
+ More advanced discovery service and query mechanisms that may be used for more demanding deployments are described in <a href="#provenance-services" class="sectionRef"></a>, <a href="#querying-provenance-information" class="sectionRef"></a> and <a href="#incremental-provenance-retrieval" class="sectionRef"></a>.
+ </li>
+ </ul>
+ </p>
+
+ <section>
+ <h2>Concepts</h2>
+ <p>
+ In defining the specification below, we make use of the following concepts.
+ <dl>
+ <dt><dfn>Provenance information</dfn></dt>
+ <dd>refers to provenance represented in some fashion.</dd>
+ <dt><dfn>Provenance-URI</dfn></dt>
+ <dd>a URI denoting some <a class="internalDFN">provenance information</a>.</dd>
+ <dt><dfn>Entity</dfn></dt>
+ <dd>an aspect of a <a class="internalDFN">resource</a>, about which one wishes to present some <a 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 class="internalDFN">resource</a>. See also [[PROV-DM]], and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
+ <dt><dfn>Entity-URI</dfn></dt>
+ <dd>a URI denoting an <a class="internalDFN">entity</a>, which allows that entity to be identified for the purpose of finding and expressing <a class="internalDFN">provenance information</a> (see <a href="#provenance-entities-resources" class="sectionRef"></a> for discussion)</dd>
+ <dt><dfn>Provenance service</dfn></dt>
+ <dd>a service that provides <class="internalDFN">provenance information</a> given a <a class="internalDFN">resource</a> URI or an <a class="internalDFN">entity-URI</a>.</dd>
+ <dt><dfn>Service-URI</dfn></dt>
+ <dd>the URI of a <a class="internalDFN">provenance service</a>.</dd>
+ <dt><dfn>Resource</dfn></dt>
+ <dd>also referred to as <dfn>web resource</dfn>: a resource as described by the Architecture of the World Wide Web [[WEBARCH]], <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">entities</a> (see <a href="#provenance-entities-resources" class="sectionRef"></a> for discussion)</dd>
+ </dl>
+ </p>
+
+ </section>
+
+ <section>
+ <h2 id="provenance-entities-resources">Provenance, entities and resources</h2>
+ <p>
+ Fundamentally, <a 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">entity</a> is simply a resource (in the sense defined by [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>) that is a contextualized view or instance of an original resource. For example, a W3C 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 W3C 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">provenance information</a> may be not universally applicable to a <a 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 class="internalDFN">entity</a>, and an <a class="internalDFN">entity-URI</a> is used to refer to it within provenance information.
+ </p>
+ </section>
+
+ <section>
+ <h2>Interpreting provenance information</h2>
+ <p><a class="internalDFN">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">entities</a>. Within some provenance information, the entities thus described are identified by their <a 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>
+ </section>
+
+ </section>
+
+<!-- == Sect 2 =================================================================================== -->
+
+ <section>
+ <h2>Accessing provenance information</h2>
+ <p>Web applications may access <a class="internalDFN">provenance information</a> in the same way as any web resource, by dereferencing its URI. Thus, any provenance information may be associated with a <a class="internalDFN">provenance-URI</a>, and may be accessed by dereferencing that URI using web mechanisms.
+ </p>
+ <p>
+ How much or how little provenance information is returned in response to a retrieval request is a matter for the provenance provider application.
+ </p>
+ <p>
+ It may be useful to provide provenance information through a service interface. A REST protocol for provenance retrieval is defined in Section <a href="#provenance-services" class="sectionRef"></a>.
+ </p>
+ When publishing provenance information, the location of that information either at a URI or within a Service should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef"></a>.
+ </p>
+
+
+
+ </section>
+
+<!-- == Sect 3 =================================================================================== -->
+
+ <section>
+ <h2>Locating provenance information</h2>
+ <p>
+ When <a class="internalDFN">provenance information</a> is a resource that can be accessed using web retrieval, one needs to know a <a class="internalDFN">provenance-URI</a> to dereference. If this is known in advance, there is nothing more to specify. If a provenance-URI is not known then a mechanism to discover one must be based on information that is available to the would-be accessor. Likewise, provenance information may be exposed by a service. In this case, the <a class="internalDFN">Service-URI</a> needs to be known.
+ </p>
+ <p>Provenance information about a resource may be provided by several parties other than the provider of that resource, each using different locations, and each with different concerns. (It is possible that these different parties may provide contradictory provenance information.)
+ </p>
+ <p>
+ Once provenance information about a resource 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">entity</a> and is identified by an <a class="internalDFN">entity-URI</a>.
+ </p>
+ <p>
+ We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">Service-URI</a>along with a <a class="internalDFN">entity-URI</a>.
+
+ Three mechanisms are described here:
+ <ul>
+ <li>The requester knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
+ <li>The requester has a copy of a resource represented as HTML or XHTML</li>
+ <li>The requester has a copy of a resource represented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
+ </ul>
+ These particular cases are selected as corresponding to primary current web protocol and data formats. Finally, in <a href="#arbitrary-data" class="sectionRef"></a>, we discuss the case of a resource in an unspecified format which has been provided by some means other than HTTP.
+ </p>
+ <p>
+ The mechanisms specified for use with HTTP and HTML are similar to those proposed by POWDER [[POWDER-DR]] (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>
+
+ <section>
+ <h2>Resource accessed by HTTP</h2>
+ <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> [[LINK-REL]]. The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
+ </p>
+ <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"></a>, and may be used as shown:
+ <pre class="pattern">Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
+ 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 within the referenced provenance information as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
+ </p>
+ <p>
+ If no <code>anchor</code> link is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the resource.
+ </p>
+ <p>
+ 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 MAY 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"></a>).
+ </p>
+ <p>
+ Provenance resources indicated in this way are not guaranteed to be authoritative. Trust in the linked provenance information must be determined separately from trust in the original resource. Just as in the web at large, it is a user's 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. (See also <a href="#security-considerations" class="sectionRef"></a>.)
+ </p>
+
+ <section>
+ <h2>Specifying Provenance Services</h2>
+ <p>
+ The document provider may indicate that provenance information about the document is provided by a <a 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>
+ <pre class="pattern">
+Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
+ <p>
+ The <code>provenance-service</code> link identifies the <a class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ </p>
+ <p>
+ There may be multiple <code>provenance-service</code> link header fields, and these may appear in an HTTP response together with <code>provenance</code> link header fields (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
+ </p>
+ </section>
+
+ </section>
+
+ <section>
+ <h2>Resource represented as HTML</h2>
+ <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"></a>, and may be used as shown:
+ <pre class="pattern">
+ <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>">
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ ...
+ </body>
+ </html></pre>
+ </p>
+ <p>
+ The <code><cite>provenance-URI</cite></code> given by the <code>provenance</code> link element identifies the provenance-URI for the document.
+ </p>
+ <p>
+ The <code><cite>entity-URI</cite></code> given by the <code>anchor</code> link element specifies an specifies an identifier for the entity that may be used within the provenance information when referring to the document.
+ </p>
+ <p>
+ An HTML document header MAY include multiple <code>provenance</code> 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 MAY 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 RECOMMENDED that this convention be used only when the document is static.
+ </p>
+
+ <section>
+ <h2>Specifying Provenance Services</h2>
+ <p>
+ The document creator may specify that the provenance information about the document is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a third link relation type following the same pattern as above:
+ </p>
+ <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>">
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ ...
+ </body>
+ </html></pre>
+ <p>
+ The <code>provenance-service</code> link element identifies the <a class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ </p>
+ <p>
+ There may be multiple <code>provenance-service</code> link elements, and these MAY appear in the same document as <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>
+ </section>
+ </section>
+
+ <section>
+ <h2>Resource represented as RDF</h2>
+ <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. For this purpose three new RDF properties, <code>prov:hasProvenance</code>, <code>prov:hasAnchor</code>, and <code>prov:hasProvenanceService</code>, are defined in the following.
+ (These terms may be used to indicate provenance of other resources too, but discussion of such usage is beyond the scope of this section.)
+ </p>
+ <p>
+ The 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. This property corresponds to a <a href="#registration-template-for-link-relation---provenance">provenance link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code><link></code> element.
+ </p>
+ <p>
+ Property <code>prov:hasAnchor</code> specifies an <a class="internalDFN">entity-URI</a> used in the provenance information to refer to the containing RDF document.
+ This corresponds to use of the <code>anchor</code> parameter in an HTTP provenance <code>Link</code> header field, or an <a href="#registration-template-for-link-relation---anchor">anchor link relation</a> in an HTML <code><link></code> element, which similarly indicate a URI used by the provenance information to refer to the described document.
+ </p>
+ <p>
+ Property <code>prov:hasProvenanceService</code> specifies a <a class="internalDFN">service-URI</a>s associated with the RDF document for possible access to provenance information. This property corresponds to a <a href="#registration-template-for-link-relation---provenance-service">provenance-service link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code><link></code> element.
+ </p>
+ <pre class="example code">
+ @prefix prov: <<provns/>>
+
+ <> dcterms:title "Welcome to example.com" ;
+ prov:anchor <http://example.com/data/resource.rdf> ;
+ prov:hasProvenance <http://example.com/provenance/resource.rdf> ;
+ prov:hasProvenanceService <http://example.com/provenance-service/> .
+ :
+ (RDF data)
+ :
+ </pre>
+ </section>
+
+ <section>
+ <h2>Arbitrary data</h2>
+ <p>
+ 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">entity-URI</a>, <a class="internalDFN">provenance-URI</a> and/or <a class="internalDFN">service-URI</a>. Format-specific metadata provision might also be used to include <a 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:
+ <ul>
+ <li>MIME multipart/related [[RFC2387]]: 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 (e.g., <a href="http://www.openarchives.org/ore/">ORE</a>, <a href="http://xml.coverpages.org/mpeg21-didl.html">MPEG-21 DIDL</a>, <a href="https://wiki.ucop.edu/display/Curation/BagIt">BagIt</a>) to name a handful. Practical implementations of these are commonly based on the ZIP file format.
+ </li>
+ <li>
+ Packaging formats along the lines of those used for shipping Java web applications (basically, a ZIP file with a manifest and some imposed structure)
+ </li>
+ <li>
+ Ongoing work in the research community (e.g. <a href="http://eprints.ecs.soton.ac.uk/21587/">Why Linked Data is Not Enough for Scientists</a>, ePub, etc.) to encapsulate data, code, annotations and metadata into a common exchangeable format.
+ </li>
+ </ul>
+ </p>
+ </section>
+
+ </section>
+
+<!-- == Sect 4 =================================================================================== -->
+
+ <section>
+ <h2>Provenance Services</h2>
+ <p>
+ This section describes a REST based protocol [[REST-APIs]] for provenance services with facilities for the retrieval of provenance information. The protocol specifies the semantics of HTTP operations for retrival of provenance information from a provenance service. This protocol follows the approach of the SPARQl Graph Store HTTP Protocol.
+
+ The introduction of this protocol is motivated by the following reasons:
+ <ul>
+ <li>the naming authority associated with the entity-uri is not the same as the server managing provenance information</li>
+ <li> other services may have provenance information about the same entity</li>
+ <li> the naming authority for the entity-uri is not available <li.
+ <li> there is no dereferencable provenance-uri containing provenance information for a particular entity</li>
+ <li> provenance services may provide additional extensibility points for allowing the control over returned provenance information.
+ </ul>
+
+ <section>
+ <h2>HTTP GET</h2>
+ <p class="TODO">
+ @@ TODO needs revisiting. There's discussion in SPARQL WG about how appropriate the pattern copied may be. In any case, I don't think URI-escaping is needed here. Cf. http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2011Nov/0051.html et seq. Esp. http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2011Dec/0032.html
+ </p>
+ <blockquote>As discussed in [[RFC3986]], query components are often used to carry identifying information in the form of key / value pairs where the value is another URI. -- [[SPARQL-HTTP]]</blockquote>
+
+ This protocol leverages this convention and provides a specific interface whereby a entity-uri can be embedded within the query component of the request URI:
+ <p>
+ <code>
+ <pre>
+ GET /provenance/service?<b>provenance-element</b>=http%3A//www.example.com/entity HTTP/1.1
+ Host: example.com
+ </pre>
+ </code>
+ The embedded entity-uri (http://www.example.com/entity) is precent-encoded and identifies the entity for which provenance information is to be returned. Any server that implements this protocol and receives a request URI in this form SHOULD return provenance information for the URI embedded in the query component where the URI is the result of percent-decoding the value associated with the provenance-element key. The embedded URI MUST be an absolute URI and the server MUST respond with a 400 Bad Request if it is not.
+ <p>
+ If the provenance information identified in the request does not exist in the server, a 404 Not Found response code SHOULD be provided in the response.
+ </p>
+ <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 [[PROV-DM]] and its associated serializations. Services must identity the <code>Content-Type</code> of the information returned. Furthermore, services SHOULD respect the <code>Content-Type</code> specified by the client.
+ </p>
+
+ <p class="TODO">
+ @@TODO:Should we allow more than one provenance element?<br/>
+ @@TODO: It would be helpful to have content types for PROV-O, PROV-XML and so on. How? This would help with interoprability.<br/>
+ @@TODO: Should we rename to protocol?
+ </p>
+ </section>
+
+ <!-- <section class="informative"> -->
+ <section>
+ <h2>Provenance service discovery</h2>
+ <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.
+ </p>
+ <p>
+ To facilitate service discovery, we recommend that RDF publication of service descriptions uses the provenance service type <code><provns/>ProvenanceService</code>, defined by the <a href="http://dvcs.w3.org/hg/prov/file/0abd4c442b42/ontology/components/ProvenanceService.ttl">provenance ontology</a> [[PROV-O]].
+ The RDF examples in <a href="#provenance-service-format-examples" class="sectionRef"></a> show this use.
+ </p>
+ <p class="TODO">
+ @@TODO: Fix up URI used in the "provenance ontology" link above, when finalized. <br/>
+ @@TODO: Do we need this discussion? <br/>
+ @@TODO What are the "provenance service format examples" supposed to provide?
+ </p>
+ </section>
+
+ <!-- <section class="informative"> -->
+ <section>
+ <h2>Provenance service description</h2>
+ <p class="TODO">
+ @@TODO: Do we want anything for this? It's referenced by sections 3.1.1, 3.2.1, and is IMO an essential part of a true REST i/f
+ </p>
+ </section>
+
+ </section>
+
+<!-- == Sect 5 =================================================================================== -->
+
+ <section>
+ <h2> Best Practice </h2>
+
+ <section id="querying-provenance-information">
+ <h2>Using SPARQL for Provenance Queries</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.:
+ <ul>
+ <li>the entity for which provenance information is required is not identified by a known URI</li>
+ <li>the provenance information for an entity is not directly identified by a known URI</li>
+ <li>a requirement to access provenance information for a number of distinct but related entities in a single atomic operation</li>
+ <li><i>etc.</i></li>
+ </ul>
+ </p>
+ <p>
+ 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 [[RDF-SPARQL-PROTOCOL]] [[RDF-SPARQL-QUERY]]. 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>
+ <p>
+ A SPARQL protocol service description may be published using the <cite>SPARQL 1.1 Service Description</cite> vocabulary [[SPARQL-SD]].
+ </p>
+
+ <section>
+ <h2>Find provenance-URI given entity-URI of resource</h2>
+ <p>
+ If the requester has an <a class="internalDFN">entity-URI</a>, a simple SPARQL query may be used to return the corresponding <a class="internalDFN">provenance-URI</a>. E.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
+ <code>
+ <pre class="example code">
+ @prefix prov: <<provns/>>
+ SELECT ?provenance_uri WHERE
+ {
+ <http://example.org/resource> prov:hasProvenance ?provenance_uri
+ }
+ </pre>
+ </code>
+ </p>
+ </section>
+
+ <section>
+ <h2>Find Provenance-URI given identifying information about a resource</h2>
+ <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 [[PRISM]] recommended by FaBio [[FABIO]], might look like this:
+ <pre class="example code">
+ @prefix prov: <<provns/>>
+ @prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
+ SELECT ?provenance_uri WHERE
+ {
+ [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
+ }
+ </pre>
+ </p>
+ </section>
+
+ <section>
+ <h2>Obtain provenance information directly given an entity-URI of a resource</h2>
+ <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.
+ </p>
+ <p>
+ If the original resource has an entity-URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this:
+ <pre class="example code">
+ @prefix prov: <<provns/>>
+ CONSTRUCT
+ {
+ <http://example.org/resource> ?p ?v
+ }
+ WHERE
+ {
+ <http://example.org/resource> ?p ?v
+ }
+ </pre>
+ This query essentially extracts all available properties and values available from the query service used that are directly about the specified entity, and returns them as an RDF graph. This may be fine if the service contains <em>only</em> provenance information about the indicated resource, or if the non-provenance information is also of interest. A more complex query using specific provenance vocabulary terms may be needed to selectively retrieve just provenance information when other kinds of information are also available.
+ </p>
+ <p class="TODO">
+ @@TODO: specific provenance namespace and property to be determined by the model specification? The above query pattern assumes provenance information is included in direct properties about the entity. When an RDF provenance vocabulary is fully formulated, this may well turn out to not be the case. A better example would be one that retrieves specific provenance information when the vocabulary terms have been defined.
+ </p>
+ </section>
+
+ </section>
+
+ <!-- == Sect 5.2 ===================================================================================== -->
+
+ <section id="incremental-provenance-retrieval">
+ <h2>Incremental Provenance Retrieval</h2>
+ <p><a 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>
+
+ <section>
+ <h2>Via Web Retrieval</h2>
+ <p>Publishers are not required to publish all the provenance information associated with a given entity at a particular <a 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:
+ <ol>
+ <li>For a given entity (<code>entity-uri-1</code>) retrieve it's associated <code>provenance-uri-1</code> and its associated <code>entity-uri-1</code> using the HTTP <code>Link</code> header (<a href="#resource-accessed-by-http" class="sectionRef"></a>)</li>
+ <li>Dereference <code>provenance-uri-1</code></li>
+ <li>Navigate the provenance information</li>
+ <li>When reaching a dead-end during navigation, that is on encountering a reference to an entity (<code>entity-uri-2</code>) with no provided provenance information, find its provenance-URI and continue from Step 2. (Note: an HTTP HEAD request for <code>entity-uri-2</code> may be used to obtain the Link headers without retrieving the entity content.)</li>
+ </ol>
+ </p>
+ <p>To reduce the overhead of multiple HTTP requests, a provenance information publisher are encouraged to 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">provenance service</a> API (<a href="#provenance-services" class="sectionRef"></a>). However, instead of performing an HTTP HEAD or GET against a resource one queries the provenance service using the given <a class="internalDFN">entity-uri</a>.
+ </p>
+ </section>
+
+ <section>
+ <h2>Via SPARQL Queries</h2>
+ <p>Provenance information may be made available using a SPARQL endpoint (<a href="#querying-provenance-information" class="sectionRef"></a>) [[RDF-SPARQL-PROTOCOL]] [[RDF-SPARQL-QUERY]]. Using SPARQL queries, provenance can be selectively retrieved using combinations of filters and or path queries.
+ </p>
+ </section>
+
+ </section>
+
+ </section>
+
+<!-- ==== Section 6 ===================================================================================== -->
+
+ <section>
+ <h2>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>
+ <section>
+ <h2>Registration template for link relation: "provenance"</h2>
+ <p>
+ <dl>
+ <dt>Relation Name:</dt>
+ <dd>
+ <code>provenance</code>
+ </dd>
+ <dt>Description:</dt>
+ <dd>
+ the resource identified by target IRI of the link provides provenance information about the entity identified by the context link
+ </dd>
+ <dt>Reference:</dt>
+ <dd>
+ @@this spec, @@provenance-model-spec
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ ...
+ </dd>
+ <dt>Application Data:</dt>
+ <dd>
+ ...
+ </dd>
+ </dl>
+ </p>
+ </section>
+ <section>
+ <h2>Registration template for link relation: "anchor"</h2>
+ <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>.
+ </p>
+ <p>
+ <dl>
+ <dt>Relation Name:</dt>
+ <dd>
+ <code>anchor</code>
+ </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.
+ </dd>
+ <dt>Reference:</dt>
+ <dd>
+ @@this spec, @@provenance-model-spec
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ ...
+ </dd>
+ <dt>Application Data:</dt>
+ <dd>
+ ...
+ </dd>
+ </dl>
+ </p>
+ </section>
+ <section>
+ <h2>Registration template for link relation: "provenance-service"</h2>
+ <p>
+ <dl>
+ <dt>Relation Name:</dt>
+ <dd>
+ <code>provenance-service</code>
+ </dd>
+ <dt>Description:</dt>
+ <dd>
+ the resource identified by target URI of the link is an provenance service per <a href="#provenance-services" class="sectionRef"></a> of this specification.
+ </dd>
+ <dt>Reference:</dt>
+ <dd>
+ @@this spec, @@provenance-model-spec
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ ...
+ </dd>
+ <dt>Application Data:</dt>
+ <dd>
+ ...
+ </dd>
+ </dl>
+ </p>
+ </section>
+ </section>
+
+<!-- ==== Section 7 ===================================================================================== -->
+
+ <section>
+ <h2>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 information is maintained.
+ </p>
+ <p>
+ When using HTTP to access provenance information, or to determine a provenance URI, secure HTTP (https) SHOULD be used.
+ </p>
+ <p>
+ When retrieving a provenance URI from a document, steps SHOULD 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>
+ </section>
+
+<!-- ===================================================================================== -->
+
+ <section class='appendix'>
+ <h2>Acknowledgements</h2>
+ <p>
+ The editors acknowledge the contribution and review from members of the provenance working group.
+ </p>
+ <p>
+ Many thanks to Robin Berjon for making our lives so much easier with his cool <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html">ReSpec</a> tool.
+ </p>
+ </section>
+
+<!-- ===================================================================================== -->
+
+ <section class='appendix'>
+ <h2>Names added to prov: namespace</h2>
+ <p>
+ This specification defines the following additional names in the provenance namespace.
+ </p>
+ <p>
+ The provenance namespace URI is <provns/>.
+ </p>
+ <p>
+ <table>
+ <tr>
+ <th>name</th><th>Description</th><th>Definition ref</th>
+ </tr>
+ <tr>
+ <td>ProvenanceService</td><td>Class for a service described by a provenance service description</td><td>...</td>
+ </tr>
+ <tr>
+ <td>anchor</td><td>Indicates anchor URI for a potentially dynamic resource instance</td><td>...</td>
+ </tr>
+ <tr>
+ <td>hasProvenance</td><td>Relates a resource to its provenance</td><td>...</td>
+ </tr>
+ <tr>
+ <td>hasProvenanceService</td><td>Relates a resource to a provenance service</td><td>...</td>
+ </tr>
+ </table>
+ </p>
+ </section>
+
+
+<!-- ===================================================================================== -->
+
+ <!--
+<section class='appendix'>
+ <h2>Provenance service format examples</h2>
+ <p>
+ In <a href="#provenance-services" class="sectionRef"></a>, the provenance service description was represented as a JSON-formatted document. As noted, HTTP content negotiation MAY 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>
+
+ <section>
+ <h2>RDF Turtle example of service description</h2>
+ <p>
+ This example uses the RDF Turtle format [[TURTLE]], presented as MIME content-type <code>text/turtle</code>.
+ </p>
+ <pre class="example code">
+ @prefix provds: <@@TBD@@#> .
+ @prefix prov: <http://www.w3.org/ns/prov-o/> .
+
+ <http://example.org/provenance_service/> a prov:ProvenanceService ;
+ 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>
+ <p class="note">
+ The provenance URI templates are encoded in RDF as plain string literals, <em>not</em> as resource URIs.
+ </p>
+ <p class="TODO">
+ Finalize URIs in the above example.
+ </p>
+ </section>
+
+ <section>
+ <h2>RDF/XML example of service description</h2>
+ <p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [[RDF-SYNTAX-GRAMMAR]], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
+ <pre class="example code">
+ <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:prov = "http://www.w3.org/ns/prov-o/"
+ >
+ <prov:ProvenanceService 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> ;
+ </prov:ProvenanceService>
+ </rdf:RDF>
+ </pre>
+ <p class="TODO">
+ Finalize URIs in the above example.
+ </p>
+ </section>
+
+ <section>
+ <h2>Plain XML example of service description</h2>
+ <p class="TODO">
+ @@TODO: provide example and schema
+ </p>
+ </section>
+
+ <section>
+ <h2>RDF Turtle example of provenance locations</h2>
+ <p>
+ This example uses the RDF Turtle format [[TURTLE]], presented as MIME content type <code>text/turtle</code>.
+ </p>
+ <pre class="example code">
+ @prefix prov: <@@TBD@@#> .
+ <http://example.org/qdata/> a prov:Entity ;
+ prov:hasProvenance <http://source1.example.org/provenance/qdata/> ;
+ prov:hasProvenance <http://source2.example.org/prov/qdata/> ;
+ prov:hasProvenance <http://source3.example.com/prov?id=qdata>
+ .
+ </pre>
+ <p class="issue">
+ NOTE: The namespace URI used here for the provenance properties is different from that used in the service description. I am anticipating that it will be defined as part of the provenance model. If it is not defined as part of the provenance model, then a property name should be allocated in the provenance discovery service namespace.
+ </p>
+ <p class="TODO">@@TODO: revise to conform with Provenance Model vocabulary; review URIs</p>
+ </section>
+
+ <section>
+ <h2>RDF/XML example of provenance locations</h2>
+ <p>
+ This is essentially the same as the Turtle example above, but encoded in RDF/XML [[RDF-SYNTAX-GRAMMAR]], and presented with MIME content type <code>application/rdf+xml</code>.
+ </p>
+ <pre class="example code">
+ <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@@#"
+ >
+ <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>
+ <p class="TODO">@@TODO: revise to conform with Provenance Model vocabulary</p>
+ </section>
+
+ <section>
+ <h2>Plain XML example of provenance locations</h2>
+ <p class="TODO">
+ @@TODO: provide example and schema
+ </p>
+ </section>
+
+ </section>
+ -->
+
+<!-- ===================================================================================== -->
+
+<!--
+ <section class="appendix">
+ <h2>Motivating scenario</h2>
+ <p class="pending">
+ I propose to replace this appendix with text based on Yogesh's walk-through of the scenario, renaming to be something like "Motivating scenario and examples"
+ </p>
+ <p><a href="http://www.w3.org/2011/prov/wiki/ProvenanceAccessScenario">This scenario</a> was selected by the provenance working group as a touchstone for evaluating any provenance access proposal. This appendix evaluates the foregoing proposals against the requirements implied by that scenario.</p>
+ <p>
+ <ul>
+ <li>Obtaining the document D: for the purpose of this analysis, it is assumed that the access to the document is either from a known Web URI, or the document is available as HTML or RDF (the primary web standards for documents and data). The mechanisms here are in principle applicable to other document forms of a per-format basis.
+ <ul>
+ <li>D1, D2: use the HTTP <code>Link:</code> header. Any server providing the document may provide this information. Different servers might offer links to different provenance sources.</li>
+ <li>D3: information provided as an image with a known URI, but from a non-provenance-aware source. The image URI can be used as a key to access a third party provenance discovery service.
+ <li>D4, D6, D7, D8: information provided as an image, without a known web location. At the very least, some mechanism, not specified here, is needed to identify the image provided. In the case of an email attachment, it is possible (but not guaranteed) that the email message MIME wrapper specifies a URI for the image, which can be used as a key. Some image formats support embedded metadata which might be used for this purpose. <em>(Arbitrary data files could be wrapped in a package, say MIME multipart/related [[RFC2387]], that could include additional metadata. Image files could be wrapped in a minimal HTML document. It is not clear to me at this stage that a single mechanism is appropriate for all situations)</em>.</li>
+ <li>D5: HTML email. Depending on how the HTML is constructed, the HTML header could include <code><link></code> elements.</li>
+ </ul>
+ </li>
+ <li>Lacking identification or in-band metadata, some independent identification of the thing represented by an available mechanism is required. <em>I think this is unavoidable</em></li>
+ <li>Enacting the "Oh yeah?" feature
+ <ul>
+ <li>W: once a URI for provenance information has been determined, accessing it using a web browser or other web client software should be straightforward. If the provenance is accessible via a third party query service, that may be less straightforward.</li>
+ <li>E: this scenario seems to envisage a wholesale overhaul of email client software, which seems unlikely. If a URI for provenance can be provided, the natural way to access it would be via a web client of some kind, which might be a browser or other software.</li>
+ <li>S: this scenario effectively calls for this: given an arbitrary data resource, implement a general purpose application to discover, retrieve and analyze provenance about that resource. At the present time, this is a matter for experimental development, which could be based substantially on the mechanisms described for provenance discovery and access via third party services.</li>
+ </ul>
+ </li>
+ <li>I: Accessing the provenance
+ <ul>
+ <li>W: a web client needs one or more URIs for provenance information, and/or URI(s) for a provenance query service and sufficient additional information about the resource to formulate an effective query. They may also need access information that can be used to assess (or help a user assess) the trustworthiness of provenance of information obtained, (which could be more provenance information)</li>
+ <li>E: an email client is a passive receiver of information, so asking one to retrieve provenance information is a perverse expectation. There have been some attempts to standardize email protocols that interact with the email sender but such mechanisms have not been significantly deployed in practice. This case can be viewed as a variation on the shell-client case (S) below. If all provenance information is sent <em>with</em> the original content using standard email mechanisms (MIME multipart, etc.) then the email client may use that (or hand it off to a helper application) as the basis for provenance-based analysis or presentation.</li>
+ <li>S: command shell or other local application. This is the general case for provenance access. Given some arbitrary information, what does a provenance-aware application need to access the required provenance information? It may employ any of the mechanisms described above.</li>
+ </ul>
+ </li>
+ </ul>
+ </p>
+ <section>
+ <h2>Gap analysis</h2>
+ <p>
+ There are clearly a number of capabilities needed for a provenance-aware application that are not covered by the mechanisms described above. But most of these amount to implementation details and decisions for a particular application, and as such are beyond the scope of this document to specify.
+ </p>
+ <p>
+ One feature not covered above that might be a candidate for specification is a common format for a data package that combines original content along with provenance-related metadata or data. At this stage, it is not clear what format that might take, but some possible candidates are discussed in <a href="#arbitrary-data" class="sectionRef"></a>.
+ In any case, it seems to me that a specification that is specific for provenance to the exclusion of other metadata is unlikely to obtain traction, as provenance is just part of a wider landscape of information quality, trust, preservation and more.
+ </p>
+ </section>
+ </section>
+
+-->
+
+ </body>
+</html>