Added describesService in appendix B
authorGraham Klyne
Tue, 26 Feb 2013 18:33:34 +0000
changeset 5759 473af1a90df2
parent 5758 211ff39ee699
child 5760 25eb1149862f
Added describesService in appendix B
paq/prov-aq.html
--- a/paq/prov-aq.html	Tue Feb 26 18:24:04 2013 +0000
+++ b/paq/prov-aq.html	Tue Feb 26 18:33:34 2013 +0000
@@ -1204,13 +1204,24 @@
             <td>Indicates a <a class="internalDFN">provenance query service</a> that can access provenance related to its subject or anchor resource.</td>
             <td><a href="#specifying-provenance-query-services" class="sectionRef"></a></td>
           </tr>
-
           <tr style="vertical-align: top;">
-            <td><code>prov:describesService</code></td>
-            <td>...</td>
-            <td><a href="#..." class="sectionRef"></a></td>
+            <td><code>describesService</code></td>
+            <td>relates a generic provenance query service resource (type <code>prov:ServiceDescription</code>) to a specific query service description (e.g. a <code>prov:DirectQueryService</code> or a <code>sd:Service</code>).</td>
+            <td><a href="#provenance-query-service-description" class="sectionRef"></a></td>
           </tr>
           <tr style="vertical-align: top;">
+            <td><code>provenanceUriTemplate</code></td>
+            <td>Indicates a URI template string for constructing provenance-URIs</td>
+            <td><a href="#direct-http-query-service-description" class="sectionRef"></a></td>
+          </tr>
+          <tr style="vertical-align: top;">
+            <td><code>pingback</code></td>
+            <td>Relates a resource to a provenance pingback service that may receive forward provenance links about the resource.</td>
+            <td><a href="#forward-provenance" class="sectionRef"></a></td>
+          </tr>
+
+          <!--
+          <tr style="vertical-align: top;">
             <td><code>...</code></td>
             <td>...</td>
             <td><a href="#..." class="sectionRef"></a></td>
@@ -1225,30 +1236,9 @@
             <td>...</td>
             <td><a href="#..." class="sectionRef"></a></td>
           </tr>
-
-
-
+          -->
 
-          <tr style="vertical-align: top;">
-            <td><code>provenanceUriTemplate</code></td>
-            <td>Indicates a URI template string for constructing provenance-URIs</td>
-            <td><a href="#direct-http-query-service-description" class="sectionRef"></a></td>
-          </tr>
-          <tr style="vertical-align: top;">
-            <td><code>pingback</code></td>
-            <td>Relates a resource to a provenance pingback service that may receive provenance about the resource.</td>
-            <td><a href="#forward-provenance" class="sectionRef"></a></td>
-          </tr>
         </table>
-        <p class="note">
-          It is tempting to think of <code>prov:DirectQueryService</code> as a particular kind of <code>prov:ServiceDescription</code>, but they are, in practice, distinct resources.
-          <br/>
-          <br/>
-          This is seen when one considers that a <code>prov:ServiceDescription</code> may have multiple query mechanisms associated with it (e.g. a <code>prov:DirectQueryService</code> <em>and</em> an <code>sd:Service</code>).  Also, they serve quite different purposes in the process of using provenance query services:  look for <code>prov:ServiceDescription</code> to discover query services of any kind, then for associated <code>prov:DirectQueryService</code> or <code>sd:Service</code> resources to get details of specific mechanisms to use to access the service.
-        </p>
-        <p class="TODO">
-          review pingback in light of Stian's proposal
-        </p>
     </section>
  
 <!-- ===================================================================================== -->