--- a/ontology/Overview.html Wed Oct 26 14:55:27 2011 +0100
+++ b/ontology/Overview.html Wed Oct 26 14:56:34 2011 +0100
@@ -478,8 +478,155 @@
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
+</style><style type="text/css">
+/* --- EDITORIAL NOTES --- */
+.pending {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #BFEFFF;
+}
+
+.pending::before {
+ content: "Pending Review";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.resolved {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #9BCD9B;
+}
+
+.resolved::before {
+ content: "Resolved";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+.inference {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.inference::before {
+ content: "Inference";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.unamedconstraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+
+.unamedconstraint::before {
+ content: "Constraint";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+
+.constraint {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #00f;
+ background: #fff;
+}
+
+.constraint[id]::before {
+ content: "Constraint: " attr(id);
+ width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
+}
+
+
+.constraint::before {
+ content: "Constraint";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #00f;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+
+
+.conditional {
+ color: blue;
+}
+
+.grammar {
+ margin-top: 1ex;
+ margin-bottom: 1ex;
+ padding-left: 1ex;
+ padding-right: 1ex;
+ padding-top: 1ex;
+ padding-bottom: 0.6ex;
+ border: 1px dashed #2f6fab;
+ font-family: monospace;
+}
+.nonterminal {
+ font-weight: bold;
+ font-family: sans-serif;
+ font-size: 95%;
+}
+
+.name {
+ font-family: monospace;
+}
+
+
+.xmpl {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #fff;
+}
+
+.xmpl::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8" /></head>
- <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p><h1 id="title" class="title">PROV Ontology Model</h1><h2 id="w3c-working-draft-21-october-2011">W3C Working Draft 21 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111021/">http://www.w3.org/TR/2011/WD-prov-o-20111021/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111013/">http://www.w3.org/TR/2011/WD-prov-o-20111013/</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
+ <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p><h1 id="title" class="title">PROV Ontology Model</h1><h2 id="w3c-working-draft-26-october-2011">W3C Working Draft 26 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111026/">http://www.w3.org/TR/2011/WD-prov-o-20111026/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111013/">http://www.w3.org/TR/2011/WD-prov-o-20111013/</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
<dd><a href="http://tw.rpi.edu/instances/Deborah_L_McGuinness">Deborah McGuinness</a>, Rensselaer Polytechnic Institute, USA</dd>
<dt>Authors:</dt><dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester, UK</dd>
<dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh, UK</dd>
@@ -493,7 +640,7 @@
Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] in the OWL2 Web Ontology Language (OWL2). The PROV ontology consists of a set of classes, properties, and restrictions that can be used to represent provenance information. The PROV ontology is specialized to create domain-specific provenance ontologies that model the provenance information specific to different applications. The PROV ontology supports a set of entailments based on OWL2 formal semantics and provenance specific inference rules. The PROV ontology is available for download as a separate OWL2 document.</p>
</div><div class="introductory section" id="sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
-<p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-wg@w3.org">public-prov-wg@w3.org</a> (<a href="mailto:public-prov-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#prov-ontology" class="tocxref"><span class="secno">1. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">1.1 </span>OWL2 Syntax Used in this Document</a></li><li class="tocline"><a href="#namespace-and-owl2-version" class="tocxref"><span class="secno">1.2 </span>Namespace and OWL2 version</a></li></ul></li><li class="tocline"><a href="#prov-ontology--owl-encoding-of-prov-data-model" class="tocxref"><span class="secno">2. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">2.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">2.1.1 </span>Entity</a></li><li class="tocline"><a href="#processexecution" class="tocxref"><span class="secno">2.1.2 </span>ProcessExecution</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">2.1.3 </span>Agent</a></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">2.1.4 </span>Recipe</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.1.5 </span>TemporalEntity</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.1.6 </span>Time</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">2.1.7 </span>Revision</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">2.1.8 </span>ProvenanceContainer</a><ul class="toc"><li class="tocline"><a href="#modeling-provenancecontainer-and-account-as-rdf-graph" class="tocxref"><span class="secno">2.1.8.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">2.1.9 </span>Location</a></li><li class="tocline"><a href="#entityinrole" class="tocxref"><span class="secno">2.1.10 </span>EntityInRole</a></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">2.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">2.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">2.2.2 </span>wasDerivedFrom</a><ul class="toc"><li class="tocline"><a href="#waseventuallyderivedfrom" class="tocxref"><span class="secno">2.2.2.1 </span>wasEventuallyDerivedFrom</a></li><li class="tocline"><a href="#dependedon" class="tocxref"><span class="secno">2.2.2.2 </span>dependedOn</a></li></ul></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">2.2.3 </span>used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">2.2.4 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">2.2.5 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">2.2.6 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">2.2.7 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">2.2.8 </span>wasInformedBy</a></li><li class="tocline"><a href="#wascheduledafter" class="tocxref"><span class="secno">2.2.9 </span>wasScheduledAfter</a></li><li class="tocline"><a href="#followed" class="tocxref"><span class="secno">2.2.10 </span>followed</a></li><li class="tocline"><a href="#hastemporalvalue" class="tocxref"><span class="secno">2.2.11 </span>hasTemporalValue</a></li><li class="tocline"><a href="#startedAt" class="tocxref"><span class="secno">2.2.12 </span>startedAt</a></li><li class="tocline"><a href="#endedAt" class="tocxref"><span class="secno">2.2.13 </span>endedAt</a></li><li class="tocline"><a href="#wasGeneratedAt" class="tocxref"><span class="secno">2.2.14 </span>wasGeneratedAt</a></li><li class="tocline"><a href="#wasAssumedBy" class="tocxref"><span class="secno">2.2.15 </span>wasAssumedBy</a></li><li class="tocline"><a href="#assumedRole" class="tocxref"><span class="secno">2.2.16 </span>assumedRole</a></li><li class="tocline"><a href="#assumedRoleAt" class="tocxref"><span class="secno">2.2.17 </span>assumedRoleAt</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">2.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">2.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">2.5 </span>Overview of the ontology</a></li><li class="tocline"><a href="#data-model-properties-not-addressed-in-prov-ontology" class="tocxref"><span class="secno">2.6 </span>Data model properties not yet addressed in PROV-O</a></li></ul></li><li class="tocline"><a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications" class="tocxref"><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</a><ul class="toc"><li class="tocline"><a href="#moeling-the-crime-file-scenario" class="tocxref"><span class="secno">3.1 </span>Modeling the Crime File Scenario</a><ul class="toc"><li class="tocline"><a href="#specialization-of-prov-ontology-classes" class="tocxref"><span class="secno">3.1.1 </span>Specialization of PROV Ontology Classes</a><ul class="toc"><li class="tocline"><a href="#cf-journalist" class="tocxref"><span class="secno">3.1.1.1 </span>cf:Journalist</a></li><li class="tocline"><a href="#cf-crimefile" class="tocxref"><span class="secno">3.1.1.2 </span>cf:CrimeFile</a></li><li class="tocline"><a href="#cf-filecreation" class="tocxref"><span class="secno">3.1.1.3 </span>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:Emailing, cf:SpellChecking</a></li></ul></li><li class="tocline"><a href="#specialization-of-prov-ontology-properties" class="tocxref"><span class="secno">3.1.2 </span>Specialization of PROV Ontology Properties</a><ul class="toc"><li class="tocline"><a href="#cf-hadfilepath" class="tocxref"><span class="secno">3.1.2.1 </span>cf:hadFilePath</a></li></ul></li></ul></li><li class="tocline"><a href="#modeling-an-example-scientific-workflow-scenario" class="tocxref"><span class="secno">3.2 </span>Modeling an Example Scientific Workflow Scenario</a><ul class="toc"><li class="tocline"><a href="#workflow-extensions-to-prov-classes" class="tocxref"><span class="secno">3.2.1 </span>Workflow extensions to PROV classes</a></li><li class="tocline"><a href="#workflow-extensions-to-prov-properties" class="tocxref"><span class="secno">3.2.2 </span>Workflow extensions to PROV properties</a></li><li class="tocline"><a href="#workflow-structure" class="tocxref"><span class="secno">3.2.3 </span>Workflow structure</a></li><li class="tocline"><a href="#example-workflow" class="tocxref"><span class="secno">3.2.4 </span>Example workflow</a></li><li class="tocline"><a href="#example-workflow-run" class="tocxref"><span class="secno">3.2.5 </span>Example workflow run</a></li></ul></li></ul></li><li class="tocline"><a href="#formal-semantics-of-the-prov-ontology" class="tocxref"><span class="secno">4. </span>Formal Semantics of the PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#rdf-semantics-for-prov-ontology" class="tocxref"><span class="secno">4.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">4.2 </span>OWL2 Semantics for PROV Ontology</a></li><li class="tocline"><a href="#entailments-supported-by-the-provenance-model" class="tocxref"><span class="secno">4.3 </span>Provenance-specific Entailments Supported by PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#provenance-constraint-on-processexecution" class="tocxref"><span class="secno">4.3.1 </span>Provenance constraint on ProcessExecution</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby-generation-affects-attributes" class="tocxref"><span class="secno">4.3.2 </span>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby-generation-pe-ordering" class="tocxref"><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby-generation-unicity" class="tocxref"><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</a></li><li class="tocline"><a href="#provenance-constraint-on-used-use-attributes" class="tocxref"><span class="secno">4.3.5 </span>Provenance constraint on Used (use-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-used-pe-ordering" class="tocxref"><span class="secno">4.3.6 </span>Provenance constraint on Used (use-pe-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-attributes" class="tocxref"><span class="secno">4.3.7 </span>Provenance constraint on wasDerivedFrom (derivation-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-use-generation-ordering" class="tocxref"><span class="secno">4.3.8 </span>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-events" class="tocxref"><span class="secno">4.3.9 </span>Provenance constraint on wasDerivedFrom (derivation-events)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-process-execution" class="tocxref"><span class="secno">4.3.10 </span>Provenance constraint on wasDerivedFrom (derivation-events)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-use" class="tocxref"><span class="secno">4.3.11 </span>Provenance constraint on wasDerivedFrom (derivation-use)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-generation-generation-ordering" class="tocxref"><span class="secno">4.3.12 </span>Provenance constraint on wasEventuallyDerivedFrom (derivation-generation-generation-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-linked-independent" class="tocxref"><span class="secno">4.3.13 </span>Provenance constraint on wasEventuallyDerivedFrom (derivation-linked-independent)</a></li><li class="tocline"><a href="#provenance-constraint-on-complementof-necessary-cond" class="tocxref"><span class="secno">4.3.14 </span>Provenance constraint on wasComplementOf (wasComplementOf-necessary-cond)</a></li><li class="tocline"><a href="#provenance-constraint-on-hasParticipant-participant" class="tocxref"><span class="secno">4.3.15 </span>Provenance constraint on hadParticipant (participant)</a></li></ul></li></ul></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="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
+<p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-wg@w3.org">public-prov-wg@w3.org</a> (<a href="mailto:public-prov-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#prov-ontology" class="tocxref"><span class="secno">1. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">1.1 </span>OWL2 Syntax Used in this Document</a></li><li class="tocline"><a href="#namespace-and-owl2-version" class="tocxref"><span class="secno">1.2 </span>Namespace and OWL2 version</a></li></ul></li><li class="tocline"><a href="#prov-ontology--owl-encoding-of-prov-data-model" class="tocxref"><span class="secno">2. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">2.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">2.1.1 </span>Entity</a></li><li class="tocline"><a href="#processexecution" class="tocxref"><span class="secno">2.1.2 </span>ProcessExecution</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">2.1.3 </span>Agent</a></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">2.1.4 </span>Recipe</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.1.5 </span>TemporalEntity</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.1.6 </span>Time</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">2.1.7 </span>ProvenanceContainer</a><ul class="toc"><li class="tocline"><a href="#modeling-provenancecontainer-and-account-as-rdf-graph" class="tocxref"><span class="secno">2.1.7.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">2.1.8 </span>Location</a></li><li class="tocline"><a href="#entityinrole" class="tocxref"><span class="secno">2.1.9 </span>EntityInRole</a></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">2.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">2.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">2.2.2 </span>wasRevisionOf</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">2.2.3 </span>wasDerivedFrom</a><ul class="toc"><li class="tocline"><a href="#waseventuallyderivedfrom" class="tocxref"><span class="secno">2.2.3.1 </span>wasEventuallyDerivedFrom</a></li><li class="tocline"><a href="#dependedon" class="tocxref"><span class="secno">2.2.3.2 </span>dependedOn</a></li></ul></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">2.2.4 </span>used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">2.2.5 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">2.2.6 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">2.2.7 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">2.2.8 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">2.2.9 </span>wasInformedBy</a></li><li class="tocline"><a href="#wascheduledafter" class="tocxref"><span class="secno">2.2.10 </span>wasScheduledAfter</a></li><li class="tocline"><a href="#followed" class="tocxref"><span class="secno">2.2.11 </span>followed</a></li><li class="tocline"><a href="#attribution" class="tocxref"><span class="secno">2.2.12 </span>wasAttributedTo</a></li><li class="tocline"><a href="#quotation" class="tocxref"><span class="secno">2.2.13 </span>wasQuoteOf</a></li><li class="tocline"><a href="#summary" class="tocxref"><span class="secno">2.2.14 </span>wasSummaryOf</a></li><li class="tocline"><a href="#originalsource" class="tocxref"><span class="secno">2.2.15 </span>hadOriginalSource</a></li><li class="tocline"><a href="#hastemporalvalue" class="tocxref"><span class="secno">2.2.16 </span>hasTemporalValue</a></li><li class="tocline"><a href="#startedAt" class="tocxref"><span class="secno">2.2.17 </span>startedAt</a></li><li class="tocline"><a href="#endedAt" class="tocxref"><span class="secno">2.2.18 </span>endedAt</a></li><li class="tocline"><a href="#wasGeneratedAt" class="tocxref"><span class="secno">2.2.19 </span>wasGeneratedAt</a></li><li class="tocline"><a href="#wasAssumedBy" class="tocxref"><span class="secno">2.2.20 </span>wasAssumedBy</a></li><li class="tocline"><a href="#assumedRole" class="tocxref"><span class="secno">2.2.21 </span>assumedRole</a></li><li class="tocline"><a href="#assumedRoleAt" class="tocxref"><span class="secno">2.2.22 </span>assumedRoleAt</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">2.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">2.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#collections" class="tocxref"><span class="secno">2.5 </span>Collections</a><ul class="toc"><li class="tocline"><a href="#collection-adding" class="tocxref"><span class="secno">2.5.1 </span>Expansion</a></li><li class="tocline"><a href="#collection-removal" class="tocxref"><span class="secno">2.5.2 </span>Reduction</a></li><li class="tocline"><a href="#emptycollection" class="tocxref"><span class="secno">2.5.3 </span>EmptyCollection</a></li><li class="tocline"><a href="#collection-content" class="tocxref"><span class="secno">2.5.4 </span>Collection content</a></li></ul></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">2.6 </span>Overview of the ontology</a></li></ul></li><li class="tocline"><a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications" class="tocxref"><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</a><ul class="toc"><li class="tocline"><a href="#moeling-the-crime-file-scenario" class="tocxref"><span class="secno">3.1 </span>Modeling the Crime File Scenario</a><ul class="toc"><li class="tocline"><a href="#specialization-of-prov-ontology-classes" class="tocxref"><span class="secno">3.1.1 </span>Specialization of PROV Ontology Classes</a><ul class="toc"><li class="tocline"><a href="#cf-journalist" class="tocxref"><span class="secno">3.1.1.1 </span>cf:Journalist</a></li><li class="tocline"><a href="#cf-crimefile" class="tocxref"><span class="secno">3.1.1.2 </span>cf:CrimeFile</a></li><li class="tocline"><a href="#cf-filecreation" class="tocxref"><span class="secno">3.1.1.3 </span>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:Emailing, cf:SpellChecking</a></li></ul></li><li class="tocline"><a href="#specialization-of-prov-ontology-properties" class="tocxref"><span class="secno">3.1.2 </span>Specialization of PROV Ontology Properties</a><ul class="toc"><li class="tocline"><a href="#cf-hadfilepath" class="tocxref"><span class="secno">3.1.2.1 </span>cf:hadFilePath</a></li></ul></li></ul></li><li class="tocline"><a href="#modeling-an-example-scientific-workflow-scenario" class="tocxref"><span class="secno">3.2 </span>Modeling an Example Scientific Workflow Scenario</a><ul class="toc"><li class="tocline"><a href="#workflow-extensions-to-prov-classes" class="tocxref"><span class="secno">3.2.1 </span>Workflow extensions to PROV classes</a></li><li class="tocline"><a href="#workflow-extensions-to-prov-properties" class="tocxref"><span class="secno">3.2.2 </span>Workflow extensions to PROV properties</a></li><li class="tocline"><a href="#workflow-structure" class="tocxref"><span class="secno">3.2.3 </span>Workflow structure</a></li><li class="tocline"><a href="#example-workflow" class="tocxref"><span class="secno">3.2.4 </span>Example workflow</a></li><li class="tocline"><a href="#example-workflow-run" class="tocxref"><span class="secno">3.2.5 </span>Example workflow run</a></li></ul></li></ul></li><li class="tocline"><a href="#formal-semantics-of-the-prov-ontology" class="tocxref"><span class="secno">4. </span>Formal Semantics of the PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#rdf-semantics-for-prov-ontology" class="tocxref"><span class="secno">4.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">4.2 </span>OWL2 Semantics for PROV Ontology</a></li><li class="tocline"><a href="#entailments-supported-by-the-provenance-model" class="tocxref"><span class="secno">4.3 </span>Provenance-specific Entailments Supported by PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#provenance-constraint-on-processexecution" class="tocxref"><span class="secno">4.3.1 </span>Provenance constraint on ProcessExecution</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby-generation-affects-attributes" class="tocxref"><span class="secno">4.3.2 </span>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby-generation-pe-ordering" class="tocxref"><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby-generation-unicity" class="tocxref"><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</a></li><li class="tocline"><a href="#provenance-constraint-on-used-use-attributes" class="tocxref"><span class="secno">4.3.5 </span>Provenance constraint on Used (use-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-used-pe-ordering" class="tocxref"><span class="secno">4.3.6 </span>Provenance constraint on Used (use-pe-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-attributes" class="tocxref"><span class="secno">4.3.7 </span>Provenance constraint on wasDerivedFrom (derivation-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-use-generation-ordering" class="tocxref"><span class="secno">4.3.8 </span>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-events" class="tocxref"><span class="secno">4.3.9 </span>Provenance constraint on wasDerivedFrom (derivation-events)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-process-execution" class="tocxref"><span class="secno">4.3.10 </span>Provenance constraint on wasDerivedFrom (derivation-events)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-use" class="tocxref"><span class="secno">4.3.11 </span>Provenance constraint on wasDerivedFrom (derivation-use)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-generation-generation-ordering" class="tocxref"><span class="secno">4.3.12 </span>Provenance constraint on wasEventuallyDerivedFrom (derivation-generation-generation-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-derivation-linked-independent" class="tocxref"><span class="secno">4.3.13 </span>Provenance constraint on wasEventuallyDerivedFrom (derivation-linked-independent)</a></li><li class="tocline"><a href="#provenance-constraint-on-complementof-necessary-cond" class="tocxref"><span class="secno">4.3.14 </span>Provenance constraint on wasComplementOf (wasComplementOf-necessary-cond)</a></li><li class="tocline"><a href="#provenance-constraint-on-hasParticipant-participant" class="tocxref"><span class="secno">4.3.15 </span>Provenance constraint on hadParticipant (participant)</a></li></ul></li></ul></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="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
@@ -702,19 +849,8 @@
c</p>
</div>
-
- <div id="revision" class="section">
- <h4><span class="secno">2.1.7 </span>Revision</h4>
- <div><b>Class Description</b></div>
- <p>Revision is defined as a modified version of a Entity.</p>
- <div><b>OWL syntax</b></div>
- <pre>prov:Revision rdfs:subClassOf owl:Thing.</pre>
- </div>
-
-
-
<div id="provenancecontainer" class="section">
- <h4><span class="secno">2.1.8 </span>ProvenanceContainer</h4>
+ <h4><span class="secno">2.1.7 </span>ProvenanceContainer</h4>
<div><b>Class Description</b></div>
<p>ProvenanceContainer is defined to be an aggregation of provenance assertions. A provenance container should have an URI associated with it. The ProvenanceContainer class can also be used to model the PROV-DM concept of <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Account">Account</a>.</p>
<div><b>OWL syntax</b></div>
@@ -726,7 +862,7 @@
<div class="issue">Scope and Identifiers.
This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
<div id="modeling-provenancecontainer-and-account-as-rdf-graph" class="section">
- <h5><span class="secno">2.1.8.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</h5>
+ <h5><span class="secno">2.1.7.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</h5>
<p>Placeholder for Tim's description</p>
</div>
</div>
@@ -734,7 +870,7 @@
<div id="location" class="section">
- <h4><span class="secno">2.1.9 </span>Location</h4>
+ <h4><span class="secno">2.1.8 </span>Location</h4>
<div><b>Class Description</b></div>
<p>Location is defined to be "is an identifiable geographic place (ISO 19112)." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
<div><b>OWL syntax</b></div>
@@ -754,7 +890,7 @@
<div id="entityinrole" class="section">
- <h4><span class="secno">2.1.10 </span>EntityInRole</h4>
+ <h4><span class="secno">2.1.9 </span>EntityInRole</h4>
<div><b>Class Description</b></div>
<p>EntityInRole is defined to be a "realizable entity" (cite?) "assumed by a Entity or an agent." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
<div><b>OWL syntax</b></div>
@@ -825,10 +961,13 @@
</div>
</div>
-
+ <div id="revision" class="section">
+ <h4><span class="secno">2.2.2 </span>wasRevisionOf</h4>
+ <p>wasRevisionOf links two instances of Entity class, where one instance is a revision of another.</p>
+ </div>
<div id="wasderivedfrom" class="section">
- <h4><span class="secno">2.2.2 </span>wasDerivedFrom</h4>
+ <h4><span class="secno">2.2.3 </span>wasDerivedFrom</h4>
<p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
<img alt="wasDerivedFrom links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasDerivedFrom.png" />
<div><b>Example</b></div>
@@ -842,17 +981,31 @@
<div class="issue">Should we specifically mention derivation of agents? This is <a href="http://www.w3.org/2011/prov/track/issues/42">ISSUE-42</a>.</div>
<div id="waseventuallyderivedfrom" class="section">
- <h5><span class="secno">2.2.2.1 </span>wasEventuallyDerivedFrom</h5>
+ <h5><span class="secno">2.2.3.1 </span>wasEventuallyDerivedFrom</h5>
<p>This object property is used to link two entities that are not directly used and generated respectively by a single instance of ProcessExecution.
</p>
- <img alt="wasEventuallyDerivedFrom links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasEventuallyDerivedFrom.png" />
+ <img alt="wasEventuallyDerivedFrom links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasEventuallyDerivedFrom.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasEventuallyDerivedFrom property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e5 wasEventuallyDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e5">
+ <prov:wasEventuallyDerivedFrom rdf:resource="http://www.example.com/crimeFile#e2"/>
+</rdf:Description> </pre>
+ </div>
<div class="issue">Is the current definition of wasEventuallyDerivedFrom inconsistent with definition of wasDerivedFrom? This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/126">ISSUE-126</a></div>
</div>
<div id="dependedon" class="section">
- <h5><span class="secno">2.2.2.2 </span>dependedOn</h5>
+ <h5><span class="secno">2.2.3.2 </span>dependedOn</h5>
<p>dependedOn links two instances of Entity to model derivation of one instance of Entity from another instance of Entity. This property is asserted to be transitive</p>
- <img alt="dependedOn links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/dependedOn.png" />
+ <img alt="dependedOn links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/dependedOn.png" />
+ <div><b>Example</b></div>
+ <p> Example of dependedOn property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e5 dependedOn e2</i>. The RDF/XML syntax for asserting this is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e5">
+ <prov:dependedOn rdf:resource="http://www.example.com/crimeFile#e2"/>
+</rdf:Description> </pre>
+ </div>
<div class="issue">Is dependedOn a parent property of wasDerivedFrom? This is <a href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a>
</div></div>
</div>
@@ -860,7 +1013,7 @@
<div id="used" class="section">
- <h4><span class="secno">2.2.3 </span>used</h4>
+ <h4><span class="secno">2.2.4 </span>used</h4>
<p>used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
<img alt="used links ProcessExecution to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/used.png" />
@@ -877,17 +1030,24 @@
<div id="hadparticipant" class="section">
- <h4><span class="secno">2.2.4 </span>hadParticipant</h4>
+ <h4><span class="secno">2.2.5 </span>hadParticipant</h4>
<p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
</p><p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img alt="hadParticipant links ProcessExecution to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/hadParticipant.png" />
+ <img alt="hadParticipant links ProcessExecution to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/hadParticipant.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadParticipant property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 hadParticipant e2</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
+ <prov:hadParticipant rdf:resource="http://www.example.com/crimeFile#e2"/>
+</rdf:Description> </pre>
+ </div>
<div class="pending">Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
</div>
<div id="wascomplementof" class="section">
- <h4><span class="secno">2.2.5 </span>wasComplementOf</h4>
+ <h4><span class="secno">2.2.6 </span>wasComplementOf</h4>
<p>wasComplementOf links two instances of Entity, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." <i>(from the Provenance Conceptual Model)</i></p>
<img alt="wasComplementOf links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasComplementOf.png" />
</div>
@@ -895,7 +1055,7 @@
<div id="wascontrolledby" class="section">
- <h4><span class="secno">2.2.6 </span>wasControlledBy</h4>
+ <h4><span class="secno">2.2.7 </span>wasControlledBy</h4>
<p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
<img alt="wasControlledBy links ProcessExecution to Agent" style="height: 3em" src="diagram-history/khalidDiagrams/wasControlledBy.png" />
<div><b>Example</b></div>
@@ -914,7 +1074,7 @@
<div id="hadrecipe" class="section">
- <h4><span class="secno">2.2.7 </span>hadRecipe</h4>
+ <h4><span class="secno">2.2.8 </span>hadRecipe</h4>
<p>The ProcessExecution activity performed can be described as
having the given recipe resource. It is out of the scope for PROV to
define the structure or meaning of the recipe. The recipe
@@ -922,35 +1082,115 @@
Execution.
</p>
<img alt="hadRecipe links ProcessExecution to Agent" style="height: 3em" src="diagram-history/khalidDiagrams/hadRecipe.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadRecipe property as an addition to the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is pe1 using some file appending instructions (instructions1) (<i> pe1 hadRecipe instructions1</i>). The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#instructions1"/>
+</rdf:Description> </pre>
+ </div>
</div>
<div id="wasinformedby" class="section">
- <h4><span class="secno">2.2.8 </span>wasInformedBy</h4>
+ <h4><span class="secno">2.2.9 </span>wasInformedBy</h4>
<p> This object property links two process executions. It is used to express the fact that a given process execution used an entity that was generated by another process execution.
</p>
<img alt="wasInformedBy links ProcessExecution to ProcessExecution" style="height: 3em" src="diagram-history/khalidDiagrams/wasInformedBy.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasInformedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe4 wasInformedBy pe3</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe4">
+ <prov:wasInformedBy rdf:resource="http://www.example.com/crimeFile#pe3"/>
+</rdf:Description> </pre>
+ </div>
</div>
<div id="wascheduledafter" class="section">
- <h4><span class="secno">2.2.9 </span>wasScheduledAfter</h4>
+ <h4><span class="secno">2.2.10 </span>wasScheduledAfter</h4>
<p>
This object property links two instances of ProcessExecution to specify the order in which they took place. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
</p>
<img alt="wasScheduledAfter links ProcessExecution to ProcessExecution" style="height: 3em" src="diagram-history/khalidDiagrams/wasScheduledAfter.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasScheduledAfter property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe4 wasScheduledAfter pe3</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe4">
+ <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#pe3"/>
+</rdf:Description> </pre>
+ </div>
</div>
<div id="followed" class="section">
- <h4><span class="secno">2.2.10 </span>followed</h4>
+ <h4><span class="secno">2.2.11 </span>followed</h4>
<p>wasInformedBy links two instances of ProcessExecution to model ordering of the ProcessExecution instances.</p>
- <img alt="followed links ProcessExecution to ProcessExecution" style="height: 3em" src="diagram-history/khalidDiagrams/followed.png" />
+ <img alt="followed links ProcessExecution to ProcessExecution" style="height: 3em" src="diagram-history/khalidDiagrams/followed.png" />
+ <div><b>Example</b></div>
+ <p> Example of followed property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe4 followed pe1</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe4">
+ <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#pe1"/>
+</rdf:Description> </pre>
+ </div>
+ </div>
+
+ <div id="attribution" class="section">
+ <h4><span class="secno">2.2.12 </span>wasAttributedTo</h4>
+ <p>wasAttributedTo links an instance of the Entity class to an instance of Agent class.</p>
+ <img alt="wasAttributedTo links Entity to Agent" style="height: 3em" src="diagram-history/khalidDiagrams/wasAttributedTo.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasAttributedTo property as an addition to the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is the attribution of e3 to David for writting editing the file (<i>e3 wasAttributedTo David</i>). The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
+ <prov:wasAttributedTo rdf:resource="http://www.example.com/crimeFile#David"/>
+</rdf:Description> </pre>
+ </div>
+ </div>
+
+ <div id="quotation" class="section">
+ <h4><span class="secno">2.2.13 </span>wasQuoteOf</h4>
+ <p>wasQuoteOf links an instance of the Entity class to an instance of of the Agent class.</p>
+ <img alt="wasQuoteOf links Entity to Agent" style="height: 3em" src="diagram-history/khalidDiagrams/wasQuoteOf.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasQuoteOf property as an addition to the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is e2 quoting Alice words, recorded by Bob (<i> e2 wasQuoteOf Alice</i>). The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
+ <prov:wasQuoteOf rdf:resource="http://www.example.com/crimeFile#Alice"/>
+</rdf:Description> </pre>
+ </div>
+ </div>
+
+ <div id="summary" class="section">
+ <h4><span class="secno">2.2.14 </span>wasSummaryOf</h4>
+ <p>wasSummaryOf links two instances of the Entity class.</p>
+ <img alt="wasSummaryOf links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasSummaryOf.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasSummaryOf property as an addition to the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is e3 summarizing some additional statistics(<i> e3 wasSummaryOf statistics</i>). The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
+ <prov:wasSummaryOf rdf:resource="http://www.example.com/crimeFile#statistics"/>
+</rdf:Description> </pre>
+ </div>
+ </div>
+
+ <div id="originalsource" class="section">
+ <h4><span class="secno">2.2.15 </span>hadOriginalSource</h4>
+ <p>hadOriginalSource links two instances of the Entity class. This property is defined to be a specialization of the wasEventuallyDerivedFrom propery.</p>
+ <img alt="hadOriginalSource links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/hadOriginalSource.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadOriginalSource property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> <i> e6 hadOriginalSource e1</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e6">
+ <prov:hadOriginalSource rdf:resource="http://www.example.com/crimeFile#e1"/>
+</rdf:Description> </pre>
+ </div>
</div>
<div id="hastemporalvalue" class="section">
- <h4><span class="secno">2.2.11 </span>hasTemporalValue</h4>
+ <h4><span class="secno">2.2.16 </span>hasTemporalValue</h4>
<p> This object property links an instance of
<code>ProcessExecution</code> or <code>Entity</code> with an
<code>time:TemporalEntity</code> from [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>], thereby
@@ -967,13 +1207,14 @@
</p>
</div>
<div id="startedAt" class="section">
- <h4><span class="secno">2.2.12 </span>startedAt</h4>
+ <h4><span class="secno">2.2.17 </span>startedAt</h4>
<p> This object property defines the time when a
<code>ProcessExecution</code> started. The time is specified as an
<code>time:Instant</code> [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>], which <em class="rfc2119" title="may">may</em> be a
<code>Time</code> subclass by specifying the time using a
<code>time:inXSDDateTime</code> data property.
</p>
+ <img alt="startedAt links ProcessExecution to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/startedAt.png" />
<div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
<prov:startedAt rdf:parseType="Resource">
@@ -984,13 +1225,14 @@
</div>
</div>
<div id="endedAt" class="section">
- <h4><span class="secno">2.2.13 </span>endedAt</h4>
+ <h4><span class="secno">2.2.18 </span>endedAt</h4>
<p> This object property defines the time when a
<code>ProcessExecution</code> ended. The time is specified as an
<code>time:Instant</code> [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>], which <em class="rfc2119" title="may">may</em> be a
<code>Time</code> subclass by specifying the time using a
<code>time:inXSDDateTime</code> data property.
</p>
+ <img alt="endedAt links ProcessExecution to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/endedAt.png" />
<div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
<prov:endedAt rdf:parseType="Resource">
@@ -1001,7 +1243,7 @@
</div>
</div>
<div id="wasGeneratedAt" class="section">
- <h4><span class="secno">2.2.14 </span>wasGeneratedAt</h4>
+ <h4><span class="secno">2.2.19 </span>wasGeneratedAt</h4>
<p> This object property defines the time when a
<code>Entity</code> was generated (as specified using
<code>wasGeneratedBy</code>), meaning the instant when the entity
@@ -1011,6 +1253,7 @@
<code>Time</code> subclass by specifying the time using a
<code>time:inXSDDateTime</code> data property.
</p>
+ <img alt="wasGeneratedAt links Entity to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/wasGeneratedAt.png" />
<p>
Note that by constraint
</p>
@@ -1024,7 +1267,7 @@
</div>
</div>
<div id="wasAssumedBy" class="section">
- <h4><span class="secno">2.2.15 </span>wasAssumedBy</h4>
+ <h4><span class="secno">2.2.20 </span>wasAssumedBy</h4>
<p>This object property defines which
<code>Entity</code> assumed a <em>role</em>, forming
a placeholder <code>EntityInRole</code> for use in
@@ -1035,6 +1278,7 @@
is assumed by one and only one <code>Entity</code>.
<code>wasAssumedBy</code> is a subproperty of <code>wasComplementOf</code>.
</p>
+ <img alt="wasAssumedBy links EntityInRole to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasAssumedBy.png" />
<div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
<prov:used>
@@ -1052,13 +1296,14 @@
</p>
</div>
<div id="assumedRole" class="section">
- <h4><span class="secno">2.2.16 </span>assumedRole</h4>
+ <h4><span class="secno">2.2.21 </span>assumedRole</h4>
<p>This object property defines which
<code>Role</code> has been assumed in an
<code>EntityInRole</code>. This property is applied in
relations such as <code>used</code> and
<code>wasGeneratedBy</code>.
</p>
+ <img alt="assumedRole links EntityInRole to Role" style="height: 3em" src="diagram-history/khalidDiagrams/assumedRole.png" />
<p>
The definition and interpretation of the <code>Role</code>
is outside the scope for PROV-O. The <code>Role</code> class is
@@ -1087,7 +1332,7 @@
</div>
</div>
<div id="assumedRoleAt" class="section">
- <h4><span class="secno">2.2.17 </span>assumedRoleAt</h4>
+ <h4><span class="secno">2.2.22 </span>assumedRoleAt</h4>
<p> This object property defines the first time an
<code>Entity</code> assumed a <em>role</em>, ie. when the
<code>EntityInRole</code> which <code>wasAssumedBy</code> was active.
@@ -1098,6 +1343,7 @@
<code>Time</code> subclass by specifying the time using a
<code>time:inXSDDateTime</code> data property.
</p>
+ <img alt="assumedRoleAt links EntityInRole to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/assumedRoleAt.png" />
<p>
According to the constraint <a href="#provenance-constraint-on-wasgeneratedby-generation-unicity">generation-unicity</a>
from [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] an entity can only be generated once by a single process
@@ -1243,8 +1489,234 @@
</div>
</div>
+
+ <div id="collections" class="section">
+ <h3><span class="secno">2.5 </span>Collections</h3>
+ <p>A <code>Collection</code> is a type of
+ <code>Entity</code> which have been composed of other
+ entities. A PROV-O <code>Collection</code> can represent
+ any kind of collection, such as a ordered list, array,
+ associative list, dictionary, hashtable, map. It is out of scope
+ for PROV to further define the exact nature of the collection, but
+ PROV-O defines shortcuts for defining that a entity have
+ been added or removed to a collection. These operations are
+ modelled as subproperties of <code>wasDerivedFrom</code>
+ between two static collections, corresponding to <a href="http://www.w3.org/TR/prov-dm/#expression-Collection">collection
+ assertions</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].
+ </p>
+
+ <div id="collection-adding" class="section">
+ <h4><span class="secno">2.5.1 </span>Expansion</h4>
+ <p>
+ An <code>Entity</code> can be added to a
+ <code>Collection</code>, producing a new (derived)
+ <code>Collection</code> which contains the new item
+ in addition to the items of the old collection.
+ The item can be added at a certain <em>key</em> (represented
+ as another <code>Entity</code>), which could be
+ a <em>position</em> (for ordered lists), a <em>hash key</em>
+ for a dictionary, or the value itself (for sets).
+ In PROV-O the addition is specified using the functional
+ properties <code>wasExpandedFrom</code>,
+ wasExpandedBy and <code>wasExpandedAt</code>.
+ These correspond to the PROV-ASN <a href="http://www.w3.org/TR/prov-dm/#expression-Collection">collection
+ assertions</a>
+ <code>wasAddedTo_Coll</code> (the expanded collection),
+ <code>wasAddedTo_Entity</code> (the expansion)
+ and <code>wasAddedTo_Key</code> (the key it was expanded at). The properties are
+ functional so that only one expansion is asserted at a time,
+ relating the three properties without requiring an
+ explicit "Expansion" class, and also asserting that no other
+ entities have been added or removed to the two
+ collections related using <code>prov:wasExpandedBy</code>.
+ </p>
+ <div class="issue">[<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] does not make the guarantee
+ that other entities have not been added. Is it fair to make
+ such an assumption here?
+ </div>
+ <div class="exampleOuter">
+ <pre class="example">:col1 a prov:Collection ;
+ prov:wasExpandedFrom :col0 ;
+ prov:wasExpandedBy :e1 ;
+ prov:wasExpandedAt :key1 .
+
+:col2 a prov:Collection ;
+ prov:wasExpandedFrom :col1 ;
+ prov:wasExpandedBy :e2 ;
+ prov:wasExpandedAt :key2 . </pre>
+ </div>
+ <p>
+ The above example describes collections <code>:col0</code>,
+ <code>:col1</code> and <code>:col2</code>. We know that
+ <code>:col2:</code> has the entries:
+ <code>(:key2, :e2)</code> and <code>(:key1, :e2)</code>. As
+ we don't have the provenance of :col0 it might or might not
+ contain other keys and entities.
+ </p>
+ <div id="expanded-collection" class="constraint">
+ If a Collection has one of the functional
+ <code>prov:wasExpandedFrom</code>,
+ <code>prov:wasExpandedBy</code> or
+ <code>prov:wasExpandedAt</code> properties asserted, then it
+ is an <code>ExpandedCollection</code> and the
+ existence of the remaining <code>wasExpanded*</code> properties are implied.
+ </div>
+ <div class="issue">TODO: Express the constraint <em>expanded-collection</em> in the OWL ontology</div>
+ <div class="issue">TODO: Write Collection examples as RDF/XML</div>
+ <div class="issue">Does prov:Collection allow replacement or
+ multiple additions on the same key?
+ If we do a second expansion using the :key1,
+ will :e1 still be in the collection? We
+ recommend that for <em>map</em> functionality replacement
+ should always be represented by first an explicit removal
+ (wasReducedBy) followed by insertion (wasExpandedBy).
+ </div>
+ </div>
+
+ <div id="collection-removal" class="section">
+ <h4><span class="secno">2.5.2 </span>Reduction</h4>
+ <p>
+ Removing from a collection is modelled in a similar way as
+ expansion, by deriving a new <em>reduced</em> collection
+ which does not have the removed item or key. This is done
+ using the properties <code>prov:wasReducedFrom</code>,
+ <code>prov:wasReducedBy</code> and
+ <code>prov:wasReducedAt</code>, which correspond go
+ [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] properties <code>wasRemovedFrom_Coll</code>
+ and <code>wasRemovedFrom_Key</code>.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">:col3 a prov:Collection ;
+ prov:wasReducedFrom :col2 ;
+ prov:wasReducedAt :key1 .
+
+:col4 a prov:Collection ;
+ prov:wasReducedFrom :col3 ;
+ prov:wasReducedBy :e2 ;
+ prov:wasReducedAt :key2 . </pre>
+ </div>
+ <p>
+ The example above says that in :col3 does not contain
+ what :col2 had at <code>:key1</code>, e.g. (:key1, :e1).
+ :col4 does not contain (:key2, :e2).
+ </p>
+ <div id="reduced-collection" class="constraint">
+ If a Collection has one of the functional
+ <code>prov:wasReducedFrom</code>,
+ <code>prov:wasReducedBy</code> or
+ <code>prov:wasReducedAt</code> properties asserted, then it
+ is a <code>ReducedCollection</code> and the
+ existence of the remaining <code>wasReduced*</code> properties are
+ implied. A <code>ReducedCollection</code> is disjoint from a
+ <code>ExpandedCollection</code>, so it is not possible to
+ combine any <code>wasReduced*</code> property with any
+ <code>wasExpanded*</code> property.
+ </div>
+ <div class="issue">TODO: Express the constraint <em>reduced-collection</em> in the OWL ontology</div>
+ <div class="issue">
+ Does removal at :key1 mean it is no longer present in
+ the collection? What if the collection is a linked list,
+ where :key1 is a position? (:e2 would now be at :key1).
+ Does removal assert that the key existed in the
+ collection, or simply that it no longer is in the
+ collection? If it is possible to insert several values
+ at the same key, is it possible to remove only one of
+ these at a given key?
+ </div>
+ <p>
+ Asserting <code>prov:wasReducedBy</code> is optional, as
+ <code>prov:wasReducedAt</code> will remove any value at that
+ key. (PROV-DM does not describe wasRemovedFrom_Entity).
+ </p>
+ </div>
+ <div class="collection-empty section" id="emptycollection">
+ <h4><span class="secno">2.5.3 </span>EmptyCollection</h4>
+ <p>PROV-O defines
+ a subclass of <code>Collection</code> called
+ <code>EmptyCollection</code>. Asserting that a
+ collection is empty means that it does not contain
+ any key/value pairs. Combined with expansion and
+ reduction statements this allows the assertion of
+ the complete content of a collection.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">:col0 a prov:EmptyCollection .
+:col4 a prov:EmptyCollection .</pre>
+ </div>
+ <div class="issue">[<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] does not describe the concept
+ of an empty collection</div>
+ <p>
+ With the additional information given above, one can
+ conclude that <code>:col1</code> (which
+ <code>prov:wasExpandedFrom :col0</code>) only
+ contains the expanded entity <code>:e1</code>, and that
+ <code>:col2</code> only contains the keys <code>:key1</code>
+ and <code>:key2</code>.</p>
+
+
+ <div id="empty-collection-disjoint" class="constraint">
+ An EmptyCollection is disjoint from an ExpandedCollection.
+ </div>
+ <div id="empty-collection-range" class="constraint">It is not valid for an asserted
+ <code>EmptyCollection</code> to be
+ in the domain of <code>prov:wasExpandedFrom</code> or
+ in the range of <code>prov:wasReducedFrom</code>.
+ </div>
+ <div class="issue">TODO: Include the constraints
+ <em>empty-collection-disjoint</em> and
+ <em>empty-collection-range</em> in the OWL ontology</div>
+ </div>
+ <div id="collection-content" class="section">
+ <h4><span class="secno">2.5.4 </span>Collection content</h4>
+ <p>To describe the complete content of a Collection (its
+ keys and values), an asserter can form a chain of
+ <code>wasExpandedFrom</code> assertions starting from an
+ <code>EmptyCollection</code>. Note that although this does
+ enforce an ordering of the addition of the elements to the
+ final collection, it does not neccessarily assert that this
+ happened sequentially, as the corresponding implied
+ <code>ProcessExecution</code>s could have had zero duration.
+ To assert that the intermediate expansions occurred
+ "instantly" and not expose any temporal ordering of the
+ insertions, you may state that the <em>generation time</em>
+ of the initial and final collection is the same:
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">:col0 a prov:EmptyCollection ;
+ <b>prov:wasGeneratedAt :t0 .</b>
+:col1 a prov:Collection ;
+ prov:wasExpandedFrom :col0 ;
+ prov:wasExpandedBy :e1 .
+:col2 a prov:Collection ;
+ prov:wasExpandedFrom :col1 ;
+ prov:wasExpandedBy :e2 ;
+ <b>prov:wasGeneratedAt :t0 .</b></pre>
+ </div>
+ <p>The collection <code>:col2</code> described above was
+ created with the entities
+ <code>:e1</code> and <code>:e2</code>. Both items were
+ inserted at the same time <code>:t0</code>. (The
+ wasGeneratedAt :t0 for :col1 is implied above due to the
+ <a href="http://www.w3.org/TR/prov-dm/#derivation-use-generation-ordering">derivation-use-generation-ordering</a>
+ constraint.)
+ </p>
+ <div class="issue">
+ FIXME: What if the asserter knows and want to assert the
+ content, and she knows it was inserted in a temporal order - but
+ don't know that order? (for instance "members of the Royal
+ Society"). Should there be a prov:hadContent property? Is it
+ possible to use rdf collections for such a shorthand?
+ </div>
+ <div class="issue">
+ Is it possible to express set operations (union, difference,
+ intersection, negation) between two collections without
+ having to express all the individual members?
+ </div>
+ </div>
+ </div>
+
<div id="overview-of-the-ontology" class="section">
- <h3><span class="secno">2.5 </span>Overview of the ontology</h3>
+ <h3><span class="secno">2.6 </span>Overview of the ontology</h3>
<p>The following diagram illustrates the complete PROV ontology. </p>
<img alt="Classes and properties of the PROV ontology" style="min-width: 45em; width: 55em; max-width: 95%" src="diagram-history/2011-10-03-tlebo/ProvenanceOntology.png " />
@@ -1255,17 +1727,6 @@
-->
</div>
- <div id="data-model-properties-not-addressed-in-prov-ontology" class="section">
- <h3><span class="secno">2.6 </span>Data model properties not yet addressed in PROV-O</h3>
- <p>The following data model properties have not yet been discussed and included in the ontology: </p>
- <ul>
- <li><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#attribution-expression">Attribution expression</a></li>
- <li><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#quotation-expression">Quotation expression</a></li>
- <li><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#summary-expression">Summary expression</a></li>
- <li><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#original-source-expression">Original source expression</a></li>
- <li><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Revision">Revision expression</a></li>
- </ul>
- </div>
</div>
<div id="specializing-provenance-ontology-for-domain-specific-provenance-applications" class="section">
@@ -1274,8 +1735,8 @@
<h2><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
<p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:</p>
<ul>
- <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
- <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
+ <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</li>
+ <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property" [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</li>
</ul>
<p>To illustrate the specialization mechanism, the PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
@@ -1283,9 +1744,7 @@
<div id="moeling-the-crime-file-scenario" class="section">
<h3><span class="secno">3.1 </span>Modeling the Crime File Scenario</h3>
- <p>The example scenario can be encoded as a <a href="http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href="">Figure X</a>:</p>
- <div class="issue">insert figure X</div>
- <p><a href="">Figure X</a> represents the ontology schema that extends the PROV ontology to model the provenance details of the crime file scenario. For example,</p>
+ <p>The example scenario can be encoded as a <a href="http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF)</a>. For example,</p>
<ul>
<li>specialization of <a href="#agent">Agent</a> to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
<li><a href="#processexecution">ProcessExecution</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
@@ -2077,6 +2536,7 @@
</dd><dt id="bib-OWL2-SYNTAX">[OWL2-SYNTAX]</dt><dd>Boris Motik; Peter F. Patel-Schneider; Bijan Parsia. <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/"><cite>OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/">http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/</a>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau, Paolo Missier<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. 18 October 2011. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/">http://www.w3.org/TR/2011/WD-prov-dm-20111018/</a>
</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd>Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd>Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210"><cite>RDF Vocabulary Description Language 1.0: RDF Schema.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
</dd><dt id="bib-XMLSCHEMA-2">[XMLSCHEMA-2]</dt><dd>Paul V. Biron; Ashok Malhotra. <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML Schema Part 2: Datatypes Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>
</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-Ontology-Namespace">[PROV-Ontology-Namespace]</dt><dd>TBD<a href="http://www.w3.org/ns/prov-o/"><cite>PROV Ontology Namespace</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/ns/prov-o/">http://www.w3.org/ns/prov-o/</a>