Examples of contraints checked in test cases
authorTrung Dong Huynh <tdh@ecs.soton.ac.uk>
Wed, 17 Oct 2012 16:51:59 +0100
changeset 4536 d48718204b33
parent 4535 a05d63264f8d
child 4537 e5992f533efb
Examples of contraints checked in test cases
reports/prov-implementations.html
testcases/constraints/process.html
--- a/reports/prov-implementations.html	Tue Oct 16 23:30:28 2012 +0100
+++ b/reports/prov-implementations.html	Wed Oct 17 16:51:59 2012 +0100
@@ -912,13 +912,13 @@
           <td class="notused">&nbsp;</td>
         </tr>
         <tr>
-          <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text"></a></td>
+          <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a></td>
           <td class="implemented">&nbsp;</td>
           <td class="notused">&nbsp;</td>
           <td class="notused">&nbsp;</td>
         </tr>
         <tr>
-          <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a><a href="http://www.w3.org/TR/prov-constraints/#activity-start-end-inference_text"></a></td>
+          <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a></td>
           <td class="implemented">&nbsp;</td>
           <td class="notused">&nbsp;</td>
           <td class="notused">&nbsp;</td>
--- a/testcases/constraints/process.html	Tue Oct 16 23:30:28 2012 +0100
+++ b/testcases/constraints/process.html	Wed Oct 17 16:51:59 2012 +0100
@@ -61,9 +61,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 of 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" },
           ],
  
@@ -97,7 +97,7 @@
 <body>
 
 <section id="abstract">
-<p>This document describes the process for generating the implementation report for PROV-CONSTRAINTS.
+<p>This document describes the process for generating the implementation report for [[PROV-CONSTRAINTS]].
 It provides the instructions for implementers on running PROV-CONSTRAINTS test cases and reporting their results.
 It also outlines the organization of test cases and results by the Prov Working Group.</p>
 </section>
@@ -148,12 +148,14 @@
 <section id="test-results">
 <h3>Test Results</h3>
 
-<p>Implementers are asked to validate each  test case with their implementation and recorded the validation results <em>two  plain text files</em>: <strong>success.txt</strong> and <strong>fail.txt</strong>.  These files should contain the identifiers (one on each line) of the test cases  that have been successfully validated in the former and those that fail  validation in the latter. Test cases that are not supported by the  implementation <strong>should not</strong> be included in either of the files.</p>
+<p>Implementers are asked to validate each test case with their implementation and recorded the validation results <em>two  plain text files</em>: <strong>success.txt</strong> and <strong>fail.txt</strong>.
+These files MUST contain the identifiers (one on each line) of the test cases that have been successfully validated in the former and those that fail validation in the latter.
+Test cases that are not supported by the  implementation SHOULD NOT be included in either of the files.</p>
 
 <p>The test result files will need to be  &lt;emailed to|uploaded at&gt;. </p>
 
-<p class="note">Dong: What else the implementer should provide us with? With the test results, I think they won't need to fill in the questionnaire. Therefore, we
-might need to ask them to provide some basic information about their
+<p class="note">Dong: What else the implementer should provide us with? Having provided the test results, I think they won't need to fill in the questionnaire.
+Therefore, we might need to ask them to provide some basic information about their
 implementations (i.e. the questionnaire 1<sup>st</sup> page).</p>
 </section>
 
@@ -179,7 +181,10 @@
   </tr>
   <tr>
     <td><b>activity1</b></p></td>
-    <td>&nbsp;</td>
+    <td><a href="http://www.w3.org/TR/prov-constraints/#key-object_text">Constraint 23 (key-object)</a> <br />
+        <a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><br />
+        <a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a>
+    </td>
     <td>Success</p></td>
     <td>&nbsp;</td>
   </tr>
@@ -287,13 +292,13 @@
   </tr>
   <tr>
     <td><b>association1</b></p></td>
-    <td>&nbsp;</td>
+    <td><a href="http://www.w3.org/TR/prov-constraints/#typing_text">Constraint 52 (typing)</a></td>
     <td>Fail</p></td>
     <td>&nbsp;</td>
   </tr>
   <tr>
     <td><b>association2</b></p></td>
-    <td>&nbsp;</td>
+    <td><a href="http://www.w3.org/TR/prov-constraints/#typing_text">Constraint 52 (typing)</a></td>
     <td>Fail</p></td>
     <td>&nbsp;</td>
   </tr>
@@ -431,13 +436,13 @@
   </tr>
   <tr>
     <td><b>delegation1</b></p></td>
-    <td>&nbsp;</td>
+    <td><a href="http://www.w3.org/TR/prov-constraints/#typing_text">Constraint 52 (typing)</a></td>
     <td>Fail</p></td>
     <td>&nbsp;</td>
   </tr>
   <tr>
     <td><b>delegation2</b></p></td>
-    <td>&nbsp;</td>
+    <td><a href="http://www.w3.org/TR/prov-constraints/#typing_text">Constraint 52 (typing)</a></td>
     <td>Fail</p></td>
     <td>&nbsp;</td>
   </tr>