--- a/paq/provenance-access.html	Wed Nov 09 22:00:38 2011 -0500
+++ b/paq/provenance-access.html	Thu Nov 10 10:43:01 2011 +0000
@@ -171,15 +171,12 @@
     
     <section>
       <h2>Accessing provenance information</h2>
-      <p>
-        A general expectation is that web applications may access <a class="internalDFN">provenance information</a> in the same way as any web resource, by dereferencing its URI. Typically, this will be by performing an HTTP GET operation. Thus, any provenance information may be associated with a <a class="internalDFN">provenance-URI</a>, and may be accessed by dereferencing that URI using normal web mechanisms.
-      </p>
-      <p>
-        This specification thus recommends that if a publisher wishes to make <a class="internalDFN">provenance information</a> available, it is published as a normal web resource, and provision is made for the <a class="internalDFN">provenance-URI</a> to be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef"></a>.
-      </p>
-      <p>
-        This presumption of using web retrieval to access provenance information does not preclude use of other mechanisms.  In particular, alternative mechanisms may be needed if there is no URI associated with some particular provenance information.  Possible mechanisms are suggested in <a href="#provenance-services" class="sectionRef"></a> and <a href="#querying-provenance-information" class="sectionRef"></a>.
-      </p>
+        <p>Web applications may access <a class="internalDFN">provenance information</a> in the same way as any web resource, by dereferencing its URI. Typically, this will be by performing an HTTP GET operation. Thus, any provenance information may be associated with a <a class="internalDFN">provenance-URI</a>, and may be accessed by dereferencing that URI using normal web mechanisms.
+        </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>.
+        </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>.
+        </p>
     </section>
  
 <!-- == Sect 3 =================================================================================== -->