--- a/paq/prov-aq.html Wed Feb 27 13:56:36 2013 +0000
+++ b/paq/prov-aq.html Wed Feb 27 15:33:13 2013 +0000
@@ -280,15 +280,12 @@
<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>
- <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>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>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 <a class="sectionRef" href="#provenance-and-resources"></a>, [[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>
+ <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 expressing its provenance.
+ a URI denoting a <a class="internalDFN">resource</a> (including any <a class="internalDFN">constrained resource</a>), and which identifies that resource for the purpose of expressing provenance. Such a resource is typically an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">entity</a> in the sense of [[PROV-DM]], but may be something else described by provenance records, such as an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">activity</a>.
</dd>
</dt><a href="#dfn-provenance-record"><dfn>Provenance record</dfn></a></dt>
<dd>
@@ -300,7 +297,7 @@
</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 an <a class="internalDFN">entity-URI</a> or other information about the desired provenance.
+ a service that accesses provenance given a query containing a <a class="internalDFN">target-URI</a> or other information that identifies the desired provenance.
</dd>
<dt><a href="#dfn-service-uri"><dfn>Service-URI</dfn></a></dt>
<dd>
@@ -357,10 +354,10 @@
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">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.
+ 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.
</p>
<p>
- 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.
+ Requests for provenance about a resource may return provenance records that use one or more target-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 target-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.
@@ -370,19 +367,18 @@
<section>
<h2>Interpreting provenance records</h2>
<p class="TODO">
- Rework terminology here and elsewhere to align with PROV-DM: talk about "entities" and "entity-URI"s.
- Also, review second para below. Move definition of provider/consumer to concepts section?
+ Review second para below.
</p>
<p>
The mechanisms described in this document are intended to allow a provider to supply information that allows a consumer to access <a class="internalDFN">provenance record</a>s, which themselves explicitly identify the <a class="internalDFN" href="#dfn-entity">entities</a> they describe.
- A provenance record may contain information about several entities, referring to them using their various <a class="internalDFN">entity-URI</a>s.
+ A provenance record may contain information about several entities, referring to them using their various <a class="internalDFN">target-URI</a>s.
Thus a consumer should be selective in its use of the information provided when interpreting a provenance record.
</p>
<p>
- A provenance record consumer 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-URIs used. The mechanisms defined later allow a provider to expose such URIs.
+ A provenance record consumer 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 target-URIs than the original resource, in which case it will need to know about the target-URIs used. The mechanisms defined later allow a provider to expose such URIs.
</p>
<p>
- 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 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.
+ 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 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>
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>.)
@@ -401,8 +397,8 @@
<th>Dereferences to</th>
</tr>
<tr style="vertical-align: top;">
- <td><a class="internalDFN">Entity-URI</a></td>
- <td>An entity; any resource for which provenance is provided.</td>
+ <td><a class="internalDFN">Target-URI</a></td>
+ <td>Any resource that is described by some provenance - typically an <a class="externalRef" href="http://www.w3.org/TR/prov-dm/#section-entity-activity">entity</a> (in the sense of [[PROV-DM]], but may be an activity).</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;">
@@ -467,7 +463,7 @@
A <a class="internalDFN">provenance record</a> can be accessed using direct web retrieval, given its <a class="internalDFN">provenance-URI</a>. If this is known in advance, there is nothing more to specify. If a provenance-URI is not known then a mechanism to discover one must be based on information that is available to the would-be accessor. Likewise, provenance may be exposed by a query service, in which case, the corresponding <a class="internalDFN">service-URI</a> must be discovered.
</p>
<p>
- Three mechanisms are defined for a provenance <a class="internalDFN">consumer</a> to find information about 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 defined for a provenance <a class="internalDFN">consumer</a> to find information about a <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">service-URI</a>, along with a <a class="internalDFN">target-URI</a>:
</p>
<ol>
<li>The consumer knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
@@ -491,10 +487,10 @@
<pre class="pattern">
Link: <<cite>provenance-URI</cite>>;
rel="http://www.w3.org/ns/prov#has_provenance";
- 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>
+ 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>
<p>
- 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.
+ 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.
</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.
@@ -537,7 +533,7 @@
<pre class="pattern">
Link: <<cite>service-URI</cite>>;
rel="http://www.w3.org/ns/prov#has_query_service";
- anchor="<cite>entity-URI</cite>"
+ anchor="<cite>target-URI</cite>"
</pre>
<p>
The <code>has_query_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 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.
@@ -612,7 +608,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<b><link rel="http://www.w3.org/ns/prov#has_provenance" href="<cite>provenance-URI</cite>"></b>
- <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>entity-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
<title>Welcome to example.com</title>
</head>
<body>
@@ -624,10 +620,10 @@
The <code><cite>provenance-URI</cite></code> given by the first link element (<code>#has_provenance</code> ) identifies the provenance-URI for the document.
</p>
<p>
- The <code><cite>entity-URI</cite></code> given by the second link element (<code>#has_anchor</code>) specifies an identifier for the document that may be used within the provenance record when referring to the document.
+ The <code><cite>target-URI</cite></code> given by the second link element (<code>#has_anchor</code>) specifies an identifier for the document that may be used within the provenance record when referring to the document.
</p>
<p>
- If no <code><cite>entity-URI</cite></code> is provided (via a <code>#has_anchor</code> link element) then is it 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><cite>target-URI</cite></code> is provided (via a <code>#has_anchor</code> link element) then is it 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 present multiple <code><cite>provenance-URI</cite></code>s over several <code>#has_provenance</code> link elements, indicating a number of different provenance records that are known to the publisher of the document, each of which may provide provenance about the document (see <a href="#interpreting-provenance-records" class="sectionRef"></a>).
@@ -645,7 +641,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<b><link rel="http://www.w3.org/ns/prov#has_query_service" href="<cite>service-URI</cite>"></b>
- <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>entity-URI</cite>"></b>
+ <b><link rel="http://www.w3.org/ns/prov#has_anchor" href="<cite>target-URI</cite>"></b>
<title>Welcome to example.com</title>
</head>
<body>
@@ -676,7 +672,7 @@
The RDF property <code>prov:has_provenance</code> is a relation between two resources, where the object of the property is a <a class="internalDFN">provenance-URI</a> that denotes a provenance record about the subject resource. Multiple <code>prov:has_provenance</code> assertions may be made about a subject resource.
</p>
<p>
- Property <code>prov:has_anchor</code> specifies an <a class="internalDFN">entity-URI</a> used in the indicated provenance to refer to the containing RDF document.
+ Property <code>prov:has_anchor</code> specifies a <a class="internalDFN">target-URI</a> used in the indicated provenance to refer to the containing RDF document.
</p>
<p>
Property <code>prov:has_query_service</code> specifies a <a class="internalDFN">service-URI</a> for provenance queries.
@@ -714,7 +710,7 @@
</p>
<ul>
<li>
- third-party providers of provenance descriptions may be unable to use the mechanisms of Section 3 because the corresponding <a class="internalDFN">entity-URI</a> is outside their control;
+ third-party providers of provenance descriptions may be unable to use the mechanisms of Section 3 because the corresponding <a class="internalDFN">target-URI</a> is outside their control;
</li>
<li>
services unknown to the original publisher may have provenance records about the same resource;
@@ -798,7 +794,7 @@
<section>
<h2>Direct HTTP query service description</h2>
<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">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>
+ <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>
<pre class="pattern">
@prefix prov: <http://www.w3c.org/ns/prov#>
<direct-query-description> a prov:DirectQueryService ;
@@ -808,11 +804,11 @@
where <cite><code>query-URI</code></cite> is the base URI of the direct query service, and <code><cite>direct-query-description</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 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).
+ 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).
</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.
- For example, a query service might offer to include just the immediate provenance of an entity, or to also supply provenance of entities from which the target resource is derived. Suppose a service accepts an additional parameter <code>steps</code> that defines the number of previous steps to include in a provenance trace, it might publish its service description thus:
+ For example, a query service might offer to include just the immediate provenance of a target, or to also supply provenance of other resources from which the target is derived. Suppose a service accepts an additional parameter <code>steps</code> that defines the number of previous steps to include in a provenance trace, it might publish its service description thus:
</p>
<pre class="example code">
<<cite>direct-query-description</cite>> a prov:DirectQueryService ;
@@ -902,23 +898,23 @@
<section>
<h2>Direct HTTP query service invocation</h2>
<p>
- This protocol combines the <a class="internalDFN">entity-URI</a> with a supplied URI template to formulate an HTTP GET request.
+ This protocol combines the <a class="internalDFN">target-URI</a> with a supplied URI template to formulate an HTTP GET request.
</p>
<p>
- Thus, if the URI template extracted from the service description is <code>http://example.com/provenance/service?target={uri}</code> and the supplied entity-URI is <code>http://www.example.com/entity123</code>, the resulting HTTP request would be:
+ Thus, if the URI template extracted from the service description is <code>http://example.com/provenance/service?target={uri}</code> and the supplied target-URI is <code>http://www.example.com/entity123</code>, the resulting HTTP request would be:
<pre class="example code">
GET /provenance/service?<b>target</b>=http%3A%2F%2Fwww.example.com%2Fentity123 HTTP/1.1
Host: example.com
</pre>
</p>
<p>
- Any server that implements this protocol and receives a request URI in this form SHOULD return a provenance record for the entity-URI embedded in the query component, where that URI is the result of percent-decoding [[RFC3986]] the part of the request URI corresponding to <code>{var}</code> in the URI template. E.g., in the above example, the decoded entity-URI is <code>http://www.example.com/entity123</code>. The entity-URI MUST be an absolute URI, and the server SHOULD respond with <code>400 Bad Request</code> if it is not.
+ Any server that implements this protocol and receives a request URI in this form SHOULD return a provenance record for the target-URI embedded in the query component, where that URI is the result of percent-decoding [[RFC3986]] the part of the request URI corresponding to <code>{var}</code> in the URI template. E.g., in the above example, the decoded target-URI is <code>http://www.example.com/entity123</code>. The target-URI MUST be an absolute URI, and the server SHOULD respond with <code>400 Bad Request</code> if it is not.
</p>
<p>
- A server SHOULD NOT offer a template containing <code>{+uri}</code> or other non-simple variable expansion options [[URI-template]] unless all valid entity-URIs for which it can provide provenance do not contain problematic characters like <code>'#'</code> or <code>'&'</code>.
+ A server SHOULD NOT offer a template containing <code>{+uri}</code> or other non-simple variable expansion options [[URI-template]] unless all valid target-URIs for which it can provide provenance do not contain problematic characters like <code>'#'</code> or <code>'&'</code>.
</p>
<p class="note">
- The defined URI template expansion process [[URI-template]] generally takes care of %-escaping characters that are not permitted in URIs. However, when expanding a template with <code>{+uri}</code>, some permitted characters such as <code>'#'</code> and <code>'&'</code> are not escaped. If the supplied entity-URI contains these characters, then they may disrupt interpretation of the resulting query URI. To prevent this, <code>'#'</code> and <code>'&'</code> characters in the entity-URI may be replaced with <code>%23</code> and <code>%26</code> respectively, before performing the URI template expansion. An alternative, simpler and more reliable approach is to use <code>{uri}</code> in the URI template string, which will cause all URI-reserved characters to be %-escaped as part of the URI-template expansion, as in the example above.
+ The defined URI template expansion process [[URI-template]] generally takes care of %-escaping characters that are not permitted in URIs. However, when expanding a template with <code>{+uri}</code>, some permitted characters such as <code>'#'</code> and <code>'&'</code> are not escaped. If the supplied target-URI contains these characters, then they may disrupt interpretation of the resulting query URI. To prevent this, <code>'#'</code> and <code>'&'</code> characters in the target-URI may be replaced with <code>%23</code> and <code>%26</code> respectively, before performing the URI template expansion. An alternative, simpler and more reliable approach is to use <code>{uri}</code> in the URI template string, which will cause all URI-reserved characters to be %-escaped as part of the URI-template expansion, as in the example above.
</p>
<p>
If the provenance described by the request is unknown to the server, a suitable error response code SHOULD be returned. In the absence of any security of privacy concerns about the resource, that might be <code>404 Not Found</code>. But if the existence or non-existence of a resource is considered private or sensitive, an authorization failure or other error response may be returned.
@@ -1037,7 +1033,7 @@
The pingback request supplies a list of <a class="internalDFN">provenance-URI</a>s from which forward provenance may be retrieved. The pingback service may do as it chooses with these URIs; e.g., it may choose to save them for later use, to retrieve the associated provenance and save that, to publish the URIs along with other provenance information about the original entity to which they relate, or even to ignore them.
</p>
<p>
- The client MAY further supply <code>#has_query_service</code> <code>Link:</code> headers indicating provenance query services that can describe the target-URI. The anchor MUST be included, and SHOULD be the entity-URI of the resource to which this pingback service belongs, or some related resource with relevant provenance.
+ The client MAY further supply <code>#has_query_service</code> <code>Link:</code> headers indicating provenance query services that can describe the target-URI. The anchor MUST be included, and SHOULD be the target-URI of the resource to which this pingback service belongs, or some related resource with relevant provenance.
</p>
<pre class="example code">
C: POST http://acme.example.org/pingback/super-widget HTTP/1.1
@@ -1191,7 +1187,7 @@
</tr>
<tr style="vertical-align: top;">
<td><code>has_anchor</code></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>Indicates a <a class="internalDFN">target-URI</a> for an resource, 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;">