--- a/ontology/Overview.html Thu Nov 17 18:10:00 2011 +0000
+++ b/ontology/Overview.html Thu Nov 17 22:36:16 2011 +0000
@@ -478,157 +478,11 @@
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 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>
+ <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-17-november-2011">W3C Working Draft 17 November 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111117/">http://www.w3.org/TR/2011/WD-prov-o-20111117/</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>
+<dt>Authors:</dt><dd><span>(In alphabetical order)</span></dd>
+<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>
<dd><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a>, Universidad Politécnica de Madrid, Spain</dd>
<dd><a href="http://tw.rpi.edu/instances/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute, USA</dd>
@@ -636,11 +490,10 @@
</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>
+<p> The PROV Ontology (also PROV-O) 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="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#guide-to-this-document" class="tocxref"><span class="secno">1.1 </span>Guide to this Document</a></li></ul></li><li class="tocline"><a href="#prov-ontology" class="tocxref"><span class="secno">2. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">2.1 </span>OWL2 Syntax Used in this Document</a></li><li class="tocline"><a href="#namespace-and-owl2-version" class="tocxref"><span class="secno">2.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">3. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">3.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#processexecution" class="tocxref"><span class="secno">3.1.2 </span>ProcessExecution</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">3.1.3 </span>Agent</a></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">3.1.4 </span>Recipe</a></li><li class="tocline"><a href="#temporalentity" class="tocxref"><span class="secno">3.1.5 </span>TemporalEntity</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">3.1.6 </span>Time</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">3.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">3.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">3.1.8 </span>Location</a></li><li class="tocline"><a href="#entityinrole" class="tocxref"><span class="secno">3.1.9 </span>EntityInRole</a></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">3.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">3.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">3.2.2 </span>wasRevisionOf</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">3.2.3 </span>wasDerivedFrom</a></li><li class="tocline"><a href="#waseventuallyderivedfrom" class="tocxref"><span class="secno">3.2.4 </span>wasEventuallyDerivedFrom</a></li><li class="tocline"><a href="#dependedon" class="tocxref"><span class="secno">3.2.5 </span>dependedOn</a></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">3.2.6 </span>used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">3.2.7 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">3.2.8 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">3.2.9 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">3.2.10 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">3.2.11 </span>wasInformedBy</a></li><li class="tocline"><a href="#wascheduledafter" class="tocxref"><span class="secno">3.2.12 </span>wasScheduledAfter</a></li><li class="tocline"><a href="#followed" class="tocxref"><span class="secno">3.2.13 </span>followed</a></li><li class="tocline"><a href="#attribution" class="tocxref"><span class="secno">3.2.14 </span>wasAttributedTo</a></li><li class="tocline"><a href="#quotation" class="tocxref"><span class="secno">3.2.15 </span>wasQuoteOf</a></li><li class="tocline"><a href="#summary" class="tocxref"><span class="secno">3.2.16 </span>wasSummaryOf</a></li><li class="tocline"><a href="#originalsource" class="tocxref"><span class="secno">3.2.17 </span>hadOriginalSource</a></li><li class="tocline"><a href="#hastemporalvalue" class="tocxref"><span class="secno">3.2.18 </span>hasTemporalValue</a></li><li class="tocline"><a href="#startedAt" class="tocxref"><span class="secno">3.2.19 </span>startedAt</a></li><li class="tocline"><a href="#endedAt" class="tocxref"><span class="secno">3.2.20 </span>endedAt</a></li><li class="tocline"><a href="#wasGeneratedAt" class="tocxref"><span class="secno">3.2.21 </span>wasGeneratedAt</a></li><li class="tocline"><a href="#wasAssumedBy" class="tocxref"><span class="secno">3.2.22 </span>wasAssumedBy</a></li><li class="tocline"><a href="#assumedRole" class="tocxref"><span class="secno">3.2.23 </span>assumedRole</a></li><li class="tocline"><a href="#assumedRoleAt" class="tocxref"><span class="secno">3.2.24 </span>assumedRoleAt</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">3.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">3.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#collections" class="tocxref"><span class="secno">3.5 </span>Collections</a><ul class="toc"><li class="tocline"><a href="#collection-adding" class="tocxref"><span class="secno">3.5.1 </span>Expansion</a></li><li class="tocline"><a href="#collection-removal" class="tocxref"><span class="secno">3.5.2 </span>Reduction</a></li><li class="tocline"><a href="#emptycollection" class="tocxref"><span class="secno">3.5.3 </span>EmptyCollection</a></li><li class="tocline"><a href="#collection-content" class="tocxref"><span class="secno">3.5.4 </span>Collection content</a></li></ul></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">3.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">4. </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">4.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">4.1.1 </span>Specialization of PROV Ontology Classes</a><ul class="toc"><li class="tocline"><a href="#cf-journalist" class="tocxref"><span class="secno">4.1.1.1 </span>cf:Journalist</a></li><li class="tocline"><a href="#cf-crimefile" class="tocxref"><span class="secno">4.1.1.2 </span>cf:CrimeFile</a></li><li class="tocline"><a href="#cf-filecreation" class="tocxref"><span class="secno">4.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">4.1.2 </span>Specialization of PROV Ontology Properties</a><ul class="toc"><li class="tocline"><a href="#cf-hadfilepath" class="tocxref"><span class="secno">4.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">4.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">4.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">4.2.2 </span>Workflow extensions to PROV properties</a></li><li class="tocline"><a href="#workflow-structure" class="tocxref"><span class="secno">4.2.3 </span>Workflow structure</a></li><li class="tocline"><a href="#example-workflow" class="tocxref"><span class="secno">4.2.4 </span>Example workflow</a></li><li class="tocline"><a href="#example-workflow-run" class="tocxref"><span class="secno">4.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">5. </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">5.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#guide-to-this-document" class="tocxref"><span class="secno">1.1 </span>Guide to this Document</a></li></ul></li><li class="tocline"><a href="#prov-ontology" class="tocxref"><span class="secno">2. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#mapping-the-prov-dm-terms-to-prov-ontology" class="tocxref"><span class="secno">2.1 </span>Mapping the PROV-DM terms to PROV Ontology</a></li><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">2.2 </span>OWL2 Syntax Used in this Document</a></li><li class="tocline"><a href="#namespace-and-owl2-version" class="tocxref"><span class="secno">2.3 </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">3. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">3.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#processexecution" class="tocxref"><span class="secno">3.1.2 </span>ProcessExecution</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">3.1.3 </span>Agent</a></li><li class="tocline"><a href="#temporalentity" class="tocxref"><span class="secno">3.1.4 </span>TemporalEntity</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">3.1.5 </span>ProvenanceContainer</a><ul class="toc"><li class="tocline"><a href="#modeling-provenancecontainer-and-account-as-rdf-graph" class="tocxref"><span class="secno">3.1.5.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">3.1.6 </span>Location</a></li><li class="tocline"><a href="#qualifiedinvolvement" class="tocxref"><span class="secno">3.1.7 </span>QualifiedInvolvement</a><ul class="toc"><li class="tocline"><a href="#usage" class="tocxref"><span class="secno">3.1.7.1 </span>Usage</a></li><li class="tocline"><a href="#participation" class="tocxref"><span class="secno">3.1.7.2 </span>Participation</a></li><li class="tocline"><a href="#control" class="tocxref"><span class="secno">3.1.7.3 </span>Control</a></li><li class="tocline"><a href="#generation" class="tocxref"><span class="secno">3.1.7.4 </span>Generation</a></li></ul></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">3.1.8 </span>Recipe</a></li><li class="tocline"><a href="#role" class="tocxref"><span class="secno">3.1.9 </span>Role</a></li><li class="tocline"><a href="#classes-under-discussion" class="tocxref"><span class="secno">3.1.10 </span>Classes under Discussion</a><ul class="toc"><li class="tocline"><a href="#time" class="tocxref"><span class="secno">3.1.10.1 </span>Time</a></li></ul></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">3.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">3.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">3.2.2 </span>wasRevisionOf</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">3.2.3 </span>wasDerivedFrom</a></li><li class="tocline"><a href="#waseventuallyderivedfrom" class="tocxref"><span class="secno">3.2.4 </span>wasEventuallyDerivedFrom</a></li><li class="tocline"><a href="#dependedon" class="tocxref"><span class="secno">3.2.5 </span>dependedOn</a></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">3.2.6 </span>used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">3.2.7 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">3.2.8 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">3.2.9 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">3.2.10 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">3.2.11 </span>wasInformedBy</a></li><li class="tocline"><a href="#wascheduledafter" class="tocxref"><span class="secno">3.2.12 </span>wasScheduledAfter</a></li><li class="tocline"><a href="#hadtemporalvalue" class="tocxref"><span class="secno">3.2.13 </span>hadTemporalValue</a><ul class="toc"><li class="tocline"><a href="#startedat" class="tocxref"><span class="secno">3.2.13.1 </span>startedAt</a></li><li class="tocline"><a href="#endedat" class="tocxref"><span class="secno">3.2.13.2 </span>endedAt</a></li><li class="tocline"><a href="#wasGeneratedat" class="tocxref"><span class="secno">3.2.13.3 </span>wasGeneratedAt</a></li></ul></li><li class="tocline"><a href="#attribution" class="tocxref"><span class="secno">3.2.14 </span>wasAttributedTo</a></li><li class="tocline"><a href="#quotation" class="tocxref"><span class="secno">3.2.15 </span>wasQuoteOf</a></li><li class="tocline"><a href="#summary" class="tocxref"><span class="secno">3.2.16 </span>wasSummaryOf</a></li><li class="tocline"><a href="#originalsource" class="tocxref"><span class="secno">3.2.17 </span>hadOriginalSource</a></li><li class="tocline"><a href="#hadqualifiedusage" class="tocxref"><span class="secno">3.2.18 </span>hadQualifiedUsage</a></li><li class="tocline"><a href="#hadqualifiedparticipation" class="tocxref"><span class="secno">3.2.19 </span>hadQualifiedParticipation</a></li><li class="tocline"><a href="#hadqualifiedcontrol" class="tocxref"><span class="secno">3.2.20 </span>hadQualifiedControl</a></li><li class="tocline"><a href="#hadqualifiedgeneration" class="tocxref"><span class="secno">3.2.21 </span>hadQualifiedGeneration</a></li><li class="tocline"><a href="#hadqualifiedentity" class="tocxref"><span class="secno">3.2.22 </span>hadQualifiedEntity</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">3.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">3.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">3.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">4. </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">4.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">4.1.1 </span>Specialization of PROV Ontology Classes</a><ul class="toc"><li class="tocline"><a href="#cf-journalist" class="tocxref"><span class="secno">4.1.1.1 </span>cf:Journalist</a></li><li class="tocline"><a href="#cf-crimefile" class="tocxref"><span class="secno">4.1.1.2 </span>cf:CrimeFile</a></li><li class="tocline"><a href="#cf-filecreation" class="tocxref"><span class="secno">4.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">4.1.2 </span>Specialization of PROV Ontology Properties</a><ul class="toc"><li class="tocline"><a href="#cf-hadfilepath" class="tocxref"><span class="secno">4.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">4.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">4.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">4.2.2 </span>Workflow extensions to PROV properties</a></li><li class="tocline"><a href="#workflow-structure" class="tocxref"><span class="secno">4.2.3 </span>Workflow structure</a></li><li class="tocline"><a href="#example-workflow" class="tocxref"><span class="secno">4.2.4 </span>Example workflow</a></li><li class="tocline"><a href="#example-workflow-run" class="tocxref"><span class="secno">4.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">5. </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">5.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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">5.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>
@@ -649,27 +502,19 @@
<!-- OddPage -->
<h2><span class="secno">1. </span>Introduction</h2>
<p>
- PROV Ontology Model (also PROV ontology) defines the normative modeling of the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] using the W3C OWL2 Web Ontology Language. This document specification describes the set of classes, properties, and restrictions that constitute the PROV ontology, which have been introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. This ontology specification provides the foundation for implementation of provenance applications in different applications using the PROV ontology for representing, exchanging, and integrating provenance information. Together with the PROV Access and Query [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-PAQ">PROV-PAQ</a></cite>] and PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>], this document forms a framework for provenance information management in domain-specific Web-based applications.
+ PROV Ontology (also PROV-O) defines the normative modeling of the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] using the W3C OWL2 Web Ontology Language. This document specification describes the set of classes, properties, and restrictions that constitute the PROV ontology, which have been introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. This ontology specification provides the foundation for implementation of provenance applications in different domains using the PROV ontology for representing, exchanging, and integrating provenance information. Together with the PROV Access and Query [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-PAQ">PROV-PAQ</a></cite>] and PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>], this document forms a framework for provenance information interchange and management in domain-specific Web-based applications.
</p>
<p>
- The PROV ontology classes and properties are defined such that they can be specialized for modeling application-specific provenance information in a variety of domains. Thus, the PROV ontology is expected to serve as a <i>reference model</i> for domain-specific provenance ontology and thereby facilitate consistent provenance interchange. This document uses an example <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] to demonstrate the specialization of PROV ontology.
+ The PROV ontology classes and properties are defined such that they can not only be used directly to represent provenance information, but also can be specialized for modeling application-specific provenance details in a variety of domains. Thus, the PROV ontology is expected to be both directly usable in applications as well as serve as a <i>reference model</i> for creation of domain-specific provenance ontology and thereby facilitate interoperable provenance modeling. This document uses an example <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] to demonstrate the use PROV-O classes and properties to model provenance information.
</p>
<p>
Finally, this document describes the formal semantics of the PROV ontology using the OWL2 semantics, [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-DIRECT-SEMANTICS">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>], and a set of provenance-specific inference rules. This is expected to support provenance implementations to automatically check for consistency of provenance information represented using PROV ontology and explicitly assert implicit provenance knowledge.
</p>
- <p>The key words "<em class="rfc2119" title="must">must</em>", "<em class="rfc2119" title="must not">must not</em>", "<em class="rfc2119" title="required">required</em>", "<em class="rfc2119" title="shall">shall</em>", "<em class="rfc2119" title="shall
- not">shall
- 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>
+ <p>The key words "<em class="rfc2119" title="must">must</em>", "<em class="rfc2119" title="must not">must not</em>", "<em class="rfc2119" title="required">required</em>", "<em class="rfc2119" title="shall">shall</em>", "<em class="rfc2119" title="shall not">shall 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 id="guide-to-this-document" class="section">
<h3><span class="secno">1.1 </span>Guide to this Document</h3>
- <p> This document is intended for provide an understanding of
- the PROV ontology and how it can be used by various applications
- to represent their provenance information. The intended audience
- of this document include users who are new to provenance
- modeling as well as experienced users who would like their provenance model compatible with the PROV ontology to facilitate standardization.This document assumes a basic understanding of the W3C OWL2 specification , including modeling of classes, properties, and restrictions in an OWL2 ontology. Readers are referred to the OWL2 documentations, starting with the [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>], for the OWL2 specification.
+ <p> This document is intended for provide an understanding of the PROV ontology and how it can be used by different applications to represent their provenance information. The intended audience of this document include users who are new to provenance modeling as well as experienced users who would like their provenance model compatible with the PROV ontology to facilitate standardization. This document assumes a basic understanding of the W3C RDF(S) and OWL2 specification. Readers are referred to the OWL2 and RDF(S) documentations, starting with the [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>] and [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>], for further details about the OWL2 and RDF(S) specifications respectively.
</p>
<p><a href="#prov-ontology--owl-encoding-of-prov-data-model">Section 2</a> describes the mapping of the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] to the PROV ontology. <a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications">Section 3</a> introduces the classes and properties of the PROV ontology. <a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications">Section 4</a> describes the approach used to specialize the PROV ontology create a domain specific ontology for an example <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. The PROV ontology supports a set of provenance entailments and these are described in <a href="#entailments-supported-by-the-provenance-model">Section 5</a>.
</p>
@@ -687,35 +532,34 @@
<h2><span class="secno">2. </span>PROV Ontology</h2>
<p> The PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] introduces a minimal set of concepts to represent provenance information in a variety of application domains. This document maps the PROV Data Model to PROV Ontology using the OWL2 ontology language, which facilitates a fixed interpretation and use of the PROV Data Model concepts based on the formal semantics of OWL2 [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-DIRECT-SEMANTICS">OWL2-DIRECT-SEMANTICS</a></cite>] [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>].
</p>
- <p>The PROV Ontology is not designed to be used directly in a domain application and its Classes and Properties represent "higher-level" or abstract level concepts that can be specialized further for representing domain-specific provenance information. We briefly introduce some of the OWL2 modeling terms that will be used to describe the PROV ontology. An OWL2 <i>instance</i> is an individual object in a domain of discourse, for example a person named Alice or a car, and a set of individuals sharing a set of common characteristics is called a <i>class</i>. Person and Car are examples of classes representing the set of individual persons and cars respectively. The OWL2 object properties are used to link individuals, classes, or create a property hierarchy. For example, the object property "hasOwner" can be used to link car with person. The OWL2 datatype properties are used to link individuals or classes to data values, including XML Schema datatypes [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a></cite>].
+ <p>The PROV Ontology can be used directly in a domain application, though many domain applications may require specialization of PROV-O Classes and Properties for representing domain-specific provenance information. We briefly introduce some of the OWL2 modeling terms that will be used to describe the PROV ontology. An OWL2 <i>instance</i> is an individual object in a domain of discourse, for example a person named Alice or a car, and a set of individuals sharing a set of common characteristics is called a <i>class</i>. Person and Car are examples of classes representing the set of individual persons and cars respectively. The OWL2 object properties are used to link individuals, classes, or create a property hierarchy. For example, the object property "hasOwner" can be used to link car with person. The OWL2 datatype properties are used to link individuals or classes to data values, including XML Schema datatypes [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a></cite>].
</p>
- <p>The PROV Data Model document [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] introduces an example <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> describing the creation of crime statistics file stored on a shared file system and edited by journalists Alice, Bob, Charles, David, and Edith. This scenario is used as a running example in this document to describe the PROV ontology classes and properties, the specialization mechanism and entailments supported by the PROV ontology.
+ <p>The PROV Data Model document [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] introduces an example <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> describing the creation of crime statistics file stored on a shared file system and edited by journalists Alice, Bob, Charles, David, and Edith. This scenario is used as a running example in this document to describe the PROV ontology classes and properties, the specialization mechanism, and the entailments supported by the PROV ontology.
</p>
- <div id="owl2-syntax-used-in-this-document" class="section">
- <h3><span class="secno">2.1 </span>OWL2 Syntax Used in this Document</h3>
- <p>This document uses the RDF/XML syntax, which is the mandatory syntax
- supported by all OWL2 syntax [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>] to represent the
- PROV ontology. Provenance assertions using PROV-O can use any
- RDF syntax.
- </p></div>
+ <div id="mapping-the-prov-dm-terms-to-prov-ontology" class="section">
+ <h3><span class="secno">2.1 </span>Mapping the PROV-DM terms to PROV Ontology</h3>
+ <p>The PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] uses an Abstract Syntax Notation (ASN) to describe the set of provenance terms that are used to construct the PROV ontology. There are a number of differences between the PROV-DM ASN and the Semantic Web RDF, RDFS and OWL2 technologies; hence the approach used to model the provenance terms in PROV ontology differ, partially or significantly, from the PROV-DM approach.
+ </p>
+ <p>For example, the notion of "expressions" used in the PROV-DM map to RDF triple assertions in PROV-O. Similarly, the PROV-DM discusses the use of "Qualifier" to assert additional information about provenance terms. Following the general knowledge representation practices and OWL2 ontologies specifically, the PROV ontology specializes a given provenance term to create either a sub class or sub property to represent "additionally" qualified terms. Throughout this document, we explicitly state the difference, if any, between the PROV-DM term and PROV ontology term.
+ </p>
+ <div class="note"> In addition, RDF is strictly monotonic and "...it cannot express closed-world assumptions, local default preferences, and several other commonly used non-monotonic constructs."[<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>], but the PROV-DM seems to introduce the notion of non-monotonic assertions through "Account" construct [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. For example, Account description in PROV-DM states that it "It provides a scoping mechanism for expression identifiers and for some contraints (such as generation-unicity and derivation-use)."
+ </div>
+ </div>
+ <div id="owl2-syntax-used-in-this-document" class="section">
+ <h3><span class="secno">2.2 </span>OWL2 Syntax Used in this Document</h3>
+ <p>This document uses the RDF/XML syntax, which is the mandatory syntax supported by all OWL2 syntax [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>] to represent the PROV ontology. Provenance assertions using PROV-O can use any of the RDF syntax defined in the RDF specification [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>].
+ </p>
+ </div>
<div id="namespace-and-owl2-version" class="section">
- <h3><span class="secno">2.2 </span>Namespace and OWL2 version</h3>
- <p>
-
- The corresponding OWL2 version of this PROV Ontology is
- available at [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>] and as
- <a href="ProvenanceOntology.owl">ProvenanceOntology.owl</a>. The namespace for
- the PROV ontology and all classes/properties defined in this
- document is <code>http://www.w3.org/ns/prov-o/</code> [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>]
- and is in this document denoted by the prefix <code>prov</code>.
+ <h3><span class="secno">2.3 </span>Namespace and OWL2 version</h3>
+ <p>
+ The corresponding OWL2 version of this PROV Ontology is available at [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>] and as <a href="ProvenanceOntology.owl">ProvenanceOntology.owl</a>. The namespace for the PROV ontology and all terms defined in this document is <code>http://www.w3.org/ns/prov-o/</code> [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>] and is in this document denoted by the prefix <code>prov</code>.
</p>
<div class="issue">
- It has been suggested that [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] and PROV-O should instead use
- the namespace <code>http://www.w3.org/ns/prov/</code> for terms that are
- common in both models. This is <a href="http://www.w3.org/2011/prov/track/issues/90">ISSUE-90</a>
+ It has been suggested that [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] and PROV-O should instead use the namespace <code>http://www.w3.org/ns/prov/</code> for terms that are common in both models. This is <a href="http://www.w3.org/2011/prov/track/issues/90">ISSUE-90</a>
</div>
</div>
</div>
@@ -727,14 +571,15 @@
<!-- OddPage -->
<h2><span class="secno">3. </span>PROV Ontology: Classes and Properties</h2>
- <p> We now introduce the classes and properties that constitute the PROV ontology. We first give a textual description of each ontology term, followed by OWL2 syntax representing the ontology term and an example use of the term in the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a>.
+ <p> We now introduce the classes and properties that constitute the PROV ontology. We first give a textual description of each ontology term, followed by OWL2 syntax representing the ontology term and an example use of the class in the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a>.
</p>
<div id="classes" class="section">
<h3><span class="secno">3.1 </span>Classes</h3>
- <p>The PROV ontology consists of classes that can be organized in a taxonomic structure.
- </p>
- <img alt="Class hierarchy of the PROV ontology" style="width: 50%; min-width: 25em; max-width: 37em" src="diagram-history/khalidDiagrams/Ontology_hierarchy.png" />
+ <p>The PROV ontology consists of classes that can be organized into a hierarchical structure using the <code>rdfs:subClassOf</code> property.
+
+ <img alt="Class hierarchy of the PROV ontology" style="width: 70%; min-width: 25em; max-width: 60em" src="diagram-history/khalidDiagrams/Ontology_hierarchy.png" />
<br />
+ </p>
<p><i>Note: CamelBack notation is used for class names</i></p>
<div id="entity" class="section">
<h4><span class="secno">3.1.1 </span>Entity</h4>
@@ -750,22 +595,15 @@
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
</rdf:Description></pre>
</div>
- <p>Attributes that are characterising the entity (as defined
- in PROV-DM) are stated using RDF properties of the asserted
- entity. Such properties <em class="rfc2119" title="should">should</em> be in a declared namespace,
- and <em class="rfc2119" title="may">may</em> be described by an application-specific vocabulary.
- Specialisation by subclassing or <code>rdf:type</code> is
- equivalent to specifying the reserved attribute <code>type</code>
- in PROV-DM.
+ <p>Additional assertions can be made about the Entity instances that describe additional attributes of the entities. Following common knowledge representation approach, the Entity class can be specialized to create multiple sub classes, using the <code>rdfs:subClassOf</code> property, representing distinct categories of entities using additional characterizing attributes (as defined in the [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]). The additional attributes <em class="rfc2119" title="should">should</em> use an appropriate namespace, and the new sub classes <em class="rfc2119" title="may">may</em> be introduced by application-specific provenance ontologies.
</p>
<div><b>Example</b></div>
<div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
- <rdf:type rdf:resource="http://www.example.com/crime#CrimeFile"/>
- <cf:hasLocation rdf:resource="http://www.example.com/crimeFile#sharedDirectoryLocation1"/>
- <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There
- was a lot of crime in London last month.</cf:hasFileContent>
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
+ <rdf:type rdf:resource="http://www.example.com/crime#CrimeFile">
+</rdf:Description>
+<rdf:Description rdf:about="http://www.example.com/crime#CrimeFile">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
</rdf:Description></pre>
</div>
@@ -780,14 +618,13 @@
<div><b>OWL syntax</b></div>
<pre>prov:ProcessExecution rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
- <p> Example of instances of class ProcessExecution from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are file creation (<i>pe0</i>) and file editing (<i>pe2</i>) . The RDF/XML syntax for asserting that pe2 is an instance of ProcessExecution is given below.
+ <p> Example instances of the class ProcessExecution (from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a>) are "file creation" (<i>pe0</i>) and "file editing" (<i>pe2</i>) . The RDF/XML syntax for asserting that pe2 is an instance of ProcessExecution is given below.
</p><div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
- <rdf:type rdf:resource="http://www.example.com/crime#Emailing"/>
</rdf:Description></pre>
</div>
- <div class="note"> pe2 is an instance of class <code>:Emailing</code>, which in the CrimeFile ontology is defined to be sub-class of class <code>prov:ProcessExecution</code>. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of <code>prov:ProcessExecution</code>. However, not all PROV-O clients might be able to do RDFS reasoning over third-party ontologies, therefore asserters <em class="rfc2119" title="should">should</em> explicitly assert any <code>prov</code> type or property which can be inferred from the specialising ontologies.
+ <div class="note"> pe2 is an instance of class <code>:Emailing</code>, which is defined to be sub-class of class <code>prov:ProcessExecution</code> in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of <code>prov:ProcessExecution</code>.
</div>
</div>
@@ -808,73 +645,57 @@
</div>
<div class="note"> Similar to example for Entity, both Alice and Edith are instances of class Journalist, which is defined to be "sub-class" of class Agent in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that both Alice and Edith are also instances of Agent.
</div>
- </div>
-
-
-
- <div id="recipe" class="section">
- <h4><span class="secno">3.1.4 </span>Recipe</h4>
- <div><b>Class Description</b></div>
- <p>Recipe represents a process specification. The definition of process specifications is outside the scope of PROV. Therefore, this class acts as a place holder in the ontology that can be extended and specialized by users.</p>
- <div><b>OWL syntax</b></div>
- <pre>prov:Recipe rdfs:subClassOf owl:Thing.</pre>
- <div><b>Example</b></div>
- <p> Recipe examples include backing recipes, programs and workflows.
- </p></div>
-
+ </div>
<div id="temporalentity" class="section">
- <h4><span class="secno">3.1.5 </span>TemporalEntity</h4>
+ <h4><span class="secno">3.1.4 </span>TemporalEntity</h4>
<div><b>Class Description</b></div>
- <p>TemporalEntity represents temporal information about
- entities in the Provenance model. This class has been re-used
- from the OWL Time ontology [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]. The PROV ontology also models the two sub classes of TemporalEntity, namely Instant and Interval.</p>
+ <p>TemporalEntity represents temporal information about entities in the Provenance model. This class has been re-used from the OWL Time ontology [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]. The PROV ontology also models the two sub classes of TemporalEntity, namely Instant and Interval.</p>
+ <p>The Instant class represents "point-line" temporal information that have "no interior points" [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]. The Interval class represents temporal information that have a non-zero duration [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]</p>
<div><b>OWL syntax</b></div>
<pre>time:TemporalEntity rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
- <p> Example of instances of class TemporalEntity from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#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/2006/time#Instant"/>
+ <p> Example of instances of class TemporalEntity from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. t+1 is associated with the instance of ProcessExecution pe2. The instances of TemporalEntity are linked to instances of Entity or ProcessExecution classes by the <a href="#hadtemporalvalue">hadTemporalValue</a> property that is described later in this document. </p>
+ <p>The RDF/XML syntax for this asserting that t+1 is an instance of class TemporalEntity and t+1 is associated with pe2 is given below.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
+ <prov:hadTemporalValue rdf:about="http://www.example.com/crimeFile#t+1">
+ <rdf:type rdf:resource="http://www.w3.org/2006/time#TemporalEntity"/>
+ </prov:hadTemporalValue>
</rdf:Description></pre>
</div>
- </div>
-
- <div id="time" class="section">
- <h4><span class="secno">3.1.6 </span>Time</h4>
- <div><b>Class Description</b></div>
- <p><code>Time</code> is subclass of <code>time:Instant</code>
- from [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>] which requires that the time is defined
- using the <code>time:inXSDDateTime</code> property. This
- class used with <code>startedAt</code> and other subproperties
- of <code>hasTemporalValue</code> ensures compatibility with <code>xsd:dateTime</code> literals
- expressions in [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] ASN and other serialisations.
- c</p>
- </div>
+
+ </div>
<div id="provenancecontainer" class="section">
- <h4><span class="secno">3.1.7 </span>ProvenanceContainer</h4>
+ <h4><span class="secno">3.1.5 </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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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 RDF graph containing set of assertions describing the provenance of a car, such as its manufacturer, date of manufacture, and place of manufacture.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#ProvenanceContainer1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/#ProvenanceContainer"/>
+ <cf:contains rdf:resource="http://www.example.com/crimeFile#Statement1"/>
+ <cf:contains rdf:resource="http://www.example.com/crimeFile#Statement2"/>
+ <cf:assertedBy rdf:resource="http://www.example.com/crimeFile#Alice"/>
+</rdf:Description> </pre>
+ </div>
<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">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">3.1.7.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</h5>
- <p>Placeholder for Tim's description</p>
+ <h5><span class="secno">3.1.5.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</h5>
+ <p>If a RDF graph contains a set of RDF assertions then, (a) if an explicit asserter is associated with the RDF graph it corresponds to the term "Account" in PROV-DM, and (b) if an asserted is not associated with the RDF graph it corresponds to the term "ProvenanceContainer" in PROV-DM.</p>
</div>
-
</div>
<div id="location" class="section">
- <h4><span class="secno">3.1.8 </span>Location</h4>
+ <h4><span class="secno">3.1.6 </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>
@@ -893,72 +714,153 @@
- <div id="entityinrole" class="section">
- <h4><span class="secno">3.1.9 </span>EntityInRole</h4>
+ <div id="qualifiedinvolvement" class="section">
+ <h4><span class="secno">3.1.7 </span>QualifiedInvolvement</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>
+ <p>The QualifiedInvolvement class represents an n-ary property to capture qualifying information related to the use of Entity by ProcessExecution.</p>
<div><b>OWL syntax</b></div>
- <pre>prov:EntityInRole rdfs:subClassOf prov:Entity.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class EntityInRole from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>author</i> role assumed by Bob and <i>file creator</i> role assumed by Alice. The RDF/XML syntax for asserting that Bob assumes the role of an author is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/>
- <prov:assumedRole rdf:resource="http://www.example.com/crime#author"/>
+ <pre>prov:QualifiedInvolvement rdfs:subClassOf owl:Thing.</pre>
+
+ <div id="usage" class="section">
+ <h5><span class="secno">3.1.7.1 </span>Usage</h5>
+ <div><b>Class Description</b></div>
+ <p>The Usage class represents an n-ary property to capture qualifying information related to the the use, generation, control, and participation.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Usage rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Usage from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> provenance scenario ??? is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#u1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Usage"/>
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#Bob"/>
</rdf:Description></pre>
- </div>
- <p>
- An <code>EntityInRole</code> is used together with
- <code>used</code>, <code>wasGeneratedBy</code> and
- <code>wasControlledBy</code> to specify that the
- <code>wasAssumedBy</code> entity
- participated in the relation in a given <em>role</em>. The role is
- specified using <code>assumedRole</code>, referring to a
- <code>Role</code>.
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/>
- <prov:assumedRole rdf:resource="http://www.example.com/crime#author"/>
- <crime:parameter>p1</crime:parameter>
- </prov:used>
-</rdf:Description> </pre>
- </div>
- <p>
- The example above corresponds to in [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] ASN
- <code>used(pe1, Bob, qualifier(role="author", parameter="p1")</code>.
- </p>
-
- <div class="issue">The PROV-DM defines the term <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#expression-qualifier">Qualifier</a> is not modeled explicitly in PROV ontology.</div>
+ </div>
+ </div>
+
+ <div id="participation" class="section">
+ <h5><span class="secno">3.1.7.2 </span>Participation</h5>
+ <div><b>Class Description</b></div>
+ <p>The Participation class represents an n-ary property to capture qualifying information related to the participation of Entity in ProcessExecution.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Participation rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Participation from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> provenance scenario ??? is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#p1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Participation"/>
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#Bob"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+
+ <div id="control" class="section">
+ <h5><span class="secno">3.1.7.3 </span>Control</h5>
+ <div><b>Class Description</b></div>
+ <p>The Control class represents an n-ary property to capture qualifying information related to the control of ProcessExecution by Agent.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Control rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div><b>Example</b></div>
+ <p>Example of instances of class Control from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> provenance scenario ??? is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#c1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Control"/>
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#Bob"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+
+ <div id="generation" class="section">
+ <h5><span class="secno">3.1.7.4 </span>Generation</h5>
+ <div><b>Class Description</b></div>
+ <p>The Generation class represents an n-ary property to capture qualifying information related to the generation of Entity by ProcessExecution.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Generation rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Generation from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario</a> ??? is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#g1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Generation"/>
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#Bob"/>
+</rdf:Description></pre>
+ </div>
+ </div>
</div>
+
+ <div id="recipe" class="section">
+ <h4><span class="secno">3.1.8 </span>Recipe</h4>
+ <div><b>Class Description</b></div>
+ <p>Recipe represents the specification of a <a href="#processexecution">ProcessExecution</a>. PROV ontology does not define the different types of recipes that can be created by provenance applications in different domains.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Recipe rdfs:subClassOf owl:Thing.</pre>
+ <div><b>Example</b></div>
+ <p>An example of recipe from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario </a>may be the editing protocol followed by the journalists to edit a news report.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#news_editing">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExection"/>
+ <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#NewsReportEditingProtocol"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+
+ <div id="role" class="section">
+ <h4><span class="secno">3.1.9 </span>Role</h4>
+ <div><b>Class Description</b></div>
+ <p>Role class models additional information about Entity or ProcessExecution class with respect to the QualifiedInvolvement class [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Role rdfs:subClassOf owl:Thing.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Role from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>author (for Alice)</i> and <i>save (for pe1)</i>. The RDF/XML syntax for asserting that Alice played a role of author in the usage u1 (instance of class Usage) of file e1 in the activity of adding content.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#u1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Usage"/>
+ <prov:hadRole rdf:resource="www.example.com/crimeFile#author"/>
+</rdf:Description></pre>
+ </div>
+ <div class="note"> It is not clear how two roles can be modeled using the QualifiedInvolvement class-based approach, where an Entity plays a role of "author", while the ProcessExecution plays the role of "save" (from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a>).
+ </div>
+ </div>
+
+ <div id="classes-under-discussion" class="section">
+ <h4><span class="secno">3.1.10 </span>Classes under Discussion</h4>
+ <p>Temporary section for terms not part of "core" ontology.</p>
+
+ <div id="time" class="section">
+ <h5><span class="secno">3.1.10.1 </span>Time</h5>
+ <div><b>Class Description</b></div>
+ <p><code>Time</code> is subclass of <code>time:Instant</code>
+ from [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>] which requires that the time is defined
+ using the <code>time:inXSDDateTime</code> property. This
+ class used with <code>startedAt</code> and other subproperties
+ of <code>hasTemporalValue</code> ensures compatibility with <code>xsd:dateTime</code> literals
+ expressions in [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] ASN and other serialisations.
+ c</p>
+ </div>
+
+ </div>
</div>
<div id="object-properties" class="section">
<h3><span class="secno">3.2 </span>Object Properties</h3>
- <p>The Provenance Model consists of the following object properties. </p>
+ <p>The PROV ontology has the following object properties. </p>
<p><i>Note: Names of properties starts with a verb in lower case followed by verb(s) starting with upper case </i></p>
<div id="wasgeneratedby" class="section">
<h4><span class="secno">3.2.1 </span>wasGeneratedBy</h4>
- <p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
+ <p>The wasGeneratedBy property links the Entity class with the ProcessExecution class.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
<img alt="wasGeneratedBy links Entity to ProcessExecution" style="height: 3em" src="diagram-history/khalidDiagrams/wasGeneratedBy.png" />
<div><b>Example</b></div>
- <p> Example of wasGeneratedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
- </p><div class="exampleOuter">
+ <p>Example of wasGeneratedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this information is given below.
+ </p>
+ <div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e1">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
- <rdf:type rdf:resource="http://www.example.com/crime#CrimeFile"/>
<prov:wasGeneratedBy>
<rdf:Description rdf:about="http://www.example.com/crimeFile#pe0">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
- <rdf:type rdf:resource="http://www.example.com/crime#FileCreation"/>
</rdf:Description>
<prov:wasGeneratedBy>
</rdf:Description> </pre>
@@ -967,27 +869,43 @@
<div id="revision" class="section">
<h4><span class="secno">3.2.2 </span>wasRevisionOf</h4>
- <p>wasRevisionOf links two instances of Entity class, where one instance is a revision of another.</p>
+ <p>The wasRevisionOf property links two instances of Entity class, where one instance is a revision of another instance, and there is explicit role of an Agent in asserting this information.</p>
+ <div><b>Example</b></div>
+ <p>Example of wasRevisionOf property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e3 wasRevisionOf e2</i>. The RDF/XML syntax for asserting this information is given below.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
+ <prov:wasRevisionOf>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
+ </rdf:Description>
+ <prov:wasRevisionOf>
+</rdf:Description> </pre>
+ </div>
+ <div class="note"> Can instance of Agents be reasoning agents that infer the information that one Entity instance is a revision of another Entity instance and then asserts the information? In other words, is assertion after inference supported by this property?
+ </div>
</div>
<div id="wasderivedfrom" class="section">
<h4><span class="secno">3.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>
+ <p>The wasDerivedFrom property links two instances of Entity class, where "some characterized entity is transformed from, created from, or affected by another characterized entity." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
<img alt="wasDerivedFrom links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasDerivedFrom.png" />
<div><b>Example</b></div>
- <p> Example of wasDerivedFrom property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
- </p><div class="exampleOuter">
+ <p> Example of wasDerivedFrom property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom 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#e3">
<prov:wasDerivedFrom rdf:resource="http://www.example.com/crimeFile#e2"/>
</rdf:Description> </pre>
</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 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>
<div id="waseventuallyderivedfrom" class="section">
<h4><span class="secno">3.2.4 </span>wasEventuallyDerivedFrom</h4>
- <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>This object property is used to link two instances of Entity class that "...are not directly used and generated respectively" by a single instance of ProcessExecution class [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].
</p>
<img alt="wasEventuallyDerivedFrom links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasEventuallyDerivedFrom.png" />
<div><b>Example</b></div>
@@ -1002,11 +920,11 @@
<div id="dependedon" class="section">
<h4><span class="secno">3.2.5 </span>dependedOn</h4>
- <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>
+ <p>The dependedOn property links two instances of Entity class to model the derivation of one instance from another instance. This is a <i>transitive</i> property, in other words if an Entity instance a1 dependedOn a2 and a2 dependedOn a3, then a1 dependedOn a3 is also true.</p>
<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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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">
+ <p>Example of dependedOn property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#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>
@@ -1020,7 +938,7 @@
<div id="used" class="section">
<h4><span class="secno">3.2.6 </span>used</h4>
- <p>used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
+ <p>The used property links the ProcessExecution class to the Entity class, where the Entity instance is "consumed" by a ProcessExecution instance.</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><b>Example</b></div>
@@ -1035,8 +953,8 @@
<div id="hadparticipant" class="section">
<h4><span class="secno">3.2.7 </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>
+ <p>The hadPariticipant property links Entity class to ProcessExecution class, 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><b>Example</b></div>
<p> Example of hadParticipant property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 hadParticipant e2</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -1046,21 +964,25 @@
</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 class="note"> The current definition of hasParticipant does not account for involvement of an Entity in ProcessExecution where it was neither "used" or "generated". For example, a witness in a criminal activity.
+ </div>
</div>
<div id="wascomplementof" class="section">
<h4><span class="secno">3.2.8 </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>
+ <p>The wasComplementOf property links two instances of set of assertions about Entity instances, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
<img alt="wasComplementOf links Entity to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/wasComplementOf.png" />
+ <div class="note"> Should the wasComplementOf property link two instances of ProvenanceContainer (or Account) classes since they are two classes modeling a set of (one or more) provenance assertions?
+ </div>
</div>
<div id="wascontrolledby" class="section">
<h4><span class="secno">3.2.9 </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>
+ <p>The wasControlledBy property links ProcessExecution class to Agent class, where control represents the involvement of the Agent in modifying the characteristics of the instance of the ProcessExecution class"[<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].</p>
<img alt="wasControlledBy links ProcessExecution to Agent" style="height: 3em" src="diagram-history/khalidDiagrams/wasControlledBy.png" />
<div><b>Example</b></div>
<p> Example of wasControlledBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
@@ -1079,15 +1001,11 @@
<div id="hadrecipe" class="section">
<h4><span class="secno">3.2.10 </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
- might or might not have been followed exactly by the Process
- Execution.
+ <p>This property links the ProcessExecution class to the Recipe class, which describes the execution characteristics of the instance of the ProcessExecution class. The recipe might or might not have been followed exactly by the ProcessExecution.
</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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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>
+ <p> Example of hadRecipe property in the (extended)<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is that pe1 (instance of ProcessExecution class) followed some file appending instructions (instructions1). 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"/>
@@ -1099,7 +1017,7 @@
<div id="wasinformedby" class="section">
<h4><span class="secno">3.2.11 </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> This object property links two instances of the ProcessExecution classes. It is used to express the information 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>
@@ -1116,7 +1034,7 @@
<div id="wascheduledafter" class="section">
<h4><span class="secno">3.2.12 </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.
+ This property links two instances of ProcessExecution class to specify the order of their executions. 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>
@@ -1126,24 +1044,78 @@
<prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#pe3"/>
</rdf:Description> </pre>
</div>
+ <div class="issue"> There is proposal to either rename wasScheduledAfter or clarify its definition in PROV-DM. These are issues <a href="http://www.w3.org/2011/prov/track/issues/148">Issue-148</a>
+ </div>
</div>
- <div id="followed" class="section">
- <h4><span class="secno">3.2.13 </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><b>Example</b></div>
- <p> Example of followed property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#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"/>
+
+ <div id="hadtemporalvalue" class="section">
+ <h4><span class="secno">3.2.13 </span>hadTemporalValue</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 allowing association of time value with instances of the two classes and their subclasses.
+ </p>
+ <img alt="hadTemporalValue links ProcessExecution or Entity to time:TemporalValue" style="height: 3em" src="diagram-history/khalidDiagrams/hadTemporalValue.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadTemporalValue property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> is <i>t+3</i> time value is associated with the pe3 ProcessExecution instanc. 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#pe3">
+ <prov:hasTemporalValue rdf:resource="http://www.example.com/crimeFile#t+3"/>
</rdf:Description> </pre>
</div>
- </div>
-
+ <div id="startedat" class="section">
+ <h5><span class="secno">3.2.13.1 </span>startedAt</h5>
+ <p> This object property defines the time when <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>].
+ </p>
+ <img alt="startedAt links ProcessExecution to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/startedAt.png" />
+ <div><b>Example</b></div>
+ <p> Example of startedAt property is that a pe1 (instance of ProcessExecution class) is "2011-10-20T17:14:12Z". 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:startedAt rdf:about="http://www.example.com/crimeFile#t1>
+ <rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
+ <time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
+ </prov:startedAt>
+</rdf:Description> </pre>
+ </div>
+
+ </div>
+ <div id="endedat" class="section">
+ <h5><span class="secno">3.2.13.2 </span>endedAt</h5>
+ <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>].
+ </p>
+ <img alt="endedAt links ProcessExecution to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/endedAt.png" />
+ <div><b>Example</b></div>
+ <p> Example of endedAt property is that a pe1 (instance of ProcessExecution class) is "2011-10-20T20:14:12Z". 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:endedAt rdf:about="http://www.example.com/crimeFile#t2>
+ <rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
+ <time:inXSDDateTime>2011-10-20T20:14:12Z</time:inXSDDateTime>
+ </prov:endedAt>
+</rdf:Description></pre>
+ </div>
+
+ </div>
+ <div id="wasGeneratedat" class="section">
+ <h5><span class="secno">3.2.13.3 </span>wasGeneratedAt</h5>
+ <p> This object property defines the time when a <code>Entity</code> was generated by ProcessExecution.
+ </p>
+ <img alt="wasGeneratedAt links Entity to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/wasGeneratedAt.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasGeneratedAt property is that a e1 (instance of Entity class) wasGeneratedAt "2011-10-20T20:12:12Z". 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#e1">
+ <prov:wasGeneratedAt rdf:about="http://www.example.com/crimeFile#t3>
+ <rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
+ <time:inXSDDateTime>2011-10-20T20:12:12Z</time:inXSDDateTime>
+ </prov:startedAt>
+ </rdf:Description></pre>
+ </div>
+ </div>
+ </div>
+
<div id="attribution" class="section">
<h4><span class="secno">3.2.14 </span>wasAttributedTo</h4>
- <p>wasAttributedTo links an instance of the Entity class to an instance of Agent class.</p>
+ <p>The wasAttributedTo property 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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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>
@@ -1156,10 +1128,10 @@
<div id="quotation" class="section">
<h4><span class="secno">3.2.15 </span>wasQuoteOf</h4>
- <p>wasQuoteOf links an instance of the Entity class to an instance of of the Agent class.</p>
+ <p>The wasQuoteOf property links an instance of the Entity class to an instance 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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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>
+ <p> Example of wasQuoteOf property as an addition to the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is e2 quoting Alice, 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"/>
@@ -1169,7 +1141,7 @@
<div id="summary" class="section">
<h4><span class="secno">3.2.16 </span>wasSummaryOf</h4>
- <p>wasSummaryOf links two instances of the Entity class.</p>
+ <p>The wasSummaryOf property 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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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>
@@ -1182,7 +1154,7 @@
<div id="originalsource" class="section">
<h4><span class="secno">3.2.17 </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>
+ <p>The hadOriginalSource property 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://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> e6 hadOriginalSource e1</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -1193,181 +1165,70 @@
</div>
</div>
- <div id="hastemporalvalue" class="section">
- <h4><span class="secno">3.2.18 </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
- allowing association of time value with instances of the
- two classes and their subclasses. This property can be
- considered an abstract property, specialised by
- <code>startedAt</code>, <code>endedAt</code>,
- <code>wasGeneratedAt</code> and
- <code>assumedRoleAt</code> where the time <em class="rfc2119" title="must">must</em> be specified as
- an <code>time:Instant</code> or more specifically <em class="rfc2119" title="may">may</em> be
- specified using the PROV-O subclass <code>Time</code>
- which mandates the use of the
- <code>time:inXSDDateTime</code> data property.
- </p>
- </div>
- <div id="startedAt" class="section">
- <h4><span class="secno">3.2.19 </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">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-10-20T16:26:45Z</time:inXSDDateTime>
- </prov:startedAt>
+ <div id="hadqualifiedusage" class="section">
+ <h4><span class="secno">3.2.18 </span>hadQualifiedUsage</h4>
+ <p>The hadQualifiedUsage property links the ProcessExecution class with the Usage class.</p>
+ <img alt="hadQualifiedUsage links ProcessExecution to Usage" style="height: 3em" src="diagram-history/khalidDiagrams/hadQualifiedUsage.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadQualifiedUsage property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> pe1 hadQualifiedUsage u1</i>, where the hadRole describes the usage of e1 as a "load". 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:hadQualifiedUsage rdf:resource="http://www.example.com/Usage#u1"/>
</rdf:Description> </pre>
- </div>
- </div>
- <div id="endedAt" class="section">
- <h4><span class="secno">3.2.20 </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">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-11-21T18:36:52Z</time:inXSDDateTime>
- </prov:endedAt>
+ </div>
+ </div>
+
+ <div id="hadqualifiedparticipation" class="section">
+ <h4><span class="secno">3.2.19 </span>hadQualifiedParticipation</h4>
+ <p>The hadQualifiedParticipation property links the ProcessExecution class with the Participation class.</p>
+ <img alt="hadQualifiedParticipation links ProcessExecution to Participation" style="height: 3em" src="diagram-history/khalidDiagrams/hadQualifiedParticipation.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadQualifiedParticipation property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> pe1 hadQualifiedParticipation p1</i>, where the hadRole describes the participation of Alice as an "author" in pe1. 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:hadQualifiedParticipation rdf:resource="http://www.example.com/crimeFile#p1"/>
</rdf:Description> </pre>
- </div>
- </div>
- <div id="wasGeneratedAt" class="section">
- <h4><span class="secno">3.2.21 </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
- first existed (and could be used by other process
- executions). 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="wasGeneratedAt links Entity to Instant" style="height: 3em" src="diagram-history/khalidDiagrams/wasGeneratedAt.png" />
- <p>
- Note that by constraint
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
- <prov:wasGeneratedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
- </prov:wasGeneratedAt>
+ </div>
+ </div>
+
+ <div id="hadqualifiedcontrol" class="section">
+ <h4><span class="secno">3.2.20 </span>hadQualifiedControl</h4>
+ <p>The hadQualifiedControl property links the ProcessExecution class with the Control class.</p>
+ <img alt="hadQualifiedControl links ProcessExecution to Control" style="height: 3em" src="diagram-history/khalidDiagrams/hadQualifiedControl.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadQualifiedControl property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> pe0 hadQualifiedControl c1</i>, where the hadRole describes the control of pe0 by Alice as "creator". 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#pe0">
+ <prov:hadQualifiedControl rdf:resource="http://www.example.com/crimeFile#c1"/>
</rdf:Description> </pre>
- </div>
+ </div>
</div>
- <div id="wasAssumedBy" class="section">
- <h4><span class="secno">3.2.22 </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
- relations such as <code>used</code> and
- <code>wasGeneratedBy</code>.
- <code>wasAssumedBy</code> is a required, functional property of
- <code>EntityInRole</code>, so an <code>EntityInRole</code>
- 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>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <strong><prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/></strong>
- <prov:assumedRole rdf:resource="http://www.example.com/crime#author"/>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
+
+ <div id="hadqualifiedgeneration" class="section">
+ <h4><span class="secno">3.2.21 </span>hadQualifiedGeneration</h4>
+ <p>The hadQualifiedGeneration property links the ProcessExecution class with the Generation class.</p>
+ <img alt="hadQualifiedGeneration links ProcessExecution to Generation" style="height: 3em" src="diagram-history/khalidDiagrams/hadQualifiedGeneration.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadQualifiedGeneration property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> e1 hadQualifiedGeneration g1</i>, where the hadRole describes the generation of e1 by "save". 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#e1">
+ <prov:hadQualifiedGeneration rdf:resource="http://www.example.com/crimeFile#u1"/>
</rdf:Description> </pre>
- </div>
- <p>
- The example above corresponds to the PROV-ASN assertion:
- <code>used(pe1, bob, qualifier(role="author")</code>
- </p>
+ </div>
</div>
- <div id="assumedRole" class="section">
- <h4><span class="secno">3.2.23 </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
- a placeholder that can be extended and specialized.
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/>
- <strong><prov:assumedRole rdf:resource="http://www.example.com/crime#author"/></strong>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
+
+ <div id="hadqualifiedentity" class="section">
+ <h4><span class="secno">3.2.22 </span>hadQualifiedEntity</h4>
+ <p>The hadQualifiedEntity property links the QualifiedInvolvement class with the Entity class.</p>
+ <img alt="hadQualifiedInvolvement links QualifiedInvolvement to Entity" style="height: 3em" src="diagram-history/khalidDiagrams/hadQualifiedEntity.png" />
+ <div><b>Example</b></div>
+ <p> Example of hadQualifiedEntity property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> u2 hadQualifiedEntity e2</i>, where the hadRole describes the usage of e2 as an "attachment". 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#u2">
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#e2"/>
</rdf:Description> </pre>
- </div>
- <p>
- The example above corresponds to the PROV-ASN assertion:
- <code>used(pe1, bob, qualifier(role="author")</code>
- </p>
- <div class="issue">
- It has been suggested that roles should be represented as
- classes, allowing hierarchies and composition of roles. <a href="http://www.w3.org/TR/owl2-new-features/#F12:_Punning">OWL2 punning</a>
- would allow both <code>:entityInRole rdf:type :ExampleRole</code> and
- <code>:entityInRole prov:assumedRole :ExampleRole</code>.
- </div>
- </div>
- <div id="assumedRoleAt" class="section">
- <h4><span class="secno">3.2.24 </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.
- This is intended to be used together with a
- <code>used</code> statement to define the instant when an
- entity was first used. 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="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
- execution. This ontology further assumes that all
- assertions about that generation must have the same
- start time.
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <strong><prov:assumedRoleAt rdf:parseType="Resource"></strong>
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <strong><time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime></strong>
- </prov:assumedRoleAt>
- </prov:used>
-</rdf:Description> </pre>
- </div>
- </div>
-
+ </div>
+ </div>
</div>
<div id="characteristics-of-object-properties" class="section">
@@ -1458,19 +1319,7 @@
</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>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 class="note">Some of the properties 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">
@@ -1491,241 +1340,12 @@
</p>
<div class="note"> Is there a need to define standard provenance-specific annotation properties?
</div>
- </div>
-
-
- <div id="collections" class="section">
- <h3><span class="secno">3.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">3.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>,
- <code>wasExpandedBy</code> 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>
- <div class="issue">TODO: Write Collection examples as RDF/XML</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">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">3.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">3.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">3.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>
<div id="overview-of-the-ontology" class="section">
- <h3><span class="secno">3.6 </span>Overview of the ontology</h3>
+ <h3><span class="secno">3.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.png " />
+ <img alt="Classes and properties of the PROV ontology" style="min-width: 45em; width: 55em; max-width: 95%" src="diagram-history/khalidDiagrams/ProvenanceOntology.png " />
<!--
<p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
@@ -1780,13 +1400,13 @@
</prov:wasControlledBy>
<prov:startedAt>
<rdf:Description rdf:about="http://www.example.com/crimeFile#t1">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <rdf:type rdf:resource="http://www.w3.org/2006/time#Instant"/>
<time:inXSDDateTime>2011-10-20T16:26:45Z</time:inXSDDateTime>
</rdf:Description>
</prov:startedAt>
<prov:endedAt>
<rdf:Description rdf:about="http://www.example.com/crimeFile#t3">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <rdf:type rdf:resource="http://www.w3.org/2006/time#Instant"/>
<time:inXSDDateTime>2011-11-21T18:36:52Z</time:inXSDDateTime>
</rdf:Description>
</prov:endedAt>
@@ -1794,7 +1414,7 @@
</prov:wasGeneratedBy>
<prov:wasGeneratedAt>
<rdf:Description rdf:about="http://www.example.com/crimeFile#t2">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <rdf:type rdf:resource="http://www.w3.org/2006/time#Instant"/>
<time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
</rdf:Description>
</prov:wasGeneratedAt>
@@ -2470,7 +2090,7 @@
<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
</rdf:Description></pre>
</div>
- <p>we can infer that</p>
+ <p>we can infer the following</p>
<div class="exampleOuter">
<pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#Alice">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Agent"/>
@@ -2608,7 +2228,7 @@
-<div id="references" class="appendix section">
+<div id="respec-err" style="position: fixed; width: 350px; top: 10px; right: 10px; border: 3px double #f00; background: #fff" class="removeOnSave"><ul><li style="color: #c00">There appears to have been a problem fetching the style sheet; status=0</li></ul></div><div id="references" class="appendix section">
<!-- OddPage -->
<h2><span class="secno">B. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL-TIME">[OWL-TIME]</dt><dd>Feng Pan; Jerry R. Hobbs. <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927"><cite>Time Ontology in OWL.</cite></a> 27 September 2006. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927">http://www.w3.org/TR/2006/WD-owl-time-20060927</a>
</dd><dt id="bib-OWL2-DIRECT-SEMANTICS">[OWL2-DIRECT-SEMANTICS]</dt><dd>Boris Motik; Peter F. Patel-Schneider; Bernardo Cuenca Grau. <a href="http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/"><cite>OWL 2 Web Ontology Language:Direct Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/">http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/</a>
@@ -2617,6 +2237,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-PRIMER">[RDF-PRIMER]</dt><dd>Frank Manola; Eric Miller. <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/"><cite>RDF Primer.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-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>