--- a/paq/working/prov-aq.html	Fri Mar 30 13:43:45 2012 +0100
+++ b/paq/working/prov-aq.html	Fri Mar 30 16:03:20 2012 +0200
@@ -482,10 +482,10 @@
         <h2>HTTP GET</h2>
         <p>This protocol combines the <a class="internalDFN">resource-URI</a> with the <a class="internalDFN">service-URI</a> to formulate an HTTP GET request, according to the following convention:
           <pre class="pattern">
-  GET /provenance/service?<b>provenance-element</b>=http://www.example.com/entity HTTP/1.1
+  GET /provenance/service?<b>provenance-resource</b>=http://www.example.com/entity HTTP/1.1
   Host: example.com</pre>
         </p>
-        <p>The embedded resource-URI (<code>http://www.example.com/entity</code>) identifies the resource for which provenance information is to be returned. Any server that implements this protocol and receives a request URI in this form SHOULD return provenance information for the resource-URI embedded in the query component where that URI is the result of percent-decoding the value associated with the provenance-element key. The embedded URI MUST be an absolute URI and the server MUST respond with a 400 Bad Request if it is not.  If the supplied resource-URI includes a fragment identifier, the '#' MUST be %-encoded as <code>%23</code> when constructing the provenance-URI value; similarly, any '&amp;' character in the resource-URI must be %-encoded as <code>%26</code>.
+        <p>The embedded resource-URI (<code>http://www.example.com/entity</code>) identifies the resource for which provenance information is to be returned. Any server that implements this protocol and receives a request URI in this form SHOULD return provenance information for the resource-URI embedded in the query component where that URI is the result of percent-decoding the value associated with the provenance-resource key. The embedded URI MUST be an absolute URI and the server MUST respond with a 400 Bad Request if it is not.  If the supplied resource-URI includes a fragment identifier, the '#' MUST be %-encoded as <code>%23</code> when constructing the provenance-URI value; similarly, any '&amp;' character in the resource-URI must be %-encoded as <code>%26</code>.
         </p>
         <p>If the provenance information identified in the request does not exist in the server, a 404 Not Found response code SHOULD be returned.
         </p>
@@ -508,13 +508,13 @@
       <!-- <section class="informative"> -->
       <section>
         <h2>Provenance service description</h2>
-        <p>The provenance service interface as described above violates REST constraints by requiring the client to know about the structure of URIs offered by the service (see [[REST-APIs]], 4th bullet point).  The provenance service description mitigates this coupling by providing a mechanism for discovering the URI format to be used, starting with just the service URI.
-        </p>
+        <!--<p>The provenance service interface as described above violates REST constraints by requiring the client to know about the structure of URIs offered by the service (see [[REST-APIs]], 4th bullet point).  The provenance service description mitigates this coupling by providing a mechanism for discovering the URI format to be used, starting with just the service URI.
+        %</p> -->
         <p>Dereferencing a provenance service URI should yield a provenance service description.  The provenance service description should be available as RDF (in any of its common serializations, and determined through HTTP content negotiation), and it should contain RDF statements of the form:
         </p>
         <pre class="pattern">
   &lt;<cite>service-URI</cite>&gt; a prov:ProvenanceService ;
-    prov:provenanceUriTemplate "<cite>service-URI</cite>?provenance-element={+uri}" .</pre>
+    prov:provenanceUriTemplate "<cite>service-URI</cite>?provenance-resource={+uri}" .</pre>
         <p>where <cite><code>service-URI</code></cite> is the URI of the provenance service.  Note that the object of the <code>prov:provenanceUriTemplate</code> statement is a literal text value, not a URI.
         </p>
         <p>A client may retrieve this service description and extract the associated value for <code>prov:provenance-uri-template</code>.  This value is a string containing a URI template [[URI-template]] (level 2). A URI for the desired provenance information is obtained by expanding the URI template with the variable <code>uri</code> set to the resource-URI for which provenance is required.  If the resource-URI contains '#' or '&amp;' these  must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion.