--- a/paq/prov-aq.html Wed Jun 13 22:44:02 2012 +0100
+++ b/paq/prov-aq.html Wed Jun 13 22:44:27 2012 +0100
@@ -23,6 +23,8 @@
"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>",
+ "RFC2392" : "E. Levinson. <a href=\"http://www.ietf.org/rfc/rfc2392.txt\"><cite>Content-ID and Message-ID Uniform Resource Locators.</cite></a> August 1998. Internet RFC 2392. URL: <a href=\"http://www.ietf.org/rfc/rfc2392.txt\">http://www.ietf.org/rfc/rfc2392.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>",
@@ -84,27 +86,28 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
+ // publishDate: "2012-06-19",
// if the specification's copyright date is a range of years, specify
// the start date here:
- copyrightStart: "2011",
+ copyrightStart: "2012",
// 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",
+ previousPublishDate: "2012-01-10",
+ 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",
+ //edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/working/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: [],
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+ //extraCSS: [],
// editors, add as many as you like
// only "name" is required
@@ -172,26 +175,26 @@
<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
+including HTTP, to obtain information about the provenance of
+resources on the Web. 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.
+ This document is part of a set of specifications produced by the W3C provenance working group 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.
<h4>PROV Family of Specifications</h4>
The PROV family of specifications aims to define the various aspects that are necessary to achieve the vision of inter-operable
interchange of provenance information in heterogeneous environments such as the Web.
The specifications are as follows.
<ul>
-<li> PROV-DM, the PROV data model for provenance (this document),</li>
+<li> PROV-DM, the PROV data model for provenance,</li>
<li> PROV-DM-CONSTRAINTS, a set of constraints applying to the PROV data model,</li>
<li> PROV-N, a notation for provenance aimed at human consumption,</li>
-<li> PROV-O, the PROV ontology, an OWL-RL ontology allowing the mapping of PROV to RDF;</li>
-<li> PROV-AQ, the mechanisms for accessing and querying provenance; </li>
+<li> PROV-O, the PROV ontology, an OWL-RL ontology allowing the mapping of PROV to RDF,</li>
+<li> PROV-AQ, the mechanisms for accessing and querying provenance (this document), </li>
<li> PROV-PRIMER, a primer for the PROV data model,</li>
<li> PROV-SEM, a formal semantics for the PROV data model.</li>
<li> PROV-XML, an XML schema for the PROV data model.</li>
@@ -206,9 +209,9 @@
should focus on PROV-DM and PROV-DM-CONSTRAINTS. PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
</ul>
<h4>Second Public Working Draft</h4>
+<p>
This is the second public working draft. The changes focus on revising the provenance-service specification to provide better guidance to developers as well as introducing better naming conventions for the use of link headers in locating provenance.
-<p>
-
+</p>
</section>
@@ -221,6 +224,7 @@
</p>
<p>
This note describes how standard web protocols may be used to locate, retrieve and query provenance information:
+ </p>
<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> .
@@ -229,39 +233,43 @@
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.
+
+ <p>In defining the specification below, we make use of the following concepts. </p>
<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>Constrained resource</dfn></dt>
- <dd>an aspect, version or instance of a <a class="internalDFN">resource</a>, about which one may wish 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 constrained resource is itself a <a class="internalDFN">resource</a>, and may have it's own URI different from that of the original. See also [[PROV-DM]], and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
+ <dd>an aspect, version or instance of a <a class="internalDFN">resource</a>, about which one may wish 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. A constrained resource is itself a <a class="internalDFN">resource</a>, and may have it's own URI different from that of the original. See also [[PROV-DM]], and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
<dt><dfn>Target-URI</dfn></dt>
- <dd>a URI denoting a <a class="internalDFN">resource</a> (including any <a class="internalDFN">constrained resource</a>), which identifies that resource 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>
+ <dd>a URI denoting a <a class="internalDFN">resource</a> (including any <a class="internalDFN">constrained resource</a>), which identifies that resource for the purpose of finding and expressing <a class="internalDFN">provenance information</a> associated with it (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">target-uri</a>.</dd>
+ <dd>a service that provides <a class="internalDFN">provenance information</a> given a <a class="internalDFN">target-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 instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
+ <dd>also referred to as <dfn>resource on the Web</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 instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
+-->
+ <dt><dfn>Resource</dfn></dt>
+ <dd>a resource in the general sense of "whatever might be identified by a URI", 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 instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
</dl>
- </p>
+
</section>
<section>
<h2 id="provenance-entities-resources">Provenance and resources</h2>
<p>
- Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resource</a>s. 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 class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resource</a>s. In general, resources may vary over time and context. E.g., a resource describing the weather in London changes from day-to-day, or a listing of 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 resources (e.g. a 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 a notion of constrained resources. A <a class="internalDFN">constrained resource</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 some other 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 also have <a class="internalDFN">target-uri</a>s, each 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. Target-URIs may use any URI scheme, and are not required to be dereferencable.
+ Provenance descriptions of dynamic and context-dependent resources are possible through a notion of constrained resources. A <a class="internalDFN">constrained resource</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 some other 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 throughout its lifetime. Each individual revision would also have its own <a class="internalDFN">target-URI</a> denoting the specification at that 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. Target-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 target-URIs to refer to versions of that resource. Some given provenance information may use multiple target-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 target-URIs of the various revisions.
@@ -274,11 +282,13 @@
<section>
<h2>Interpreting provenance information</h2>
<p>
- <a class="internalDFN">Provenance information</a> describes relationships between <a class="internalDFN">resource</a>s, including activities and agents. Any given provenance information may contain information about several resources, referring to them using their <a class="internalDFN">target-uri</a>s.
+ Any given <a class="internalDFN">provenance information</a> may contain information about several resources, referring to them using their various <a class="internalDFN">target-URI</a>s.
+ Thus, when interpreting provenance information, it is important to be aware that statements about several resources 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 resource.)
</p>
<p>
- Thus, when interpreting provenance information, it is important to be aware that statements about several resources 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 resource.)
+ Provenance information is not of itself guaranteed to be authoritative or correct. Trust in 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 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>
</section>
@@ -288,7 +298,7 @@
<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.
+ Web applications may access <a class="internalDFN">provenance information</a> in the same way as any resource on the Web, 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.
@@ -297,7 +307,7 @@
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>
<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>.
+ When publishing provenance information, a corresponding <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">service-URI</a> should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef"></a>.
</p>
<p>
Some alternative practices for accessing provenance information are discussed in <a href="#best-practice" class="sectionRef"></a>
@@ -314,16 +324,18 @@
<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 may also need to know how to locate information about that resource within the provenance information. This may be a <a class="internalDFN">constrained resource</a> identified by a separate <a class="internalDFN">target-uri</a>.
+ Once provenance information about a resource is retrieved, one may also need to know how to locate information about that resource within the provenance information. This may be a <a class="internalDFN">constrained resource</a> identified by a separate <a class="internalDFN">target-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">target-uri</a>.
+ 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">target-URI</a>.
Three mechanisms are described here:
+ </p>
<ul>
<li>The requester knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
<li>The requester has a copy of a resource represented as HTML or XHTML</li>
<li>The requester has a copy of a resource represented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
</ul>
+ <p>
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>
@@ -335,13 +347,9 @@
<p>
For a resource accessible using HTTP, provenance information may be indicated using an HTTP <code>Link</code> header field, as defined by <a href="http://tools.ietf.org/html/rfc5988">Web Linking (RFC 5988)</a> [[LINK-REL]]. The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
</p>
+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>target-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 resource is identified within the referenced provenance information as <code><cite>target-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
<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>target-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 resource is identified within the referenced provenance information as <code><cite>target-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>target-uri</cite></code> is assumed to be the URI of the resource, used in the corresponding HTTP request.
+ If no <code>anchor</code> parameter is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the resource, used in the corresponding HTTP request.
</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.
@@ -359,10 +367,10 @@
<section>
<h2>Specifying Provenance Services</h2>
<p>
- The resource 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:
+ The resource provider may indicate that provenance information about the resource 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>target-uri</cite>"; rel="provenance-service"</pre>
+Link: <cite>provenance-service-URI</cite>; anchor="<cite>target-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 a <a class="internalDFN">resource</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
</p>
@@ -375,26 +383,26 @@
<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.
+ <div>
+ For a document presented as HTML or XHTML, without regard for how it has been obtained, provenance information may be associated with a resource by adding a <code><link></code> element to the HTML <code><head></code> section.
Two new link relation types for referencing provenance information are registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>, and may be used as shown:
<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>target-uri</cite>">
+ <link rel="anchor" href="<cite>target-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
...
</body>
</html></pre>
- </p>
+ </div>
<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>target-uri</cite></code> given by the <code>anchor</code> link element specifies an specifies an identifier for the document that may be used within the provenance information when referring to the document.
+ The <code><cite>target-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the document 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 sources that are known to the creator of the document, each of which may provide provenance information about the document.
@@ -405,7 +413,7 @@
</p>
-->
<p>
- If no "anchor" link element is provided then the <code><cite>target-uri</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this convention be used only when the document is static and has an easily-determined URI.
+ If no "anchor" link element is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this convention be used only when the document is static and has a stable URI that is reasonably expected to be available to anyone accessing the document (e.g. when delivered from a web server, or as part of a MIME structure containing content identifiers [[RFC2392]]).
</p>
<section>
@@ -417,7 +425,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance-service" href="<cite>service-URI</cite>">
- <link rel="anchor" href="<cite>target-uri</cite>">
+ <link rel="anchor" href="<cite>target-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -436,21 +444,21 @@
<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.
+ 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 as follows.
(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 a <a class="internalDFN">target-uri</a> used in the provenance information to refer to the containing RDF document.
+ Property <code>prov:hasAnchor</code> specifies a <a class="internalDFN">target-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.
+ Property <code>prov:hasProvenanceService</code> specifies a <a class="internalDFN">service-URI</a> 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/>>
+ @prefix prov: <http://www.w3.org/ns/prov#>
<> dcterms:title "Welcome to example.com" ;
prov:hasAnchor <http://example.com/data/resource.rdf> ;
@@ -468,15 +476,15 @@
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">target-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.
+ 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">target-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:
+ 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 [[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.
+ 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://www.loc.gov/standards/mets/">METS</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.
</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)
@@ -485,7 +493,6 @@
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>, <a href="http://idpf.org/epub/30/spec/epub30-overview.html">ePub</a>, etc.) to encapsulate data, code, annotations and metadata into a common exchangeable format.
</li>
</ul>
- </p>
</section>
</section>
@@ -497,25 +504,25 @@
<p>
This section describes a REST-based protocol [[REST]] for provenance services with facilities for the retrieval of provenance information. The protocol specifies HTTP operations for retrieval of provenance information from a provenance service. It follows the approach of the SPARQL Graph Store HTTP Protocol [[SPARQL-HTTP]].
</p>
- <p>The introduction of this protocol is motivated by the following possible considerations:
+ <p>The introduction of this protocol is motivated by the following possible considerations: </p>
<ul>
- <li>the naming authority associated with the <a class="internalDFN">target-uri</a> is not the same as the service offering provenance information</li>
+ <li>the naming authority associated with the <a class="internalDFN">target-URI</a> is not the same as the service offering provenance information</li>
<li>multiple services have <a class="internalDFN">provenance information</a> about the same resource</li>
- <li>the service associated with the target-uri is not accessible for adding additional information when handling retrieval requests</li>
- <li>there is no dereferencable <a class="internalDFN">provenance-uri</a> containing provenance information for a particular resource</li>
+ <li>the service associated with the target-URI is not accessible for adding additional information when handling retrieval requests</li>
+ <li>there is no dereferencable <a class="internalDFN">provenance-URI</a> containing provenance information for a particular resource</li>
<li>provenance services may provide additional extensibility points for control over returned provenance information.</li>
</ul>
- </p>
+
<section>
<h2>HTTP GET</h2>
- <p>This protocol combines the <a class="internalDFN">target-uri</a> with the <a class="internalDFN">service-URI</a> to formulate an HTTP GET request, according to the following convention:
+ <div>This protocol combines the <a class="internalDFN">target-URI</a> with the <a class="internalDFN">service-URI</a> to formulate an HTTP GET request, according to the following convention:
<pre class="pattern">
GET /provenance/service?<b>target</b>=http://www.example.com/entity HTTP/1.1
Host: example.com</pre>
- </p>
- <p>The embedded target-URI (<code>http://www.example.com/entity</code>) identifies the resource 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 resource-URI embedded in the query component where that URI is the result of percent-decoding the value associated with the provenance-resource key. The embedded URI MUST be an absolute URI and the server MUST respond with a 400 Bad Request if it is not. If the supplied resource-URI includes a fragment identifier, the '#' MUST be %-encoded as <code>%23</code> when constructing the provenance-URI value; similarly, any '&' character in the resource-URI must be %-encoded as <code>%26</code>.
- </p>
+ </div>
+ <div>The embedded target-URI (<code>http://www.example.com/entity</code>) identifies the resource 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 resource-URI embedded in the query component where that URI is the result of percent-decoding the value associated with the provenance-resource key. The embedded URI MUST be an absolute URI and the server MUST respond with a 400 Bad Request if it is not. If the supplied resource-URI includes a fragment identifier, the '#' MUST be %-encoded as <code>%23</code> when constructing the provenance-URI value; similarly, any '&' character in the resource-URI must be %-encoded as <code>%26</code>.
+ </div>
<p>If the provenance information identified in the request does not exist in the server, a 404 Not Found response code SHOULD be returned.
</p>
<p>The format of returned provenance information is not defined here, but may be established through content type negotiation using <code>Accept:</code> header fields in the HTTP request. A provenance service SHOULD be capable of returning RDF using the vocabulary defined by [[PROV-O]], in any standard RDF serialization (e.g. RDF/XML), or any other standard serialization of the Provenance Model specification [[PROV-DM]]. Services MUST identify the <code>Content-Type</code> of the information returned.
@@ -529,9 +536,12 @@
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 provenance ontology [[PROV-O]].
+ To facilitate service discovery, we recommend that RDF publication of service descriptions uses the provenance service type <code>prov:ProvenanceService</code>, defined by the provenance ontology [[PROV-O]].
The RDF service description example below in <a href="#provenance-service-description" class="sectionRef"></a> shows this use.
</p>
+ <p class="TODO">
+ @@TODO: sync up term definitions with provenance ontology specification.
+ </p>
</section>
<!-- <section class="informative"> -->
@@ -546,7 +556,10 @@
prov:provenanceUriTemplate "<cite>service-URI</cite>?target={+uri}" .</pre>
<p>where <cite><code>service-URI</code></cite> is the URI of the provenance service. Note that the object of the <code>prov:provenanceUriTemplate</code> statement is a literal text value, not a URI.
</p>
- <p>A client may retrieve this service description and extract the associated value for <code>prov:provenance-uri-template</code>. This value is a string containing a URI template [[URI-template]] (level 2). A URI for the desired provenance information is obtained by expanding the URI template with the variable <code>uri</code> set to the resource-URI for which provenance is required. If the target-URI contains '#' or '&' these must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion.
+ <p>A client may retrieve this service description and extract the associated value for <code>prov:provenance-URI-template</code>. This value is a string containing a URI template [[URI-template]] (level 2). A URI for the desired provenance information is obtained by expanding the URI template with the variable <code>uri</code> set to the resource-URI for which provenance is required. If the target-URI contains '#' or '&' these must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion.
+ </p>
+ <p class="TODO">
+ @@TODO: sync up term definitions with provenance ontology specification.
</p>
</section>
@@ -560,77 +573,75 @@
<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.:
+ Simply identifying and retrieving provenance information as a resource on the Web may not always meet the requirements of a particular application or service, e.g.:</p>
<ul>
<li>the resource for which provenance information is required is not identified by a known URI</li>
- <li>the provenance information for an resource is not directly identified by a known URI</li>
+ <li>the provenance information for a resource is not directly identified by a known URI</li>
<li>a requirement to access provenance information for a number of distinct but related resources in a single atomic operation</li>
<li><i>etc.</i></li>
</ul>
+
+ <p>
+ A provenance query service provides an alternative way to access provenance information and/or provenance-URIs. An application will need a URI for the provenance query service, and some relevant information about the resource whose provenance is to be accessed.
</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 resource 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.
+ 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 <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>
+(often referred to as a "SPARQL endpoint").
+ 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>
-
+ <p>
+ The following subsections illustrate use cases for querying a SPARQL-based provenance query service.
+ </p>
<section>
- <h2>Find a provenance-URI given a target-uri</h2>
+ <h2>Find a provenance-URI given a target-URI</h2>
<p>
- If the requester has an <a class="internalDFN">target-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 target-uri <code>http://example.org/resource</code>:
+ If the requester has a <a class="internalDFN">target-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 target-URI <code>http://example.org/resource</code>:</p>
<pre class="example code">
- @prefix prov: <<provns/>>
+ @prefix prov: <http://www.w3.org/ns/prov#>
SELECT ?provenance_uri WHERE
{
<http://example.org/resource> prov:hasProvenance ?provenance_uri
}
</pre>
- </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 a resource 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:
+ 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 a resource 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:</p>
<pre class="example code">
- @prefix prov: <<provns/>>
+ @prefix prov: <http://www.w3.org/ns/prov#>
@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 a target-uri</h2>
+ <h2>Obtain provenance information directly given a target-URI</h2>
<p>
This scenario retrieves provenance information directly given the URI of a resource, 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 a URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this:
+ If the original resource has a URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this: </p>
<pre class="example code">
- @prefix prov: <<provns/>>
- CONSTRUCT
- {
- <http://example.org/resource> ?p ?v
- }
- WHERE
- {
- <http://example.org/resource> ?p ?v
+ @prefix prov: <http://www.w3.org/ns/prov#>
+ SELECT ?generationStartTime WHERE {
+ <http://example.org/resource> prov:wasGeneratedBy ?activity .
+ ?activity prov:startedAtTime ?generationStartTime .
}
</pre>
- </p>
+
<p>
- This query essentially extracts all available properties and values available from the query service used that are directly about the specified resource, 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 resource. 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.
+ This query extracts a "generation start time" for an artifact by following links to the start time of the activity which generated it.
</p>
</section>
@@ -645,17 +656,17 @@
<section>
<h2>Via Web Retrieval</h2>
- <p>Publishers are not required to publish all the provenance information associated with a given resource 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:
+ <p>Publishers are not required to publish all the provenance information associated with a given resource 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:</p>
<ol>
- <li>For a given resource (<code>target-uri-1</code>) retrieve it's associated <code>provenance-uri-1</code> and its associated <code>target-uri-1</code> using a returned HTTP <code>Link:</code> header field (<a href="#resource-accessed-by-http" class="sectionRef"></a>)</li>
- <li>Dereference <code>provenance-uri-1</code></li>
+ <li>For a given resource (<code>resource-URI</code>) retrieve it's associated <code>provenance-URI-1</code> and its associated <code>target-URI-1</code> using a returned HTTP <code>Link:</code> header field (<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 a resource (<code>target-uri-2</code>) with no provided provenance information, find its provenance-URI and continue from Step 2. (Note: an HTTP HEAD request for <code>target-uri-2</code> may be used to obtain the <code>Link:</code> headers without retrieving the resource representation.)</li>
+ <li>When reaching a dead-end during navigation, that is on encountering a reference to a resource (<code>target-URI-2</code>) with no provided provenance information, find its provenance-URI and continue from Step 2. (Note: an HTTP HEAD request for <code>target-URI-2</code> may be used to obtain the <code>Link:</code> headers without retrieving the resource representation.)</li>
</ol>
- </p>
+
<p>To reduce the overhead of multiple HTTP requests, a provenance information publishers 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 access the resource'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">target-uri</a>.
+ <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">target-URI</a>.
</p>
</section>
@@ -680,7 +691,6 @@
</p>
<section>
<h2>Registration template for link relation: "provenance"</h2>
- <p>
<dl>
<dt>Relation Name:</dt>
<dd>
@@ -703,11 +713,10 @@
...
</dd>
</dl>
- </p>
+
</section>
<section>
<h2>Registration template for link relation: "anchor"</h2>
- <p>
<dl>
<dt>Relation Name:</dt>
<dd>
@@ -730,11 +739,9 @@
...
</dd>
</dl>
- </p>
</section>
<section>
<h2>Registration template for link relation: "provenance-service"</h2>
- <p>
<dl>
<dt>Relation Name:</dt>
<dd>
@@ -757,7 +764,7 @@
...
</dd>
</dl>
- </p>
+
</section>
</section>
@@ -769,7 +776,7 @@
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.
+ Secure HTTP (https) SHOULD be used across unsecured networks when accessing provenance information that may be used as a basis for trust decisions, or to obtain a provenance URI for same.
</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).
@@ -777,6 +784,9 @@
<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>
+ <p class="TODO">
+ @@TODO Expand on trust-in-provenance issues. Suggested by Curt: Just as provenance information can help determine trust of the information content of a resource, provenance information related to the provenance itself ("provenance of provenance") can help determine trust of the provenance.
+ </p>
</section>
<!-- ===================================================================================== -->
@@ -798,10 +808,10 @@
<p>
This specification defines the following additional names in the provenance namespace.
</p>
+
<p>
- The provenance namespace URI is <provns/>.
+ The provenance namespace URI is http://www.w3.org/ns/prov#.
</p>
- <p>
<table>
<tr>
<th>name</th><th>Description</th><th>Definition ref</th>
@@ -822,7 +832,6 @@
<td>provenanceUriTemplate</td><td>Relates a provenance service to a URI template string for constructing provenance-URIs</td><td>...</td>
</tr>
</table>
- </p>
</section>