prov-n prep for CR
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 19 Nov 2012 14:07:54 +0000
changeset 4800 e6bbdbe46b1d
parent 4799 264a2dcf69cb (current diff)
parent 4798 2d78a4857f76 (diff)
child 4801 35cc1da2a4c9
prov-n prep for CR
--- a/paq/css/prov-aq.css	Mon Nov 19 14:07:41 2012 +0000
+++ b/paq/css/prov-aq.css	Mon Nov 19 14:07:54 2012 +0000
@@ -4,8 +4,20 @@
     color:  #224433;
 }
 
+    /* Be more specific: above override doesn't work */
+p code {
+    font-family: monospace;
+    color:  #224433;
+}
+
+div code {
+    font-family: monospace;
+    color:  #224433;
+}
+
 
 /* --- PATTERNS --- */
+
 pre.pattern {
     border-top: 1px solid #224433;
     border-bottom: 1px solid #224433;
@@ -18,6 +30,17 @@
     color:  #224433;
 }
 
+pre.example.code {
+    border-bottom: 1px solid #224433;
+    border-top: 1px solid #224433;
+    margin-top: 1em;
+    padding: 1em;
+}
+
+pre.example.code:before {
+    background: #224433;
+}
+
 /*
 pre.pattern::before {
     content:    "";
@@ -163,3 +186,9 @@
     font-family: monospace;
 }
 
+/* External link. CSS and image data copied from wikimedia.org.  Thanks! */
+a.externalRef {
+background:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAVklEQVR4Xn3PgQkAMQhDUXfqTu7kTtkpd5RA8AInfArtQ2iRXFWT2QedAfttj2FsPIOE1eCOlEuoWWjgzYaB/IkeGOrxXhqB+uA9Bfcm0lAZuh+YIeAD+cAqSz4kCMUAAAAASUVORK5CYII=) center right no-repeat;
+background:url(images/external-link-ltr-icon.png) center right no-repeat!ie;padding-right:13px
+}
+
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/images/README.txt	Mon Nov 19 14:07:54 2012 +0000
@@ -0,0 +1,4 @@
+External link icon copied from Wikipedia http://bits.wikimedia.org/static-1.21wmf3/skins/vector/images/external-link-ltr-icon.png
+
+Re-used with assumed permission per http://wikimediafoundation.org/wiki/Terms_of_use
+
Binary file paq/images/external-link-ltr-icon.png has changed
--- a/paq/prov-aq.html	Mon Nov 19 14:07:41 2012 +0000
+++ b/paq/prov-aq.html	Mon Nov 19 14:07:54 2012 +0000
@@ -95,7 +95,7 @@
           // subtitle   :  "an excellent document",
 
           // if you wish the publication date to be other than today, set this
-        // publishDate:  "2012-06-19",
+          // publishDate:  "2012-06-19",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -240,31 +240,29 @@
             More advanced discovery service and query mechanisms that may be used for more demanding deployments are described in <a href="#provenance-services" class="sectionRef"></a>, <a href="#querying-provenance-information" class="sectionRef"></a> and <a href="#incremental-provenance-retrieval" class="sectionRef"></a>.
           </li>
         </ul>
-     
-      
+      <p>
+        For ease of reference, the main body of this document contains some links to external web pages.  Such links are distinguished from internal references thus: <a href="http://www.w3.org/2011/prov/wiki/Main_Page" class="externalRef">W3C Provenance Working Group</a>
+      </p>
+
       <section>
         <h2>Concepts</h2>
        
-          <p>In defining the specification below, we make use of the following concepts. </p>
+          <p>In defining the specification below, we make use of the following concepts.</p>
           <dl>
-            <dt><dfn>Resource</dfn></dt>
-            <dd>a resource in the general sense of "whatever might be identified by a URI", as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
-            <dt><dfn>Constrained resource</dfn></dt>
-            <dd>an aspect, version or instance of a <a class="internalDFN">resource</a>, about which one may wish to present some <a class="internalDFN">provenance information</a>. For example, a weather report for a given date may be an aspect of a resource that is maintained as the current weather report. A constrained resource is itself a <a class="internalDFN">resource</a>, and may have it's own URI different from that of the original.  See also [[PROV-DM]], and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
-            <dt><dfn>Target-URI</dfn></dt>
+            <a href="#dfn-resource"><dt><dfn>Resource</dfn></dt></a>
+            <dd>a resource in the general sense of "whatever might be identified by a URI", as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
+            <a href="#dfn-constrained-resource"><dt><dfn>Constrained resource</dfn></dt></a>
+            <dd>an aspect, version or instance of a <a class="internalDFN">resource</a>, about which one may wish to present some <a class="internalDFN">provenance information</a>. For example, a weather report for a given date may be an aspect of a resource that is maintained as the current weather report. A constrained resource is itself a <a class="internalDFN">resource</a>, and may have it's own URI different from that of the original.  See also [[PROV-DM]], and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse" class="externalRef">section 2.3.2</a>.</dd>
+            <a href="#dfn-target-uri"><dt><dfn>Target-URI</dfn></dt></a>
             <dd>a URI denoting a <a class="internalDFN">resource</a> (including any <a class="internalDFN">constrained resource</a>), which identifies that resource for the purpose of finding and expressing <a class="internalDFN">provenance information</a> associated with it (see <a href="#provenance-entities-resources" class="sectionRef"></a> for discussion)</dd>
-            <dt><dfn>Provenance information</dfn></dt>
+            <a href="#dfn-provenance-information"><dt><dfn>Provenance information</dfn></dt></a>
             <dd>refers to provenance represented in some fashion.</dd>
-            <dt><dfn>Provenance-URI</dfn></dt>
+            <a href="#dfn-provenance-uri"><dt><dfn>Provenance-URI</dfn></dt></a>
             <dd>a URI denoting some <a class="internalDFN">provenance information</a>.</dd>
-            <dt><dfn>Provenance service</dfn></dt>
+            <a href="#dfn-provenance-service"><dt><dfn>Provenance service</dfn></dt></a>
             <dd>a service that provides <a class="internalDFN">provenance information</a> given a <a class="internalDFN">target-URI</a>.</dd>
-            <dt><dfn>Service-URI</dfn></dt>
+            <a href="#dfn-service-uri"><dt><dfn>Service-URI</dfn></dt></a>
             <dd>the URI of a <a class="internalDFN">provenance service</a>.</dd>
-<!--
-            <dt><dfn>Resource</dfn></dt>
-            <dd>also referred to as <dfn>resource on the Web</dfn>: a resource as described by the Architecture of the World Wide Web [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple instances or views (<a class="internalDFN">constrained resource</a>s) with differing provenance.</dd>
--->
           </dl>
 
       </section>
@@ -275,7 +273,7 @@
           Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resource</a>s.  In general, resources may vary over time and context.  E.g., a resource describing the weather in London changes from day-to-day, or a listing of restaurants near you will vary depending on your location.  Provenance information, to be useful, must be persistent and not itself dependent on context.  Yet we may still want to make provenance assertions about dynamic or context-dependent resources (e.g. a weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
         </p>
         <p>
-          Provenance descriptions of dynamic and context-dependent resources are possible through a notion of constrained resources.  A <a class="internalDFN">constrained resource</a> is simply a resource (in the sense defined by [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>) that is a contextualized view or instance of some other resource.  For example, a W3C specification typically undergoes several public revisions before it is finalized.  A URI that refers to the "current" revision might be thought of as denoting the specification throughout its lifetime.  Each individual revision would also have its own <a class="internalDFN">target-URI</a> denoting the specification at that particular stage in its development.  Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor.  Target-URIs may use any URI scheme, and are not required to be dereferencable.
+          Provenance descriptions of dynamic and context-dependent resources are possible through a notion of constrained resources.  A <a class="internalDFN">constrained resource</a> is simply a resource (in the sense defined by [[WEBARCH]], <a href="http://www.w3.org/TR/webarch/#id-resources" class="externalRef">section 2.2</a>) that is a contextualized view or instance of some other resource.  For example, a W3C specification typically undergoes several public revisions before it is finalized.  A URI that refers to the "current" revision might be thought of as denoting the specification throughout its lifetime.  Each individual revision would also have its own <a class="internalDFN">target-URI</a> denoting the specification at that particular stage in its development.  Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor.  Target-URIs may use any URI scheme, and are not required to be dereferencable.
         </p>
         <p>
            Requests for provenance about a resource may return provenance information that uses one or more target-URIs to refer to versions of that resource.  Some given provenance information may use multiple target-URIs if there are assertions referring to the same underlying resource in different contexts.  For example, provenance information describing a W3C document might include information about all revisions of the document using statements that use the different target-URIs of the various revisions.
@@ -358,32 +356,33 @@
         These particular cases are selected as corresponding to primary current web protocol and data formats.  Similar approaches  may be possible for other protocols or resource formats.  Finally, in <a href="#arbitrary-data" class="sectionRef"></a>, we discuss the case of a resource in an unspecified format which has been provided by some means other than HTTP.
       </p>
       <p>
-        The mechanisms described here are intended to allow a provider to supply information that may assist a client in finding related provenance information.  While a provider should avoid giving spurious information, there are no fixed semantics, particularly when multiple resources are indicated, and a client should not assume that a specific given provenance-uri will yield information about a specific given target-uri.  In the general case, a client presented with multiple provenance-uris and multiple target-uris should look at all of the provenance-uris for information about any or all of the target-uris.
+        The mechanisms described here are intended to allow a provider to supply information that may assist a client in finding related provenance information, and the provenance information itself should explicitly identify the target resources it describes.  While a provider should avoid giving spurious information, there are no fixed semantics, particularly when multiple resources are indicated, and a client should not assume that a specific given provenance-uri will yield information about a specific given target-uri.  In the general case, a client presented with multiple provenance-uris and multiple target-uris should look at all of the provenance-uris for information about any or all of the target-uris.
       </p>
       <p>
-        The mechanisms specified for use with HTTP and HTML are similar to those proposed by POWDER [[POWDER-DR]] (sections <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#assoc-markup">4.1.1</a> and <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink">4.1.3</a>).
+        The mechanisms specified for use with HTTP and HTML are similar to those proposed by POWDER [[POWDER-DR]] (sections <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#assoc-markup" class="externalRef">4.1.1</a> and <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink" class="externalRef">4.1.3</a>).
       </p>
 
       <section>
         <h2>Resource accessed by HTTP</h2>
-        <p class="TODO">
-          @@TODO: Use URIs for link relations (?)
+        <p>
+          For a resource accessible using HTTP, provenance information may be indicated using an HTTP <code>Link</code> header field, as defined by <a href="http://tools.ietf.org/html/rfc5988" class="externalRef">Web Linking (RFC 5988)</a> [[LINK-REL]].  The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
         </p>
         <p>
-          For a resource accessible using HTTP, provenance information may be indicated using an HTTP <code>Link</code> header field, as defined by <a href="http://tools.ietf.org/html/rfc5988">Web Linking (RFC 5988)</a> [[LINK-REL]].  The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
+          A <code>hasProvenance</code> link relation type for referencing provenance information may be used as shown:
         </p>
-A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>, and may be used as shown:  <pre class="pattern">Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>target-URI</cite>"</pre> When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated resource is identified within the referenced provenance information as <code><cite>target-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
+        <pre class="pattern">Link: <cite>provenance-URI</cite>; rel="http://www.w3.org/ns/prov#hasProvenance"; anchor="<cite>target-URI</cite>"</pre>
+        <p>When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated resource is identified within the referenced provenance information as <code><cite>target-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)</p>
         <p>
-        If no <code>anchor</code> parameter is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the resource, used in the corresponding HTTP request.
+          If no <code>anchor</code> parameter is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the resource, used in the corresponding HTTP request.
         </p>
         <p>
-          At this time, the meaning of these links returned with other HTTP response codes is not defined: future revisions of this specification may define interpretations for these.
+          This specification does not define the meaning of these links returned with other HTTP response codes: future revisions may define interpretations for these.
         </p>
         <p>
-          An HTTP response MAY include multiple <code>provenance</code> link header fields, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource.
+          An HTTP response MAY include multiple <code>hasProvenance</code> link header fields, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource.
         </p>
         <p>
-          The presence of a <code>provenance</code> 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="#provenance-services" class="sectionRef"></a>).
+          The presence of a <code>hasProvenance</code> 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="#provenance-services" class="sectionRef"></a>).
         </p>
         <p>
           Provenance resources indicated in this way are not guaranteed to be authoritative.  Trust in the linked provenance information must be determined separately from trust in the original resource. Just as in the web at large, it is a user's responsibility to determine an appropriate level of trust in any other linked resource; e.g. based on the domain that serves it, or an associated digital signature. (See also <a href="#security-considerations" class="sectionRef"></a>.)
@@ -391,34 +390,70 @@
 
         <section>
           <h2>Specifying Provenance Services</h2>
-            <p>
-              The resource provider may indicate that provenance information about the resource is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
-            </p>
-            <pre class="pattern">
-Link: <cite>provenance-service-URI</cite>; anchor="<cite>target-URI</cite>"; rel="provenance-service"</pre>
-            <p>
-              The <code>provenance-service</code> link identifies the <a class="internalDFN">service-URI</a>.  Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for a <a class="internalDFN">resource</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
-            </p>
-            <p>
-            There may be multiple <code>provenance-service</code> link header fields, and these may appear in an HTTP response together with <code>provenance</code> link header fields (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
+          <p>
+            The resource provider may indicate that provenance information about the resource is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a <code>hasProvenanceService</code> link relation type following the same pattern as above:
           </p>
+          <pre class="pattern">
+Link: <cite>provenance-service-URI</cite>; rel="http://www.w3.org/ns/prov#hasProvenanceService"; anchor="<cite>target-URI</cite>"</pre>
+          <p>
+            The <code>hasProvenanceService</code> link identifies the <a class="internalDFN">service-URI</a>.  Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for a <a class="internalDFN">resource</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+          </p>
+          <p>
+          There may be multiple <code>hasProvenanceService</code> link header fields, and these may appear in an HTTP response together with <code>hasProvenance</code> link header fields (though, in simple cases, we anticipate that <code>hasProvenance</code> and <code>hasProvenanceService</code> link relations will not be used together).
+        </p>
+        </section>
+
+        <section>
+          <h2>Content negotiation, redirection and Link: headers</h2>
+          <p>
+            When performing content negotiation for a resource, it is common for HTTP 302 or 303 redirect response codes to be used to direct a client to an appropriately-formatted resource.  When accessing a resource for which provenance information is available, link headers SHOULD be included with the response to the final redirected request, and not on the intermediate 303 responses.  (When accessing a resource from a browser using Javascript, the intermediate 303 responses are usually handled transparently by the browser and are not visible to the HTTP client code.) 
+          </p>
+          <p>
+            Following content negotiation, any link to provenance information returned refers to the resource whose URI is used in the corresponding HTTP request, or the given anchor parameter if that is different. (The provenance information itself may also refer to other resources; see the discussion at the start of <a href="#locating-provenance-information" class="sectionRef"></a>.)
+          </p>
+          <p>
+            An example transaction using content negotiation and redirection might look like this (where <code>C:</code> and <code>S:</code> prefixes indicate client and server emitted data respectively):
+          </p>
+          <pre class="pattern">
+  C: GET /resource/
+  C: Host: http://example.com/
+  C: Accept: text/html
+
+  S: 302 Found
+  S: Location: /resource/content.html
+  S: Vary: Accept
+  S:
+  S: HTML content for http://example.com/resource/ 
+  S: is available at http://example.com/resource/content.html
+
+  C: GET /resource/content.rdf
+  C: Host: http://example.com/
+  C: Accept: text/html
+
+  S: 200 OK
+  S: Content-type: text/html
+  S: Vary: Accept
+  S: Link: &lt;http://example.com/resource/provenance/&gt;; 
+           rel="http://www.w3.org/ns/prov#hasProvenance"; 
+           anchor="http://example.com/resource/"
+  S:
+  S: &lt;html ...&gt;
+  S:  :
+  S: &lt;/html&gt;</pre>
         </section>
 
       </section>
 
       <section>
         <h2>Resource represented as HTML</h2>
-        <p class="TODO">
-          @@TODO: Use URIs for link relations (?)
-        </p>
         <div>
           For a document presented as HTML or XHTML, without regard for how it has been obtained, provenance information may be associated with a resource by adding a <code>&lt;link&gt;</code> element to the HTML <code>&lt;head&gt;</code> section.
-          Two new link relation types for referencing provenance information are registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>, and may be used as shown:
+          Two link relation types for referencing provenance information may be used as shown:
           <pre class="pattern">
   &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
-        &lt;link rel="provenance" href="<cite>provenance-URI</cite>"&gt;
-        &lt;link rel="anchor" href="<cite>target-URI</cite>"&gt;
+        &lt;link rel="http://www.w3.org/ns/prov#hasProvenance" href="<cite>provenance-URI</cite>"&gt;
+        &lt;link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>target-URI</cite>"&gt;
         &lt;title&gt;Welcome to example.com&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
@@ -427,21 +462,16 @@
   &lt;/html&gt;</pre>
    </div>
         <p>
-          The <code><cite>provenance-URI</cite></code> given by the <code>provenance</code> link element identifies the provenance-URI for the document.
-        </p>
-        <p>
-          The <code><cite>target-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the document that may be used within the provenance information when referring to the document.
+          The <code><cite>provenance-URI</cite></code> given by the <code>hasProvenance</code> link element identifies the provenance-URI for the document.
         </p>
         <p>
-          An HTML document header MAY include multiple <code>provenance</code> link elements, indicating a number of different provenance sources that are known to the creator of the document, each of which may provide provenance information about the document. 
+          The <code><cite>target-URI</cite></code> given by the <code>hasAnchor</code> link element specifies an identifier for the document that may be used within the provenance information when referring to the document.
         </p>
-<!--
         <p>
-          Likewise, the header MAY include multiple "anchor" link elements indicating that, e.g., different revisions of the document can be identified in the provenance information using the different  <code><cite>resource-URIs</cite></code>.
+          An HTML document header MAY include multiple <code>hasProvenance</code> link elements, indicating a number of different provenance sources that are known to the creator of the document, each of which may provide provenance information about the document. 
         </p>
--->
         <p>
-          If no "anchor" link element is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this convention be used only when the document is static and has a stable URI that is reasonably expected to be available to anyone accessing the document (e.g. when delivered from a web server, or as part of a MIME structure containing content identifiers [[RFC2392]]).
+          If no <code>hasAnchor</code> link element is provided then the <code><cite>target-URI</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this convention be used only when the document is static and has a stable URI that is reasonably expected to be available to anyone accessing the document (e.g. when delivered from a web server, or as part of a MIME structure containing content identifiers [[RFC2392]]).
         </p>
 
         <section>
@@ -452,8 +482,8 @@
             <pre class="pattern">
   &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
-        &lt;link rel="provenance-service" href="<cite>service-URI</cite>"&gt;
-        &lt;link rel="anchor" href="<cite>target-URI</cite>"&gt;
+        &lt;link rel="http://www.w3.org/ns/prov#hasProvenanceService" href="<cite>service-URI</cite>"&gt;
+        &lt;link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>target-URI</cite>"&gt;
         &lt;title&gt;Welcome to example.com&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
@@ -461,10 +491,10 @@
      &lt;/body&gt;
   &lt;/html&gt;</pre>
           <p>
-            The <code>provenance-service</code> link element identifies the <a class="internalDFN">service-URI</a>.  Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN">provenance information</a> for a <a class="internalDFN">resource</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+            The <code>hasProvenanceService</code> link element identifies the <a class="internalDFN">service-URI</a>.  Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN">provenance information</a> for a <a class="internalDFN">resource</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
           </p>
           <p>
-            There MAY be multiple <code>provenance-service</code> link elements, and these MAY appear in the same document as <code>provenance</code> link elements (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations would not be used together).
+            There MAY be multiple <code>hasProvenanceService</code> link elements, and these MAY appear in the same document as <code>provenance</code> link elements (though, in simple cases, we anticipate that <code>hasProvenance</code> and <code>hasProvenanceService</code> link relations would not be used together).
           </p>
         </section>
       </section>
@@ -472,18 +502,18 @@
       <section>
         <h2>Resource represented as RDF</h2>
         <p>
-          If a resource is represented as RDF (in any of its recognized syntaxes, including RDFa), it may contain references to its own provenance using additional RDF statements.  For this purpose three new RDF properties, <code>prov:hasProvenance</code>, <code>prov:hasAnchor</code>, and <code>prov:hasProvenanceService</code>, are defined as follows.
-          (These terms may be used to indicate provenance of other resources too, but discussion of such usage is beyond the scope of this section.)
+          If a resource is represented as RDF (in any of its recognized syntaxes, including RDFa), it may contain references to its own provenance using additional RDF statements.  For this purpose the link relations introduced above may be used as RDF properties: <code>prov:hasProvenance</code>, <code>prov:hasAnchor</code>, and <code>prov:hasProvenanceService</code>.
+          (These terms may be used to indicate provenance of arbitrary other resources too, but discussion of such usage is beyond the scope of this section.)
         </p>
         <p>
-          The RDF property <code>prov:hasProvenance</code> is defined as a relation between two resources, where the object of the property is a resource that provides provenance information about the subject resource.  Multiple <code>prov:hasProvenance</code> assertions may be made about a subject resource.  This property corresponds to a <a href="#registration-template-for-link-relation---provenance">provenance link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code>&lt;link&gt;</code> element.
+          The RDF property <code>prov:hasProvenance</code> is a relation between two resources, where the object of the property is a resource that provides provenance information about the subject resource.  Multiple <code>prov:hasProvenance</code> assertions may be made about a subject resource.  This property corresponds to a <code>hasProvenance</code> e link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code>&lt;link&gt;</code> element (see above).
         </p>
         <p>
-          Property <code>prov:hasAnchor</code> specifies a <a class="internalDFN">target-URI</a> used in the provenance information to refer to the containing RDF document.
-          This corresponds to use of the <code>anchor</code> parameter in an HTTP provenance <code>Link</code> header field, or an <a href="#registration-template-for-link-relation---anchor">anchor link relation</a> in an HTML <code>&lt;link&gt;</code> element, which similarly indicate a URI used by the provenance information to refer to the described document.
+          Property <code>prov:hasAnchor</code> specifies a <a class="internalDFN">target-URI</a> used in the indicated provenance information to refer to the containing RDF document.
+          This corresponds to use of the <code>anchor</code> parameter in an HTTP provenance <code>Link</code> header field, or a <code>hasAnchor</code> link relation</a> in an HTML <code>&lt;link&gt;</code> element, which similarly indicate a URI used by the provenance information to refer to the described document.
         </p>
         <p>
-          Property <code>prov:hasProvenanceService</code> specifies a <a class="internalDFN">service-URI</a> associated with the RDF document for possible access to provenance information.  This property corresponds to a <a href="#registration-template-for-link-relation---provenance-service">provenance-service link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code>&lt;link&gt;</code> element.
+          Property <code>prov:hasProvenanceService</code> specifies a <a class="internalDFN">service-URI</a> associated with the RDF document for possible access to provenance information.  This property corresponds to a <code>hasProvenanceService</code> link relation used with an HTTP <code>Link</code> header field, or HTML <code>&lt;link&gt;</code> element.
         </p>
         <pre class="example code">
     @prefix prov: &lt;http://www.w3.org/ns/prov#&gt;
@@ -556,15 +586,13 @@
           The RDF service description example below in <a href="#provenance-service-description" class="sectionRef"></a> shows this use.
         </p>
         <p class="TODO">
-          @@TODO: sync up term definitions with provenance ontology specification.
+          @@TODO: rework the above to take account of hasProvenanceService links
         </p>
       </section>
 
       <!-- <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>Dereferencing a provenance service URI should yield a provenance service description. This is to be compatible with the constraints of [[REST-APIs]]. 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">
@@ -572,13 +600,10 @@
     prov:provenanceUriTemplate "<cite>service-URI</cite>?target={+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 target-URI contains '#' or '&amp;' these  must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion.
+        <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 target-URI contains '#' or '&amp;' these  must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion [[RFC3986]].
         </p>
         <p>While use of RDF for service descriptions is a recommended option, this specification does not preclude the use of non-RDF formats that a service may choose to offer, and which can be selected using HTTP content negotiation.
         </p>
-        <p class="TODO">
-          @@TODO: sync up term definitions with provenance ontology specification.
-        </p>
       </section>
 
     </section>
@@ -588,6 +613,10 @@
     <section>
     <h2>Best practice</h2> 
 
+      <p class="TODO">
+        @@TODO: rtemove this section; cover in FAQ
+      </p>
+
       <section id="querying-provenance-information">
         <h2>Using SPARQL for provenance queries</h2>
         <p>
@@ -604,7 +633,7 @@
         </p>
         <p>
           The details of a provenance query service is an implementation choice, but for interoperability between different providers and users we recommend use of SPARQL [[RDF-SPARQL-PROTOCOL]] [[RDF-SPARQL-QUERY]].
-          The query service URI would then be the URI of a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a> 
+          The query service URI would then be the URI of a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service" class="externalRef">SPARQL protocol service</a> 
 (often referred to as a "SPARQL endpoint").
             The following subsections provide examples for what are considered to be some plausible common scenarios for using SPARQL, and are not intended to cover all possibilities.
         </p>
@@ -701,94 +730,6 @@
 <!-- ==== Section 6 ===================================================================================== -->
 
     <section>
-      <h2>IANA considerations</h2>
-      <p>This document requests registration of new link relations, per <a href="http://tools.ietf.org/html/rfc5988#section-6.2.1">section-6.2.1 of RFC 5988</a>.
-      </p>
-      <p class="TODO">
-          @@TODO The following templates should be completed and submitted to [email protected], or this section removed if URIs are used for link relations in §3:  Use some material for  table of UREIs introduced.
-      </p>
-      <section>
-        <h2>Registration template for link relation: "provenance"</h2>
-          <dl>
-            <dt>Relation Name:</dt>
-            <dd>
-              <code>provenance</code>
-            </dd>
-            <dt>Description:</dt>
-            <dd>
-              the resource identified by target IRI of the link provides provenance information about the resource identified by the context link
-            </dd>
-            <dt>Reference:</dt>
-            <dd>
-              @@this spec, @@provenance-model-spec
-            </dd>
-            <dt>Notes:</dt>
-            <dd>
-              ...
-            </dd>
-            <dt>Application Data:</dt>
-            <dd>
-              ...
-            </dd>
-          </dl>
-       
-      </section>
-      <section>
-        <h2>Registration template for link relation: "anchor"</h2>
-          <dl>
-            <dt>Relation Name:</dt>
-            <dd>
-              <code>anchor</code>
-            </dd>
-            <dt>Description:</dt>
-            <dd>
-              when used in conjunction with a "provenance" link, the resource identified by target IRI of the link is one for which provenance information may be provided.  This may be used, for example, to isolate relevant information from a referenced document that contains provenance information for several entities.
-            </dd>
-            <dt>Reference:</dt>
-            <dd>
-              @@this spec, @@provenance-model-spec
-            </dd>
-            <dt>Notes:</dt>
-            <dd>
-              ...
-            </dd>
-            <dt>Application Data:</dt>
-            <dd>
-              ...
-            </dd>
-          </dl>
-      </section>
-      <section>
-        <h2>Registration template for link relation: "provenance-service"</h2>
-          <dl>
-            <dt>Relation Name:</dt>
-            <dd>
-              <code>provenance-service</code>
-            </dd>
-            <dt>Description:</dt>
-            <dd>
-              the resource identified by target URI of the link is an provenance service per <a href="#provenance-services" class="sectionRef"></a> of this specification.
-            </dd>
-            <dt>Reference:</dt>
-            <dd>
-              @@this spec, @@provenance-model-spec
-            </dd>
-            <dt>Notes:</dt>
-            <dd>
-              ...
-            </dd>
-            <dt>Application Data:</dt>
-            <dd>
-              ...
-            </dd>
-          </dl>
-     
-      </section>
-    </section>
- 
-<!-- ==== Section 7 ===================================================================================== -->
-
-    <section>
       <h2>Security considerations</h2>
       <p>
         Provenance is central to establishing trust in data. If provenance information is corrupted, it may lead agents (human or software) to draw inappropriate and possibly harmful conclusions.  Therefore, care is needed to ensure that the integrity of provenance information is maintained.  Just as provenance information can help determine a level of trust in some information, provenance information related to the provenance itself ("provenance of provenance") can help determine trust in the provenance itself.
@@ -804,8 +745,6 @@
       </p>
       <p>Provenance information may be used by audits to establish accountability for information use [[INFO-ACC]] and to verify use of proper processes in information processing activities.  Thus, provenance management systems can provide mechanisms to support auditing and enforcement of information handling policies. In such cases, provenance information itself may be a valuable target for attack by malicious agents, and care must be taken to ensure it is stored securely and in a fashion that resists attempts to tamper with it.
       </p>
-
-
     </section>
  
 <!-- ===================================================================================== -->
@@ -816,7 +755,7 @@
         The editors acknowledge the contribution and review from members of the W3C Provenance working group for their feedback throughout the development of this specification.
       </p>
       <p>
-        Thanks to Robin Berjon for making our lives easier with his <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html">ReSpec</a> tool.
+        Thanks to Robin Berjon for making our lives easier with his <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html" class="externalRef">ReSpec</a> tool.
       </p>
     </section>
 
@@ -824,149 +763,44 @@
     
     <section class='appendix'>
       <h2>Names added to prov: namespace</h2>
-      <p class="TODO">
-          @@TODO Create table of URIs introduced, and what they mean.  Use some material from IOANA considerations.  Consider separate tables for classes and properties.
-      </p>
 
       <p>
-        This specification defines the following additional names in the provenance namespace.
-      </p>
-      
-      <p>
-        The provenance namespace URI is http://www.w3.org/ns/prov#.
+        This specification defines the following additional names in the provenance namespace
+        with URI <a href="http://www.w3.org/ns/prov#" class="externalRef">http://www.w3.org/ns/prov#</a>.
       </p>
         <table>
           <tr>
-            <th>name</th><th>Description</th><th>Definition ref</th>
-          </tr>
-          <tr>
-            <td>ProvenanceService</td><td>Class for a service described by a provenance service description</td><td>...</td>
+            <th>Name</th><th>Description</th><th>Definition ref</th>
           </tr>
           <tr>
-            <td>hasAnchor</td><td>Indicates anchor URI for a potentially dynamic resource instance</td><td>...</td>
+            <td>ProvenanceService</td>
+            <td>Class for a provenance service. Mainly for use in RDF provenance service descriptions, to facilitate discover..</td>
+            <td><a href="#provenance-service-description" class="sectionRef"></a></td>
           </tr>
           <tr>
-            <td>hasProvenance</td><td>Relates a resource to its provenance</td><td>...</td>
+            <td>hasAnchor</td>
+            <td>Indicates a <a class="internalDFN">target-URI</a>target-URI for a potentially dynamic resource instance</td>
+            <td><a href="#resource-represented-as-html" class="sectionRef"></a></td>
           </tr>
           <tr>
-            <td>hasProvenanceService</td><td>Relates a resource to a provenance service</td><td>...</td>
+            <td>hasProvenance</td>
+            <td>Indicates a <a class="internalDFN">provenance-URI</a> for a resource;  the resource identified by this property provides provenance information about its subject or anchor resource.
+            </td>
+            <td><a href="#resource-accessed-by-http" class="sectionRef"></a>, <a href="#resource-represented-as-html" class="sectionRef"></a></td>
           </tr>
           <tr>
-            <td>provenanceUriTemplate</td><td>Relates a provenance service to a URI template string for constructing provenance-URIs</td><td>...</td>
+            <td>hasProvenanceService</td>
+            <td>Indicates a <a class="internalDFN">provenance service</a> that can provide provenance information about its sibject or anchowresource.</td>
+            <td><a href="#specifying-provenance-services" class="sectionRef"></a></td>
+          </tr>
+          <tr>
+            <td>provenanceUriTemplate</td>
+            <td>Relates a provenance service to a URI template string for constructing provenance-URIs</td>
+            <td><a href="#provenance-service-description" class="sectionRef"></a></td>
           </tr>
         </table>
     </section>
 
-
-<!-- ===================================================================================== -->
-
-    <!-- 
-<section class='appendix'>
-      <h2>Provenance service format examples</h2>
-      <p>
-        In <a href="#provenance-services" class="sectionRef"></a>, the provenance service description was represented as a JSON-formatted document.  As noted, HTTP content negotiation MAY be enabled to retrieve the document in alternative formats.  This appendix provides examples of service description document represented using RDF Turtle and XML syntaxes, and XML. 
-      </p>
-
-      <section>
-        <h2>RDF Turtle example of service description</h2>
-        <p>
-          This example uses the RDF Turtle format [[TURTLE]], presented as MIME content-type <code>text/turtle</code>.
-        </p>
-        <pre class="example code">
-  @prefix provds: &lt;@@[email protected]@#&gt; .
-  @prefix prov: &lt;http://www.w3.org/ns/prov-o/&gt; .
-  
-  &lt;http://example.org/provenance_service/&gt; a prov:ProvenanceService ;
-    provds:provenance_locations_template       "http://example.org/provenance_service/locations/?uri={uri}" ;
-    provds:provenance_content_template     "http://example.org/provenance_service/provenance/?uri={uri}"
-    .
-        </pre>
-        <p class="note">
-          The provenance URI templates are encoded in RDF as plain string literals, <em>not</em> as resource URIs.
-        </p>
-        <p class="TODO">
-          Finalize URIs in the above example.
-        </p>
-      </section>
-
-      <section>
-        <h2>RDF/XML example of service description</h2>
-        <p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [[RDF-SYNTAX-GRAMMAR]], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
-        <pre class="example code">
-  &lt;rdf:RDF
-    xmlns:rdf    = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-    xmlns:rdfs   = "http://www.w3.org/2000/01/rdf-schema#"
-    xmlns:provds = "@@[email protected]@#"
-    xmlns:prov   = "http://www.w3.org/ns/prov-o/"
-  &gt;
-    &lt;prov:ProvenanceService rdf:about="http://example.org/provenance_service/"&gt;
-     example.org &lt;provds:provenance_locations_template&gt;http://example.org/provenance_service/locations/?uri={uri}&lt;/provds:location_template&gt; ;
-      &lt;provds:provenance_content_template&gt;http://example.org/provenance_service/provenance/?uri={uri}&lt;/provds:provenance_template&gt; ;
-    &lt;/prov:ProvenanceService&gt;
-  &lt;/rdf:RDF&gt;
-        </pre>
-        <p class="TODO">
-          Finalize URIs in the above example.
-        </p>
-      </section>
-
-      <section>
-        <h2>Plain XML example of service description</h2>
-        <p class="TODO">
-          @@TODO: provide example and schema
-        </p>
-      </section>
-
-      <section>
-        <h2>RDF Turtle example of provenance locations</h2>
-        <p>
-          This example uses the RDF Turtle format [[TURTLE]], presented as MIME content type <code>text/turtle</code>.
-        </p>
-        <pre class="example code">
-  @prefix prov: &lt;@@[email protected]@#&gt; .
-  &lt;http://example.org/qdata/&gt; a prov:Entity ;
-    prov:hasProvenance  &lt;http://source1.example.org/provenance/qdata/&gt; ;
-    prov:hasProvenance  &lt;http://source2.example.org/prov/qdata/&gt; ;
-    prov:hasProvenance  &lt;http://source3.example.com/prov?id=qdata&gt;
-    .
-        </pre>
-        <p class="issue">
-          NOTE: The namespace URI used here for the provenance properties is different from that used in the service description.  I am anticipating that it will be defined as part of the provenance model.  If it is not defined as part of the provenance model, then a property name should be allocated in the provenance discovery service namespace.
-        </p>
-        <p class="TODO">@@TODO: revise to conform with Provenance Model vocabulary; review URIs</p>
-      </section>
-
-      <section>
-        <h2>RDF/XML example of provenance locations</h2>
-        <p>
-          This is essentially the same as the Turtle example above, but encoded in RDF/XML [[RDF-SYNTAX-GRAMMAR]], and presented with MIME content type <code>application/rdf+xml</code>.
-        </p>
-        <pre class="example code">
-  &lt;rdf:RDF
-    xmlns:rdf    = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-    xmlns:rdfs   = "http://www.w3.org/2000/01/rdf-schema#"
-    xmlns:prov   = "@@[email protected]@#"
-  &gt;
-    &lt;prov:Entity rdf:about="http://example.org/qdata/"&gt;
-      &lt;prov:hasProvenance  rdf:resource="http://source1.example.org/provenance/qdata/" /&gt; ;
-      &lt;prov:hasProvenance  rdf:resource="http://source2.example.org/prov/qdata/" /&gt; ;
-      &lt;prov:hasProvenance  rdf:resource="http://source3.example.com/prov?id=qdata" /&gt; ;
-    &lt;/prov:Entity&gt;
-  &lt;/rdf:RDF&gt;
-        </pre>
-        <p class="TODO">@@TODO: revise to conform with Provenance Model vocabulary</p>
-      </section>
-
-      <section>
-        <h2>Plain XML example of provenance locations</h2>
-        <p class="TODO">
-          @@TODO: provide example and schema
-        </p>
-      </section>
-
-    </section>
- -->
-
 <!-- ===================================================================================== -->
 
   </body>
--- a/reports/prov-implementations.html	Mon Nov 19 14:07:41 2012 +0000
+++ b/reports/prov-implementations.html	Mon Nov 19 14:07:54 2012 +0000
@@ -2,29 +2,12 @@
 
 <html><head> 
     <title>PROV Implementation Report</title> 
-    <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+    <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+    <script src="../model/provbib.js" class="remove"></script>
     <script class="remove"> 
-      var addExtraReferences = function() {
-          for (var k in extraReferences)
-              berjon.biblio[k] = extraReferences[k];
-      };
-      var extraReferences = {
-		  "PROV-DM":
-			"Luc Moreau, Paolo Missier"+
-			"<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
-			"2012, Working Draft. "+
-			"URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
-	 
-		  "PROV-CONSTRAINTS":
-			"James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
-			"<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
-			"2012, Working Draft. "+
-			"URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
-
-		  };
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "ED",
+          specStatus:           "NOTE",
           
           // the specification's short name, as in http://www.w3.org/TR/short-name/
           shortName:            "prov-implementations",
@@ -87,8 +70,8 @@
           // Team Contact.
           wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46974/status",
 
-          // Add extraReferences to bibliography database
-          preProcess: [addExtraReferences],
+          // Add PROV references to bibliography database
+          preProcess: [addProvReferences],
       };
     </script> 
 <link href="reports.css" rel="stylesheet" type="text/css">
@@ -125,25 +108,29 @@
         <tr>
           <th scope="row">ProvPy</th>
           <td>Framework / API</td>
-          <td>PROV-N, PROV-JSON</td>
+          <td>PROV-N, Other</td>
           <td><a href="https://github.com/trungdong/w3-prov">https://github.com/trungdong/w3-prov</a></td>
-          <td>&nbsp;</td>
+          <td>Other encodings supported: PROV-JSON</td>
         </tr>
         <tr>
           <th scope="row">ProvToolbox</th>
           <td>Application</td>
-          <td>PROV-N, PROV-RDF, PROV-XML, PROV-JSON</td>
+          <td>PROV-N, PROV-RDF, PROV-XML, Other</td>
           <td><a href="https://github.com/lucmoreau/ProvToolbox">https://github.com/lucmoreau/ProvToolbox</a></td>
-          <td>&nbsp;</td>
+          <td>Other encodings supported: PROV-JSON</td>
         </tr>
       </table>
 
     </section>
 
   <section id="prov-terms">
-    <h2>PROV Language Implementation</h2>
+    <h2>PROV Language Implementation</h2>
+    <p>This section enumerates the PROV-DM terms [[PROV-DM]] that are consumed (<img src="consume.png" width="27" height="16" alt="Consume Icon" />),
+    produced (<img src="produce.png" width="27" height="16" alt="Produce Icon" />),
+    or both consumed and produced (<img src="conprod.png" width="27" height="16" alt="Consume and Produce Icon" />)
+    by a particular implementation.</p>
     <table class="feature-table">
-      <caption id="prov-terms-table">Table 2: Coverage of PROV-DM [[PROV-DM]] terms in implementations of type Application, Framework / API, or Service.</caption>
+      <caption id="prov-terms-table">Table 2: Coverage of PROV-DM terms in implementations of type Application, Framework / API, or Service.</caption>
       <tr>
         <th scope="col">PROV Component</th>
         <th scope="col">Term</th>
--- a/testcases/constraints/process.html	Mon Nov 19 14:07:41 2012 +0000
+++ b/testcases/constraints/process.html	Mon Nov 19 14:07:54 2012 +0000
@@ -7,50 +7,13 @@
 
     <title>PROV-CONSTRAINTS Test Cases</title>
     <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
-
-    <script class="remove"> 
-
-      var addExtraReferences = function() {
-
-          for (var k in extraReferences)
-
-              berjon.biblio[k] = extraReferences[k];
-
-      };
-
-      var extraReferences = {
-
-		  "PROV-DM":
-
-			"Luc Moreau, Paolo Missier"+
-
-			"<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
-
-			"2012, Working Draft. "+
-
-			"URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
-
-	 
-
-		  "PROV-CONSTRAINTS":
-
-			"James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
-
-			"<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
-
-			"2012, Working Draft. "+
-
-			"URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
-
-
-
-		  };
-
+    <script src="../../model/provbib.js" class="remove"></script>    
+    <script type="text/javascript" >
       var respecConfig = {
 
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
 
-          specStatus:           "ED",
+          specStatus:           "NOTE",
 
           
 
@@ -178,7 +141,7 @@
 
           // Add extraReferences to bibliography database
 
-          preProcess: [addExtraReferences],
+          preProcess: [addProvReferences],
 
       };
 
@@ -209,12 +172,15 @@
 <h3>Test cases</h3>
 
 <p>The test cases will be made available  online at: &lt;URI&gt;<br />
+  Every test case has an identifier, e.g. <strong>association2-c24-c55-FAIL-c52</strong>.
+  In order to facilitate the testing process, we include the numberings of the constraints covered by
+  each test case its identifier, e.g. <b>c24</b>, <b>c55</b>, and <b>c52</b>. In addition, the identifier
+  also indicates whether the test case should be successfully validated (i.e. <b>PASS</b>) or not (i.e. <b>FAIL</b>).
+  In case of the latter, the constraint numberings that follow <b>FAIL</b> are those of the constraints we expect to
+  cause the test case to fail validation. 
+</p>
 
-  Every test case has an identifier, e.g. <strong>entity10-c23-c56-c57</strong>.
-  The numberings of the constraints covered by a test case are included with its identifier, e.g. c23, c56, and c57. 
-  The provenance document for each test case will be provided in the following representations:</p>
-
-
+<p>The provenance document for each test case will be provided in the following representations:</p>
 
 <table border="1" cellspacing="0" cellpadding="0" width="623">
 
@@ -236,7 +202,7 @@
 
     <td><p><strong>PROV-XML</strong></p></td>
 
-    <td><p>.xml</p></td>
+    <td><p>.provx</p></td>
 
     <td><p><a href="http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html">http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html</a></p></td>
 
@@ -276,9 +242,9 @@
 
 
 
-<p>For example, the files <strong>entity10-c23-c56-c57.xml</strong>, <strong>entity10-c23-c56-c57.trig</strong>,
-<strong>entity10-c23-c56-c57.json</strong>, and <strong>entity10-c23-c56-c57.provn</strong> for the test case
-<strong>entity10-c23-c56-c57</strong> can be found at &lt;URI&gt;.</p>
+<p>For example, the available files for the test case <strong>association2-c24-c55-FAIL-c52</strong> are: <strong>association2-c24-c55-FAIL-c52.xml</strong>,
+<strong>association2-c24-c55-FAIL-c52.trig</strong>, <strong>association2-c24-c55-FAIL-c52.json</strong>, and <strong>association2-c24-c55-FAIL-c52.provn</strong>.
+They can all be found at &lt;URI&gt;.</p>
 
 
 
@@ -322,7 +288,7 @@
 
 
 
-<p>All test cases need to be checked for the  constraints they cover and their expected validation results (i.e. Success or  Fail).</p>
+<p>All test cases need to be checked for the  constraints they cover and their expected validation results (i.e. Pass or  Fail).</p>
 
 
 
@@ -347,14 +313,14 @@
 
   <tr>
 
-    <td><b>activity1-c23-c56-c57</b></p></td>
+    <td><b>activity1-PASS-c23-c56-c57</b></p></td>
 
     <td><a href="http://www.w3.org/TR/prov-constraints/#key-object_text">Constraint 23 (key-object)</a> <br />
         <a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><br />
         <a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a>
     </td>
 
-    <td>Success</p></td>
+    <td>Pass</p></td>
 
     <td>&nbsp;</td>
 
@@ -362,14 +328,14 @@
 
   <tr>
 
-    <td><b>activity2-c23-c56-c57</b></p></td>
+    <td><b>activity2-PASS-c23-c56-c57</b></p></td>
 
     <td><a href="http://www.w3.org/TR/prov-constraints/#key-object_text">Constraint 23 (key-object)</a> <br />
         <a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><br />
         <a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a>
     </td>
 
-    <td>Success</p></td>
+    <td>Pass</p></td>
 
     <td>&nbsp;</td>
 
@@ -377,7 +343,7 @@
 
   <tr>
 
-    <td><b>association1-c24-c52</b></p></td>
+    <td><b>association1-c24-FAIL-c52</b></p></td>
 
     <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
         <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a>
@@ -391,7 +357,7 @@
 
   <tr>
 
-    <td><b>association2-c24-c52</b></p></td>
+    <td><b>association2-c24-c55-FAIL-c52</b></p></td>
 
     <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
         <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a>
@@ -405,7 +371,7 @@
 
   <tr>
 
-    <td><b>delegation1-c24-c52-c55</b></p></td>
+    <td><b>delegation1-c24-c55-FAIL-c52</b></p></td>
 
     <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
         <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a><br />
@@ -420,7 +386,7 @@
 
   <tr>
 
-    <td><b>delegation2-c24-c52-c55</b></p></td>
+    <td><b>delegation2-c24-c55-FAIL-c52</b></p></td>
 
     <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
         <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a><br />
--- a/xml/prov-xml.html	Mon Nov 19 14:07:41 2012 +0000
+++ b/xml/prov-xml.html	Mon Nov 19 14:07:54 2012 +0000
@@ -45,6 +45,7 @@
     <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js" class="remove"></script>
     <script src="../model/glossary.js" class="remove"></script>
 
+    <script src="../model/provbib.js" class="remove"></script>
 
     <script>
     $(function() {
@@ -80,74 +81,12 @@
       };
       var extraReferences = {
         
-        "CLOCK":
-         "Lamport, L. "+
-         "<a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
-         "Communications of the ACM 21 (7): 558–565. 1978. "+
-         "URL: <a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
-         "DOI: doi:10.1145/359545.359563.",
-        
-        "CSP":
-         "Hoare, C. A. R. "+
-         "<a href=\"http://www.usingcsp.com/cspbook.pdf\"><cite>Communicating Sequential Processes</cite></a>."+
-         "Prentice-Hall. 1985"+
-         "URL: <a href=\"http://www.usingcsp.com/cspbook.pdf\">http://www.usingcsp.com/cspbook.pdf</a>",
-        
-        "Logic":
-          "W. E. Johnson"+
-          "<a href=\"http://www.ditext.com/johnson/intro-3.html\"><cite>Logic: Part III</cite></a>."+
-          "1924. "+
-          "URL: <a href=\"http://www.ditext.com/johnson/intro-3.html\">http://www.ditext.com/johnson/intro-3.html</a>",
-        
-        "PROV-SEM":
-          "James Cheney "+
-          "<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
-          "2011, Work in progress. "+
-          "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
-          
-        "PROV-PRIMER":
-          "Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
-          "<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
-          "2012, Working Draft. "+
-          "URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
-
-        "PROV-O":
-          "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik "+
-          "<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
-          "2012, Working Draft. "+
-          "URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
-
-
-        "PROV-DM":
-          "Luc Moreau and Paolo Missier (eds.) ... "+
-          "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>PART 1: PROV-DM ...</cite></a>. "+
-          "2012, Working Draft. "+
-          "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
-
-
-        "PROV-CONSTRAINTS":
-          "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
-          "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
-          "2012, Working Draft. "+
-          "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
-
-        "PROV-N":
-          "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
-          "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
-          "2012, Working Draft. "+
-          "URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
-          
-        "PROV-AQ":
-          "Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
-          "<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
-          "2012, Working Draft. "+
-          "URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
-        
         "Mappings":
           "Satya Sahoo and Paul Groth and Olaf Hartig and Simon Miles and Sam Coppens and James Myers and Yolanda Gil and Luc Moreau and Jun Zhao and Michael Panzer and Daniel Garijo "+
           "<a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\"><cite>Provenance Vocabulary Mappings</cite></a>. "+
           "August 2010 "+
           "URL: <a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>",
+        
       };
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -224,7 +163,7 @@
           wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46974/status",
 
           // Add extraReferences to bibliography database
-          preProcess: [addExtraReferences],
+          preProcess: [addExtraReferences, addProvReferences],
           
           // will we have a postProcess?
       };
@@ -2223,8 +2162,73 @@
 
 <section class="appendix"> 
       <h2>Acknowledgements</h2> 
+
+This document has been produced by the PROV Working Group, and its
+contents reflect extensive discussion within the Working Group as a
+whole. The editors extend special thanks to Luc Moreau (University of
+Southampton), Paul Groth (Vrije Universiteit) and James Cheney
+(University of Edinburgh) for their thorough reviews.
+
       <p> 
-        WG membership to be listed here.
+Members of the PROV Working Group at the time of publication of this document were:
+
+Ilkay Altintas (Invited expert),
+Reza B'Far (Oracle Corporation),
+Khalid Belhajjame (University of Manchester),
+James Cheney (University of Edinburgh, School of Informatics),
+Sam Coppens (IBBT),
+David Corsar (University of Aberdeen, Computing Science),
+Stephen Cresswell (The National Archives),
+Tom De Nies (IBBT),
+Helena Deus (DERI Galway at the National University of Ireland, Galway, Ireland),
+Simon Dobson (Invited expert),
+Martin Doerr (Foundation for Research and Technology - Hellas(FORTH)),
+Kai Eckert (Invited expert),
+Jean-Pierre EVAIN (European Broadcasting Union, EBU-UER),
+James Frew (Invited expert),
+Irini Fundulaki (Foundation for Research and Technology - Hellas(FORTH)),
+Daniel Garijo (Universidad Politécnica de Madrid),
+Yolanda Gil (Invited expert),
+Ryan Golden (Oracle Corporation),
+Paul Groth (Vrije Universiteit),
+Olaf Hartig (Invited expert),
+David Hau (National Cancer Institute, NCI),
+Sandro Hawke (W3C/MIT),
+Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
+Ivan Herman, (W3C/ERCIM),
+Ralph Hodgson (TopQuadrant),
+Hook Hua (Invited expert),
+Trung Dong Huynh (University of Southampton),
+Graham Klyne (University of Oxford),
+Michael Lang (Revelytix, Inc.),
+Timothy Lebo (Rensselaer Polytechnic Institute),
+James McCusker (Rensselaer Polytechnic Institute),
+Deborah McGuinness (Rensselaer Polytechnic Institute),
+Simon Miles (Invited expert),
+Paolo Missier (School of Computing Science, Newcastle university),
+Luc Moreau (University of Southampton),
+James Myers (Rensselaer Polytechnic Institute),
+Vinh Nguyen (Wright State University),
+Edoardo Pignotti (University of Aberdeen, Computing Science),
+Paulo da Silva Pinheiro (Rensselaer Polytechnic Institute),
+Carl Reed (Open Geospatial Consortium),
+Adam Retter (Invited Expert),
+Christine Runnegar (Invited expert),
+Satya Sahoo (Invited expert),
+David Schaengold (Revelytix, Inc.),
+Daniel Schutzer (FSTC, Financial Services Technology Consortium),
+Yogesh Simmhan (Invited expert),
+Stian Soiland-Reyes (University of Manchester),
+Eric Stephan (Pacific Northwest National Laboratory),
+Linda Stewart (The National Archives),
+Ed Summers (Library of Congress),
+Maria Theodoridou (Foundation for Research and Technology - Hellas(FORTH)),
+Ted Thibodeau (OpenLink Software Inc.),
+Curt Tilmes (National Aeronautics and Space Administration),
+Craig Trim (IBM Corporation),
+Stephan Zednik (Rensselaer Polytechnic Institute),
+Jun Zhao (University of Oxford),
+Yuting Zhao (University of Aberdeen, Computing Science).
       </p> 
     </section>