--- a/paq/provenance-access.html Thu Nov 17 17:27:38 2011 +0000
+++ b/paq/provenance-access.html Thu Nov 17 17:42:36 2011 +0000
@@ -31,11 +31,16 @@
"<a href=\"http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven\">REST APIs must be hypertext driven</a>. "+
"October 2008 (blog post), "+
"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":
+ "PROV-DM":
"L. Moreau; P. Missier. "+
"<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://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
+ "PROV-O":
+ "S. Sahoo, D. McGuinness"+
+ "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html\"><cite>PROV Ontology Model</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html/\">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a>",
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -121,8 +126,14 @@
<section>
<h2>Introduction</h2>
- <p class="TODO">
- @@TODO Introductory text
+ <p>
+ The Provenance Data Model [[PROV-DM]] and Provenance Ontology [[PROV-O]] specifications define how to represent provenance information in the World Wide Web.
+ </p>
+ <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>
@@ -135,7 +146,7 @@
<dt><dfn>Provenance-URI</dfn></dt>
<dd>a URI denoting some <a class="internalDFN">provenance information</a>.</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>
+ <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-DM]], 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>
@@ -360,10 +371,8 @@
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="TODO">
- @@TODO: example
- </p>
- <p class="TODO">
- @@TODO: document namespace. Check naming style. Use provenance model namespace? Define as part of model?
+ @@TODO: document namespace. Check naming style. Use provenance model namespace? Define as part of model?<br/>
+ @@TODO: example, when vocabulary issues are settled.
</p>
</section>
@@ -518,7 +527,7 @@
<section>
<h2>Provenance information</h2>
<p>
- Provenance information about a resource or resources may be returned in any format. It is recommended that the format be one defined by the Provenance Model specification [[PROV-MODEL]].
+ Provenance information about a resource or resources may be returned in any format. It is recommended that the format be one defined by the Provenance Model specification [[PROV-DM]].
</p>
<p>
Assuming a given resource URI <code>http://example.info/qdata/</code>, and