--- a/ontology/ProvenanceFormalModel.html Fri Oct 07 14:14:04 2011 -0400
+++ b/ontology/ProvenanceFormalModel.html Fri Oct 07 14:20:36 2011 -0400
@@ -316,10 +316,15 @@
</section>
<div class='issue'>The PROV-DM defines the term <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a>, which is incorporated implicitly in definition of OWL sub-classes and sub-properties that specialize a parent class or property by defining additional qualifying constraints. Hence, <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a> is not modeled explicitly in PROV ontology.</div>
</section>
+
+
<section>
<h3>Object Properties</h3>
<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>
@@ -342,6 +347,9 @@
</pre>
</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>
@@ -358,6 +366,9 @@
<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>
</section>
+
+
+
<section>
<h4>Used</h4>
<p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
@@ -374,16 +385,26 @@
</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>
</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>
</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>
@@ -406,6 +427,9 @@
<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>hadRecipe</h4>
<p>The ProcessExecution activity performed can be described as
@@ -416,13 +440,19 @@
</p>
<img src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" alt="prov:hadRecipe links ProcessExecution to Recipe."/>
</section>
- <section>
+
+
+
+ <section>
<h4>wasInformedBy</h4>
<p> This object property links two process executions. It is used to express the fact that a given process execution used an entity that was generated by another process execution.
</p>
<img src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" alt="prov:wasInformedBy links ProcessExecution to ProcessExecution"/>
</section>
- <section>
+
+
+
+ <section>
<h4>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.
@@ -521,6 +551,7 @@
</div>
</section>
</section>
+
<section>
<h3>Annotation Properties</h3>
<p>The PROV ontology uses the OWL2 annotation properties to describe additional information about the PROV ontology classes, properties, individuals, and axioms. OWL2 defines nine annotation properties that are part of the OWL2 structural specification (see OWL2 Syntax document for additional details [[!OWL2-SYNTAX]]):
@@ -540,21 +571,27 @@
<div class='note'> Is there a need to define standard provenance-specific annotation properties?
</div>
</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" alt="Object properties among all classes in the PROV OWL ontology"/>
-
</section>
+
</section>
+
+
<section>
<h2>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
- <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:
- <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 PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
+ <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:</p>
+ <ul>
+ <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
+ <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
+ </ul>
+ <p>To illustrate the specialization mechanism, the PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
+
+
+
<section>
<h3>Modeling the Crime File Scenario</h3>
<p>The example scenario can be encoded as a <a href = "http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href = "">Figure X</a>:</p>