Update test case identifier naming scheme. Added three test cases.
authorT Dong Huynh <tdh@ecs.soton.ac.uk>
Wed, 21 Nov 2012 00:02:42 +0000
changeset 4876 34ecb72268ea
parent 4871 a8c5a6e3ec5d
child 4877 0d9c0798a077
Update test case identifier naming scheme. Added three test cases.
testcases/constraints/derivation1-PASS.provn
testcases/constraints/derivation1-PASS.provx
testcases/constraints/derivation1-PASS.ttl
testcases/constraints/derivation2-FAIL-ordering.provn
testcases/constraints/derivation2-FAIL-ordering.provx
testcases/constraints/derivation2-FAIL-ordering.ttl
testcases/constraints/derivation3-PASS.provn
testcases/constraints/derivation3-PASS.provx
testcases/constraints/derivation3-PASS.ttl
testcases/constraints/process.html
testcases/process.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation1-PASS.provn	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,13 @@
+bundle
+prefix xsd <http://www.w3.org/2001/XMLSchema>
+prefix prim <http://openprovenance.org/primitives#>
+prefix ex <http://example.org/>
+prefix prov <http://www.w3.org/ns/prov#>
+prefix xsi <http://www.w3.org/2001/XMLSchema-instance>
+prefix pc1 <http://www.ipaw.info/pc1/>
+entity(ex:e1)
+entity(ex:e2)
+wasGeneratedBy(ex:gen1;ex:e1,-,-)
+wasGeneratedBy(ex:gen2;ex:e2,-,-)
+wasDerivedFrom(ex:der1;ex:e2, ex:e1)
+endBundle
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation1-PASS.provx	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<prov:document xmlns:prov="http://www.w3.org/ns/prov#" xmlns:prim="http://openprovenance.org/primitives#" xmlns:ex="http://example.org/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
+        <prov:entity prov:id="ex:e1">
+        </prov:entity>
+        <prov:entity prov:id="ex:e2">
+        </prov:entity>
+
+	    <prov:wasGeneratedBy prov:id="ex:gen1">
+	      <prov:entity  prov:ref="ex:e1"/>
+            </prov:wasGeneratedBy>
+	    <prov:wasGeneratedBy prov:id="ex:gen2">
+	      <prov:entity  prov:ref="ex:e2"/>
+            </prov:wasGeneratedBy>
+            <prov:wasDerivedFrom prov:id="ex:der1">
+                <prov:generatedEntity prov:ref="ex:e2"/>
+                <prov:usedEntity prov:ref="ex:e1"/>
+            </prov:wasDerivedFrom>
+
+</prov:document>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation1-PASS.ttl	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,24 @@
+@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix prim: <http://openprovenance.org/primitives#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix ex: <http://example.org/> .
+@prefix xsi: <http://www.w3.org/2001/XMLSchema-instance> .
+@prefix pc1: <http://www.ipaw.info/pc1/> .
+
+
+ex:e1 a prov:Entity .
+
+ex:e2 a prov:Entity .
+
+ex:gen1 a prov:Generation .
+
+ex:e1 prov:qualifiedGeneration ex:gen1 .
+
+ex:gen2 a prov:Generation .
+
+ex:e2 prov:qualifiedGeneration ex:gen2 .
+
+ex:der1 a prov:Derivation ;
+	prov:entity ex:e1 .
+
+ex:e2 prov:qualifiedDerivation ex:der1 .
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation2-FAIL-ordering.provn	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,14 @@
+bundle
+prefix xsd <http://www.w3.org/2001/XMLSchema>
+prefix prim <http://openprovenance.org/primitives#>
+prefix ex <http://example.org/>
+prefix prov <http://www.w3.org/ns/prov#>
+prefix xsi <http://www.w3.org/2001/XMLSchema-instance>
+prefix pc1 <http://www.ipaw.info/pc1/>
+entity(ex:e1)
+entity(ex:e2)
+wasGeneratedBy(ex:gen1;ex:e1,-,-)
+wasGeneratedBy(ex:gen2;ex:e2,-,-)
+wasDerivedFrom(ex:der1;ex:e2, ex:e1)
+wasDerivedFrom(ex:der2;ex:e1, ex:e2)
+endBundle
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation2-FAIL-ordering.provx	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<prov:document xmlns:prov="http://www.w3.org/ns/prov#" xmlns:prim="http://openprovenance.org/primitives#" xmlns:ex="http://example.org/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
+        <prov:entity prov:id="ex:e1">
+        </prov:entity>
+        <prov:entity prov:id="ex:e2">
+        </prov:entity>
+
+	    <prov:wasGeneratedBy prov:id="ex:gen1">
+	      <prov:entity  prov:ref="ex:e1"/>
+            </prov:wasGeneratedBy>
+	    <prov:wasGeneratedBy prov:id="ex:gen2">
+	      <prov:entity  prov:ref="ex:e2"/>
+            </prov:wasGeneratedBy>
+            <prov:wasDerivedFrom prov:id="ex:der1">
+                <prov:generatedEntity prov:ref="ex:e2"/>
+                <prov:usedEntity prov:ref="ex:e1"/>
+            </prov:wasDerivedFrom>
+            <prov:wasDerivedFrom prov:id="ex:der2">
+                <prov:generatedEntity prov:ref="ex:e1"/>
+                <prov:usedEntity prov:ref="ex:e2"/>
+            </prov:wasDerivedFrom>
+
+</prov:document>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation2-FAIL-ordering.ttl	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,29 @@
+@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix prim: <http://openprovenance.org/primitives#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix ex: <http://example.org/> .
+@prefix xsi: <http://www.w3.org/2001/XMLSchema-instance> .
+@prefix pc1: <http://www.ipaw.info/pc1/> .
+
+
+ex:e1 a prov:Entity .
+
+ex:e2 a prov:Entity .
+
+ex:gen1 a prov:Generation .
+
+ex:e1 prov:qualifiedGeneration ex:gen1 .
+
+ex:gen2 a prov:Generation .
+
+ex:e2 prov:qualifiedGeneration ex:gen2 .
+
+ex:der1 a prov:Derivation ;
+	prov:entity ex:e1 .
+
+ex:e2 prov:qualifiedDerivation ex:der1 .
+
+ex:der2 a prov:Derivation ;
+	prov:entity ex:e2 .
+
+ex:e1 prov:qualifiedDerivation ex:der2 .
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation3-PASS.provn	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,15 @@
+bundle
+prefix xsd <http://www.w3.org/2001/XMLSchema>
+prefix prim <http://openprovenance.org/primitives#>
+prefix ex <http://example.org/>
+prefix prov <http://www.w3.org/ns/prov#>
+prefix xsi <http://www.w3.org/2001/XMLSchema-instance>
+prefix pc1 <http://www.ipaw.info/pc1/>
+entity(ex:e1)
+entity(ex:e2)
+activity(ex:a1,-,-)
+wasGeneratedBy(ex:gen1;ex:e1,-,-)
+wasGeneratedBy(ex:gen2;ex:e2,-,-)
+used(ex:use1;ex:a1,ex:e1,-)
+wasDerivedFrom(ex:der1;ex:e2, ex:e1, ex:a1, ex:gen2, ex:use1)
+endBundle
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation3-PASS.provx	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<prov:document xmlns:prov="http://www.w3.org/ns/prov#" xmlns:prim="http://openprovenance.org/primitives#" xmlns:ex="http://example.org/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
+        <prov:entity prov:id="ex:e1">
+        </prov:entity>
+        <prov:entity prov:id="ex:e2">
+        </prov:entity>
+        <prov:activity prov:id="ex:a1">
+        </prov:activity>
+
+
+	    <prov:wasGeneratedBy prov:id="ex:gen1">
+	      <prov:entity  prov:ref="ex:e1"/>
+            </prov:wasGeneratedBy>
+	    <prov:wasGeneratedBy prov:id="ex:gen2">
+	      <prov:entity  prov:ref="ex:e2"/>
+            </prov:wasGeneratedBy>
+	    <prov:used prov:id="ex:use1">
+	      <prov:activity prov:ref="ex:a1"/>
+	      <prov:entity  prov:ref="ex:e1"/>
+	    </prov:used>
+            <prov:wasDerivedFrom prov:id="ex:der1">
+                <prov:generatedEntity prov:ref="ex:e2"/>
+                <prov:usedEntity prov:ref="ex:e1"/>
+		<prov:activity prov:ref="ex:a1"/>
+		<prov:generation prov:ref="ex:gen2"/>
+		<prov:usage prov:ref="ex:use1"/>
+            </prov:wasDerivedFrom>
+
+</prov:document>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/constraints/derivation3-PASS.ttl	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,35 @@
+@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix prim: <http://openprovenance.org/primitives#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix ex: <http://example.org/> .
+@prefix xsi: <http://www.w3.org/2001/XMLSchema-instance> .
+@prefix pc1: <http://www.ipaw.info/pc1/> .
+
+
+ex:e1 a prov:Entity .
+
+ex:e2 a prov:Entity .
+
+ex:a1 a prov:Activity .
+
+ex:gen1 a prov:Generation .
+
+ex:e1 prov:qualifiedGeneration ex:gen1 .
+
+ex:gen2 a prov:Generation .
+
+ex:e2 prov:qualifiedGeneration ex:gen2 .
+
+ex:use1 a prov:Usage ;
+	prov:entity ex:e1 .
+
+ex:a1 prov:qualifiedUsage ex:use1 .
+
+ex:der1 a prov:Derivation ;
+	prov:entity ex:e1 .
+
+ex:e2 prov:qualifiedDerivation ex:der1 .
+
+ex:der1 prov:hadGeneration ex:gen2 ;
+	prov:hadUsage ex:use1 ;
+	prov:hadActivity ex:a1 .
--- a/testcases/constraints/process.html	Tue Nov 20 23:04:52 2012 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,431 +0,0 @@
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml">
-
-<head>
-
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-
-    <title>PROV-CONSTRAINTS Test Cases</title>
-    <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
-    <script src="../../model/provbib.js" class="remove"></script>    
-    <script type="text/javascript" >
-      var respecConfig = {
-
-          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-
-          specStatus:           "unofficial",
-
-          
-
-          // the specification's short name, as in http://www.w3.org/TR/short-name/
-
-          shortName:            "prov-constraints-implementations",
-
- 
-
-          // if your specification has a subtitle that goes below the main
-
-          // formal title, define it here
-
-          subtitle   :  "The process for reporting PROV-CONSTRAINTS implementations",
-
- 
-
-          // if you wish the publication date to be other than today, set this
-
-          // publishDate:  "2011-10-18",
-
- 
-
-          // if the specification's copyright date is a range of years, specify
-
-          // the start date here:
-
-          // copyrightStart: "2005"
-
- 
-
-          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
-
-          // and its maturity status
-
-          //previousPublishDate:  "2011-12-15",
-
-          //previousMaturity:  "WD",
-
- 
-
-          // if there a publicly available Editor's Draft, this is the link
-
-          edDraftURI:           "http://dvcs.w3.org/hg/prov/raw-file/default/testcases/constraints/process.html",
-
- 
-
-          // if this is a LCWD, uncomment and set the end of its review period
-
-          // lcEnd: "2009-08-05",
-
- 
-
-          // if you want to have extra CSS, append them to this list
-
-          // it is recommended that the respec.css stylesheet be kept
-
-          extraCSS:             ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
-
- 
-
-          // editors, add as many as you like
-
-          // only "name" is required
-
-          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/",
-
-                company: "VU University of Amsterdam" },
-
-              { name: "Stephan Zednik", url: "http://tw.rpi.edu/web/person/StephanZednik",
-
-                company: "Rensselaer Polytechnic Institute" },
-
-          ],
-
- 
-
-          // authors, add as many as you like. 
-
-          // This is optional, uncomment if you have authors as well as editors.
-
-          // only "name" is required. Same format as editors.
-
- 
-
-          
-
-          // name of the WG
-
-          wg:           "Provenance Working Group",
-
-          
-
-          // URI of the public WG page
-
-          wgURI:        "http://www.w3.org/2011/prov/",
-
-          
-
-          // name (with the @w3c.org) of the public mailing to which comments are due
-
-          wgPublicList: "public-prov-wg",
-
-          
-
-          // URI of the patent status for this WG, for Rec-track documents
-
-          // !!!! IMPORTANT !!!!
-
-          // This is important for Rec-track documents, do not copy a patent URI from a random
-
-          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
-
-          // Team Contact.
-
-          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46974/status",
-
-
-
-          // Add extraReferences to bibliography database
-
-          preProcess: [addProvReferences],
-
-      };
-
-    </script>
-
-</head>
-
-
-
-<body>
-
-<section id="abstract">
-
-<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>
-
-
-<section id="implementers">
-
-<h2>Process for Implementers</h2>
-
-
-<section id="test-cases">
-
-<h3>Test cases</h3>
-
-<p>The test cases will be made available  online at: &lt;URI&gt;<br />
-  Every test case has an identifier, e.g. <strong>association2-c24-c55-FAIL-c52</strong>.
-  In order to facilitate the testing process, we include the numberings of the constraints covered by
-  each test case its identifier, e.g. <b>c24</b>, <b>c55</b>, and <b>c52</b>. In addition, the identifier
-  also indicates whether the test case should be successfully validated (i.e. <b>PASS</b>) or not (i.e. <b>FAIL</b>).
-  In case of the latter, the constraint numberings that follow <b>FAIL</b> are those of the constraints we expect to
-  cause the test case to fail validation. 
-</p>
-
-<p>The provenance document for each test case will be provided in the following representations:</p>
-
-<table border="1" cellspacing="0" cellpadding="0" width="623">
-
-  <caption>Table 1. File representations provided for test cases.</caption>
-
-  <tr>
-
-    <td><br />
-
-      <strong>Representation</strong></td>
-
-    <td><p><strong>File extension</strong></p></td>
-
-    <td><p><strong>Documentation</strong></p></td>
-
-  </tr>
-
-  <tr>
-
-    <td><p><strong>PROV-XML</strong></p></td>
-
-    <td><p>.provx</p></td>
-
-    <td><p><a href="http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html">http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html</a></p></td>
-
-  </tr>
-
-  <tr>
-
-    <td><p><strong>PROV-RDF</strong></p></td>
-
-    <td><p>.trig</p></td>
-
-    <td><p><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></p></td>
-
-  </tr>
-
-  <tr>
-
-    <td><p><strong>PROV-JSON</strong></p></td>
-
-    <td><p>.json</p></td>
-
-    <td><p><a href="http://users.ecs.soton.ac.uk/tdh/json/">http://users.ecs.soton.ac.uk/tdh/json/</a></p></td>
-
-  </tr>
-
-  <tr>
-
-    <td><p><strong>PROV-N</strong></p></td>
-
-    <td><p>.provn</p></td>
-
-    <td><p><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></p></td>
-
-  </tr>
-
-</table>
-
-
-
-<p>For example, the available files for the test case <strong>association2-c24-c55-FAIL-c52</strong> are: <strong>association2-c24-c55-FAIL-c52.xml</strong>,
-<strong>association2-c24-c55-FAIL-c52.trig</strong>, <strong>association2-c24-c55-FAIL-c52.json</strong>, and <strong>association2-c24-c55-FAIL-c52.provn</strong>.
-They can all be found at &lt;URI&gt;.</p>
-
-
-
-<p>Each test case is designed to test  particular constraints, an overview of which is provided in Table 2 below.</p>
-
-</section>
-
-<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 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? 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>
-
-</section>
-
-<section id="wg-process">
-
-<h2>Process for the Working Group</h2>
-
-
-<section id="categorization">
-
-<h3>Categorizing Test Cases</h3>
-
-
-
-<p>All test cases need to be checked for the  constraints they cover and their expected validation results (i.e. Pass or  Fail).</p>
-
-
-
-<p class="note">Dong: We need to check whether all the constraints are sufficiently covered and curate from the WG or generate ourselves the test cases for constraints that haven’t been covered by these.</p>
-
-
-<table border="1" cellspacing="0" cellpadding="0">
-
-  <caption>Table 2. Available test cases (127 in total)</caption>
-
-  <tr>
-
-    <td><b>Identifier</b></p></td>
-
-    <td><b>Constraints Tested</b></p></td>
-
-    <td><b>Expected Validation Result</b></p></td>
-
-    <td><b>Notes</b></p></td>
-
-  </tr>
-
-  <tr>
-
-    <td><b>activity1-PASS-c23-c56-c57</b></p></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>Pass</p></td>
-
-    <td>&nbsp;</td>
-
-  </tr>
-
-  <tr>
-
-    <td><b>activity2-PASS-c23-c56-c57</b></p></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>Pass</p></td>
-
-    <td>&nbsp;</td>
-
-  </tr>
-
-  <tr>
-
-    <td><b>association1-c24-FAIL-c52</b></p></td>
-
-    <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
-        <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a>
-    </td>
-
-    <td>Fail</p></td>
-
-    <td>&nbsp;</td>
-
-  </tr>
-
-  <tr>
-
-    <td><b>association2-c24-c55-FAIL-c52</b></p></td>
-
-    <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
-        <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a>
-    </td>
-
-    <td>Fail</p></td>
-
-    <td>&nbsp;</td>
-
-  </tr>
-
-  <tr>
-
-    <td><b>delegation1-c24-c55-FAIL-c52</b></p></td>
-
-    <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
-        <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a><br />
-        <a href="http://www.w3.org/TR/prov-constraints/#impossible-property-overlap_text">Constraint 55 (impossible-property-overlap)</a>
-    </td>
-
-    <td>Fail</p></td>
-
-    <td>&nbsp;</td>
-
-  </tr>
-
-  <tr>
-
-    <td><b>delegation2-c24-c55-FAIL-c52</b></p></td>
-
-    <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
-        <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a><br />
-        <a href="http://www.w3.org/TR/prov-constraints/#impossible-property-overlap_text">Constraint 55 (impossible-property-overlap)</a>
-    </td>
-
-    <td>Fail</p></td>
-
-    <td>&nbsp;</td>
-
-  </tr>
-
-</table>
-<p class="note">The constraints in bold above (in the second column) are the ones that SHOULD fail to validate.</p>
-
-<p>For each report, the successful and failed
-
-    validations will need to be checked against the expected validation results in  Table 2   above  . A
-
-    test case is considered to be successful if its validation result is the same
-
-as the expected result in  Table 2.</p>
-
-<p>The test case results will also need to be
-
-  collated against the constraints they cover to indicate which constraints
-
-  have/have not been successfully tested.</p>
-
-<p>The collated result will be made available
-
-  to the implementer soon after they submit their result</p>
-</section>
-
-
-</section>
-  
-
-</body>
-
-</html>
-
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/testcases/process.html	Wed Nov 21 00:02:42 2012 +0000
@@ -0,0 +1,297 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml">
+
+<head>
+
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+
+    <title>PROV-CONSTRAINTS Test Cases</title>
+    <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+    <script src="../model/provbib.js" class="remove"></script>    
+    <script type="text/javascript" >
+      var respecConfig = {
+
+          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+
+          specStatus:           "unofficial",
+
+          
+
+          // the specification's short name, as in http://www.w3.org/TR/short-name/
+
+          shortName:            "prov-constraints-implementations",
+
+ 
+
+          // if your specification has a subtitle that goes below the main
+
+          // formal title, define it here
+
+          subtitle   :  "The process for reporting PROV-CONSTRAINTS implementations",
+
+ 
+
+          // if you wish the publication date to be other than today, set this
+
+          // publishDate:  "2011-10-18",
+
+ 
+
+          // if the specification's copyright date is a range of years, specify
+
+          // the start date here:
+
+          // copyrightStart: "2005"
+
+ 
+
+          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+
+          // and its maturity status
+
+          //previousPublishDate:  "2011-12-15",
+
+          //previousMaturity:  "WD",
+
+ 
+
+          // if there a publicly available Editor's Draft, this is the link
+
+          edDraftURI:           "http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html",
+
+ 
+
+          // if this is a LCWD, uncomment and set the end of its review period
+
+          // lcEnd: "2009-08-05",
+
+ 
+
+          // if you want to have extra CSS, append them to this list
+
+          // it is recommended that the respec.css stylesheet be kept
+
+          extraCSS:             ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+
+ 
+
+          // editors, add as many as you like
+
+          // only "name" is required
+
+          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/",
+
+                company: "VU University of Amsterdam" },
+
+              { name: "Stephan Zednik", url: "http://tw.rpi.edu/web/person/StephanZednik",
+
+                company: "Rensselaer Polytechnic Institute" },
+
+          ],
+
+ 
+
+          // authors, add as many as you like. 
+
+          // This is optional, uncomment if you have authors as well as editors.
+
+          // only "name" is required. Same format as editors.
+
+ 
+
+          
+
+          // name of the WG
+
+          wg:           "Provenance Working Group",
+
+          
+
+          // URI of the public WG page
+
+          wgURI:        "http://www.w3.org/2011/prov/",
+
+          
+
+          // name (with the @w3c.org) of the public mailing to which comments are due
+
+          wgPublicList: "public-prov-wg",
+
+          
+
+          // URI of the patent status for this WG, for Rec-track documents
+
+          // !!!! IMPORTANT !!!!
+
+          // This is important for Rec-track documents, do not copy a patent URI from a random
+
+          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+
+          // Team Contact.
+
+          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46974/status",
+
+
+
+          // Add extraReferences to bibliography database
+
+          preProcess: [addProvReferences],
+
+      };
+
+    </script>
+
+</head>
+
+
+
+<body>
+
+<section id="abstract">
+
+<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>
+
+
+<section id="implementers">
+
+<h2>Process for Implementers</h2>
+
+
+<section id="test-cases">
+
+<h3>Test cases</h3>
+
+<p>The test cases will be made available  online at: &lt;URI&gt;<br />
+  Every test case has an identifier, e.g. <strong>association2-FAIL-c52</strong>.
+  In order to facilitate the testing process, the identifier
+  also indicates whether the test case should be successfully validated (i.e. <b>PASS</b>)
+  or not (i.e. <b>FAIL</b>). In addition, in case of the latter, we also include the
+  numberings of the constraints that we expect to cause the test case to fail validation,
+  e.g. <b>c52</b>. 
+</p>
+
+<p>The provenance document for each test case will be provided in the following representations:</p>
+
+<table border="1" cellspacing="0" cellpadding="0" width="623">
+  <caption>Table 1. File representations provided for test cases.</caption>
+  <tr>
+    <td><strong>Representation</strong></td>
+    <td><strong>File extension</strong></td>
+    <td><strong>Documentation</strong></td>
+  </tr>
+  <tr>
+    <td><p><strong>PROV-XML</strong></p></td>
+    <td><p>.provx</p></td>
+    <td><p><a href="http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html">http://dvcs.w3.org/hg/prov/raw-file/default/xml/prov-xml.html</a></p></td>
+  </tr>
+  <tr>
+    <td><p><strong>PROV-RDF</strong></p></td>
+    <td><p>.ttl</p></td>
+    <td><p><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></p></td>
+  </tr>
+  <tr>
+    <td><p><strong>PROV-N</strong></p></td>
+    <td><p>.provn</p></td>
+    <td><p><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></p></td>
+  </tr>
+</table>
+
+
+
+<p>For example, the available files for the test case <strong>association2-FAIL-c52</strong>
+are: <strong>association2-FAIL-c52.xml</strong>, <strong>association2-FAIL-c52.ttl</strong>,
+and <strong>association2-FAIL-c52.provn</strong>. They can all be found at <a
+href="http://dvcs.w3.org/hg/prov/raw-file/default/testcases/constraints/">http://dvcs.w3.org/hg/prov/raw-file/default/testcases/constraints/</a>.</p>
+
+</section>
+
+<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 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? 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>
+
+</section>
+
+<section id="wg-process">
+
+<h2>Process for the Working Group</h2>
+
+
+<section id="categorization">
+
+<h3>Categorizing Test Cases</h3>
+
+<p>All test cases need to be checked for the  constraints they cover and their expected
+validation results (i.e. Pass or  Fail).</p>
+
+<p class="note">Dong: We need to check whether all the constraints are sufficiently covered and curate from the WG or generate ourselves the test cases for constraints that haven’t been covered by these.</p>
+
+<table border="1" cellspacing="0" cellpadding="0">
+
+  <caption>Table 2. PROV-CONSTRAINTS test cases</caption>
+  <tr>
+    <td><b>Identifier</b></p></td>
+    <td><b>Constraints Violated</b></p></td>
+    <td><b>Expected Validation Result</b></p></td>
+    <td><b>Notes</b></p></td>
+  </tr>
+  <tr>
+    <td><b>derivation1-PASS</b></p></td>
+    <td>&nbsp;</td>
+    <td>Pass</p></td>
+    <td>&nbsp;</td>
+  </tr>
+  <tr>
+    <td><b>derivation2-FAIL-ordering</b></p></td>
+    <td>&nbsp;</td>
+    <td>Pass</p></td>
+    <td>&nbsp;</td>
+  </tr>
+  <tr>
+    <td><b>derivation3-PASS</b></p></td>
+    <td>&nbsp;</td>
+    <td>Pass</p></td>
+    <td>&nbsp;</td>
+  </tr>
+</table>
+
+<p>For each report, the successful and failed validations will need to be checked against
+the expected validation results in Table 2 above. A test case is considered to be
+successful if its validation result is the same as the expected result in Table 2.</p>
+
+<p>The test case results will also need to be collated against the constraints they cover
+to indicate which constraints have/have not been successfully tested.</p>
+
+<p>The collated result will be made available to the implementer soon after they submit
+their result</p>
+
+</section>
+
+</section>
+
+</body>
+
+</html>
+