--- a/ontology/Overview.html Thu Oct 20 15:08:17 2011 +0100
+++ b/ontology/Overview.html Thu Oct 20 15:09:48 2011 +0100
@@ -479,7 +479,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</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 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-13-october-2011">W3C Working Draft 13 October 2011</h2><dl><dt>This version:</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>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 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-20-october-2011">W3C Working Draft 20 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111020/">http://www.w3.org/TR/2011/WD-prov-o-20111020/</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>
@@ -489,10 +489,11 @@
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr /></div>
<div id="abstract" class="introductory section"><h2>Abstract</h2>
-<p> The PROV Ontology Model (also PROV ontology) encodes the PROV Data 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>TODO: <em class="rfc2119" title="must">must</em> include at least one customized paragraph. This section <em class="rfc2119" title="should">should</em> include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs <em class="rfc2119" title="should">should</em> explain the publication context, including rationale and relationships to other work. See examples and more discussion in the Manual of Style.<a href="http://www.w3.org/2001/06/manual/#Status">TODO</a></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></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>Time</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">2.1.6 </span>Revision</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">2.1.7 </span>ProvenanceContainer</a></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="#wasderivedfrom" class="tocxref"><span class="secno">2.2.2 </span>wasDerivedFrom</a></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></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></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="#remaining-constraints" class="tocxref"><span class="secno">4.3.7 </span>Remaining constraints not yet adressed by PROV-O</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> The PROV Ontology Model (also PROV ontology) encodes the PROV Data
+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></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="#revision" class="tocxref"><span class="secno">2.1.6 </span>Revision</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="#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></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>
@@ -513,7 +514,7 @@
not</em>", "<em class="rfc2119" title="should">should</em>", "<em class="rfc2119" title="should not">should not</em>", "<em class="rfc2119" title="recommended">recommended</em>", "<em class="rfc2119" title="may">may</em>", and
"<em class="rfc2119" title="optional">optional</em>" in this document are to be interpreted as described in
[<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
-
+
<div class="section">
<h3 id="guide-to-this-document">Guide to this Document</h3>
<p> This document is intended for provide an understanding of
@@ -605,7 +606,6 @@
</rdf:Description></pre>
</div>
- <div class="issue">Definition of Entity in PROV-DM is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
</div>
<!-- Classes -->
@@ -662,16 +662,16 @@
<div id="time" class="section">
- <h4><span class="secno">2.1.5 </span>Time</h4>
+ <h4><span class="secno">2.1.5 </span>TemporalEntity</h4>
<div><b>Class Description</b></div>
- <p>Time represents temporal information about entities in the Provenance model.</p>
+ <p>TemporalEntity represents temporal information about entities in the Provenance model. This class has been re-used from the OWL Time ontology. The PROV ontology also models the two sub classes of TemporalEntity, namely Instant and Interval.</p>
<div><b>OWL syntax</b></div>
- <pre>prov:Time rdfs:subClassOf owl:Thing.</pre>
+ <pre>time:TemporalEntity rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
- <p> Example of instances of class Time from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of Time is given below.
+ <p> Example of instances of class TemporalEntity from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of class Instant is given below.
</p><div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#t+1">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <rdf:type rdf:resource="http://www.w3.org/2006/time#Instant"/>
</rdf:Description></pre>
</div>
</div>
@@ -684,8 +684,7 @@
<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 class="issue">Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
- </div>
+ </div>
@@ -695,11 +694,15 @@
<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>
<pre>prov:ProvenanceContainer rdfs:subClassOf owl:Thing.</pre>
- <p>Examples of instance of class ProvenanceContainer includes a file describing the manufacturing details of a car, such as its batch number, manufacturer, date of manufacture, place of manufacture etc. </p>
+ <p>Examples of instance of class ProvenanceContainer includes a file describing the manufacturing details of a car, such as its batch number, manufacturer, date of manufacture, place of manufacture etc. </p>
+
<div class="note"> According to the definitions of ProvenanceContainer and Account, both contain a set of provenance assertions and have an identifier. Hence, ProvenanceContainer class can also be used to create instances of accounts.
</div>
- <div class="issue">Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
<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.7.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</h5>
+ <p>Placeholder for Tim's description</p>
+ </div>
</div>
@@ -795,18 +798,32 @@
</div>
<div class="issue">Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
<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>
+ <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" />
+ <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>
+ <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" />
+ <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>
<div id="used" class="section">
- <h4><span class="secno">2.2.3 </span>Used</h4>
- <p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
+ <h4><span class="secno">2.2.3 </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" />
- <div class="issue">Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
<div><b>Example</b></div>
- <p> Example of Used 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 Used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of used 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 used 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:used rdf:resource="http://www.example.com/crimeFile#e2"/>
@@ -821,6 +838,7 @@
<h4><span class="secno">2.2.4 </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" />
<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>
@@ -829,6 +847,7 @@
<div id="wascomplementof" class="section">
<h4><span class="secno">2.2.5 </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>
@@ -847,11 +866,7 @@
</rdf:Description>
</prov:wasControlledBy>
</rdf:Description> </pre>
- </div>
- <div class="issue">Mutual ivpOf each other should be agreed. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
- <div class="issue">Do we need a sameAsEntity relation. This is <a href="http://www.w3.org/2011/prov/track/issues/35">ISSUE-35</a></div>
- <div class="issue">Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
- <div class="issue"> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
+ </div>
</div>
@@ -886,6 +901,18 @@
<img alt="wasScheduledAfter links ProcessExecution to ProcessExecution" style="height: 3em" src="diagram-history/khalidDiagrams/wasScheduledAfter.png" />
</div>
+ <div id="followed" class="section">
+ <h4><span class="secno">2.2.10 </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" />
+ </div>
+
+ <div id="hastemporalvalue" class="section">
+ <h4><span class="secno">2.2.11 </span>hasTemporalValue</h4>
+ <p> This object property links an instance of ProcessExecution or Entity with TemporalEntity thereby allowing association of time value with instances of the two classes and their subclasses
+ </p>
+ </div>
+
</div>
<div id="characteristics-of-object-properties" class="section">
@@ -976,8 +1003,19 @@
</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
</td></tr></tbody></table>
- <div class="note">Some of them may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>isUsedBY</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>isUsedBY</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.
- </div>
+ <div class="note">Some of them may be subject to discussion. In
+ particular, regarding the object properties
+ <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>used</i>,
+ we did not specify whether they are transitive or not. One may
+ argue that given that an agent can be a process execution, a
+ process execution, e.g., <i>pe1</i>, can be controlled by an
+ agent <i>pe2</i>, which happens to be a process execution that
+ is controlled by an agent <i>ag</i>, and that, therefore,
+ <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument
+ can be applied to <i>wasGeneratedBy</i> and <i>used</i>. That
+ said, we are not convinced that these properties should be
+ declared as transitive. In fact, we are more inclined towards
+ specifying that they are not. </div>
</div>
<div id="annotation-properties" class="section">
@@ -1003,7 +1041,7 @@
<div id="overview-of-the-ontology" class="section">
<h3><span class="secno">2.5 </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_11_October_2011.png " />
+ <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 " />
<!--
<p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
@@ -1012,10 +1050,19 @@
-->
</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">
<!-- OddPage -->
@@ -1717,7 +1764,8 @@
<div id="provenance-constraint-on-wasgeneratedby-generation-pe-ordering" class="section">
<h4><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
<p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of the PE instance.</p>
- <div class="issue">"Given an assertion wasGeneratedBy(x,pe,r) or wasGeneratedBy(x,pe,r,t), one can infer that the generation of the thing denoted by x precedes the end of pe and follows the beginning of pe." 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/105">ISSUE-105</a></div>
+ <div class="note"> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ </div>
</div>
<div id="provenance-constraint-on-wasgeneratedby-generation-unicity" class="section">
<h4><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</h4>
@@ -1735,125 +1783,72 @@
<p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a ProcessExecution instance pe by Used relation) to be "used" before pe terminates and also the "generation" of e precedes "use" of e.
</p>
<div class="issue">"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by pe and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
- </div>
- <div id="remaining-constraints" class="section">
- <h4><span class="secno">4.3.7 </span>Remaining constraints not yet adressed by PROV-O</h4>
- <ul>
-<li><a id="use-pe-ordering">use-pe-ordering</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
- assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds, one can
-infer that the use of the thing denoted by <b>e</b> precedes the end
-of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
-can infer that the generation of the thing denoted by <b>e</b> always precedes
-its use." (<a href="../model/ProvenanceModel.html#use-pe-ordering">definition</a>)
-</li>
-
-<li> <a id="derivation-attributes">derivation-attributes</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, if and only if:
- the values of some attributes
-of <b>e2</b> are partly or fully determined by the values of some
-attributes of <b>e1</b>." (<a href="../model/ProvenanceModel.html#derivation-attributes">definition</a>)
-</li>
-
-<li><a id="derivation-use-generation-ordering">derivation-use-generation-ordering</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, then
-the use
-of characterized thing denoted by <b>e1</b> precedes the generation of
-the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#derivation-use-generation-ordering">definition</a>)
-</li>
-
-<li><a id="derivation-process-execution">derivation-process-execution</a> "If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
-such that:
- <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b>." (<a href="../model/ProvenanceModel.html#derivation-process-execution">definition</a>)
-</li>
-
-
-<li><a id="derivation-events">derivation-events</a> "If
-<b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then
-<b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also hold."
-(<a href="../model/ProvenanceModel.html#derivation-events">definition</a>)
-</li>
-
-<li> <a id="derivation-use">derivation-use</a>
-<p>Given a process execution expression identified by <span class="name">pe</span>, entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier
-<span class="name">q2</span>,
-<span class="conditional">if</span> <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">wasGeneratedBy(e2,pe,q2)</span> hold, <span class="conditional">then</span> there exists a qualifier <span class="name">q1</span>,
-such that <span class="name">used(pe,e1,q1)</span> also holds.
-(<a href="../model/ProvenanceModel.html#derivation-use">definition</a>)
-</p></li>
-
-
-<li>
-<a id="derivation-generation-generation-ordering">derivation-generation-generation-ordering</a>
-Given two entity expressions denoted by <span class="name">e1</span> and
-<span class="name">e2</span>, <span class="conditional">if</span> the
-expression <span class="name">wasEventuallyDerivedFrom(e2,e1)</span>
- holds, <span class="conditional">then</span> the
- generation event of the characterized thing represented by the entity
- expression denoted by <span class="name">e1</span> precedes the
- generation event of
- the characterized thing represented by the entity expression denoted by
- <span class="name">e2</span>.
-(<a href="../model/ProvenanceModel.html#derivation-generation-generation-ordering">definition</a>)
-</li>
-
-<li>
-<a id="derivation-linked-independent">derivation-linked-independent</a>
-Given two entity expressions denoted by <span class="name">e1</span> and
-<span class="name">e2</span>, <span class="conditional">if</span> the
-assertion <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,q12,q1)</span>
- holds, <span class="conditional">then</span> the
- the expression <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> also holds.
-
-(<a href="../model/ProvenanceModel.html#derivation-linked-independent">definition</a>)
-</li>
-
-<li>
-<a id="wasComplementOf-necessary-cond">wasComplementOf-necessary-cond</a>
-An assertion "wasComplementOf(B,A)" holds over the temporal intersection
-of A and B, <span class="conditional">only if</span>:
-<ol>
-<li> if a mapping can be established from an attribute X of entity
-expression identified by B to an attribute Y of entity expression
-identified by A, then the values of A and B must be consistent with that
-mapping;</li>
- <li>entity expression identified by B has some attribute that entity
- expression identified by A does not have.
- </li></ol>
-(<a href="../model/ProvenanceModel.html#wasComplementOf-necessary-cond">definition</a>)
-</li>
-
-<li>
-<a id="participation">participation</a>
-Given two identifiers <span class="name">pe</span> and <span class="name">e</span>, respectively identifying a process execution
-expression and an entity expression, the expression <span class="name">hadParticipant(pe,e)</span> holds <span class="conditional">if and only if</span>:
-<ul>
-<li> <span class="name">used(pe,e)</span> holds, or</li>
-<li> <span class="name">wasControlledBy(pe,e)</span> holds, or</li>
-<li><span class="name">wasComplementOf(e1,e)</span> holds for some
-entity expression identified by <span class="name">e1</span>, and
- <span class="name">hadParticipant(pe,e1)</span> holds some process
- execution expression identified by <span class="name">pe</span>.</li>
- </ul>
-(<a href="../model/ProvenanceModel.html#participation">definition</a>)
-
-</li>
-
-</ul>
-
-<div class="note">The above constraints are extracted from the
- ProvenanceModel document. The text below should be kept consistent
- with the other document, with bidirectional links. The plan is to
- insert formalizations of these constraints once the OWL
- ontology/vocabulary is mature enough to permit this.
-
- If a constraint is changed in the model document, please copy the
- new version here, and check whether it is still consistent with the
- formalization (if any).
-
- If a constraint is dropped, please mark it as "defunct" - don't
- delete it!
- </div>
-</div>
+ </div>
+ <div id="provenance-constraint-on-derivation-attributes" class="section">
+ <h4><span class="secno">4.3.7 </span>Provenance constraint on wasDerivedFrom (derivation-attributes)</h4>
+ <p>The PROV-DM describes a constraint for asserting wasDerivedFrom property between two Entity instances if some attributes of an Entity instance are partially or fully determined by attributes values of the other Entity instance.
+ </p>
+ <div class="issue">"Given a process execution expression denoted by pe, entity expressions denoted by e1 and e2, qualifiers q1 and q2, the assertion wasDerivedFrom(e2,e1,pe,q2,q1) or wasDerivedFrom(e2,e1) holds if and only if the values of some attributes of the entity expression identified by e2 are partly or fully determined by the values of some attributes of the entity expression identified by e1." This is <a href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a></div>
+ </div>
+ <div id="provenance-constraint-on-derivation-use-generation-ordering" class="section">
+ <h4><span class="secno">4.3.8 </span>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1), then the for time instant t1 associated with a PE instance that "used" is less than the time instant t2 associated with "generation" of e2.
+ </p>
+ <div class="note"> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ </div>
+ </div>
+ <div id="provenance-constraint-on-derivation-events" class="section">
+ <h4><span class="secno">4.3.9 </span>Provenance constraint on wasDerivedFrom (derivation-events)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1, pe), then wasGeneratedBy(e2, pe) and used(pe, e1) can also be asserted.
+ </p>
+ <div class="note"> Since the above constraint defined in PROV-DM does not define how pe is linked to the derivation of e2 from e1, this constraint can be supported in the "opposite" direction in PROV-O. In other words, given e2 was generated at time instant t2 by pe and pe used e1 at time instant t1 and t1 is less than t2, then we can assert that wasDerivedFrom(e2, e1).
+ </div>
+ </div>
+ <div id="provenance-constraint-on-derivation-process-execution" class="section">
+ <h4><span class="secno">4.3.10 </span>Provenance constraint on wasDerivedFrom (derivation-events)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, then there exists some PE instance such that wasGeneratedBy(e2, pe) and used(pe, e1) can also be asserted.
+ </p>
+ <div class="note"> This constraint is a re-statement of the generic Semantic Web "open-world assumption". Hence, it is not mapped to PROV ontology.
+ </div>
+ </div>
+ <div id="provenance-constraint-on-derivation-use" class="section">
+ <h4><span class="secno">4.3.11 </span>Provenance constraint on wasDerivedFrom (derivation-use)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, and wasGeneratedBy(e2, pe) is also asserted then Used(pe, e1) can also be asserted.
+ </p>
+ <div class="note"> This will be asserted as a rule.
+ </div>
+ </div>
+ <div id="provenance-constraint-on-derivation-generation-generation-ordering" class="section">
+ <h4><span class="secno">4.3.12 </span>Provenance constraint on wasEventuallyDerivedFrom (derivation-generation-generation-ordering)</h4>
+ <p>The PROV-DM describes a constraint that if wasEventuallyDerivedFrom property is asserted between two Entity instances e1 and e2, then generation of e1 occurred before generation of e2.
+ </p>
+ <div class="note"> Without an explicit association of <a href="#time">TemporalEntity</a> (or event) with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ </div>
+ </div>
+ <div id="provenance-constraint-on-derivation-linked-independent" class="section">
+ <h4><span class="secno">4.3.13 </span>Provenance constraint on wasEventuallyDerivedFrom (derivation-linked-independent)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, then wasEventuallyDerivedFrom property can also be asserted between the two Entity instances.
+ </p>
+ <div class="note"> Is this an equivalence constraint or can we assert a subPropertyOf property between wasDerivedFrom and wasEventuallyFrom?
+ </div>
+ </div>
+ <div id="provenance-constraint-on-complementof-necessary-cond" class="section">
+ <h4><span class="secno">4.3.14 </span>Provenance constraint on wasComplementOf (wasComplementOf-necessary-cond)</h4>
+ <p>The PROV-DM describes a constraint that wasComplementOf property holds between two entities over a temporal intersection of the two entities.
+ </p>
+ <div class="note"> Without an explicit association of time value, this constraint cannot be stated or enforced in PROV ontology.
+ </div>
+ </div>
+ <div id="provenance-constraint-on-hasParticipant-participant" class="section">
+ <h4><span class="secno">4.3.15 </span>Provenance constraint on hadParticipant (participant)</h4>
+ <p>The PROV-DM describes a constraint that hadParticipant property holds between an instance of Entity and instance of ProcessExecution if the two instances are linked by "used" of "wasControlledBy" or "wasComplementOf".
+ </p>
+ <div class="issue"> "Given two identifiers pe and e, respectively identifying a process execution expression and an entity expression, the expression hadParticipant(pe,e) holds if and only if:
+ *used(pe,e) holds, or
+ *wasControlledBy(pe,e) holds, or
+ *wasComplementOf(e1,e) holds for some entity expression identified by e1, and hadParticipant(pe,e1) holds some process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
+ </div>
+ </div>
</div>
</div>
@@ -1876,9 +1871,10 @@
</dd><dt id="bib-OWL2-PRIMER">[OWL2-PRIMER]</dt><dd>Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a>
</dd><dt id="bib-OWL2-RDF-BASED-SEMANTICS">[OWL2-RDF-BASED-SEMANTICS]</dt><dd>Michael Schneider. <a href="http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/"><cite>OWL 2 Web Ontology Language:RDF-Based Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/">http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/</a>
</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-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-DM">[PROV-DM]</dt><dd>Luc Moreau, Paolo Missier<a href="http://www.w3.org/TR/owl2-direct-semantics"><cite>PROV Conceptual Model</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html</a>
-</dd><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: </dd><dt id="bib-PROV-PAQ">[PROV-PAQ]</dt><dd>Graham Klyne and Paul Groth <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html"><cite>Provenance Access and Query</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html">http://dvcs.w3.org/hg/prov/tip/paq/provenance-access.html</a>
-</dd></dl></div></div></body></html>
\ No newline at end of file
+</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>
+</dd><dt id="bib-PROV-PAQ">[PROV-PAQ]</dt><dd>Graham Klyne and Paul Groth <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html"><cite>Provenance Access and Query</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html">http://dvcs.w3.org/hg/prov/tip/paq/provenance-access.html</a>
+</dd></dl></div></div></body></html>
--- a/ontology/ProvenanceFormalModel.html Thu Oct 20 15:08:17 2011 +0100
+++ b/ontology/ProvenanceFormalModel.html Thu Oct 20 15:09:48 2011 +0100
@@ -17,9 +17,9 @@
var extraReferences = {
"PROV-DM":
"Luc Moreau, Paolo Missier"+
- "<a href=\"http://www.w3.org/TR/owl2-direct-semantics\"><cite>PROV Conceptual Model</cite></a>. "+
- "2011, Work in progress. "+
- "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html\">http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html</a>",
+ "<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>",
"PROV-PAQ":
"Graham Klyne and Paul Groth "+
@@ -31,7 +31,7 @@
"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/</a>",
+ "URL: <a href=\"http://www.w3.org/ns/prov-o/\">http://www.w3.org/ns/prov-o/`</a>",
};
var respecConfig = {
@@ -122,7 +122,8 @@
<body>
<section id="abstract">
-<p> The PROV Ontology Model (also PROV ontology) encodes the PROV Data Model [[PROV-DM]] 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>
+<p> The PROV Ontology Model (also PROV ontology) encodes the PROV Data
+Model [[!PROV-DM]] 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>
</section>
@@ -463,13 +464,13 @@
<section id="used">
- <h4>Used</h4>
- <p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
+ <h4>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 src="diagram-history/khalidDiagrams/used.png"
style="height: 3em" alt="used links ProcessExecution to Entity" />
<div><b>Example</b></div>
- <p> Example of Used 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 Used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of used 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 used 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">
@@ -660,8 +661,19 @@
</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
</td></tr></table>
- <div class='note'>Some of them may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>isUsedBY</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>isUsedBY</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.
- </div>
+ <div class='note'>Some of them may be subject to discussion. In
+ particular, regarding the object properties
+ <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>used</i>,
+ we did not specify whether they are transitive or not. One may
+ argue that given that an agent can be a process execution, a
+ process execution, e.g., <i>pe1</i>, can be controlled by an
+ agent <i>pe2</i>, which happens to be a process execution that
+ is controlled by an agent <i>ag</i>, and that, therefore,
+ <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument
+ can be applied to <i>wasGeneratedBy</i> and <i>used</i>. That
+ said, we are not convinced that these properties should be
+ declared as transitive. In fact, we are more inclined towards
+ specifying that they are not. </div>
</section>
<section id="annotation-properties">