--- a/paq/prov-aq.html Thu Dec 01 12:58:03 2011 +0000
+++ b/paq/prov-aq.html Thu Dec 01 13:54:55 2011 +0000
@@ -178,7 +178,7 @@
<section>
<h2 id="provenance-context">Interpreting provenance information</h2>
- <p><a class="internalDFN">Provenance information</a> describes relationships between artifacts, process executions and agents. As such, any given provenance information may contain information about several <a title="Entity" class="internalDFN">entities</a>. Within some provenance information, the entities thus described are identified by their <a class="internalDFN">Entity-URI</a>s.
+ <p><a class="internalDFN">Provenance information</a> describes relationships between entities, activities and agents. As such, any given provenance information may contain information about several <a title="Entity" class="internalDFN">entities</a>. Within some provenance information, the entities thus described are identified by their <a class="internalDFN">Entity-URI</a>s.
</p>
<p>When interpreting provenance information, it is important to be aware that statements about several entities may be present, and to be accordingly selective when using the information provided. (In some exceptional cases, it may be that the provenance information returned does not contain any information relating to a specific associated entity.)
</p>
@@ -199,7 +199,7 @@
How much or how little provenance information is returned in response to to a retrieval request is a matter for the provenance provider application. At a minimum, for as long as provenance information about an entity remains available, sufficient should be returned to enable a client application to walk the provenance graph per <a class="sectionRef" href="#incremental-provenance-retrieval"></a>.
</p>
<p>
- When publishing provenance as a normal web resource, the <a class="internalDFN">provenance-URI</a> should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef"></a>.
+ When publishing provenance as a web resource, the <a class="internalDFN">provenance-URI</a> should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef"></a>.
</p>
<p>
If there is no URI for some particular provenance information, then alternative mechanisms may be needed. Possible mechanisms are suggested in <a href="#provenance-services" class="sectionRef"></a> and <a href="#querying-provenance-information" class="sectionRef"></a>.
@@ -222,8 +222,8 @@
We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN">provenance-URI</a> along with a <a class="internalDFN">entity-URI</a>. (Mechanisms that can be independent of the resource provision are discussed in <a href="#provenance-services" class="sectionRef"></a>). Three mechanisms are described here:
<ul>
<li>The requester knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
- <li>The requester has a copy of a resource presented as HTML or XHTML</li>
- <li>The requester has a copy of a resource presented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
+ <li>The requester has a copy of a resource represented as HTML or XHTML</li>
+ <li>The requester has a copy of a resource represented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
</ul>
These particular cases are selected as corresponding to primary current web protocol and data formats. Finally, in <a href="#arbitrary-data" class="sectionRef"></a>, we discuss the case of a resource in an unspecified format which has been provided by some means other than HTTP.
</p>
@@ -284,7 +284,7 @@
</section>
<section>
- <h2>Resource presented as HTML</h2>
+ <h2>Resource represented as HTML</h2>
<p class="pending">
Addresses <a href="http://www.w3.org/2011/prov/track/issues/46">ISSUE 46</a> by adding "anchor" link-relation.
</p>
@@ -360,9 +360,9 @@
</section>
<section>
- <h2>Resource presented as RDF</h2>
+ <h2>Resource represented as RDF</h2>
<p>
- If a resource is presented 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.
</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.
@@ -382,7 +382,7 @@
We have so far decided not to try and define a common mechanism for arbitrary data, because it's not clear to us what the correct choice would be. Is this a reasonable position, or is there a real need for a generic solution for provenance discovery for arbitrary, non-web-accessible data objects?
</p>
<p>
- If a resource is presented 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.
+ If a resource is represented using a data format other than HTML or RDF, and no URI for the resource is known, provenance discovery becomes trickier to achieve. This specification does not define a specific mechanism for such arbitrary resources, but this section discusses some of the options that might be considered.
</p>
<p>
For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a <a class="internalDFN">entity-URI</a>, <a class="internalDFN">provenance-URI</a> and/or <a class="internalDFN">service-URI</a>. Format-specific metadata provision might also be used to include <a class="internalDFN">provenance information</a> directly in the resource.
@@ -435,7 +435,7 @@
<section>
<h2>Using the provenance service API</h2>
<p>
- This section describes general procedures for using the provenance service API. Later sections describe the resources presented by the API, and their representations using JSON. <a href="#provenance-service-format-examples" class="sectionRef"></a>gives examples of alternative representations. Normal HTTP content negotiation mechanisms may be used to retrieve representations formats convenient for the client application.
+ This section describes general procedures for using the provenance service API. Later sections describe the resources presented by the API, and their representation using JSON. <a href="#provenance-service-format-examples" class="sectionRef"></a>gives examples of alternative representations. Normal HTTP content negotiation mechanisms may be used to retrieve representations using formats convenient for the client application.
</p>
<section>
@@ -484,9 +484,9 @@
<code>
<pre class="example">
{
- "provenance_service_uri": "http://example.info/provenance_service/",
- "provenance_locations_template": "http://example.info/provenance_service/locations/?uri={uri}",
- "provenance_content_template": "http://example.info/provenance_service/provenance/?uri={uri}"
+ "provenance_service_uri": "http://example.org/provenance_service/",
+ "provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
+ "provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
}
</pre>
</code>
@@ -501,7 +501,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.info/qdata/</code>, and using the service description example above, its URI would be <code>http://example.info/provenance_service/location/?uri=http%3A%2F%2Fexample.info%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 using the service description example above, its URI would be <code>http://example.org/provenance_service/location/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
</p>
<p>
This example uses JSON format [[RFC4627]], presented as MIME content type <code>application/json</code>.
@@ -510,10 +510,10 @@
<code>
<pre class="example">
{
- "uri": "http://example.info/qdata/",
+ "uri": "http://example.org/qdata/",
"provenance": [
- "http://source1.example.info/provenance/qdata/",
- "http://source2.example.info/prov/qdata/",
+ "http://source1.example.org/provenance/qdata/",
+ "http://source2.example.org/prov/qdata/",
"http://source3.example.com/prov?id=qdata"
]
}
@@ -530,8 +530,8 @@
Provenance information about a resource or resources may be returned in any format. It is recommended that the format be one defined by the Provenance Model specification [[PROV-DM]].
</p>
<p>
- Assuming a given resource URI <code>http://example.info/qdata/</code>, and
- using the service description example above, the provenance URI would be <code>http://example.info/provenance_service/provenance/?uri=http%3A%2F%2Fexample.info%2Fqdata%2F</code>.
+ Assuming a given resource URI <code>http://example.org/qdata/</code>, and
+ using the service description example above, the provenance URI would be <code>http://example.org/provenance_service/provenance/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
</p>
</section>
@@ -802,7 +802,7 @@
<section class='appendix'>
<h2>Provenance service format examples</h2>
<p>
- In <a href="#provenance-services" class="sectionRef"></a>, the provenance service description was presented 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 presented using RDF Turtle and XML sybntaxes, and XML.
+ 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>
@@ -813,9 +813,9 @@
<code>
<pre class="example">
@prefix provds: <http://www.w3.org/2011/provenance_discovery/@@TBD@@#> .
- <http://example.info/provenance_service/> a provds:Service_description ;
- provds:provenance_locations_template "http://example.info/provenance_service/locations/?uri={uri}" ;
- provds:provenance_content_template "http://example.info/provenance_service/provenance/?uri={uri}"
+ <http://example.org/provenance_service/> a provds:Service_description ;
+ provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
+ provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
.
</pre>
</code>
@@ -837,9 +837,9 @@
xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
xmlns:provds = "http://www.w3.org/2011/provenance_discovery/@@TBD@@#"
>
- <provds:Service_description rdf:about="http://example.info/provenance_service/">
- <provds:provenance_locations_template>http://example.info/provenance_service/locations/?uri={uri}</provds:location_template> ;
- <provds:provenance_content_template>http://example.info/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
+ <provds:Service_description rdf:about="http://example.org/provenance_service/">
+ example.org <provds:provenance_locations_template>http://example.org/provenance_service/locations/?uri={uri}</provds:location_template> ;
+ <provds:provenance_content_template>http://example.org/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
</provds:Service_description>
</rdf:RDF>
</pre>
@@ -864,9 +864,9 @@
<code>
<pre class="example">
@prefix prov: <http://www.w3.org/2011/provenance/@@TBD@@#> .
- <http://example.info/qdata/> a prov:Entity ;
- prov:hasProvenance <http://source1.example.info/provenance/qdata/> ;
- prov:hasProvenance <http://source2.example.info/prov/qdata/> ;
+ <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>
@@ -889,9 +889,9 @@
xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
xmlns:prov = "http://www.w3.org/2011/provenance/@@TBD@@#"
>
- <prov:Entity rdf:about="http://example.info/qdata/">
- <prov:hasProvenance rdf:resource="http://source1.example.info/provenance/qdata/" /> ;
- <prov:hasProvenance rdf:resource="http://source2.example.info/prov/qdata/" /> ;
+ <prov:Entity rdf:about="http://example.org/qdata/">
+ <prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source2.example.org/prov/qdata/" /> ;
<prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
</prov:Entity>
</rdf:RDF>