--- a/paq/prov-aq.html Thu Feb 21 14:06:52 2013 +0000
+++ b/paq/prov-aq.html Thu Feb 21 15:07:09 2013 +0000
@@ -275,28 +275,51 @@
<p>In defining the specification below, we make use of the following concepts.</p>
<dl>
<dt><a href="#dfn-resource"><dfn>Resource</dfn></a></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" 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>
+ <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>
+ <dt><a href="#dfn-entity"><dfn>Entity</dfn></a></dt>
+ <dd>Any <a class="internalDFN">resource</a> for which provenance may be provided.
+ </dd>
<dt><a href="#dfn-constrained-resource"><dfn>Constrained resource</dfn></a></dt>
- <dd>an aspect, version or instance of a <a class="internalDFN">resource</a>, about which one may wish to present a <a class="internalDFN">provenance record</a>s. 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 its 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>
- <dt><a href="#dfn-target-uri"><dfn>Target-URI</dfn></a></dt>
- <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 provenance associated with it.</dd>
+ <dd>a specialization (e.g. an aspect, version or instance) of a <a class="internalDFN">resource</a>, about which one may wish to present <a class="internalDFN">provenance record</a>s. 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 its own URI different from that of the original. See also [[PROV-DM]] <a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">section 5.5.1</a>, and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse" class="externalRef">section 2.3.2</a>.
+ </dd>
+ <dt><a href="#dfn-entity-uri"><dfn>Entity-URI</dfn></a></dt>
+ <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 its provenance.
+ </dd>
</dt><a href="#dfn-provenance-record"><dfn>Provenance record</dfn></a></dt>
- <dd>refers to provenance represented in some fashion.</dd>
+ <dd>
+ refers to provenance represented in some fashion.
+ </dd>
<dt><a href="#dfn-provenance-uri"><dfn>Provenance-URI</dfn></a></dt>
- <dd>a URI denoting some <a class="internalDFN">provenance record</a>.</dd>
+ <dd>
+ a URI denoting some <a class="internalDFN">provenance record</a>.
+ </dd>
<dt><a href="#dfn-provenance-query-service"><dfn>Provenance query service</dfn></a></dt>
- <dd>a service that accesses provenance using a query containing a <a class="internalDFN">target-URI</a> or other information about the desired provenance.</dd>
+ <dd>
+ a service that accesses provenance using a query containing an <a class="internalDFN">entity-URI</a> or other information about the desired provenance.
+ </dd>
<dt><a href="#dfn-service-uri"><dfn>Service-URI</dfn></a></dt>
- <dd>the URI of a <a class="internalDFN">provenance query service</a>.</dd>
+ <dd>
+ the URI of a <a class="internalDFN">provenance query service</a>.
+ </dd>
<dt><a href="#dfn-pingback-uri"><dfn>Pingback-URI</dfn></a></dt>
- <dd>the URI of a provenance pingback service that can receive forward provenance (i.e. provenance describing how a resource is used after it has been created).</dd>
+ <dd>
+ the URI of a provenance pingback service that can receive forward provenance (i.e. provenance describing how a resource is used after it has been created).
+ </dd>
<dt><a href="#dfn-accessing"><dfn>Accessing</dfn></a> provenance records</dt>
- <dd>given the identity of a resource, the process of discovering and retrieving some <a class="internalDFN">provenance record</a>(s) about that resource. This may involve <a class="internalDFN">locating</a> a provenance record, then performing an HTTP GET to retrieve it, or locating and using a query service for provenance about an identified resource, or some other mechanism not covered in this document.</dd>
+ <dd>
+ given the identity of a resource, the process of discovering and retrieving some <a class="internalDFN">provenance record</a>(s) about that resource. This may involve <a class="internalDFN">locating</a> a provenance record, then performing an HTTP GET to retrieve it, or locating and using a query service for provenance about an identified resource, or some other mechanism not covered in this document.
+ </dd>
<dt><a href="#dfn-locating"><dfn>Locating</dfn></a> provenance records</dt>
- <dd>given the identity of a resource, discovery of a URI at which some <a class="internalDFN">provenance record</a> about that resource may be retrieved.</dd>
+ <dd>
+ given the identity of a resource, discovery of a URI at which some <a class="internalDFN">provenance record</a> about that resource may be retrieved.
+ </dd>
<!--
<a href="#dfn-..."><dt><dfn>...</dfn></dt></a>
- <dd>...</dd>
+ <dd>
+ ...
+ </dd>
-->
</dl>
<p class="TODO">
@@ -311,10 +334,10 @@
Fundamentally, a <a class="internalDFN">provenance record</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 records, to be useful, must be persistent and not themselves 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 records for 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 specialization 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 records for 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 specialization 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">entity-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. Entity-URIs may use any URI scheme, and are not required to be dereferencable.
</p>
<p>
- Requests for provenance about a resource may return provenance records that use one or more target-URIs to refer to versions of that resource. Some provenance records may use multiple target-URIs if there are assertions referring to the same underlying resource in different contexts. For example, a provenance record for a W3C document might include information about all revisions of the document using statements that use the different target-URIs of the various revisions.
+ Requests for provenance about a resource may return provenance records that use one or more entity-URIs to refer to versions of that resource, such as when there are assertions referring to the same underlying resource in different contexts. For example, a provenance record for a W3C document might include information about all revisions of the document using statements that use the different entity-URIs of the various revisions.
</p>
<p>
These ideas are represented in the provenance data model [[PROV-DM]] by the concepts <a href="http://www.w3.org/TR/prov-dm/#term-entity" class="externalRef">entity</a> and <a href="http://www.w3.org/TR/prov-dm/#term-specialization" class="externalRef">specialization</a>. In particular, an entity may be a specialization of some resource whose "fixed aspects" provide sufficient constraint for expressed provenance about the resource to be invariant with respect to that entity. This entity is itself just another resource (e.g. the weather forecast for a give date as opposed to the current weather forecast), with its own URI for referring to it within a provenance record.
@@ -328,11 +351,12 @@
Also, review second para below. Move definition of provider/consumer to concepts section?
</p>
<p>
- Any given <a class="internalDFN">provenance record</a> may contain information about several resources, referring to them using their various <a class="internalDFN">target-URI</a>s.
- Thus, when interpreting provenance records, it is important to be aware that statements about several resources may be present, and to be accordingly selective when using the information provided. (In some exceptional cases, it may be that a provenance record returned does not contain any information relating to a specific associated resource.)
+ Any <a class="internalDFN">provenance record</a> may contain information about several <a class="internalDFN" href="#dfn-entity">entities</a>, referring to them using their various <a class="internalDFN">entity-URI</a>s.
+ Thus, when interpreting provenance records, it is important to be aware that statements about several entities may be present, and to be accordingly selective when using the information provided.
+ (Further, the provenance record returned may contain <em>no</em> information about the specific entity for which the request was made.)
</p>
<p>
- The consumer of a provenance record will generally need to isolate information about some specific target resource or resources. These may be <a class="internalDFN">constrained resource</a>s identified by separate target-URIs than the original resource, in which case a provenance consumer will need to know the target-URI used.
+ Thus, the consumer of a provenance record will need to isolate information about the specific entity or entities of interest. These may be <a class="internalDFN">constrained resource</a>s identified by separate entity-URIs than the original resource, in which case it will need to know about the entity-URI used.
</p>
<p>
A provenance record is not of itself guaranteed to be authoritative or correct. Trust in provenance records 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 resource; e.g. based on the domain that serves it, or an associated digital signature. (See also <a href="#security-considerations" class="sectionRef"></a>.)
@@ -351,8 +375,8 @@
<th>Dereferences to</th>
</tr>
<tr style="vertical-align: top;">
- <td><a class="internalDFN">Target-URI</a></td>
- <td>Any resource for which provenance is provided.</td>
+ <td><a class="internalDFN">Entity-URI</a></td>
+ <td>An entity; any resource for which provenance is provided.</td>
<td>If the URI is dereferencable, it should return a representation or description of the resource for which provenance is provided.</td>
</tr>
<tr style="vertical-align: top;">
@@ -432,7 +456,7 @@
<p>Provenance records may be offered by several providers other than that of the original resource, each with different concerns, and presenting provenance at different locations. It is possible that these different providers may present contradictory provenance.
</p>
<p>
- We consider here mechanisms for a provider to indicate a <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">service-URI</a> along with a <a class="internalDFN">target-URI</a>.
+ We consider here mechanisms for a provider to indicate a <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">service-URI</a> along with an <a class="internalDFN">entity-URI</a>.
Three mechanisms are described:
</p>
<ul>
@@ -444,7 +468,7 @@
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.
</p>
<p class="note">
- The mechanisms described here are intended to allow a provider to supply information that may assist a client in finding related provenance records. The provenance records should themselves explicitly identify the target resources they describe. 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 records. The provenance records should themselves explicitly identify the target resources they describe. 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 entity-URI. In the general case, a client presented with multiple provenance-URIs and multiple entity-URIs should look at all of the provenance-URIs for information about any or all of the entity-URIs.
</p>
<section>
@@ -455,10 +479,10 @@
<p>
A <code>hasProvenance</code> link relation type for referencing a provenance record may be used thus:
</p>
- <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 a provenance record about the originally requested resource, and that the requested resource is identified within the provenance record as <code><cite>target-URI</cite></code>. (See also <a href="#interpreting-provenance-records" class="sectionRef"></a>.)</p>
+ <pre class="pattern">Link: <<cite>provenance-URI</cite>>; rel="http://www.w3.org/ns/prov#hasProvenance"; anchor="<cite>entity-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 a provenance record about the originally requested resource, and that the requested resource is identified within the provenance record as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-records" 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 requested resource used in the corresponding HTTP request.
+ If no <code>anchor</code> parameter is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the requested resource used in the corresponding HTTP request.
</p>
<p>
This specification does not define the meaning of these links returned with other HTTP response codes: future revisions may define interpretations for these.
@@ -481,7 +505,7 @@
The resource provider may indicate that provenance records about the resource are provided by a <a class="internalDFN">provenance query service</a>. This is done through the use of a <code>hasQueryService</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#hasQueryService"; anchor="<cite>target-URI</cite>"</pre>
+Link: <<cite>provenance-service-URI</cite>>; rel="http://www.w3.org/ns/prov#hasQueryService"; anchor="<cite>entity-URI</cite>"</pre>
<p>
The <code>hasQueryService</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 submit a query to retrieve a <a class="internalDFN">provenance record</a> for a <a class="internalDFN">resource</a>; see <a href="#provenance-query-services" class="sectionRef"></a> for more details.
</p>
@@ -540,7 +564,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="http://www.w3.org/ns/prov#hasProvenance" href="<cite>provenance-URI</cite>">
- <link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>target-URI</cite>">
+ <link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>entity-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -552,10 +576,10 @@
The <code><cite>provenance-URI</cite></code> given by the <code>hasProvenance</code> link element identifies the provenance-URI for the document.
</p>
<p>
- 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 record when referring to the document.
+ The <code><cite>entity-URI</cite></code> given by the <code>hasAnchor</code> link element specifies an identifier for the document that may be used within the provenance record when referring to the document.
</p>
<p>
- 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 has a URI that is reasonably expected to be known or easily discoverable by a consumer of 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>entity-URI</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this convention be used only when the document has a URI that is reasonably expected to be known or easily discoverable by a consumer of the document (e.g. when delivered from a web server, or as part of a MIME structure containing content identifiers [[RFC2392]]).
</p>
<p>
An HTML document header MAY include multiple <code>hasProvenance</code> link elements, indicating a number of different provenance records that are known to the creator of the document, each of which may provide provenance about the document (see also the note in <a href="#locating-provenance-records" class="sectionRef"></a>).
@@ -570,7 +594,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="http://www.w3.org/ns/prov#hasQueryService" href="<cite>service-URI</cite>">
- <link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>target-URI</cite>">
+ <link rel="http://www.w3.org/ns/prov#hasAnchor" href="<cite>entity-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -596,7 +620,7 @@
The RDF property <code>prov:hasProvenance</code> is a relation between two resources, where the object of the property is a provenance record 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> link relation</a> used with an HTTP <code>Link</code> header field, or HTML <code><link></code> element (see above).
</p>
<p>
- Property <code>prov:hasAnchor</code> specifies a <a class="internalDFN">target-URI</a> used in the indicated provenance to refer to the containing RDF document.
+ Property <code>prov:hasAnchor</code> specifies an <a class="internalDFN">entity-URI</a> used in the indicated provenance 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><link></code> element, which similarly indicate a URI used in the provenance record to refer to the described document.
</p>
<p>
@@ -626,9 +650,9 @@
</p>
<p>The introduction of query services is motivated by the following possible considerations: </p>
<ul>
- <li>the naming authority associated with the <a class="internalDFN">target-URI</a> is not the same as the service offering <a class="internalDFN">provenance record</a>s</li>
+ <li>the naming authority associated with the <a class="internalDFN">entity-URI</a> is not the same as the service offering <a class="internalDFN">provenance record</a>s</li>
<li>multiple services have provenance records about the same resource</li>
- <li>the service associated with the target-URI is not accessible for adding additional information when handling retrieval requests</li>
+ <li>the service associated with the entity-URI is not accessible for adding additional information when handling retrieval requests</li>
<li>there is no known dereferencable <a class="internalDFN">provenance-URI</a> returning a provenance record for a particular resource</li>
<li>query services may provide additional control over what provenance is returned.</li>
</ul>
@@ -666,7 +690,7 @@
Tim's point (20): I think this will be covered by Stian's proposal; leaving for now.
</p>
<p>A direct HTTP query service is described by an RDF resource of type <code>prov:DirectQueryService</code></p>
- <p>It allows for accessing provenance about a specified <a class="internalDFN">target-URI</a>. The query URI to use is described by a URI Template [[URI-template]] (level 2 or above) in which which the variable <cite><code>uri</code></cite> stands for the target-URI; e.g.</p>
+ <p>It allows for accessing provenance about a specified <a class="internalDFN">entity-URI</a>. The query URI to use is described by a URI Template [[URI-template]] (level 2 or above) in which which the variable <cite><code>uri</code></cite> stands for the entity-URI; e.g.</p>
<pre class="pattern">
@prefix prov: <http://www.w3c.org/ns/prov#>
<cite>query_option_node</cite> a prov:DirectQueryService ;
@@ -675,7 +699,7 @@
where <cite><code>service-URI</code></cite> is the URI of the provenance query service, and <code><cite>query_option_node</cite></code> is any distinct RDF subject node (i.e. a blank node or a URI).
</p>
<p>
- The URI template indicated by <code>prov:provenanceUriTemplate</code> may expand to an absolute or relative URI reference. A URI for the desired provenance record is obtained by expanding the URI template with the variable <cite><code>uri</code></cite> set to the target-URI for which provenance is requested. In this example, if the target-URI contains '#' or '&' these must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion [[RFC3986]]. If the result is a relative reference, it is interpreted per [[RFC3986]] (section 5.2) using the URI of the service description as its base URI (which is generally the same as the query service-URI, unless HTTP redirection has been invoked).
+ The URI template indicated by <code>prov:provenanceUriTemplate</code> may expand to an absolute or relative URI reference. A URI for the desired provenance record is obtained by expanding the URI template with the variable <cite><code>uri</code></cite> set to the entity-URI for which provenance is requested. In this example, if the entity-URI contains '#' or '&' these must be %-escaped as <code>%23</code> or <code>%26</code> respectively before template expansion [[RFC3986]]. If the result is a relative reference, it is interpreted per [[RFC3986]] (section 5.2) using the URI of the service description as its base URI (which is generally the same as the query service-URI, unless HTTP redirection has been invoked).
</p>
<p>
A provenance query service MAY recognize additional parameters encoded as part of a URI for the provenance record. If it does, it SHOULD include these in the provenance URI template in the service description, so that clients may discover how a URI is formed using this additional information.
@@ -758,12 +782,12 @@
<section>
<h2>Direct HTTP query service invocation</h2>
- <p>This protocol typically combines the <a class="internalDFN">target-URI</a> with the <a class="internalDFN">service-URI</a> to formulate an HTTP GET request, according to the following convention:
+ <p>This protocol typically combines the <a class="internalDFN">entity-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>target</b>=http://www.example.com/entity HTTP/1.1
Host: example.com</pre>
</p>
- <p>The embedded target-URI (<code>http://www.example.com/entity</code>) identifies the resource for which provenance is to be returned. Any server that implements this protocol and receives a request URI in this form SHOULD return a provenance record 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 '&' character in the resource-URI must be %-encoded as <code>%26</code> [[RFC3986]].
+ <p>The embedded entity-URI (<code>http://www.example.com/entity</code>) identifies the resource for which provenance is to be returned. Any server that implements this protocol and receives a request URI in this form SHOULD return a provenance record 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 '&' character in the resource-URI must be %-encoded as <code>%26</code> [[RFC3986]].
</p>
<p>
If the provenance described by the request does not exist in the server, a <code>404 Not Found</code> response code SHOULD be returned.
@@ -841,7 +865,7 @@
:
(super-widget resource data)</pre>
<p>
- The first of the links in the response is a <code>hasProvenance</code> link with a <a class="internalDfn">provenance-URI</a> that has been described previously (<a href="#resource-accessed-by-http" class="sectionRef"></a>). The second is a distinct resource that exists to receive provenance pingbacks. Later, when a new resource has been created or action performed based upon the <code>acme.example.org/super-widget</code>, new provenance may be submitted to the pingback thus:
+ The first of the links in the response is a <code>hasProvenance</code> link with a <a class="internalDFN">provenance-URI</a> that has been described previously (<a href="#resource-accessed-by-http" class="sectionRef"></a>). The second is a distinct resource that exists to receive provenance pingbacks. Later, when a new resource has been created or action performed based upon the <code>acme.example.org/super-widget</code>, new provenance may be submitted to the pingback thus:
</p>
<pre class="pattern">
C: POST /pingback/super-widget HTTP/1.1
@@ -932,8 +956,8 @@
</tr>
<tr style="vertical-align: top;">
<td><code>hasAnchor</code></td>
- <td>Indicates a <a class="internalDFN">target-URI</a> for a potentially dynamic resource instance</td>
- <td><a href="#resource-represented-as-html" class="sectionRef"></a></td>
+ <td>Indicates an <a class="internalDFN">entity-URI</a> for an <a class="internalDFN">entity</a>, used by an associated provenance record.</td>
+ <td><a href="#resource-represented-as-html" class="sectionRef"></a>, <a href="#resource-represented-as-rdf" class="sectionRef"></a></td>
</tr>
<tr style="vertical-align: top;">
<td><code>hasProvenance</code></td>