--- a/paq/provenance-access.html	Thu Jul 28 11:12:30 2011 +0100
+++ b/paq/provenance-access.html	Thu Jul 28 13:42:51 2011 +0100
@@ -191,6 +191,9 @@
           <p>
             See in particular <a href="http://tools.ietf.org/html/rfc5988#appendix-A">Appendix A.  Notes on Using the Link Header with the HTML4 Format</a> of RFC5988 for further notes about using link relation types in HTML.
           </p>
+          <p class="note">
+             An alternative option would be to use an HTML <code>&lt;meta&gt;</code> element to present provenance links.  The <code>&lt;Link&gt;</code> is preferred as it reflects more closely the intended goal, and has been defined with somewhat consistent applicability across HTTP, HTML and potentially RDF data.  A specification to use <code>&lt;meta&gt;</code> for this would miss this opportunity to build on the existing specification and registry.
+          </p>
           <section>
             <h2>Open issues</h2>
             <p>
@@ -221,10 +224,10 @@
         <section>
           <h2>Third party services</h2>
           <p>
-            The mechanisms for provenance discovery described above have all assumed the provenance URI is being supplied by the provider of the original resource.  Where provenance information is provided by a third party without any collaboration from the original resource provider, the provenance link cannot be provided directly and a different approach must be considered.
+            The mechanisms for provenance discovery described above have all assumed the provenance URI is being supplied by the provider of the original resource.  Where provenance information is provided by a third party without any cooperation from the original resource provider, the provenance link cannot be provided through the same channels as the original resource, and a different approach must be considered.
           </p>
           <p>
-            We assume that the application or person requesting provenance information has the URI or other unique identification of the resource for which provenance is required, and also has a URI for a third-party service that provides a provenance information service.  Specifically, the third party service URI is the URI of a SPARQL endpoint which is queried for the desired provenance information.
+            We assume that the application or person requesting provenance information has the URI or other unique identification of the resource for which provenance is required, and also has a URI for a third-party service that provides a provenance information service.  The nature of this third party service is an implementation choice, to be agreed between provider and users of the service, but for ease of interoperation we recommend use of SPARQL [[RDF-SPARQL-PROTOCOL]] [[RDF-SPARQL-QUERY]].  The third party service URI would then be the URI of a SPARQL endpoint  (or, to use the SPARQL specification language, a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>) which is queried for the desired provenance information.
           </p>
           <p>
             If the requester has a URI for the original resource, they simple issue a simple SPARQL query for the URI(s) of any associated provenance data; e.g., if the original resource has URI <code>http://example.org/resource</code>, 
@@ -238,6 +241,9 @@
               </pre>
             </code>
           </p>
+          <p class="issue">
+            @@TODO: specific provenance property to be determined by the model specification?
+          </p>
           <p>
             If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate the target resource and obtain its provenance URI(s).  The nature of identifying information that can be used in this way will depend upon the third party service used,  further definition of which is out of scope for this specification.  For example, a query for a document identified by a DOI, say <code>1234.5678</code>, might look like this:
             <code>
@@ -260,8 +266,8 @@
     
     <section>
       <h2>Querying provenance data</h2>
-      <p>
-        (This section will describe the use of a SPARQL endpoint serice to obtain provenance information directly from a service provider.  No new protocol or vocabulary elements are defined: the mechanisms are used are thosed described above, coupled with possible use of provenance vocabulary terms in a SPARQL query.)
+      <p class="issue">
+        This section will build upon the previous section, describing the use of a SPARQL endpoint service to obtain provenance information directly from a service provider.  No new protocol or vocabulary elements are defined: the mechanisms are used are those described above, coupled with possible use of provenance vocabulary terms in a SPARQL query.
       </p>
       <p>
         @@TODO