--- a/paq/WD-PROV-AQ-20111201.html Thu Dec 01 17:49:17 2011 +0000
+++ b/paq/WD-PROV-AQ-20111201.html Thu Dec 01 18:21:22 2011 +0000
@@ -612,9 +612,7 @@
</p>
<p>
A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a href="#iana-considerations" class="sectionRef">section 7. IANA considerations</a>, and may be used as shown::
- <code>
- </code></p><pre class="pattern"><code> Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</code></pre><code>
- </code>
+ </p><pre class="pattern"> Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
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 some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef">section 1.3 Interpreting provenance information</a>.)
<p></p>
<p>
@@ -641,12 +639,9 @@
<p>
The document provider may indicate that provenance information about the document is provided by a <a href="#dfn-provenance-service" class="internalDFN">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
</p>
- <code>
- <pre class="pattern"> Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
-
- </code>
- <p>
- The <code>provenance-service</code> link identifies the <a href="#dfn-service-uri" class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a> or retrieve <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> for an <a href="#dfn-entity" class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
+ <pre class="pattern">Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
+ <p>
+ The <code>provenance-service</code> link identifies the <a href="#dfn-service-uri" class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a> or retrieve <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> for an <a href="#dfn-entity" class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
</p>
<p>
There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same document as <code>provenance</code> links (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
@@ -660,8 +655,7 @@
<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">section 7. IANA considerations</a>, and may be used as shown:
- <code>
- </code></p><pre class="pattern"><code> <html xmlns="http://www.w3.org/1999/xhtml">
+ </p><pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance" href="<cite>provenance-URI</cite>">
<link rel="anchor" href="<cite>entity-URI</cite>">
@@ -670,9 +664,7 @@
<body>
...
</body>
- </html>
- </code></pre><code>
- </code>
+ </html></pre>
<p></p>
<p>
The <code><cite>provenance-URI</cite></code> given by the <code>provenance</code> link element identifies the provenance-URI for the document.
@@ -695,8 +687,7 @@
<p>
The document creator may specify that the provenance information about the document is provided by a <a href="#dfn-provenance-service" class="internalDFN">provenance service</a>. This is done through the use of a third link relation type following the same pattern as above:
</p>
- <code>
- <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
+ <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance-service" href="<cite>service-URI</cite>">
<link rel="anchor" href="<cite>entity-URI</cite>">
@@ -705,9 +696,7 @@
<body>
...
</body>
- </html>
- </pre>
- </code>
+ </html></pre>
<p>
The <code>provenance-service</code> link element identifies the <a href="#dfn-service-uri" class="internalDFN">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a href="#dfn-provenance-information" class="internalDFN">provenance information</a> for an <a href="#dfn-entity" class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
</p>
@@ -835,13 +824,11 @@
This example shows a provenance service description using JSON format [<cite><a href="#bib-RFC4627" rel="biblioentry" class="bibref">RFC4627</a></cite>], which is presented as MIME content-type <code>application/json</code>.
Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>.
</p>
- <code>
- <pre class="example">{
+ <pre class="example code">{
"provenance_service_uri": "http://example.org/provenance_service/",
"provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
"provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
}</pre>
- </code>
<p class="issue">
Is there any point in including the provenance service URI here? It has been included for consistency with RDF representations, but is functionally redundant.
</p>
@@ -859,8 +846,7 @@
This example uses JSON format [<cite><a href="#bib-RFC4627" rel="biblioentry" class="bibref">RFC4627</a></cite>], presented as MIME content type <code>application/json</code>.
Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>.
</p>
- <code>
- <pre class="example">{
+ <pre class="example code">{
"uri": "http://example.org/qdata/",
"provenance": [
"http://source1.example.org/provenance/qdata/",
@@ -868,7 +854,6 @@
"http://source3.example.com/prov?id=qdata"
]
}</pre>
- </code>
<p class="note">
The template might use <code>?uri={+uri}</code> rather than just <code>?uri={uri}</code>, and thereby avoid %-escaping the <code>:</code> and <code>/</code> characters in the given URI, but this could cause difficulties for URIs containing query parameters and/or fragment identifiers. In this case, the client application would need to ensure that any such characters were %-escaped <em>before</em> being passed into a URI-template expansion processor.
</p>
@@ -922,11 +907,11 @@
<p>
If the requester has an <a href="#dfn-entity-uri" class="internalDFN">entity-URI</a>, a simple SPARQL query may be used to return the corresponding <a href="#dfn-provenance-uri" class="internalDFN">provenance-URI</a>. E.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
<code>
- </code></p><pre class="example"><code> @prefix prov: <@@TBD>
- SELECT ?provenance_uri WHERE
- {
- <http://example.org/resource> prov:hasProvenance ?provenance_uri
- }
+ </code></p><pre class="example code"><code> @prefix prov: <@@TBD>
+ SELECT ?provenance_uri WHERE
+ {
+ <http://example.org/resource> prov:hasProvenance ?provenance_uri
+ }
</code></pre><code>
</code>
<p></p>
@@ -939,15 +924,12 @@
<h3><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</h3>
<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 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 [<cite><a href="#bib-PRISM" rel="biblioentry" class="bibref">PRISM</a></cite>] recommended by FaBio [<cite><a href="#bib-FABIO" rel="biblioentry" class="bibref">FABIO</a></cite>], might look like this:
- <code>
- </code></p><pre class="example"><code> @prefix prov: <@@TBD>
- @prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
- SELECT ?provenance_uri WHERE
- {
- [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
- }
- </code></pre><code>
- </code>
+ </p><pre class="example code">@prefix prov: <@@TBD>
+@prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
+SELECT ?provenance_uri WHERE
+{
+ [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
+}</pre>
<p></p>
<p class="TODO">
@@TODO: specific provenance namespace and property to be determined by the model specification?
@@ -961,18 +943,15 @@
</p>
<p>
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>
- </code></p><pre class="example"><code> @prefix prov: <@@TBD>
- CONSTRUCT
- {
- <http://example.org/resource> ?p ?v
- }
- WHERE
- {
- <http://example.org/resource> ?p ?v
- }
- </code></pre><code>
- </code>
+ </p><pre class="example code">@prefix prov: <@@TBD>
+CONSTRUCT
+{
+ <http://example.org/resource> ?p ?v
+}
+WHERE
+{
+ <http://example.org/resource> ?p ?v
+}</pre>
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>
<p class="TODO">
@@ -1151,13 +1130,11 @@
<p>
This example uses the RDF Turtle format [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>], presented as MIME content-type <code>text/turtle</code>.
</p>
- <code>
- <pre class="example">@prefix provds: <@@TBD@@#> .
+ <pre class="example code">@prefix provds: <@@TBD@@#> .
<http://example.org/provenance_service/> a provds:Service_description ;
provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
.</pre>
- </code>
<p class="note">
The provenance URI templates are encoded in RDF as plain string literals, <em>not</em> as resource URIs.
</p>
@@ -1169,8 +1146,7 @@
<div class="section" id="rdf-xml-example-of-service-description">
<h3><span class="secno">B.2 </span>RDF/XML example of service description</h3>
<p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a href="#bib-RDF-SYNTAX-GRAMMAR" rel="biblioentry" class="bibref">RDF-SYNTAX-GRAMMAR</a></cite>], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
- <code>
- <pre class="example"><rdf:RDF
+ <pre class="example code"><rdf:RDF
xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
xmlns:provds = "@@TBD@@#"
@@ -1180,7 +1156,6 @@
<provds:provenance_content_template>http://example.org/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
</provds:Service_description>
</rdf:RDF></pre>
- </code>
<p class="TODO">
Finalize URIs in the above example.
</p>
@@ -1198,14 +1173,12 @@
<p>
This example uses the RDF Turtle format [<cite><a href="#bib-TURTLE" rel="biblioentry" class="bibref">TURTLE</a></cite>], presented as MIME content type <code>text/turtle</code>.
</p>
- <code>
- <pre class="example">@prefix prov: <@@TBD@@#> .
+ <pre class="example code">@prefix prov: <@@TBD@@#> .
<http://example.org/qdata/> a prov:Entity ;
prov:hasProvenance <http://source1.example.org/provenance/qdata/> ;
prov:hasProvenance <http://source2.example.org/prov/qdata/> ;
prov:hasProvenance <http://source3.example.com/prov?id=qdata>
.</pre>
- </code>
<p class="issue">
NOTE: The namespace URI used here for the provenance properties is different from that used in the service description. I am anticipating that it will be defined as part of the provenance model. If it is not defined as part of the provenance model, then a property name should be allocated in the provenance discovery service namespace.
</p>
@@ -1217,8 +1190,7 @@
<p>
This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a href="#bib-RDF-SYNTAX-GRAMMAR" rel="biblioentry" class="bibref">RDF-SYNTAX-GRAMMAR</a></cite>], and presented with MIME content type <code>application/rdf+xml</code>.
</p>
- <code>
- <pre class="example"><rdf:RDF
+ <pre class="example code"><rdf:RDF
xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
xmlns:prov = "@@TBD@@#"
@@ -1229,7 +1201,6 @@
<prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
</prov:Entity>
</rdf:RDF></pre>
- </code>
<p class="issue">@@TODO: revise to conform with Provenance Model vocabulary</p>
</div>
--- a/paq/css/prov-aq.css Thu Dec 01 17:49:17 2011 +0000
+++ b/paq/css/prov-aq.css Thu Dec 01 18:21:22 2011 +0000
@@ -3,10 +3,15 @@
pre.pattern {
border-top: 1px solid #ff4500;
border-bottom: 1px solid #ff4500;
+ color: #ff4500;
padding: 1em;
margin-top: 1em;
}
+pre.code {
+ color: #ff4500;
+}
+
/*
pre.pattern::before {
content: "";
@@ -124,3 +129,4 @@
span.code {
font-family: monospace;
}
+
--- a/paq/prov-aq.html Thu Dec 01 17:49:17 2011 +0000
+++ b/paq/prov-aq.html Thu Dec 01 18:21:22 2011 +0000
@@ -276,10 +276,8 @@
</p>
<p>
A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a href="#iana-considerations" class="sectionRef"></a>, and may be used as shown::
- <code>
- <pre class="pattern">
- Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
- </code>
+ <pre class="pattern">
+ Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
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 some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef"></a>.)
</p>
<p>
@@ -306,13 +304,10 @@
<p>
The document provider may indicate that provenance information about the document is provided by a <a class="internalDFN">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
</p>
- <code>
- <pre class="pattern">
- Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
- </pre>
- </code>
- <p>
- The <code>provenance-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 determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
+ <pre class="pattern">
+Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
+ <p>
+ The <code>provenance-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 determine a <a class="internalDFN">provenance-URI</a> or retrieve <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
</p>
<p>
There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same document as <code>provenance</code> links (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
@@ -326,8 +321,7 @@
<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:
- <code>
- <pre class="pattern">
+ <pre class="pattern">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance" href="<cite>provenance-URI</cite>">
@@ -337,9 +331,7 @@
<body>
...
</body>
- </html>
- </pre>
- </code>
+ </html></pre>
</p>
<p>
The <code><cite>provenance-URI</cite></code> given by the <code>provenance</code> link element identifies the provenance-URI for the document.
@@ -362,8 +354,7 @@
<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>
- <code>
- <pre class="pattern">
+ <pre class="pattern">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="provenance-service" href="<cite>service-URI</cite>">
@@ -373,9 +364,7 @@
<body>
...
</body>
- </html>
- </pre>
- </code>
+ </html></pre>
<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 access <a class="internalDFN">provenance information</a> for an <a class="internalDFN">entity</a>; see <a href="#provenance-services" class="sectionRef"></a> for more details.
</p>
@@ -503,15 +492,13 @@
This example shows a provenance service description using JSON format [[RFC4627]], which is presented as MIME content-type <code>application/json</code>.
Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef"></a>.
</p>
- <code>
- <pre class="example">
- {
- "provenance_service_uri": "http://example.org/provenance_service/",
- "provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
- "provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
- }
- </pre>
- </code>
+ <pre class="example code">
+ {
+ "provenance_service_uri": "http://example.org/provenance_service/",
+ "provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
+ "provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
+ }
+ </pre>
<p class="issue">
Is there any point in including the provenance service URI here? It has been included for consistency with RDF representations, but is functionally redundant.
</p>
@@ -529,18 +516,16 @@
This example uses JSON format [[RFC4627]], presented as MIME content type <code>application/json</code>.
Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef"></a>.
</p>
- <code>
- <pre class="example">
- {
- "uri": "http://example.org/qdata/",
- "provenance": [
- "http://source1.example.org/provenance/qdata/",
- "http://source2.example.org/prov/qdata/",
- "http://source3.example.com/prov?id=qdata"
- ]
- }
- </pre>
- </code>
+ <pre class="example code">
+ {
+ "uri": "http://example.org/qdata/",
+ "provenance": [
+ "http://source1.example.org/provenance/qdata/",
+ "http://source2.example.org/prov/qdata/",
+ "http://source3.example.com/prov?id=qdata"
+ ]
+ }
+ </pre>
<p class="note">
The template might use <code>?uri={+uri}</code> rather than just <code>?uri={uri}</code>, and thereby avoid %-escaping the <code>:</code> and <code>/</code> characters in the given URI, but this could cause difficulties for URIs containing query parameters and/or fragment identifiers. In this case, the client application would need to ensure that any such characters were %-escaped <em>before</em> being passed into a URI-template expansion processor.
</p>
@@ -594,12 +579,12 @@
<p>
If the requester has an <a class="internalDFN">entity-URI</a>, a simple SPARQL query may be used to return the corresponding <a class="internalDFN">provenance-URI</a>. E.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
<code>
- <pre class="example">
- @prefix prov: <@@TBD>
- SELECT ?provenance_uri WHERE
- {
- <http://example.org/resource> prov:hasProvenance ?provenance_uri
- }
+ <pre class="example code">
+ @prefix prov: <@@TBD>
+ SELECT ?provenance_uri WHERE
+ {
+ <http://example.org/resource> prov:hasProvenance ?provenance_uri
+ }
</pre>
</code>
</p>
@@ -612,16 +597,14 @@
<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 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>
- @prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
- SELECT ?provenance_uri WHERE
- {
- [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
- }
- </pre>
- </code>
+ <pre class="example code">
+ @prefix prov: <@@TBD>
+ @prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
+ SELECT ?provenance_uri WHERE
+ {
+ [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
+ }
+ </pre>
</p>
<p class="TODO">
@@TODO: specific provenance namespace and property to be determined by the model specification?
@@ -635,19 +618,17 @@
</p>
<p>
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>
- CONSTRUCT
- {
- <http://example.org/resource> ?p ?v
- }
- WHERE
- {
- <http://example.org/resource> ?p ?v
- }
- </pre>
- </code>
+ <pre class="example code">
+ @prefix prov: <@@TBD>
+ CONSTRUCT
+ {
+ <http://example.org/resource> ?p ?v
+ }
+ WHERE
+ {
+ <http://example.org/resource> ?p ?v
+ }
+ </pre>
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">
@@ -826,15 +807,13 @@
<p>
This example uses the RDF Turtle format [[TURTLE]], presented as MIME content-type <code>text/turtle</code>.
</p>
- <code>
- <pre class="example">
- @prefix provds: <@@TBD@@#> .
- <http://example.org/provenance_service/> a provds:Service_description ;
- provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
- provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
- .
- </pre>
- </code>
+ <pre class="example code">
+ @prefix provds: <@@TBD@@#> .
+ <http://example.org/provenance_service/> a provds:Service_description ;
+ provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
+ provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
+ .
+ </pre>
<p class="note">
The provenance URI templates are encoded in RDF as plain string literals, <em>not</em> as resource URIs.
</p>
@@ -846,20 +825,18 @@
<section>
<h2>RDF/XML example of service description</h2>
<p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [[RDF-SYNTAX-GRAMMAR]], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
- <code>
- <pre class="example">
- <rdf:RDF
- xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
- xmlns:provds = "@@TBD@@#"
- >
- <provds:Service_description rdf:about="http://example.org/provenance_service/">
- example.org <provds:provenance_locations_template>http://example.org/provenance_service/locations/?uri={uri}</provds:location_template> ;
- <provds:provenance_content_template>http://example.org/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
- </provds:Service_description>
- </rdf:RDF>
- </pre>
- </code>
+ <pre class="example code">
+ <rdf:RDF
+ xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:provds = "@@TBD@@#"
+ >
+ <provds:Service_description rdf:about="http://example.org/provenance_service/">
+ example.org <provds:provenance_locations_template>http://example.org/provenance_service/locations/?uri={uri}</provds:location_template> ;
+ <provds:provenance_content_template>http://example.org/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
+ </provds:Service_description>
+ </rdf:RDF>
+ </pre>
<p class="TODO">
Finalize URIs in the above example.
</p>
@@ -877,16 +854,14 @@
<p>
This example uses the RDF Turtle format [[TURTLE]], presented as MIME content type <code>text/turtle</code>.
</p>
- <code>
- <pre class="example">
- @prefix prov: <@@TBD@@#> .
- <http://example.org/qdata/> a prov:Entity ;
- prov:hasProvenance <http://source1.example.org/provenance/qdata/> ;
- prov:hasProvenance <http://source2.example.org/prov/qdata/> ;
- prov:hasProvenance <http://source3.example.com/prov?id=qdata>
- .
- </pre>
- </code>
+ <pre class="example code">
+ @prefix prov: <@@TBD@@#> .
+ <http://example.org/qdata/> a prov:Entity ;
+ prov:hasProvenance <http://source1.example.org/provenance/qdata/> ;
+ prov:hasProvenance <http://source2.example.org/prov/qdata/> ;
+ prov:hasProvenance <http://source3.example.com/prov?id=qdata>
+ .
+ </pre>
<p class="issue">
NOTE: The namespace URI used here for the provenance properties is different from that used in the service description. I am anticipating that it will be defined as part of the provenance model. If it is not defined as part of the provenance model, then a property name should be allocated in the provenance discovery service namespace.
</p>
@@ -898,21 +873,19 @@
<p>
This is essentially the same as the Turtle example above, but encoded in RDF/XML [[RDF-SYNTAX-GRAMMAR]], and presented with MIME content type <code>application/rdf+xml</code>.
</p>
- <code>
- <pre class="example">
- <rdf:RDF
- xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
- xmlns:prov = "@@TBD@@#"
- >
- <prov:Entity rdf:about="http://example.org/qdata/">
- <prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;
- <prov:hasProvenance rdf:resource="http://source2.example.org/prov/qdata/" /> ;
- <prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
- </prov:Entity>
- </rdf:RDF>
- </pre>
- </code>
+ <pre class="example code">
+ <rdf:RDF
+ xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:prov = "@@TBD@@#"
+ >
+ <prov:Entity rdf:about="http://example.org/qdata/">
+ <prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source2.example.org/prov/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
+ </prov:Entity>
+ </rdf:RDF>
+ </pre>
<p class="issue">@@TODO: revise to conform with Provenance Model vocabulary</p>
</section>