prov-implementations: minor editorial fixes
authorTrung Dong Huynh <tdh@ecs.soton.ac.uk>
Thu, 11 Apr 2013 15:31:52 +0100
changeset 6129 057c642b9044
parent 6128 915883486cdb
child 6130 3edb9a029518
prov-implementations: minor editorial fixes
reports/NOTE-prov-implementations-20130430/Overview.html
reports/prov-implementations.html
--- a/reports/NOTE-prov-implementations-20130430/Overview.html	Thu Apr 11 12:36:34 2013 +0100
+++ b/reports/NOTE-prov-implementations-20130430/Overview.html	Thu Apr 11 15:31:52 2013 +0100
@@ -17,7 +17,7 @@
     color: #b9ab2d;
 }
 div.issue-title { color: #e05252; }
-div.note-title { color: #52e052; }
+div.note-title { color: #2b2; }
 div.issue-title span, div.note-title span {
     text-transform: uppercase;
 }
@@ -32,7 +32,7 @@
     border-left-style: solid;
 }
 div.issue, div.note {
-    padding: 0.5em;
+    padding: 1em 1.2em 0.5em;
     margin: 1em 0;
     position: relative;
     clear: both;
@@ -236,9 +236,8 @@
           index</a> at http://www.w3.org/TR/.</em>
         </p>
         
-      During the Candidate Recommendation period of PROV, implementation experience was reported. This document summarises those experiences. The version at <a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</a> is the version used for purposes of transition to proposed recommendation. 
-
-For comments, please send a mail to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> [<a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archive</a>].
+      During the lifetime of the Provenance Working Group, implementation experience of the PROV specifications was reported. This document summarises those experiences. The version at <a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</a> is the version used for purposes of transition to proposed recommendation.
+      For comments, please send a mail to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> [<a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archive</a>].
     
         <p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a Working Group Note.
@@ -285,7 +284,7 @@
     
   
 </section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#Introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#Exit-Criteria" class="tocxref"><span class="secno">1.1 </span> Meeting the Exit Criteria</a></li></ul></li><li class="tocline"><a href="#implementations" class="tocxref"><span class="secno">2. </span>List of Implementations</a></li><li class="tocline"><a href="#Feature-Coverage" class="tocxref"><span class="secno">3. </span> Feature Coverage</a><ul class="toc"><li class="tocline"><a href="#prov-terms" class="tocxref"><span class="secno">3.1 </span>PROV Usage </a></li><li class="tocline"><a href="#prov-extensions" class="tocxref"><span class="secno">3.2 </span>PROV Usage by Extension</a></li><li class="tocline"><a href="#prov-usage" class="tocxref"><span class="secno">3.3 </span>PROV Usage in Datasets</a></li><li class="tocline"><a href="#prov-contraints" class="tocxref"><span class="secno">3.4 </span>PROV Constraints Implementation</a></li></ul></li><li class="tocline"><a href="#prov-exchange" class="tocxref"><span class="secno">4. </span>Implementations Exchanging Provenance</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.1 </span>Informative references</a></li></ul></li></ul></section>
-	
+    
     
     <section id="Introduction">
       <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
@@ -309,7 +308,7 @@
 
     <section id="Exit-Criteria">
       <h3><span class="secno">1.1 </span> Meeting the Exit Criteria</h3>
-      <p>At the start of the Candidate Recommendation phase, the Working Group defined <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">a series of exit criteria</a>. These exit criteria can be summarized as for each feature defined by PROV there are at least two implementations that support the feature and that there exists one interoperability pair that can exchange that feature. Section <a href="#prov-terms">3.1</a> shows that a minimum of 4 implementations both produce and consume all constructs defined in PROV-DM. PROV-O is implemented by over 40 implementations and PROV-N is implemented by 7 implementations.</p>
+      <p>At the start of the Candidate Recommendation phase, the Working Group defined <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">a series of exit criteria</a>. These exit criteria can be summarized as for each feature defined by PROV there are at least two implementations that support the feature and that there exists one interoperability pair that can exchange that feature. Section <a href="#prov-terms">3.1</a> shows that three implementations both produce and consume all constructs defined in PROV-DM. PROV-O is implemented by over 40 implementations and PROV-N is implemented by 12 implementations.</p>
       <p>In terms of implementation pairs, Section <a href="#prov-exchange">4</a> enumerates which pairs of implementations report exchanging provenance. Here, we meet the exit criteria in that each feature is exchanged by at least two implementations.</p>
       <p>Finally, three validators have implemented all of the constraints defined in PROV-Constraints passing the requisite test cases, thus, passing the exit criteria.  The working group recognizes that implementing the PROV-Constraints document requires substantial effort. It is nice to see that three radically different approaches were chosen to implement this specification: SPARQL, Java, Prolog, which speaks to the implementability of this specification.</p>
       <p>For a systematic enumeration of how the exit criteria were met, please see <a href="http://www.w3.org/2011/prov/wiki/MeetingProvCRExitCriteria"> http://www.w3.org/2011/prov/wiki/MeetingProvCRExitCriteria</a></p>
@@ -362,7 +361,7 @@
         </tr>
         <tr id="5">
           <td>5</td>
-          <th scope="row"><a href="http://www.collabmap.org/">CollabMap</a></th>
+          <th scope="row"><a href="http://www.orchid.ac.uk/collabmap">CollabMap</a></th>
           <td>Application</td>
           <td>PROV-JSON</td>
         </tr>
@@ -376,7 +375,7 @@
           <td>7</td>
           <th scope="row"><a href="https://github.com/lucmoreau/ProvToolbox">ProvToolbox</a></th>
           <td>Framework / API<br>Service</td>
-          <td>PROV-O, PROV-N, PROV-XML, prov-json</td>
+          <td>PROV-O, PROV-N, PROV-XML, PROV-JSON</td>
         </tr>
         <tr id="8">
           <td>8</td>
@@ -434,13 +433,13 @@
         </tr>
         <tr id="17">
           <td>17</td>
-          <th scope="row"><a href="https://provenance.ecs.soton.ac.uk/store">Provenance server</a></th>
+          <th scope="row"><a href="https://provenance.ecs.soton.ac.uk/store/">Provenance server</a></th>
           <td>Service</td>
           <td>PROV-N, PROV-JSON</td>
         </tr>
         <tr id="18">
           <td>18</td>
-          <th scope="row"><a href="http://hac.ecs.soton.ac.uk/agentswitch/">agentSwitch</a></th>
+          <th scope="row"><a href="http://www.orchid.ac.uk/agentswitch">agentSwitch</a></th>
           <td>Application</td>
           <td>PROV-N, PROV-JSON</td>
         </tr>
@@ -620,7 +619,7 @@
         </tr>
         <tr id="48">
           <td>48</td>
-          <th scope="row"><a href="http://purl.org/net/provenance/ns">Jun Zhao</a></th>
+          <th scope="row"><a href="http://purl.org/net/provenance/ns">Provenance Vocabulary Core Ontology Specification</a></th>
           <td>Vocabulary Extension</td>
           <td>PROV-O</td>
         </tr>
@@ -2452,7 +2451,7 @@
         <th scope="col"><a href="#45" title="roevo">#45</a></th>
         <th scope="col"><a href="#46" title="wfprov">#46</a></th>
         <th scope="col"><a href="#47" title="P-plan">#47</a></th>
-        <th scope="col"><a href="#48" title="Jun Zhao">#48</a></th>
+        <th scope="col"><a href="#48" title="Provenance Vocabulary Core Ontology Specification">#48</a></th>
         <th scope="col"><a href="#49" title="Systems molecular biology provenance ontology (SysPro) ">#49</a></th>
         <th scope="col"><a href="#50" title="Yanfeng Shu">#50</a></th>
         <th scope="col"><a href="#51" title="ISO_19115_Lineage">#51</a></th>
@@ -3742,7 +3741,7 @@
           <td class="implemented">&nbsp;</td>
         </tr>
     </tbody></table>
-    <div class="note"><div class="note-title"><span>Note</span></div><div class="">
+    <div class="note"><div class="note-title" role="heading" aria-level="4"><span>Note</span></div><div class="">
       <p>The table above was produced from the results of running
       <a href="http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html">PROV-CONSTRAINTS
       test cases</a> submitted by implementers.</p>
@@ -4190,7 +4189,7 @@
         <td>2</td>
        </tr>      
     </tbody></table>
-     <div class="note"><div class="note-title"><span>Note</span></div><p class="">Although the Provenance Server (#17) and the ProvValidator (#65) are from the same institution (i.e. University of Southampton), it is worth noting that they were built from two independent code bases (one in Python and the other in Java)</p></div>
+     <div class="note"><div class="note-title" role="heading" aria-level="3"><span>Note</span></div><p class="">Although the Provenance Server (#17) and the ProvValidator (#65) are from the same institution (i.e. University of Southampton), it is worth noting that they were built from two independent code bases (one in Python and the other in Java)</p></div>
   </section>
 
   <section class="appendix" id="acknowledgements"> 
--- a/reports/prov-implementations.html	Thu Apr 11 12:36:34 2013 +0100
+++ b/reports/prov-implementations.html	Thu Apr 11 15:31:52 2013 +0100
@@ -49,9 +49,9 @@
           editors:  [
               { name: "Trung Dong Huynh", url: "http://www.ecs.soton.ac.uk/~tdh/",
                 company: "University of Southampton" },
-			  { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
+              { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
                 company: "VU University Amsterdam" },
-			  { name: "Stephan Zednik", url: "http://tw.rpi.edu/web/person/StephanZednik",
+              { name: "Stephan Zednik", url: "http://tw.rpi.edu/web/person/StephanZednik",
                 company: "Rensselaer Polytechnic Institute" },
           ],
  
@@ -87,10 +87,9 @@
     <section id="abstract">
       <p>This document reports on implementations and usage of the four normative specifications ([[PROV-DM]], [[PROV-N]], [[PROV-O]], [[PROV-CONSTRAINTS]]) of the PROV Family of Documents [[PROV-OVERVIEW]]. In particular, it's aim is to demonstrate that the features defined in PROV are implementable and interoperable. Features are defined as: the constructs specified in [[PROV-DM]] and their realisation in OWL (see [[PROV-O]]) and in the [[PROV-N]] syntax; the constraints defined within [[PROV-CONSTRAINTS]]. Interoperability is defined through both the interchange of provenance information and the coverage of test cases.     </p>
     </section>
-	<section id="sotd">
-      During the Candidate Recommendation period of PROV, implementation experience was reported. This document summarises those experiences. The version at <a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</a> is the version used for purposes of transition to proposed recommendation. 
-
-For comments, please send a mail to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> [<a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archive</a>].
+    <section id="sotd">
+      During the lifetime of the Provenance Working Group, implementation experience of the PROV specifications was reported. This document summarises those experiences. The version at <a href="http://www.w3.org/TR/2013/WD-prov-implementations-20130312/">http://www.w3.org/TR/2013/WD-prov-implementations-20130312/</a> is the version used for purposes of transition to proposed recommendation.
+      For comments, please send a mail to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> [<a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archive</a>].
     </section>
     
     <section id="Introduction">
@@ -115,7 +114,7 @@
 
     <section id="Exit-Criteria">
       <h2> Meeting the Exit Criteria</h2>
-      <p>At the start of the Candidate Recommendation phase, the Working Group defined <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">a series of exit criteria</a>. These exit criteria can be summarized as for each feature defined by PROV there are at least two implementations that support the feature and that there exists one interoperability pair that can exchange that feature. Section <a href="#prov-terms">3.1</a> shows that a minimum of 4 implementations both produce and consume all constructs defined in PROV-DM. PROV-O is implemented by over 40 implementations and PROV-N is implemented by 7 implementations.</p>
+      <p>At the start of the Candidate Recommendation phase, the Working Group defined <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">a series of exit criteria</a>. These exit criteria can be summarized as for each feature defined by PROV there are at least two implementations that support the feature and that there exists one interoperability pair that can exchange that feature. Section <a href="#prov-terms">3.1</a> shows that three implementations both produce and consume all constructs defined in PROV-DM. PROV-O is implemented by over 40 implementations and PROV-N is implemented by 12 implementations.</p>
       <p>In terms of implementation pairs, Section <a href="#prov-exchange">4</a> enumerates which pairs of implementations report exchanging provenance. Here, we meet the exit criteria in that each feature is exchanged by at least two implementations.</p>
       <p>Finally, three validators have implemented all of the constraints defined in PROV-Constraints passing the requisite test cases, thus, passing the exit criteria.  The working group recognizes that implementing the PROV-Constraints document requires substantial effort. It is nice to see that three radically different approaches were chosen to implement this specification: SPARQL, Java, Prolog, which speaks to the implementability of this specification.</p>
       <p>For a systematic enumeration of how the exit criteria were met, please see <a href="http://www.w3.org/2011/prov/wiki/MeetingProvCRExitCriteria"> http://www.w3.org/2011/prov/wiki/MeetingProvCRExitCriteria</a></p>
@@ -168,7 +167,7 @@
         </tr>
         <tr id="5">
           <td>5</td>
-          <th scope="row"><a href="http://www.collabmap.org/">CollabMap</a></th>
+          <th scope="row"><a href="http://www.orchid.ac.uk/collabmap">CollabMap</a></th>
           <td>Application</td>
           <td>PROV-JSON</td>
         </tr>
@@ -182,7 +181,7 @@
           <td>7</td>
           <th scope="row"><a href="https://github.com/lucmoreau/ProvToolbox">ProvToolbox</a></th>
           <td>Framework / API<br>Service</td>
-          <td>PROV-O, PROV-N, PROV-XML, prov-json</td>
+          <td>PROV-O, PROV-N, PROV-XML, PROV-JSON</td>
         </tr>
         <tr id="8">
           <td>8</td>
@@ -240,13 +239,13 @@
         </tr>
         <tr id="17">
           <td>17</td>
-          <th scope="row"><a href="https://provenance.ecs.soton.ac.uk/store">Provenance server</a></th>
+          <th scope="row"><a href="https://provenance.ecs.soton.ac.uk/store/">Provenance server</a></th>
           <td>Service</td>
           <td>PROV-N, PROV-JSON</td>
         </tr>
         <tr id="18">
           <td>18</td>
-          <th scope="row"><a href="http://hac.ecs.soton.ac.uk/agentswitch/">agentSwitch</a></th>
+          <th scope="row"><a href="http://www.orchid.ac.uk/agentswitch">agentSwitch</a></th>
           <td>Application</td>
           <td>PROV-N, PROV-JSON</td>
         </tr>
@@ -426,7 +425,7 @@
         </tr>
         <tr id="48">
           <td>48</td>
-          <th scope="row"><a href="http://purl.org/net/provenance/ns">Jun Zhao</a></th>
+          <th scope="row"><a href="http://purl.org/net/provenance/ns">Provenance Vocabulary Core Ontology Specification</a></th>
           <td>Vocabulary Extension</td>
           <td>PROV-O</td>
         </tr>
@@ -2258,7 +2257,7 @@
         <th scope="col"><a href="#45" title="roevo">#45</a></th>
         <th scope="col"><a href="#46" title="wfprov">#46</a></th>
         <th scope="col"><a href="#47" title="P-plan">#47</a></th>
-        <th scope="col"><a href="#48" title="Jun Zhao">#48</a></th>
+        <th scope="col"><a href="#48" title="Provenance Vocabulary Core Ontology Specification">#48</a></th>
         <th scope="col"><a href="#49" title="Systems molecular biology provenance ontology (SysPro) ">#49</a></th>
         <th scope="col"><a href="#50" title="Yanfeng Shu">#50</a></th>
         <th scope="col"><a href="#51" title="ISO_19115_Lineage">#51</a></th>