--- a/paq/prov-aq.html	Tue Feb 26 10:24:22 2013 +0000
+++ b/paq/prov-aq.html	Tue Feb 26 10:44:26 2013 +0000
@@ -432,16 +432,15 @@
       </p>
       <p>
         When there is no easy way to associate a <a class="internalDFN">provenance-URI</a> with a resource (e.g. for resources not directly web-accessible, or whose publication mechanism is controlled by someone else), a provenance description may be obtained using a provenance query service at an indicated <a class="internalDFN">service-uri</a>.
-        A REST protocol for provenance queries is defined in Section <a href="#provenance-query-services" class="sectionRef"></a>; also described there is a mechanism for locating a SPARQL query service.
+        A REST protocol for provenance queries is defined in Section <a href="#provenance-query-services" class="sectionRef"></a>; also described there is a mechanism for locating a SPARQL query service [[SPARQL-SD]].
       </p>
       <p>
         When publishing provenance, corresponding <a class="internalDFN">provenance-URI</a>s or <a class="internalDFN">service-URI</a>s should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-records" class="sectionRef"></a>.
       </p>
-      <p>
-        Provenance may be presented as a <a href="/TR/prov-dm/#component4" class="externalRef">bundle</a>, which is "<cite>a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed</cite>" [[PROV-DM]].  There is no requirement that a bundle identifier can be dereferenced to access the corresponding provenance, but where practical it is RECOMMENDED that things are arranged to allow this.
-      </p>
       <p class="note">
-        One possible realization of a bundle is that it is published as part of an RDF Dataset [[RDF-CONCEPTS11]] or similar composite structure containing multiple RDF graphs in a single document. To access such a bundle would require accessing the RDF Dataset and then extracting the identified component; this in turn would require knowing a URI or some other way to retrieve the dataset.  This specification does not describe a specific mechanism for extracting components from a document containing multiple graphs.
+        Provenance may be presented as a <a href="/TR/prov-dm/#component4" class="externalRef">bundle</a>, which is "<cite>a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed</cite>" [[PROV-DM]].  A provenance description at a dereferencable provenance-URI may be treated as a bundle, and this is a good way to make provenance easily accessible. But there are other possible implementations of a bundle, such as a named graph in an RDF dataset [[RDF-CONCEPTS11]], for which the bundle URI may not be directly dereferencable.
+        <br/><br/>
+        When a bundle is published as part of an RDF Dataset, to access it would require accessing the RDF Dataset and then extracting the identified graph component; this in turn would require knowing a URI or some other way to retrieve the RDF dataset.  This specification does not describe a specific mechanism for extracting components from a document containing multiple graphs.
         <br/><br/>
         The W3C Linked Data Platform group (<a href="http://www.w3.org/2012/ldp/" class="externalRef">www.w3.org/2012/ldp/</a>) is chartered to produce a W3C Recommendation for HTTP-based (RESTful) application integration patterns using read/write Linked Data; we anticipate that they may address access to RDF Datasets in due course.
       </p>
@@ -686,7 +685,7 @@
     <section>
       <h2>Provenance query services</h2>
       <p>
-        This section describes a simple HTTP query protocol for accessing provenance records, and also a mechanism for locating a SPARQL service endpoint. The HTTP protocol specifies HTTP operations for retrieving provenance records from a provenance query service, following the approach of the SPARQL Graph Store HTTP Protocol [[SPARQL-HTTP]].
+        This section describes a simple HTTP query protocol for accessing provenance records, and also a mechanism for locating a SPARQL service endpoint [[SPARQL-SD]]. The HTTP protocol specifies HTTP operations for retrieving provenance records from a provenance query service, following the approach of the SPARQL Graph Store HTTP Protocol [[SPARQL-HTTP]].
       </p>
       <p>The introduction of query services is motivated by the following possible considerations: </p>
       <ul>