--- a/paq/provenance-access.html	Thu Jul 21 15:33:24 2011 +0100
+++ b/paq/provenance-access.html	Thu Jul 21 15:34:06 2011 +0100
@@ -41,7 +41,7 @@
           // previousMaturity:  "WD",
 
           // if there a publicly available Editor's Draft, this is the link
-          //edDraftURI:           "http://dev.w3.org/2009/dap/ReSpec.js/documentation.html",
+          edDraftURI:           "http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html",
 
           // if this is a LCWD, uncomment and set the end of its review period
           // lcEnd: "2009-08-05",
@@ -54,7 +54,7 @@
           // only "name" is required
           editors:  [
               { name: "Graham Klyne", url: "",
-                company: "University of Oxford", companyURL: "" },
+                company: "University of Oxford", companyURL: "http://www.ox.ac.uk/" },
           ],
 
           // authors, add as many as you like. 
@@ -133,20 +133,23 @@
         <section>
           <h2>Resource accessed by HTTP</h2>
           <p>
-            For a document accessible using HTTP, [[POWDER-DR]] describes <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink">a mechanism</a> for associating metadata with a resource by adding an HTTP <code>Link</code> header field to the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).  Since the POWDER specification was published, the HTTP linking draft has been approved by the IETF as [[LINK-REL]] (<a href="http://tools.ietf.org/html/rfc5988">http://tools.ietf.org/html/rfc5988</a>).
+            For a document accessible using HTTP, [[POWDER-DR]] describes <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink">a mechanism</a> for associating metadata with a resource by adding an HTTP <code>Link</code> header field to the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).  Since the POWDER specification was published, the HTTP linking draft has been approved by the IETF as <a href="http://tools.ietf.org/html/rfc5988">RFC 5988</a>  [[LINK-REL]].
           </p>
           <p>
-            The same basic mechanism can be used for referencing provence data, for which a new link relation type is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a> :
+            The same basic mechanism can be used for referencing provence data, for which a new link relation type is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>:
             <code>
               <pre class="example">
                 Link: <cite>provenance-URI</cite>; rel="provenance"
               </pre>
             </code>
-            When used in conjunction with an HTTP success response code (2xx ), this HTTP header indicates that <code><cite>provenance-URI</cite></code> is the URI of a provenance resource for which information is returned.  At this time, the meaning of provenance links returned with other HTTP response codes is not defined: future revisions of this specification may define interpretations for these.
+            When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header indicates that <code><cite>provenance-URI</cite></code> is the URI of a provenance resource for which information is returned.  At this time, the meaning of provenance links returned with other HTTP response codes is not defined: future revisions of this specification may define interpretations for these.
           </p>
           <p>
             An HTTP response MAY include multiple provenance link headers, indicating a number of different resources that are known to the responding server, each providing provenance about the accessed resource.
           </p>
+          <p>
+            The presence of a provenance link in an HTTP response does not preclude the possibility that other publishers may offer provenance information about the same resource.  In such cases, discovery of the additional provenance information must use other means (e.g. see <a href="#third-party-services" class="sectionRef"></a>).
+          </p>
 
           <section>
             <h2>Open issues</h2>
@@ -163,7 +166,7 @@
             For a document presented as HTML or XHTML, without regard for how it has been obtained, [[POWDER-DR]] describes <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#assoc-markup">a mechanism</a> for associating metadata with a resource by adding a <code>&lt;Link&gt;</code> element to the HTML <code>&lt;head&gt;</code> section.
           </p>
           <p>
-            The same basic mechanism can be used for referencing provence data, for which a new link relation type is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a> @@CHECK USE OF LINK RELATION REGISTRY IS OK HERE@@:
+            The same basic mechanism can be used for referencing provence data, for which a new link relation type is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>:
             <code>
               <pre class="example">
                 &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;