Expanded discussion of provenance service discovery to include prov:hasProvenanceService
--- a/paq/prov-aq.html Tue Nov 20 08:44:29 2012 -0500
+++ b/paq/prov-aq.html Tue Nov 20 14:03:18 2012 +0000
@@ -84,6 +84,12 @@
"<a href=\"http://doi.acm.org/10.1145/1349026.1349043\">http://doi.acm.org/10.1145/1349026.1349043</a>, "+
"<a href=\"http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf\">http://dig.csail.mit.edu/2008/06/info-accountability-cacm-weitzner.pdf</a> (alt)",
+ "VOiD":
+ "Keith Alexander, Richard Cyganiak, Michael Hausenblas, Jun Zhao. "+
+ "<a href=\"http://www.w3.org/TR/void/\"><cite>Describing Linked Datasets with the VoID Vocabulary</cite></a>, "+
+ "W3C Interest Group Note 03 March 2011, "+
+ "<a href=\"http://www.w3.org/TR/void/\">http://www.w3.org/TR/void/</a>"
+
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -624,11 +630,16 @@
This specification does not define any specific mechanism for discovering provenance services. Applications may use any appropriate mechanism, including but not limited to: prior configuration, search engines, service registries, etc.
</p>
<p>
- To facilitate service discovery, we recommend that RDF publication of service descriptions uses the provenance service type <code>prov:ProvenanceService</code>, defined by the provenance ontology [[PROV-O]].
- The RDF service description example below in <a href="#provenance-service-description" class="sectionRef"></a> shows this use.
+ To facilitate service discovery, we recommend that RDF publication of dataset and service descriptions use the property <code>prov:hasProvenanceService</code> and the provenance service type <code>prov:ProvenanceService</code> as appropriate (see the appendix <a href="#prov-namespace" class="sectionRef"></a>).
</p>
- <p class="TODO">
- @@TODO: rework the above to take account of hasProvenanceService links
+ <p>
+ For example, a VOiD description [[VOiD]] of a dataset might indicate a provenance service providing information resources in that dataset:
+ </p>
+ <pre class="pattern">
+ <http://example.org/dataset/> a void:Dataset ;
+ prov:hasProvenanceService <http://example.org/provenance/> .</pre>
+ <p>
+ The RDF service description example below in <a href="#provenance-service-description" class="sectionRef"></a> shows use of the <code>prov:ProvenanceService</code> type.
</p>
</section>
@@ -704,7 +715,7 @@
<!-- ===================================================================================== -->
<section class='appendix'>
- <h2>Names added to prov: namespace</h2>
+ <h2 id="prov-namespace">Names added to prov: namespace</h2>
<p>
This specification defines the following additional names in the provenance namespace
@@ -716,7 +727,7 @@
</tr>
<tr style="vertical-align: top;">
<td>ProvenanceService</td>
- <td>Class for a provenance service. Mainly for use in RDF provenance service descriptions, to facilitate discover..</td>
+ <td>Class for a provenance service. Mainly for use in RDF provenance service descriptions, to facilitate discovery.</td>
<td><a href="#provenance-service-description" class="sectionRef"></a></td>
</tr>
<tr style="vertical-align: top;">
@@ -732,7 +743,7 @@
</tr>
<tr style="vertical-align: top;">
<td>hasProvenanceService</td>
- <td>Indicates a <a class="internalDFN">provenance service</a> that can provide provenance information about its sibject or anchowresource.</td>
+ <td>Indicates a <a class="internalDFN">provenance service</a> that can provide provenance information about its subject or anchor resource.</td>
<td><a href="#specifying-provenance-services" class="sectionRef"></a></td>
</tr>
<tr style="vertical-align: top;">