--- a/paq/prov-aq.html Thu Dec 01 13:54:55 2011 +0000
+++ b/paq/prov-aq.html Thu Dec 01 14:08:33 2011 +0000
@@ -132,9 +132,6 @@
<p>
This note describes how existing web mechanisms may be used to locate, retrieve and query provenance information.
</p>
- <p class="issue">
- More introduction needed?
- </p>
<section>
<h2>Concepts</h2>
@@ -285,9 +282,6 @@
<section>
<h2>Resource represented as HTML</h2>
- <p class="pending">
- Addresses <a href="http://www.w3.org/2011/prov/track/issues/46">ISSUE 46</a> by adding "anchor" link-relation.
- </p>
<p>
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><Link></code> element to the HTML <code><head></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:
@@ -321,18 +315,9 @@
<p>
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:
- </p>
- <p class="note">
- See <a href="http://tools.ietf.org/html/rfc5988#appendix-A">Appendix A. Notes on Using the Link Header with the HTML4 Format</a> of RFC 5988 for further notes about using link relation types in HTML.
- </p>
<section>
<h2>Specifying Provenance Services</h2>
- <p class="pending">
- This is a new proposal. It needs to be reviewed as to whether it is useful.
- </p>
<p>
The document creator may specify that the provenance information about the document is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a third link relation type following the same pattern as above:
</p>
@@ -414,10 +399,6 @@
<section>
<h2>Provenance services</h2>
- <p class="pending">
- Propose simple HTTP interface for discovery. cf <a href="http://www.w3.org/2011/prov/track/issues/53">ISSUE 53</a>.
- This should be properly RESTful, per <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>. Have I properly interpreted the principles indicated here?
- </p>
<p>
This section describes a REST API [[REST-APIs]] for a provenance service with facilities for discovery and/or retrieval of provenance information, which can be implemented independently of the original resource delivery channels (e.g. by a third party service).
</p>
@@ -551,9 +532,6 @@
<section>
<h2>Querying provenance information</h2>
- <p class="pending">
- This section proposes use of SPARQL queries to address requirements that are not covered by the simple retrieval and discovery services proposed above.
- </p>
<p>
Simply identifying and retrieving provenance information as a web resource may not always meet the requirements of a particular application or service, e.g.:
<ul>
@@ -632,7 +610,7 @@
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="TODO">
- @@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.
+ @@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 fully formulated, this may well turn out to not be the case. A better example would be one that retrieves specific provenance information when the vocabulary terms have been defined.
</p>
</section>
@@ -718,7 +696,7 @@
</dd>
<dt>Description:</dt>
<dd>
- the resource identified by target IRI of the link is an entity 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.
+ when used in conjunction with a "provenance" link, the resource identified by target IRI of the link is an entity 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>
@@ -780,9 +758,6 @@
<p class="TODO">
@@TODO ... privacy, access control to provenance (note to self: discussed in Edinburgh linked data provenance workshop). In particular, note that the fact that a resource is openly accessible does not mean that its provenance information should also be.
</p>
- <p class="TODO">
- @@TODO ... more, probably
- </p>
</section>
<!-- ===================================================================================== -->