--- a/testcases/constraints/process.html Sat Nov 10 08:59:45 2012 -0500
+++ b/testcases/constraints/process.html Sat Nov 10 09:10:06 2012 -0500
@@ -1,254 +1,465 @@
<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<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 class="remove">
- var addExtraReferences = function() {
- for (var k in extraReferences)
- berjon.biblio[k] = extraReferences[k];
- };
- var extraReferences = {
- "PROV-DM":
- "Luc Moreau, Paolo Missier"+
- "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
-
- "PROV-CONSTRAINTS":
- "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
- "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
-
- };
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "NOTE",
-
- // 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: [addExtraReferences],
- };
- </script>
-</head>
-
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+
+ <script class="remove">
+
+ var addExtraReferences = function() {
+
+ for (var k in extraReferences)
+
+ berjon.biblio[k] = extraReferences[k];
+
+ };
+
+ var extraReferences = {
+
+ "PROV-DM":
+
+ "Luc Moreau, Paolo Missier"+
+
+ "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
+
+ "2012, Working Draft. "+
+
+ "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
+
+
+
+ "PROV-CONSTRAINTS":
+
+ "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
+
+ "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
+
+ "2012, Working Draft. "+
+
+ "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
+
+
+
+ };
+
+ var respecConfig = {
+
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+
+ specStatus: "ED",
+
+
+
+ // 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: [addExtraReferences],
+
+ };
+
+ </script>
+
+</head>
+
+
+
<body>
-<section id="abstract">
+<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>
+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: <URI><br />
+
+<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: <URI><br />
+
Every test case has an identifier, e.g. <strong>entity10-c23-c56-c57</strong>.
The numberings of the constraints covered by a test case are included with its identifier, e.g. c23, c56, and c57.
- 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>.xml</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>
-
+ 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>.xml</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 files <strong>entity10-c23-c56-c57.xml</strong>, <strong>entity10-c23-c56-c57.trig</strong>,
<strong>entity10-c23-c56-c57.json</strong>, and <strong>entity10-c23-c56-c57.provn</strong> for the test case
-<strong>entity10-c23-c56-c57</strong> can be found at <URI>.</p>
-
-<p>Each test case is designed to test particular constraints, an overview of which is provided in Table 2 below.</p>
+<strong>entity10-c23-c56-c57</strong> can be found at <URI>.</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>
-
+<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 <emailed to|uploaded at>. </p>
-
+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 <emailed to|uploaded at>. </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>
+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. Success 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>
+<section id="wg-process">
-<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-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>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity2-c23-c56-c57</b></p></td>
+<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. Success 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-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>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association1-c24-c52</b></p></td>
+ </td>
+
+ <td>Success</p></td>
+
+ <td> </td>
+
+ </tr>
+
+ <tr>
+
+ <td><b>activity2-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>Success</p></td>
+
+ <td> </td>
+
+ </tr>
+
+ <tr>
+
+ <td><b>association1-c24-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> </td>
- </tr>
- <tr>
- <td><b>association2-c24-c52</b></p></td>
+ </td>
+
+ <td>Fail</p></td>
+
+ <td> </td>
+
+ </tr>
+
+ <tr>
+
+ <td><b>association2-c24-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> </td>
- </tr>
- <tr>
- <td><b>delegation1-c24-c52-c55</b></p></td>
+ </td>
+
+ <td>Fail</p></td>
+
+ <td> </td>
+
+ </tr>
+
+ <tr>
+
+ <td><b>delegation1-c24-c52-c55</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> </td>
- </tr>
- <tr>
- <td><b>delegation2-c24-c52-c55</b></p></td>
+ </td>
+
+ <td>Fail</p></td>
+
+ <td> </td>
+
+ </tr>
+
+ <tr>
+
+ <td><b>delegation2-c24-c52-c55</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> </td>
- </tr>
+ </td>
+
+ <td>Fail</p></td>
+
+ <td> </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
+<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>
+
+
+</body>
+
+</html>
+