--- a/paq/prov-aq.html Mon Jan 09 10:59:50 2012 +0000
+++ b/paq/prov-aq.html Mon Jan 09 15:09:09 2012 +0000
@@ -119,7 +119,7 @@
authors: [
{ name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
company: "University of Southampton" },
- { name: "Olaf Hartig",
+ { name: "Olaf Hartig", url: "http://olafhartig.de/",
company: "Invited Expert"},
{ name: "Yogesh Simmhan",
company: "Invited Expert"},
@@ -132,7 +132,6 @@
{ name: "Simon Miles",
company: "Invited Expert", url:"http://www.inf.kcl.ac.uk/staff/simonm/" },
],
-
// name of the WG
wg: "Provenance Working Group",
@@ -356,7 +355,7 @@
The <code><cite>provenance-URI</cite></code> given by the <code>provenance</code> link element identifies the provenance-URI for the document.
</p>
<p>
- The <code><cite>entity-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the presented document view, and which may be used within the provenance information when referring to this document.
+ The <code><cite>entity-URI</cite></code> given by the <code>anchor</code> link element specifies an specifies an identifier for the entity that may be used within the provenance information when referring to the document.
</p>
<p>
An HTML document header MAY include multiple "provenance" link elements, indicating a number of different provenance resources that are known to the creator of the document, each of which may provide provenance information about the document.
@@ -396,7 +395,7 @@
<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.
+ 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. (The same RDF 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>
For this purpose a new RDF property, <code>prov:hasProvenance</code>, is defined as a relation between two resources, where the object of the property is a resource that provides provenance information about the subject resource. Multiple <code>prov:hasProvenance</code> assertions may be made about a subject resource. 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.
@@ -460,7 +459,8 @@
Service implementations may provide either discovery, retrieval or both of these services, indicated by presence of the corresponding service URI templates in the service description. Which of these services to provide is a choice for individual service implementations.
</p>
<p>
- On the Web, the normal mechanism for retrieving information is to associate it with a URI, and dereference the URI using HTTP. This approach is enabled using the provenance discovery service mechanism: given the URI of some resource for which provenance information is required, the service returns one or more URIs from which provenance information may be obtained. This approach may be preferred when the provenance service cannot specify the form of URIs used for identifying provenance information, or when there may be more than one source of provenance information known to the provenance service.
+ On the Web, the normal mechanism for retrieving information is to associate it with a URI, and dereference the URI using HTTP. This approach is enabled using the provenance discovery service mechanism: given the URI of some resource for which provenance information is required, the service returns one or more URIs from which provenance information may be obtained.
+ This approach may be preferred when the URIs used for identifying provenance information are controlled by someone other than the provider of the provenance discovery service, or when there is more than one known source of provenance information.
</p>
<p>
The provenance retrieval service returns provenance information directly. This mechanism may be preferred when the provenance information is not already presented directly to the web, or is stored in a database with a complex query protocol, or when the provenance service can control the URI from which provenance information is served and avoid the intermediate step of URI discovery.
@@ -479,23 +479,24 @@
<ol>
<li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN">service description</a>.</li>
<li>Extract the provenance locations template from the service description.</li>
- <li>Use the provenance locations template with <code>entity-URI</code> for template variable <code>uri</code> to form <code>provenance-locations-URI</code>.</li>
+ <li>Form a <code>provenance-locations-URI</code> using the provenance locations template with <code>entity-URI</code> as a substitute for template variable <code>uri</code>.</li>
<li>Dereference <code>provenance-locations-URI</code> to obtain a <a class="internalDFN">provenance locations resource</a> in one of the formats described below.</li>
</ol>
</p>
<p>
- Any or all of URIs in the returned provenance locations may be used to retrieve provenance information, per <a href="#accessing-provenance-information" class="sectionRef"></a>.
+ Any or all of the URIs in the returned provenance locations may be used to retrieve provenance information, per <a href="#accessing-provenance-information" class="sectionRef"></a>.
</p>
</section>
<section>
<h2>Retrieve Provenance information for a resource</h2>
<p>
- To use the provenance service to directly retrieve provenance information for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or context (<code>entity-URI</code>):
+ To use the provenance service to directly retrieve provenance information for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or entity (<code>entity-URI</code>):
<ol>
<li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN">service description</a>.</li>
<li>Extract the provenance information template from the service description.</li>
- <li>Use the provenance information template with <code>entity-URI</code> for template variable <code>uri</code> to form <code>provenance-URI</code>.</li>
+ <li>Form a <code>provenance-URI</code> by using the provenance information template with <code>entity-URI</code> as a substitute
+ for template variable <code>uri</code>.</li>
<li>Dereference <code>provenance-URI</code> to obtain <a class="internalDFN">provenance information</a>.</li>
</ol>
</p>
@@ -509,7 +510,7 @@
<section>
<h2>Service description</h2>
<p>
- A provenance <dfn>service description</dfn> describes the provenance discovery and retrieval service and, in particular, provides URI templates [[URI-template]] for URIs to access <a title="provenance locations resource" class="internalDFN">provenance locations resources</a> and/or <a class="internalDFN">provenance information</a>. Dereferencing the service URI returns a representation of this service description. The service description MAY contain additional metadata about the service beyond that described here: API clients are expected to ignore any metadata elements they do not understand.
+ A provenance <dfn>service description</dfn> describes the provenance discovery and retrieval service and, in particular, provides URI templates [[URI-template]] for URIs to access <a title="provenance locations resource" class="internalDFN">provenance locations resources</a> and/or <a class="internalDFN">provenance information</a>. Dereferencing a service URI returns a representation of such a service description. The service description MAY contain additional metadata about the service beyond that described here: API clients are expected to ignore any metadata elements they do not understand.
</p>
<p>
This example shows a provenance service description using JSON format [[RFC4627]], which is presented as MIME content-type <code>application/json</code>.
@@ -533,7 +534,7 @@
A <dfn>provenance locations resource</dfn> enumerates one or more <a class="internalDFN">provenance-URI</a>s identifying <a class="internalDFN">provenance information</a> associated with a given resource.
</p>
<p>
- The examples below and in <a href="#provenance-service-format-examples" class="sectionRef"></a> are for a given resource URI <code>http://example.org/qdata/</code>, and using the service description example above, its URI would be <code>http://example.org/provenance_service/location/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
+ The examples below and in <a href="#provenance-service-format-examples" class="sectionRef"></a> are for a given resource URI <code>http://example.org/qdata/</code>, and the service description example above. Hence, the URI of the corresponding provenance locations resource would be <code>http://example.org/provenance_service/location/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
</p>
<p>
This example uses JSON format [[RFC4627]], presented as MIME content type <code>application/json</code>.
@@ -670,7 +671,7 @@
</section>
-<!-- ===================================================================================== -->
+<!-- == Sect 6 ===================================================================================== -->
<section>
<h2>Incremental Provenance Retrieval</h2>