--- a/paq/releases/WD-prov-aq-20130312/Overview.html Mon Mar 04 20:38:37 2013 +0100
+++ b/paq/releases/WD-prov-aq-20130312/Overview.html Mon Mar 04 20:39:46 2013 +0100
@@ -206,11 +206,11 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-WD"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
<body><div class="head">
<p>
- <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+ <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
</p>
<h1 class="title" id="title">PROV-AQ: Provenance Access and Query</h1>
@@ -411,7 +411,7 @@
<dd>
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 [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], 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>
- <a href="#dfn-provenance-record"><dfn id="dfn-provenance-record">Provenance record</dfn></a>
+ <dt><a href="#dfn-provenance-record"><dfn id="dfn-provenance-record">Provenance record</dfn></a></dt>
<dd>
refers to provenance represented in some fashion.
</dd>
@@ -855,10 +855,10 @@
<li>
<a class="sectionRef sec-ref" href="#provenance-query-service-description">section 4.1 Provenance query service description</a> - describes an RDF-based service description format and vocabularies to convey information about direct HTTP query and/or SPARQL service options.
<ul>
- <a class="sectionRef sec-ref" href="#direct-http-query-service-description">section 4.1.1 Direct HTTP query service description</a> - RDF structure for describing a direct HTTP query service.
+ <li> <a class="sectionRef sec-ref" href="#direct-http-query-service-description">section 4.1.1 Direct HTTP query service description</a> - RDF structure for describing a direct HTTP query service. </li>
</ul>
<ul>
- <a class="sectionRef sec-ref" href="#sparql-query-service-description">section 4.1.2 SPARQL query service description</a> - RDF structure for describing a SPARQL query service.
+ <li> <a class="sectionRef sec-ref" href="#sparql-query-service-description">section 4.1.2 SPARQL query service description</a> - RDF structure for describing a SPARQL query service.</li>
</ul>
</li>
<li><a class="sectionRef sec-ref" href="#direct-http-query-service-invocation">section 4.2 Direct HTTP query service invocation</a> - describes how to perform a direct HTTP query for provenance, using information obtained from the service description.</li>
@@ -997,10 +997,10 @@
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 target-URI is <code>http://www.example.com/entity123</code>, the resulting HTTP request would be:
- </p><div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example code">GET /provenance/service?<b>target</b>=http%3A%2F%2Fwww.example.com%2Fentity123 HTTP/1.1
+ 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:</p>
+ <div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example code">GET /provenance/service?<b>target</b>=http%3A%2F%2Fwww.example.com%2Fentity123 HTTP/1.1
Host: example.com</pre></div>
- <p></p>
+
<p>
Any server that implements this protocol and receives a request URI in this form <em class="rfc2119" title="SHOULD">SHOULD</em> return a provenance record for the target-URI embedded in the query component, where that URI is the result of percent-decoding [<cite><a class="bibref" href="#bib-RFC3986">RFC3986</a></cite>] 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 <em class="rfc2119" title="MUST">MUST</em> be an absolute URI, and the server <em class="rfc2119" title="SHOULD">SHOULD</em> respond with <code>400 Bad Request</code> if it is not.
</p>
@@ -1342,11 +1342,10 @@
</p>
<section id="changes-since-20120619-publication">
<h3><span class="secno">C.1 </span>Changes since 20120619 publication</h3>
- <p>
- </p><dl>
+ <dl>
<dt>2013-02-27 16:23 +0000 35385cbbfb9f Graham Klyne</dt><dd>Further refinements and bug fixes in the forward provenance section</dd>
<dt>2013-02-27 15:33 +0000 2dfd7fac85c9 Graham Klyne</dt><dd>Merge</dd>
-<dt>2013-02-27 15:19 +0000 bae275eaaf81 Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk></soiland-reyes@cs.manchester.ac.uk></dt><dd>Added Stian as PROV-AQ author</dd>
+<dt>2013-02-27 15:19 +0000 bae275eaaf81 Stian Soiland-Reyes</dt><dd>Added Stian as PROV-AQ author</dd>
<dt>2013-02-27 15:33 +0000 ecf3af571f1e Graham Klyne</dt><dd>Changed entity-URI back to target-URI, and updated concept definition to indicate it may also denote an activity</dd>
<dt>2013-02-27 13:02 +0000 d6085196a22d Graham Klyne</dt><dd>Some tidying up of section decsribing provenance pingback</dd>
<dt>2013-02-27 12:26 +0000 018e25f63183 Graham Klyne</dt><dd>Changed all normative references to informative (this being a NOTE)</dd>
@@ -1380,7 +1379,7 @@
<dt>2013-02-07 15:42 +0000 9406759adad3 Graham Klyne</dt><dd>Editorial fixes suggested by Simon</dd>
<dt>2013-02-07 14:50 +0000 d5e7a0c76495 Graham Klyne</dt><dd>Minor editorial fixes suggested by Ivan</dd>
<dt>2013-02-07 13:44 +0000 d4cf95c11dcd Graham Klyne</dt><dd>Minor editorial fixes suggested by Ivan</dd>
-<dt>2013-01-10 15:43 +0100 cb49c07522ff Paul Groth <p.t.groth@vu.nl></p.t.groth@vu.nl></dt><dd>updated to fix minor editorial errors</dd>
+<dt>2013-01-10 15:43 +0100 cb49c07522ff Paul Groth </dt><dd>updated to fix minor editorial errors</dd>
<dt>2013-01-04 14:23 +0000 47a1f3baf67a Graham Klyne</dt><dd>Editorial tweaks</dd>
<dt>2013-01-04 13:26 +0000 a374c48027b9 Graham Klyne</dt><dd>Separate prov:DirectQueryService (specifric mechanism) from prov:ProvenanceQueryService (generic)</dd>
<dt>2013-01-04 13:11 +0000 7b4580bd6d52 Graham Klyne</dt><dd>Fix some section cross-references; rename 'prov:hasProvenanceService' as 'prov:hasQueryService'</dd>
@@ -1417,9 +1416,8 @@
<dt>2012-11-08 12:12 +0000 098e7be8b4d5 Graham Klyne</dt><dd>Updated security considerations to mention audit</dd>
<dt>2012-11-06 17:04 +0000 96247e20c8b4 Graham Klyne</dt><dd>Add TODO for producer/consumer roles, add note about multiple links, add reference to RFC3986 for %-escaping</dd>
<dt>2012-11-06 15:17 +0000 4fbe51a47591 Graham Klyne</dt><dd>Update security considerations, note about non-RDF service desription, PROV-O link, acknowledgements</dd>
-<dt>2012-06-20 14:27 -0700 d0af0446868d Paul Groth <p.t.groth@vu.nl></p.t.groth@vu.nl></dt><dd>updated to reflect newly published version</dd>
+<dt>2012-06-20 14:27 -0700 d0af0446868d Paul Groth</dt><dd>updated to reflect newly published version</dd>
</dl>
- <p></p>
</section>
</section>