--- a/paq/prov-aq.html	Thu Jan 05 12:08:44 2012 +0000
+++ b/paq/prov-aq.html	Thu Jan 05 12:22:51 2012 +0000
@@ -194,7 +194,7 @@
           Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resources</a>.  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).
         </p>
         <p>
-          Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities.  An <a class="internalDFN">entity</a> is simply a web resource that is a contextualized view or instance of an original web 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 then be <a class="internalDFN">entity-URIs</a>, 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.  Entity-URIs may use any URI scheme, and are not required to be dereferencable.
+          Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities.  An <a class="internalDFN">entity</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 an original 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 then be <a class="internalDFN">entity-URIs</a>, 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.  Entity-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 entity-URIs to refer to versions of that resource.  Some given provenance information may use multiple entity-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 entity-URIs of the various revisions.