--- a/paq/prov-aq.html Thu Feb 21 15:07:09 2013 +0000
+++ b/paq/prov-aq.html Thu Feb 21 15:22:14 2013 +0000
@@ -331,7 +331,7 @@
<section>
<h2 id="provenance-entities-resources">Provenance and resources</h2>
<p>
- Fundamentally, a <a class="internalDFN">provenance record</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 records, to be useful, must be persistent and not themselves 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).
+ Fundamentally, a <a class="internalDFN">provenance record</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 records, to be useful, must be persistent and must not themselves be 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 records for 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 specialization 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">entity-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. Entity-URIs may use any URI scheme, and are not required to be dereferencable.
@@ -381,12 +381,12 @@
</tr>
<tr style="vertical-align: top;">
<td><a class="internalDFN">Provenance-URI</a></td>
- <td>A provenance record in the sense described by [[PROV-DM]] (<a href="http://www.w3.org/TR/prov-dm/#section-prov-overview" class="externalRef">PROV Overview</a>).</td>
+ <td>A provenance record, or provenance description, in the sense described by [[PROV-DM]] (<a href="http://www.w3.org/TR/prov-dm/#section-prov-overview" class="externalRef">PROV Overview</a>).</td>
<td>A provenance record in any defined format, selectable via content negotiation.</td>
</tr>
<tr style="vertical-align: top;">
<td><a class="internalDFN">Service-URI</a></td>
- <td>A provenance query service (i.e. a resource of type <code>prov:ProvenanceQueryService</code>). This is the initial URI used when accessing a provenance query service; following REST API style [[REST-APIs]], URIs for accessing provenance are determined via the query service description.</td>
+ <td>A provenance query service. The service-URI is the initial URI used when accessing a provenance query service; following REST API style [[REST-APIs]], URIs for accessing provenance are determined via the service description.</td>
<td>A provenance query service description per <a href="#provenance-query-service-description" class="sectionRef"></a>. Alternative formats may be offered via HTTP content negotiation.</td>
</tr>
<tr style="vertical-align: top;">