--- a/paq/prov-aq.html Mon Nov 19 12:21:55 2012 +0000
+++ b/paq/prov-aq.html Mon Nov 19 12:23:51 2012 +0000
@@ -95,7 +95,7 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- // publishDate: "2012-06-19",
+ // publishDate: "2012-06-19",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -240,31 +240,29 @@
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>
+ For ease of reference, the main body of this document contains some links to external web pages. Such links are distinguished from internal references thus: <a href="http://www.w3.org/2011/prov/wiki/Main_Page" class="externalRef">W3C Provenance Working Group</a>
+ </p>
+
<section>
<h2>Concepts</h2>
- <p>In defining the specification below, we make use of the following concepts. </p>
+ <p>In defining the specification below, we make use of the following concepts.</p>
<dl>
- <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>
- <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. 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>
+ <a href="#dfn-resource"><dt><dfn>Resource</dfn></dt></a>
+ <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" class="externalRef">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>
+ <a href="#dfn-constrained-resource"><dt><dfn>Constrained resource</dfn></dt></a>
+ <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" class="externalRef">section 2.3.2</a>.</dd>
+ <a href="#dfn-target-uri"><dt><dfn>Target-URI</dfn></dt></a>
<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 information</dfn></dt>
+ <a href="#dfn-provenance-information"><dt><dfn>Provenance information</dfn></dt></a>
<dd>refers to provenance represented in some fashion.</dd>
- <dt><dfn>Provenance-URI</dfn></dt>
+ <a href="#dfn-provenance-uri"><dt><dfn>Provenance-URI</dfn></dt></a>
<dd>a URI denoting some <a class="internalDFN">provenance information</a>.</dd>
- <dt><dfn>Provenance service</dfn></dt>
+ <a href="#dfn-provenance-service"><dt><dfn>Provenance service</dfn></dt></a>
<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>
+ <a href="#dfn-service-uri"><dt><dfn>Service-URI</dfn></dt></a>
<dd>the URI of a <a class="internalDFN">provenance service</a>.</dd>
-<!--
- <dt><dfn>Resource</dfn></dt>
- <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>
--->
</dl>
</section>
@@ -275,7 +273,7 @@
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 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.
+ 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" class="externalRef">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.
@@ -361,18 +359,19 @@
The mechanisms described here are intended to allow a provider to supply information that may assist a client in finding related provenance information. While a provider should avoid giving spurious information, there are no fixed semantics, particularly when multiple resources are indicated, and a client should not assume that a specific given provenance-uri will yield information about a specific given target-uri. In the general case, a client presented with multiple provenance-uris and multiple target-uris should look at all of the provenance-uris for information about any or all of the target-uris.
</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>).
+ 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" class="externalRef">4.1.1</a> and <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink" class="externalRef">4.1.3</a>).
</p>
<section>
<h2>Resource accessed by HTTP</h2>
- <p class="TODO">
- @@TODO: Use URIs for link relations (?)
+ <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" class="externalRef">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>
- 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>.)
+A <code>hasProvenance</code> link relation type for referencing provenance information may be used as shown:
+
+<pre class="pattern">Link: <cite>provenance-URI</cite>; rel="http://www.w3.org/ns/prov#hasProvenance"; 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>
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>
@@ -380,10 +379,10 @@
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.
+ An HTTP response MAY include multiple <code>hasProvenance</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>).
+ The presence of a <code>hasProvenance</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>.)
@@ -392,15 +391,15 @@
<section>
<h2>Specifying Provenance Services</h2>
<p>
- 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:
+ 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>hasProvenanceService</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>; rel="http://www.w3.org/ns/prov#hasProvenanceService"; anchor="<cite>target-URI</cite>"</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.
+ The <code>hasProvenanceService</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>
<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).
+ There may be multiple <code>hasProvenanceService</code> link header fields, and these may appear in an HTTP response together with <code>hasProvenance</code> link header fields (though, in simple cases, we anticipate that <code>hasProvenance</code> and <code>hasProvenanceService</code> link relations will not be used together).
</p>
</section>
@@ -408,17 +407,14 @@
<section>
<h2>Resource represented as HTML</h2>
- <p class="TODO">
- @@TODO: Use URIs for link relations (?)
- </p>
<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:
+ Two link relation types for referencing provenance information 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="http://www.w3.org/ns/prov#hasProvenance" href="<cite>provenance-URI</cite>">
+ <link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>target-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -427,21 +423,16 @@
</html></pre>
</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 identifier for the document that may be used within the provenance information when referring to the document.
+ The <code><cite>provenance-URI</cite></code> given by the <code>hasProvenance</code> link element identifies the provenance-URI for 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.
+ The <code><cite>target-URI</cite></code> given by the <code>hasAnchor</code> link element specifies an identifier for the document that may be used within the provenance information when referring to 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>resource-URIs</cite></code>.
+ An HTML document header MAY include multiple <code>hasProvenance</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.
</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 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]]).
+ If no <code>hasAnchor</code> 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>
@@ -452,8 +443,8 @@
<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>target-URI</cite>">
+ <link rel="http://www.w3.org/ns/prov#hasProvenanceService" href="<cite>service-URI</cite>">
+ <link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>target-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -461,10 +452,10 @@
</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 a <a class="internalDFN">resource</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ The <code>hasProvenanceService</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 a <a class="internalDFN">resource</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).
+ There MAY be multiple <code>hasProvenanceService</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>hasProvenance</code> and <code>hasProvenanceService</code> link relations would not be used together).
</p>
</section>
</section>
@@ -472,18 +463,18 @@
<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 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.)
+ 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 the link relations introduced above may be used as RDF properties: <code>prov:hasProvenance</code>, <code>prov:hasAnchor</code>, and <code>prov:hasProvenanceService</code>.
+ (These terms may be used to indicate provenance of arbitrary 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.
+ The RDF property <code>prov:hasProvenance</code> is 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 <code>hasProvenance</code> e link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code><link></code> element (see above).
</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.
- 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.
+ Property <code>prov:hasAnchor</code> specifies a <a class="internalDFN">target-URI</a> used in the indicated 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 a <code>hasAnchor</code> 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> 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 <code>hasProvenanceService</code> link relation used with an HTTP <code>Link</code> header field, or HTML <code><link></code> element.
</p>
<pre class="example code">
@prefix prov: <http://www.w3.org/ns/prov#>
@@ -556,15 +547,13 @@
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.
+ @@TODO: rework the above to take account of hasProvenanceService links
</p>
</section>
<!-- <section class="informative"> -->
<section>
<h2>Provenance service description</h2>
- <!--<p>The provenance service interface as described above violates REST constraints by requiring the client to know about the structure of URIs offered by the service (see [[REST-APIs]], 4th bullet point). The provenance service description mitigates this coupling by providing a mechanism for discovering the URI format to be used, starting with just the service URI.
- %</p> -->
<p>Dereferencing a provenance service URI should yield a provenance service description. This is to be compatible with the constraints of [[REST-APIs]]. The provenance service description should be available as RDF (in any of its common serializations, and determined through HTTP content negotiation), and it should contain RDF statements of the form:
</p>
<pre class="pattern">
@@ -572,13 +561,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 [[RFC3986]].
</p>
<p>While use of RDF for service descriptions is a recommended option, this specification does not preclude the use of non-RDF formats that a service may choose to offer, and which can be selected using HTTP content negotiation.
</p>
- <p class="TODO">
- @@TODO: sync up term definitions with provenance ontology specification.
- </p>
</section>
</section>
@@ -588,6 +574,10 @@
<section>
<h2>Best practice</h2>
+ <p class="TODO">
+ @@TODO: rtemove this section; cover in FAQ
+ </p>
+
<section id="querying-provenance-information">
<h2>Using SPARQL for provenance queries</h2>
<p>
@@ -604,7 +594,7 @@
</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 <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>
+ 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" class="externalRef">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>
@@ -701,94 +691,6 @@
<!-- ==== 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, or this section removed if URIs are used for link relations in ยง3: Use some material for table of UREIs introduced.
- </p>
- <section>
- <h2>Registration template for link relation: "provenance"</h2>
- <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 resource 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>
-
- </section>
- <section>
- <h2>Registration template for link relation: "anchor"</h2>
- <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 one 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>
- </section>
- <section>
- <h2>Registration template for link relation: "provenance-service"</h2>
- <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>
-
- </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. Just as provenance information can help determine a level of trust in some information, provenance information related to the provenance itself ("provenance of provenance") can help determine trust in the provenance itself.
@@ -804,8 +706,6 @@
</p>
<p>Provenance information may be used by audits to establish accountability for information use [[INFO-ACC]] and to verify use of proper processes in information processing activities. Thus, provenance management systems can provide mechanisms to support auditing and enforcement of information handling policies. In such cases, provenance information itself may be a valuable target for attack by malicious agents, and care must be taken to ensure it is stored securely and in a fashion that resists attempts to tamper with it.
</p>
-
-
</section>
<!-- ===================================================================================== -->
@@ -816,7 +716,7 @@
The editors acknowledge the contribution and review from members of the W3C Provenance working group for their feedback throughout the development of this specification.
</p>
<p>
- Thanks to Robin Berjon for making our lives easier with his <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html">ReSpec</a> tool.
+ Thanks to Robin Berjon for making our lives easier with his <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html" class="externalRef">ReSpec</a> tool.
</p>
</section>
@@ -824,149 +724,44 @@
<section class='appendix'>
<h2>Names added to prov: namespace</h2>
- <p class="TODO">
- @@TODO Create table of URIs introduced, and what they mean. Use some material from IOANA considerations. Consider separate tables for classes and properties.
- </p>
<p>
- This specification defines the following additional names in the provenance namespace.
- </p>
-
- <p>
- The provenance namespace URI is http://www.w3.org/ns/prov#.
+ This specification defines the following additional names in the provenance namespace
+ with URI <a href="http://www.w3.org/ns/prov#" class="externalRef">http://www.w3.org/ns/prov#</a>.
</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>
+ <th>Name</th><th>Description</th><th>Definition ref</th>
</tr>
<tr>
- <td>hasAnchor</td><td>Indicates anchor URI for a potentially dynamic resource instance</td><td>...</td>
+ <td>ProvenanceService</td>
+ <td>Class for a provenance service. Mainly for use in RDF provenance service descriptions, to facilitate discover..</td>
+ <td><a href="#provenance-service-description" class="sectionRef"></a></td>
</tr>
<tr>
- <td>hasProvenance</td><td>Relates a resource to its provenance</td><td>...</td>
+ <td>hasAnchor</td>
+ <td>Indicates a <a class="internalDFN">target-URI</a>target-URI for a potentially dynamic resource instance</td>
+ <td><a href="#resource-represented-as-html" class="sectionRef"></a></td>
</tr>
<tr>
- <td>hasProvenanceService</td><td>Relates a resource to a provenance service</td><td>...</td>
+ <td>hasProvenance</td>
+ <td>Indicates a <a class="internalDFN">provenance-URI</a> for a resource; the resource identified by this property provides provenance information about its subject or anchor resource.
+ </td>
+ <td><a href="#resource-accessed-by-http" class="sectionRef"></a>, <a href="#resource-represented-as-html" class="sectionRef"></a></td>
</tr>
<tr>
- <td>provenanceUriTemplate</td><td>Relates a provenance service to a URI template string for constructing provenance-URIs</td><td>...</td>
+ <td>hasProvenanceService</td>
+ <td>Indicates a <a class="internalDFN">provenance service</a> that can provide provenance information about its sibject or anchowresource.</td>
+ <td><a href="#specifying-provenance-services" class="sectionRef"></a></td>
+ </tr>
+ <tr>
+ <td>provenanceUriTemplate</td>
+ <td>Relates a provenance service to a URI template string for constructing provenance-URIs</td>
+ <td><a href="#provenance-service-description" class="sectionRef"></a></td>
</tr>
</table>
</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>
- -->
-
<!-- ===================================================================================== -->
</body>