--- a/ontology/ProvenanceFormalModel.html Thu Sep 22 15:46:07 2011 +0100
+++ b/ontology/ProvenanceFormalModel.html Thu Sep 22 21:31:02 2011 -0400
@@ -106,10 +106,10 @@
<section>
<h2>Introduction</h2>
<p>
- PROV Formal Model (also PROV ontology) defines the normative modeling of the PROV Data Model [[PROV-DM]] using the W3C OWL2 Web Ontology Language. This document specification describing the set of classes, properties, and restrictions that constitute the PROV ontology, which have been introduced in the PROV Data Model [[PROV-DM]]. This ontology specification provides the foundation for implementation of provenance applications in different applications using the PROV ontology for representing, exchanging, integrating provenance information. Together with the PROV Access and Query [[PROV-PAQ]] and PROV Data Model [[PROV-DM]], this document forms a framework for provenance information management in domain-specific applications.
+ PROV Formal Model (also PROV ontology) defines the normative modeling of the PROV Data Model [[PROV-DM]] 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 [[PROV-DM]]. 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 [[PROV-PAQ]] and PROV Data Model [[PROV-DM]], this document forms a framework for provenance information 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 used an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> introduced in the PROV Data Model [[PROV-DM]] to demonstrate the specialization of PROV ontology.
+ 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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> introduced in the PROV Data Model [[PROV-DM]] to demonstrate the specialization of PROV ontology.
</p>
<p>
Finally, this document describes the formal semantics of the PROV ontology using the OWL2 formal semantics, [[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]], 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.
@@ -118,57 +118,24 @@
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[[!RFC2119]].</p>
+ <section>
+ <h3>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 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 [[!OWL2-PRIMER]], for a detailed understanding of the OWL2 specification.
+ </p>
+ <p><a href="#prov-ontology--owl-encoding-of-prov-data-model">Section 2</a> describes the mapping of the PROV Data Model [[PROV-DM]] 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="#entailments-supported-by-the-provenance-model">Section 4</a> describes the approach used to specialize the PROV ontology create a domain specific ontology for an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> introduced in the PROV Data Model [[PROV-DM]].
+ </p>
+ </section>
</section>
- <section>
- <h2>OWL2 Encoding of the Provenance Model</h2>
- <p>The PROV Data Model document [[PROV-DM]] introduces an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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. The example scenario can be encoded as a <a href = "http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href = "">Figure 1</a>:</p>
- <div class='issue'>insert figure 1</div>
- <p><a href = "">Figure 1</a> represents both the Provenance ontology schema and the instance information. For example,
- <ul>
- <li><a href="#agent">Agent</a>, e.g. alice, bob, and edith </li>
- <li><a href="#processexecution">ProcessExecution</a>, e.g. fileCreation, fileAppending </li>
- <li>specialization of <a href="#entity">Entity</a>, e.g. e1, e2, and e3 </li>
- </ul>
+ <section>
+ <h2>PROV Ontology: OWL Encoding of PROV Data Model</h2>
+ <p> The PROV Data Model [[PROV-DM]] introduces a set of concepts to represent provenance information.
</p>
- <p>Example given below describes the provenance of <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html#entity">Entity</a> e2 using RDF/XML syntax
- <div class="exampleOuter">
- <pre class="example">
- <?xml version="1.0"?>
- <rdf:RDF
- xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
- xmlns:prov="http://www.w3.org/PROV/ProvenanceOntology.owl#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:cf="http://www.w3.org/PROV/CrimeFileOntology.owl#">
-
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
- <prov:wasGeneratedBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileAppending"/>
- <prov:wasControlledBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Bob">
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
- </rdf:Description>
- </prov:wasControlledBy>
- </rdf:Description>
- </prov:wasGeneratedBy>
- <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/CrimeFile#e1"/>
- <cf:hasLocation>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
- <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
- </rdf:Description>
- </cf:hasLocation>
- <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There was a lot of crime in London last month.</cf:hasFileContent>
- </rdf:Description>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
- <prov:Used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
- </rdf:Description>
- </rdf:RDF>
- </pre>
- </div>
- </p>
-
+ <section>
+ <h3>OWL Syntax Used in this Document</h3>
+ </section>
+ </section>
+ <section>
+ <h2>PROV Ontology: Classes, Properties, and Restrictions</h2>
<section>
<h3>Visualization of the Provenance ontology</h3>
<h4>Hierarchical view of the ontology</h4>
@@ -179,101 +146,100 @@
<p>The Provenance Model consists of the following classes. </p>
<p><i>Note: CamelBack notation is used for class names</i></p>
<section>
- <h4>Entity</h4>
- <div><b>Class Description</b></div>
- <p>Entity is defined to be "An Entity represents an identifiable characterized thing." [[PROV-DM]]</p>
- <div><b>OWL syntax</b></div>
- <pre> PROV:Entity rdfs:subClassOf owl:Thing.
- </pre>
- <div><b>Example</b></div>
- <p> Example of instances of class Entity from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are files with identifiers <i>e1</i> and <i>e2</i>. The RDF/XML syntax for asserting that e1 is an instance of Entity is given below.
- <div class="exampleOuter">
+ <h4>Entity</h4>
+ <div><b>Class Description</b></div>
+ <p>Entity is defined to be "An Entity represents an identifiable characterized thing." [[PROV-DM]]</p>
+ <div><b>OWL syntax</b></div>
+ <pre> PROV:Entity rdfs:subClassOf owl:Thing.
+ </pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Entity from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are files with identifiers <i>e1</i> and <i>e2</i>. The RDF/XML syntax for asserting that e1 is an instance of Entity is given below.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e1">
<rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
</pre>
- </div>
- <div class='note'> e1 is an instance of class Journalist, which is defined to be "sub-class" of class Agent in the CrimeFile ontology and class Agent is defined to be "sub-class" of class Entity. Hence, using standard RDFS entailment allows us to infer that e1 is also an instance of Entity.
- </div>
- <div class='issue'>How is domain specific data combined with the provenance model? This is <a href="http://www.w3.org/2011/prov/track/issues/65">ISSUE-65</a>.</div>
+ </div>
+ <div class='note'> e1 is an instance of class Journalist, which is defined to be "sub-class" of class Agent in the CrimeFile ontology and class Agent is defined to be "sub-class" of class Entity. Hence, using standard RDFS entailment allows us to infer that e1 is also an instance of Entity.
+ </div>
+ <div class='issue'>How is domain specific data combined with the provenance model? This is <a href="http://www.w3.org/2011/prov/track/issues/65">ISSUE-65</a>.</div>
- <div class='issue'>Definition of Entity is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
-
+ <div class='issue'>Definition of Entity is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
</section>
<section>
- <h4>ProcessExecution</h4>
- <div><b>Class Description</b></div>
- <p>ProcessExecution is defined to be "an identifiable activity, which performs a piece of work." [[PROV-DM]]</p>
- <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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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.
- <div class="exampleOuter">
+ <h4>ProcessExecution</h4>
+ <div><b>Class Description</b></div>
+ <p>ProcessExecution is defined to be "an identifiable activity, which performs a piece of work." [[PROV-DM]]</p>
+ <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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
<rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
</pre>
- </div>
- <div class='note'> pe2 is an instance of class EmailProcessExecution, which is defined to be "sub-class" of class ProcessExecution in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of ProcessExecution.
- </div>
+ </div>
+ <div class='note'> pe2 is an instance of class EmailProcessExecution, which is defined to be "sub-class" of class ProcessExecution in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of ProcessExecution.
+ </div>
</section>
<section>
- <h4>Agent</h4>
- <div><b>Class Description</b></div>
- <p>Agent is defined to be a "characterized entity capable of activity" [[PROV-DM]]</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Agent rdfs:subClassOf PROV:Entity.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class Agent from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>Alice</i> and <i>Edith</i>. The RDF/XML syntax for asserting that Alice is an instance of Agent is given below.
- <div class="exampleOuter">
+ <h4>Agent</h4>
+ <div><b>Class Description</b></div>
+ <p>Agent is defined to be a "characterized entity capable of activity" [[PROV-DM]]</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Agent rdfs:subClassOf PROV:Entity.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Agent from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>Alice</i> and <i>Edith</i>. The RDF/XML syntax for asserting that Alice is an instance of Agent is given below.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Alice">
<rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
</pre>
- </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 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>
</section>
<section>
- <h4>Time</h4>
- <div><b>Class Description</b></div>
- <p>Time represents temporal information about entities in the Provenance model.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Time rdfs:subClassOf owl:Thing.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class Time from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of Time is given below.
- <div class="exampleOuter">
+ <h4>Time</h4>
+ <div><b>Class Description</b></div>
+ <p>Time represents temporal information about entities in the Provenance model.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Time rdfs:subClassOf owl:Thing.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Time from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of Time is given below.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#t+1">
<rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Time"/>
</pre>
- </div>
- </section>
- <section>
- <h4>Revision</h4>
- <div><b>Class Description</b></div>
- <p>Revision is defined as a modified version of a Entity.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Revision rdfs:subClassOf PROV:Entity.</pre>
- <div class='issue'>Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
+ </div>
</section>
<section>
- <h4>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.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:ProvenanceContainer rdfs:subClassOf PROV:Entity.</pre>
- <div class='issue'>Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
- <div class='issue'>Scope and Identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
+ <h4>Revision</h4>
+ <div><b>Class Description</b></div>
+ <p>Revision is defined as a modified version of a Entity.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Revision rdfs:subClassOf PROV:Entity.</pre>
+ <div class='issue'>Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
</section>
<section>
- <h4>Location</h4>
- <div><b>Class Description</b></div>
- <p>Location is defined to be "is an identifiable geographic place (ISO 19112)." [[PROV-DM]]</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Location rdfs:subClassOf PROV:Entity.</pre>
- <p> Example of instances of class Location from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is the location of the crime file in the shared directory <i>/share</i> with file path <i>/shared/crime.txt</i>. The RDF/XML syntax for asserting that the location of the crime file is the shared directory.
- <div class="exampleOuter">
+ <h4>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.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:ProvenanceContainer rdfs:subClassOf PROV:Entity.</pre>
+ <div class='issue'>Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
+ <div class='issue'>Scope and Identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
+ </section>
+ <section>
+ <h4>Location</h4>
+ <div><b>Class Description</b></div>
+ <p>Location is defined to be "is an identifiable geographic place (ISO 19112)." [[PROV-DM]]</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Location rdfs:subClassOf PROV:Entity.</pre>
+ <p> Example of instances of class Location from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is the location of the crime file in the shared directory <i>/share</i> with file path <i>/shared/crime.txt</i>. The RDF/XML syntax for asserting that the location of the crime file is the shared directory.
+ <div class="exampleOuter">
<pre class="example">
<cf:hasLocation>
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
@@ -281,25 +247,25 @@
<rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
</rdf:Description>
</cf:hasLocation>
- </pre>
- </div>
- <div class='note'> Need to clarify whether "geographic" includes "geospatial"?
+ </pre>
+ </div>
+ <div class='note'> Need to clarify whether "geographic" includes "geospatial"?
</section>
<section>
- <h4>Role</h4>
- <div><b>Class Description</b></div>
- <p>Role is defined to be a "realizable entity" (cite?) "assumed by a Entity or an agent." [[PROV-DM]]</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Role rdfs:subClassOf PROV:Entity.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class Role from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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.
- <div class="exampleOuter">
+ <h4>Role</h4>
+ <div><b>Class Description</b></div>
+ <p>Role is defined to be a "realizable entity" (cite?) "assumed by a Entity or an agent." [[PROV-DM]]</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Role rdfs:subClassOf PROV:Entity.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Role from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Alice">
<cf:assumesRole rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#author"/>
</pre>
- </div>
- <div class='issue'>start to use Role + assumedBy as the controller of a process execution? -dg</div>
+ </div>
+ <div class='issue'>start to use Role + assumedBy as the controller of a process execution? -dg</div>
</section>
</section>
<section>
@@ -307,13 +273,13 @@
<p>The Provenance Model consists of 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>
<section>
- <h4>wasGeneratedBy</h4>
- <p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" />
- <div><b>Example</b></div>
- <p> Example of wasGeneratedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
- <div class="exampleOuter">
+ <h4>wasGeneratedBy</h4>
+ <p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
+ <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasGeneratedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e1">
<rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
@@ -324,12 +290,12 @@
<cf:isGeneratedBy>
</rdf:Description>
</pre>
- </div>
+ </div>
</section>
<section>
- <h4>wasDerivedFrom</h4>
- <p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
- <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" />
+ <h4>wasDerivedFrom</h4>
+ <p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" />
<div><b>Example</b></div>
<p> Example of wasDerivedFrom property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -339,50 +305,49 @@
</rdf:Description>
</pre>
</div>
- <div class='issue'>Is derivation transitive? If so, it should not be introduced as an assertion. This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</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 class='resolved'> What's the difference between one step and multi-step derivation assertion. Justification of why one entity can be generated at most once. Multi-step derivation is also transitive. This is all in <a href="http://www.w3.org/2011/prov/track/issues/67">ISSUE-67</a>.</div>
+ <div class='issue'>Is derivation transitive? If so, it should not be introduced as an assertion. This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</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 class='resolved'> What's the difference between one step and multi-step derivation assertion. Justification of why one entity can be generated at most once. Multi-step derivation is also transitive. This is all in <a href="http://www.w3.org/2011/prov/track/issues/67">ISSUE-67</a>.</div>
</section>
<section>
- <h4>dependedOn</h4>
- <p>dependedOn links two distinct characterized entities, where "some characterized entity cannot be generated without the existence of another characterized entity."</p>
- <img src="http://www.w3.org/2011/prov/wiki/images/c/c1/DependedOn.png" />
+ <h4>dependedOn</h4>
+ <p>dependedOn links two distinct characterized entities, where "some characterized entity cannot be generated without the existence of another characterized entity."</p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/c/c1/DependedOn.png" />
</section>
<section>
- <h4>Used</h4>
- <p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" />
- <div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
- <div><b>Example</b></div>
- <p> Example of Used property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 Used e2</i>. The RDF/XML syntax for asserting this is given below.
- <div class="exampleOuter">
+ <h4>Used</h4>
+ <p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" />
+ <div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
+ <div><b>Example</b></div>
+ <p> Example of Used property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 Used e2</i>. The RDF/XML syntax for asserting this is given below.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
<cf:Used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
</rdf:Description>
</pre>
- </div>
- </section>
- <section>
- <h4>hadParticipant</h4>
- <p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <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>
</section>
<section>
- <h4>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>
+ <h4>hadParticipant</h4>
+ <p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
+ <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <div class='pending'>Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
</section>
<section>
- <h4>wasControlledBy</h4>
- <p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" />
- <div><b>Example</b></div>
- <p> Example of wasControlledBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
- <div class="exampleOuter">
+ <h4>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>
+ </section>
+ <section>
+ <h4>wasControlledBy</h4>
+ <p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" />
+ <div><b>Example</b></div>
+ <p> Example of wasControlledBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
+ <div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
<cf:isControlledBy>
@@ -392,59 +357,107 @@
</cf:isControlledBy>
</rdf:Description>
</pre>
- </div>
- <div class='issue'>Mutual ivpOf each other should be agreed. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
- <div class='issue'>Do we need a sameAsEntity relation. This is <a href="http://www.w3.org/2011/prov/track/issues/35">ISSUE-35</a></div>
- <div class='issue'>Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
- <div class='issue'> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
+ </div>
+ <div class='issue'>Mutual ivpOf each other should be agreed. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
+ <div class='issue'>Do we need a sameAsEntity relation. This is <a href="http://www.w3.org/2011/prov/track/issues/35">ISSUE-35</a></div>
+ <div class='issue'>Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
+ <div class='issue'> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
</section>
<section>
- <h4>preceded</h4>
- <p>preceded links two instances of ProcessExecution, where "Ordering of processes execution (in provenance) needs to be modeled as a property linking process entities in specific order along a particular dimension (temporal or control flow)"</p>
- <img src="http://www.w3.org/2011/prov/wiki/images/e/e5/Preceeded.png" />
- <div class='issue'>update picture above to show inverse property 'preceded'</div>
+ <h4>preceded</h4>
+ <p>preceded links two instances of ProcessExecution, where "Ordering of processes execution (in provenance) needs to be modeled as a property linking process entities in specific order along a particular dimension (temporal or control flow)"</p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/e/e5/Preceeded.png" />
+ <div class='issue'>update picture above to show inverse property 'preceded'</div>
</section>
</section>
<section>
<h3>Datatype Properties</h3>
- <p>The Provenance Model consists of the following datatype 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>
+ <p>The Provenance Model consists of the following datatype 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>
</section>
<section>
<h3>Overview of the ontology</h3>
- <p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" />
+ <p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" />
+ </section>
</section>
<section>
<h2>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
- <p>
- The Provenance Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The Provenance Ontology classes and properties can be specialized using the following two RDFS properties:
+ <p>The Provenance Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The Provenance Ontology classes and properties can be specialized using the following two RDFS properties:
<ul>
<li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
<li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
</ul>
To illustrate the specialization mechanism, the Provenance Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
- <section>
- <h3>Specialization of Provenance Ontology Classes</h3>
- <p> The provenance scenario describes
- </p>
- </section>
- <section>
- <h3>Specialization of Provenance Ontology Properties</h3>
- </section>
+ <section>
+ <h3>Modeling the Crime File Scenario</h3>
+ <p>The PROV Data Model document [[PROV-DM]] introduces an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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. The example scenario can be encoded as a <a href = "http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href = "">Figure 1</a>:</p>
+ <div class='issue'>insert figure X</div>
+ <p><a href = "">Figure X</a> represents both the Provenance ontology schema and the instance information. For example,
+ <ul>
+ <li><a href="#agent">Agent</a>, e.g. alice, bob, and edith </li>
+ <li><a href="#processexecution">ProcessExecution</a>, e.g. fileCreation, fileAppending </li>
+ <li>specialization of <a href="#entity">Entity</a>, e.g. e1, e2, and e3 </li>
+ </ul>
+ </p>
+ <p>Example given below describes the provenance of <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html#entity">Entity</a> e2 using RDF/XML syntax
+ <div class="exampleOuter">
+ <pre class="example">
+ <?xml version="1.0"?>
+ <rdf:RDF
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
+ xmlns:prov="http://www.w3.org/PROV/ProvenanceOntology.owl#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:cf="http://www.w3.org/PROV/CrimeFileOntology.owl#">
+
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
+ <prov:wasGeneratedBy>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileAppending"/>
+ <prov:wasControlledBy>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Bob">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
+ </rdf:Description>
+ </prov:wasControlledBy>
+ </rdf:Description>
+ </prov:wasGeneratedBy>
+ <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/CrimeFile#e1"/>
+ <cf:hasLocation>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
+ <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
+ </rdf:Description>
+ </cf:hasLocation>
+ <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There was a lot of crime in London last month.</cf:hasFileContent>
+ </rdf:Description>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
+ <prov:Used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
+ </rdf:Description>
+ </rdf:RDF>
+ </pre>
+ </div>
+ </p>
+ </section>
+ <section>
+ <h3>Specialization of Provenance Ontology Classes</h3>
+ <p>
+ </p>
+ </section>
+ <section>
+ <h3>Specialization of Provenance Ontology Properties</h3>
+ </section>
</section>
<section>
<h2>Entailments Supported by the Provenance Model</h2>
- <p>
- This section covers the entailments supported by the Provenance Model, which include the standard RDFS, OWL entailments. ([[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]])
+ <p>This section covers the entailments supported by the Provenance Model, which include the standard RDFS, OWL entailments. ([[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]])
</p>
<h3>Characteristics of Object Properties </h3>
<p>
The table below summarizes the characteristics of the object properties that are defined in the OWL schema. Some of them may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>isUsedBY</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>isUsedBY</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.
</p>
<table style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0">
-
-<tr>
+ <tr>
<th style="border-style: solid; border-width: 0 1px 1px 0">
</th><th style="border-style: solid; border-width: 0 1px 1px 0"> Functional
</th><th style="border-style: solid; border-width: 0 1px 1px 0"> Reverse functional
@@ -612,9 +625,11 @@
</div>
<li> Various things involving IVP-of
</li></ul>
-
</section>
</section>
+ <section>
+ <h3>PROV Data Model Terms Currently not Modeled in PROV Ontology</h3>
+ </section>
<section class='appendix'>
<h2>Acknowledgements</h2>
<p>