--- a/paq/provenance-access.html Wed Nov 02 21:43:34 2011 -0400
+++ b/paq/provenance-access.html Fri Nov 04 11:45:39 2011 +0000
@@ -33,9 +33,9 @@
"URL: <a href=\"http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven\">http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</a>",
"PROV-MODEL":
"L. Moreau; P. Missier. "+
- "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/model/ProvenanceModel.html\"><cite>Provenance Model</cite></a>. "+
+ "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
"2011, Work in progress. "+
- "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/model/ProvenanceModel.html\">http://dvcs.w3.org/hg/prov/raw-file/tip/model/ProvenanceModel.html</a>",
+ "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -134,38 +134,34 @@
<dd>refers to provenance represented in some fashion.</dd>
<dt><dfn>Provenance-URI</dfn></dt>
<dd>a URI denoting some <a class="internalDFN">provenance information</a>.</dd>
- <dt><dfn>Context</dfn></dt>
- <dd>an entity, or aspect of a <a class="internalDFN">resource</a>, about which one wishes to present some <a class="internalDFN">provenance information</a>.</dd>
- <dt><dfn>Context-URI</dfn></dt>
- <dd>a URI denoting a context, which allows that context to be isolated in some provenance information (see <a href="#provenance-context"></a> for discussion)</dd>
+ <dt><dfn>Entity</dfn></dt>
+ <dd>an aspect of a <a class="internalDFN">resource</a>, about which one wishes 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. An entity is itself a <a class="internalDFN">resource</a>. See also [[PROV-MODEL]], and [[WEBARCH]] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
+ <dt><dfn>Entity-URI</dfn></dt>
+ <dd>a URI denoting an <a class="internalDFN">entity</a>, which allows that entity to be identified for the purpose of finding and expressing <a class="internalDFN">provenance information</a> (see <a href="#provenance-context" class="sectionRef"></a> for discussion)</dd>
<dt><dfn>Provenance service</dfn></dt>
- <dd>a service that provides a <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">provenance information</a> given a <a class="internalDFN">resource</a> URI or a <a class="internalDFN">context-URI</a>.</dd>
+ <dd>a service that provides a <a class="internalDFN">provenance-URI</a> or <a class="internalDFN">provenance information</a> given a <a class="internalDFN">resource</a> URI or an <a class="internalDFN">entity-URI</a>.</dd>
<dt><dfn>Service-URI</dfn></dt>
<dd>the URI of a <a class="internalDFN">provenance service</a>.</dd>
<dt><dfn>Resource</dfn></dt>
- <dd>also referred to as <dfn>web resource</dfn>: a resource as <a href="http://www.w3.org/TR/webarch/#id-resources">described</a> by the Architecture of the World Wide Web [[WEBARCH]], section 2.2. A resource may be associated with multiple <a title="context" class="internalDFN">contexts</a> (see <a href="#provenance-context" class="sectionRef"></a> for discussion)</dd>
+ <dd>also referred to as <dfn>web resource</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 <a title="Entity" class="internalDFN">entities</a> (see <a href="#provenance-context" class="sectionRef"></a> for discussion)</dd>
</dl>
</p>
- <p class="issue">
- The terms context and context-URI are chosen to align with terminology used in describing the HTTP link header (<a href="http://tools.ietf.org/html/rfc5988#section-5.2">http://tools.ietf.org/html/rfc5988#section-5.2</a>) - does this terminology work in the current (ahem) context? See also next section.
- </p>
-
</section>
<section>
- <h2 id="provenance-context">Provenance, context and resources</h2>
- <p class="pending">
- This section has been drafted to address a number of concerns: (a) to avoid previous use of "Target" for the topic of a provenance assertion (cf. http://www.w3.org/2011/prov/track/issues/74), and (b) to clarify the use of different resources as views on a dynamic or variable subject of provenance.
+ <h2 id="provenance-context">Provenance, entities and resources</h2>
+ <p>
+ Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resources</a>. In general, resources may vary over time and context. E.g., a resource describing the weather in London changes from day-to-day, or one listing 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 web resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
</p>
<p>
- Fundamentally, <a class="internalDFN">provenance information</a> is <em>about</em> <a class="internalDFN">resources</a>. In general, resources may vary over time and context: e.g., a resource describing the weather in London changes from day-to-day, or one listing 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-varying web resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
+ Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities. An <a class="internalDFN">entity</a> is simply a web resource that is a contextualized view or instance of an original web 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 through its lifetime. Separate URIs for each individual revision would then be <a class="internalDFN">entity-URIs</a>, denoting the specification at a 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.
</p>
<p>
- Provenance descriptions of dynamic and context-dependent resources are possible through the notion of contexts. A <a class="internalDFN">context</a> is simply a web resource that is a contextualized view or instance of an original web 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 through its lifetime. Separate URIs for each individual revision would then be context-URIs, denoting the specification at a 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.
+ Requests for provenance about a resource may return provenance information that uses one or more entity-URIs to refer to it. Some given provenance information may use multiple entity-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 entity-URIs of the various revisions.
</p>
<p>
- In summary, a key notion within the concepts outlined above is that <a class="internalDFN">provenance information</a> may be not universally applicable to a <a class="internalDFN">resource</a>, but may be described with respect to a restricted view of that resource (e.g. the resource at a particular time). This restricted view is termed a <a class="internalDFN">context</a>, and a <a class="internalDFN">context-URI</a> allows one to refer to that context within the provenance information. The context-URI used to describe this restricted view of a resource is also related to the resource itself, and requests for provenance about that resource may return provenance information that uses one or more context-URIs to refer to it. Some given provenance information may use multiple context-URIs if there are provenance assertions referring to the same underlying resource in different contexts. For example, a provenance resource describing a W3C document might include information about all revisions of the document using statements that use the different context-URIs for the revisions.
+ In summary, a key notion within the concepts outlined above is that <a class="internalDFN">provenance information</a> may be not universally applicable to a <a class="internalDFN">resource</a>, but may be expressed with respect to that resource in a restricted context (e.g. at a particular time). This restricted view is called an <a class="internalDFN">entity</a>, and an <a class="internalDFN">entity-URI</a> is used to refer to it within provenance information.
</p>
</section>
@@ -194,10 +190,10 @@
On the presumption that <a class="internalDFN">provenance information</a> is a resource that can be accessed using normal web retrieval, one needs to know a <a class="internalDFN">provenance-URI</a> to dereference. The provenance-URI may be known in advance, in which case 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. We also wish to allow that provenance information could be provided by parties other than the provider of the original resource. Indeed, provenance information for a resource may be provided by several different parties, at different URIs, each with different concerns. It is quite possible that different parties may provide contradictory provenance information.
</p>
<p>
- Once provenance information information is retrieved, one needs to know how to identify the view of that resource within that provenance information. This view is known as the <a class="internalDFN">context</a> and is identified by a <a class="internalDFN">context-URI</a>.
+ Once provenance information information is retrieved, one also needs to know how to locate the view of that resource within that provenance information. This view is an <a class="internalDFN">entity</a> and is identified by an <a class="internalDFN">entity-URI</a>.
</p>
<p>
- We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN">provenance-URI</a> along with a <a class="internalDFN">context-URI</a>. (Mechanisms that can be independent of the resource provision are discussed in <a href="#provenance-services" class="sectionRef"></a>). Three mechanisms are described here:
+ We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN">provenance-URI</a> along with a <a class="internalDFN">entity-URI</a>. (Mechanisms that can be independent of the resource provision are discussed in <a href="#provenance-services" class="sectionRef"></a>). Three mechanisms are described here:
<ul>
<li>The requester knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
<li>The requester has a copy of a resource presented as HTML or XHTML</li>
@@ -212,10 +208,10 @@
<section>
<h2>Resource accessed by HTTP</h2>
<p class="pending">
- The link relation indicating a context_URI has been called "anchor" (as opposed to, say, "context"), following terminology used for the HTTP Link element.
+ The link relation indicating an entity_URI has been called "anchor" (as opposed to, say, "entity"), following terminology used for the HTTP Link element.
</p>
<p class="issue">
- Pick one or allow either of the following options for indicating the context-URI?: I am inclined to specify the separate "provenance" and "anchor" and relation type, as that approach will be more consistent with the HTML and RDF options described below. If we do this, does it make sense to retain "anchor" as the link relation type?
+ Pick one or allow either of the following options for indicating the entity-URI?: I am inclined to specify the separate "provenance" and "anchor" and relation type, as that approach will be more consistent with the HTML and RDF options described below. If we do this, does it make sense to retain "anchor" as the link relation type? [Later] following discUssion with Paul, and with greater focus on specific Entity rather than context, I am now more inclined to use the second mechanism.
</p>
<p>
For a document 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).
@@ -223,28 +219,28 @@
<code>
<pre class="pattern">
Link: <cite>provenance-URI</cite>; rel="provenance"
- Link: <cite>context-URI</cite>; rel="anchor"</pre>
+ Link: <cite>entity-URI</cite>; rel="anchor"</pre>
</code>
or
<code>
<pre class="pattern">
- Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>context-URI</cite>"</pre>
+ Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
</code>
- When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated context is identified as <code><cite>context-URI</cite></code>.
+ When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>.
</p>
<p class="issue">
- [Yogesh]: I believe there is no guarantee that the provenance-URI will provide provenance information about the context-URI. Suggest we use *should* rather than (implicitly) *must* to state that the returned provenance-uri should have provenance information about the resource view identified by the context-uri.
+ [Yogesh]: I believe there is no guarantee that the provenance-URI will provide provenance information about the entity-URI. Suggest we use *should* rather than (implicitly) *must* to state that the returned provenance-uri should have provenance information about the resource view identified by the entity-uri.
<br/><br/>
-I think I see your point, but I am concerned that making that possibility explicit here might be confusing for a reader. I wonder if this would be better served by a new sub-section in sect 2 about interpreting provenance information?
+I think I see your point, but I am concerned that making that possibility explicit here might be confusing for a reader. I wonder if this would be better served by a new sub-section after sect 1.2 about interpreting provenance information?
</p>
<p>
- If no <code>anchor</code> link is provided then the <code><cite>context-URI</cite></code> is assumed to be the URI of the resource.
+ If no <code>anchor</code> link is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the resource.
</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.
</p>
<p>
- An HTTP response MAY include multiple <code>provenance</code> link headers, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource. Likewise, an HTTP response MAY include multiple <code>anchor</code> link headers, that indicate the resource may have provenance information associated with all of the indicated <code><cite>context-URIs</cite></code>.
+ An HTTP response MAY include multiple <code>provenance</code> link headers, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource. Likewise, an HTTP response MAY include multiple <code>anchor</code> link headers, that indicate the resource may have provenance information associated with all of the indicated <code><cite>entity-URI</cite>s</code>.
</p>
<p>
The presence of a provenance link in an HTTP response does not preclude the possibility that other publishers may offer provenance information about the same resource. In such cases, discovery of the additional provenance information must use other means (e.g. see <a href="#provenance-services" class="sectionRef"></a>).
@@ -269,7 +265,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance" href="<cite>provenance-URI</cite>">
- <link rel="anchor" href="<cite>context-URI</cite>">
+ <link rel="anchor" href="<cite>entity-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -283,16 +279,16 @@
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>context-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the presented document view, and which may be used within the provenance information when referring to this document.
+ The <code><cite>entity-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the presented document view, and which may be used within the provenance information when referring to this document.
</p>
<p>
An HTML document header MAY include multiple "provenance" link elements, indicating a number of different provenance resources that are known to the creator of the document, each of which may provide provenance information about 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>context-URIs</cite></code>.
+ 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>entity-URIs</cite></code>.
</p>
<p>
- If no "anchor" link element is provided then the <code><cite>context-URI</cite></code> is assumed to be the URI of the document. It is RECOMMENDED that this only be done when the document is static.
+ If no "anchor" 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 is static.
</p>
<p class="issue">
Proposing to remove the following Note:
@@ -319,7 +315,7 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance-service" href="<cite>service-URI</cite>">
- <link rel="anchor" href="<cite>context-URI</cite>">
+ <link rel="anchor" href="<cite>entity-URI</cite>">
<title>Welcome to example.com</title>
</head>
<body>
@@ -329,8 +325,8 @@
</pre>
</code>
<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 determine a <a class="internalDFN">provenance-URI</a> for a <a class="internalDFN">context</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
- There may be multiple <code>provenance-service</code> link elements, and these MAY appear in the same document as <code>anchor</code> and <code>provenance</code> link elements (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations would not both be used).
+ 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 determine a <a class="internalDFN">provenance-URI</a> for a <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ There may be multiple <code>provenance-service</code> link elements, and these MAY appear in the same document as <code>anchor</code> and <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).
</p>
</section>
<p class="note">
@@ -347,11 +343,13 @@
For this purpose a new 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.
</p>
<p>
- Another new RDF property, <code>prov:hasContext</code>, is defined to allow the RDF content to specify one or more context-URIs of the RDF document for the purpose of provenance information (similar to the use of the "anchor" link relation in HTML).
+ Another new RDF property, <code>prov:hasAnchor</code>, is defined to allow the RDF content to specify one or more <a class="internalDFN">entity-URI</a>s of the RDF document for the purpose of provenance information (similar to the use of the "anchor" link relation in HTML).
</p>
<p class="issue">
@@TODO: needs to be completed.
<br/><br/>
+ Review choice of RDF property names
+ <br/><br/>
Discussion:
<br/><br/>
The containing RDF resource is the subject. For RDF documents, this is sometimes written as an empty URI-reference; e.g.<br/>
@@ -379,7 +377,7 @@
If a resource is presented using a data format other than HTML or RDF, and no URI for the resource is known, provenance discovery becomes trickier to achieve. This specification does not define a specific mechanism for such arbitrary resources, but this section discusses some of the options that might be considered.
</p>
<p>
- For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a <a class="internalDFN">context-URI</a>, <a class="internalDFN">provenance-URI</a> and/or <a class="internalDFN">service-URI</a>. Format-specific metadata provision might also be used to include <a class="internalDFN">provenance information</a> directly in the resource.
+ For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a <a class="internalDFN">entity-URI</a>, <a class="internalDFN">provenance-URI</a> and/or <a class="internalDFN">service-URI</a>. Format-specific metadata provision might also be used to include <a class="internalDFN">provenance information</a> directly in the resource.
</p>
<p>
Use a generic packaging format that can combine an arbitrary data file with a separate metadata file in a known format, such as RDF. At this time, it is not clear what format that should be, but some possible candidates are:
@@ -432,7 +430,7 @@
<section>
<h2>Retrieve Provenance-URIs for a resource</h2>
<p>
- To use the provenance service to retrieve a list of provenance-URIs for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or context (<code>context-URI</code>):
+ To use the provenance service to retrieve a list of provenance-URIs for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or entity (<code>entity-URI</code>):
<ol>
<li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN">service description</a>.</li>
<li>Extract the provenance locations template from the service description.</li>
@@ -453,7 +451,7 @@
<li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN">service description</a>.</li>
<li>Extract the provenance information template from the service description.</li>
<li>Use the provenance information template with <code>context-URI</code> for template variable <code>uri</code> to form <code>provenance-URI</code>.</li>
- <li>Dereference <code>provenance-URI</code> to obtain <a class="internalDFN">provenance information</a> as described by the Provenance Model specification [[PROV-MODEL]].</li>
+ <li>Dereference <code>provenance-URI</code> to obtain <a class="internalDFN">provenance information</a> (@@redundant, maybe misleading: as described by the Provenance Model specification [[PROV-MODEL]]@@).</li>
</ol>
</p>
</section>
@@ -558,9 +556,9 @@
</p>
<section>
- <h2>Find provenance-URI given context-URI of resource</h2>
+ <h2>Find provenance-URI given entity-URI of resource</h2>
<p>
- If the requester has a context-URI for the original resource, they might simply issue a simple SPARQL query for the URI(s) of any associated provenance information; e.g., if the original resource has a context-URI <code>http://example.org/resource</code>,
+ If the requester has an entity-URI for the original resource, they might simply issue a simple SPARQL query for the URI(s) of any associated provenance information; e.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
<code>
<pre class="example">
@prefix prov: <@@TBD>
@@ -572,14 +570,14 @@
</code>
</p>
<p class="issue">
- @@TODO: specific provenance namespace and property to be determined by the model specification?
+ @@TODO: specific provenance namespace and property to be determined by the model or ontology specification?
</p>
</section>
<section>
<h2>Find Provenance-URI given identifying information about a resource</h2>
<p>
- If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate a context resource and obtain its provenance-URI(s). The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification. For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [[PRISM]] recommended by FaBio [[FABIO]], might look like this:
+ If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate an entity description and obtain its provenance-URI(s). The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification. For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [[PRISM]] recommended by FaBio [[FABIO]], might look like this:
<code>
<pre class="example">
@prefix prov: <@@TBD>
@@ -597,12 +595,12 @@
</section>
<section>
- <h2>Obtain provenance information directly given context-URI of a resource</h2>
+ <h2>Obtain provenance information directly given an entity-URI of a resource</h2>
<p>
- This scenario retrieves provenance information directly given the URI of a resource, and may be useful where the provenance information has not been assigned a specific URI, or when the calling application is interested only in specific elements of provenance information.
+ This scenario retrieves provenance information directly given the URI of a resource or entity, and may be useful where the provenance information has not been assigned a specific URI, or when the calling application is interested only in specific elements of provenance information.
</p>
<p>
- If the original resource has a context-URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this:
+ If the original resource has an entity-URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this:
<code>
<pre class="example">
@prefix prov: <@@TBD>
@@ -616,10 +614,10 @@
}
</pre>
</code>
- This query essentially extracts all available properties and values available from the query service used that are directly about the specified context resource, and returns them as an RDF graph. This may be fine if the service contains <em>only</em> provenance information about the indicated resource, or if the non-provenance information is also of interest. A more complex query using specific provenance vocabulary terms may be needed to selectively retrieve just provenance information when other kinds of information are also available.
+ This query essentially extracts all available properties and values available from the query service used that are directly about the specified entity, and returns them as an RDF graph. This may be fine if the service contains <em>only</em> provenance information about the indicated resource, or if the non-provenance information is also of interest. A more complex query using specific provenance vocabulary terms may be needed to selectively retrieve just provenance information when other kinds of information are also available.
</p>
<p class="issue">
- @@TODO: specific provenance namespace and property to be determined by the model specification? The above query pattern assumes provenance information is included in direct properties about the context resource. When an RDF provenance vocabulary is formulated, this may well turn out to not be the case. A better example would probably be one that retrieves specific provenance information when the vocabulary terms have been defined.
+ @@TODO: specific provenance namespace and property to be determined by the model specification? The above query pattern assumes provenance information is included in direct properties about the entity. When an RDF provenance vocabulary is formulated, this may well turn out to not be the case. A better example would probably be one that retrieves specific provenance information when the vocabulary terms have been defined.
</p>
</section>
@@ -654,7 +652,7 @@
</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
+ the resource identified by target IRI of the link provides provenance information about the entity identified by the context link
</dd>
<dt>Reference:</dt>
<dd>
@@ -674,7 +672,7 @@
<section>
<h2>Registration template for link relation: "anchor"</h2>
<p class="pending">
- The name "anchor" has been used for the link relation name, despite the corresponding URI being described as a context-URI. This terminology has been chosen to align with usage in the description of the HTTP Link header field, per <a href="http://tools.ietf.org/html/rfc5988#section-5.2">RFC 5988</a>.
+ The name "anchor" has been used for the link relation name, despite the corresponding URI being described as an entity-URI. This terminology has been chosen to align with usage in the description of the HTTP Link header field, per <a href="http://tools.ietf.org/html/rfc5988#section-5.2">RFC 5988</a>.
</p>
<p>
<dl>
@@ -684,7 +682,7 @@
</dd>
<dt>Description:</dt>
<dd>
- the resource identified by target URI of the link is a context-URI 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 contexts.
+ the resource identified by target URI of the link is an entity-URI 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>