--- a/paq/prov-aq.html Tue Feb 26 10:44:26 2013 +0000
+++ b/paq/prov-aq.html Tue Feb 26 11:26:54 2013 +0000
@@ -580,10 +580,10 @@
S: Content-type: text/html
S: Link: <http://example.com/resource/provenance/>;
rel="http://www.w3.org/ns/prov#hasProvenance";
- anchor="http://example.com/resource/"
+ anchor="http://example.com/resource/20130226/content.html"
S:
- S: <html ...>
- S: :
+ S: <html>
+ S: <!-- HTML content here... -->
S: </html>
</pre>
</section>
@@ -603,7 +603,7 @@
<title>Welcome to example.com</title>
</head>
<body>
- ...
+ <!-- HTML content here... -->
</body>
</html></pre>
</div>
@@ -619,6 +619,9 @@
<p>
An HTML document header MAY present multiple <code><cite>provenance-URI</cite></code>s over several <code>#hasProvenance</code> link elements, indicating a number of different provenance records that are known to the publisher of the document, each of which may provide provenance about the document (see <a href="#interpreting-provenance-records" class="sectionRef"></a>).
</p>
+ <p class="TODO">
+ Check with Dong: I think the cross reference should make the assumptions explicit. I, too, feel this material is not strictly needed, but was previously asked to add some clarification about mutliple links.
+ </p>
<section>
<h2>Specifying Provenance Query Services</h2>
@@ -633,7 +636,7 @@
<title>Welcome to example.com</title>
</head>
<body>
- ...
+ <!-- HTML content here... -->
</body>
</html></pre>
<p>
@@ -642,7 +645,13 @@
<p>
There MAY be multiple <code>#hasQueryService</code> link elements, and these MAY appear in the same document as <code>#hasProvenance</code> link elements (though we do not anticipate that <code>#hasProvenance</code> and <code>#hasQueryService</code> link relations will commonly be used together).
</p>
+ <p class="TODO">
+ Check with Dong: This test was already revised in response to earlier comment.
+ I, too, feel this material is not strictly needed, but was previously asked to add some clarification.
+ </p>
+
</section>
+
</section>
<section>
@@ -710,6 +719,14 @@
<p>
The patterns for using provenance query services are designed around REST principles [[REST]], which aim to minimize coupling between client and server implementation details.
</p>
+ <p>
+ The remainder of this section covers the following topics:
+ </p>
+ <ul>
+ <li><a class="sectionRef" href="#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.</li>
+ <li><a class="sectionRef" href="#direct-http-query-service-invocation"></a> - describes how to perform a direct HTTP query for provenance, using information obtained from the service description.</li>
+ <li><a class="sectionRef" href="#provenance-query-service-discovery"></a> - briefly discusses some possible approaches to discovery of provenance query services.
+ </ul>
<!-- <section class="informative"> -->
<section>