--- a/ontology/ProvenanceFormalModel.html Mon Oct 10 13:59:39 2011 -0400
+++ b/ontology/ProvenanceFormalModel.html Mon Oct 10 19:35:05 2011 +0100
@@ -147,7 +147,11 @@
<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 the OWL2 specification.
+ <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 [[!OWL2-PRIMER]], for 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="#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://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]]. 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>
@@ -170,8 +174,17 @@
<section>
<h3>OWL2 Syntax Used in this Document</h3>
- <p>We use the RDF/XML syntax, which is the mandatory syntax supported by all OWL2 syntax [[!OWL2-PRIMER]] to represent the PROV ontology. The OWL2 document for the PROV ontology is available at [[PROV-Ontology-Namespace]], which is also the default namespace for PROV ontology and is denoted by "PROV".
+ <p>We use the RDF/XML syntax, which is the mandatory syntax
+ supported by all OWL2 syntax [[!OWL2-PRIMER]] to represent the
+ PROV ontology. The OWL2 document for the PROV ontology is
+ available at [[PROV-Ontology-Namespace]], which is also the
+ namespace for the PROV ontology and is denoted by "PROV" and
+ the prefix "prov".
</p>
+ <div class="issue">The namespace URI for the ontology has not
+ yet been decided, and the examples in this document might
+ therefore not be using consistent namespaces. This is <a
+ href="http://www.w3.org/2011/prov/track/issues/90">ISSUE-90</a></div>
</section>
</section> <!-- PROV Ontology -->
@@ -189,6 +202,10 @@
alt="Class hierarchy of the PROV OWL ontology"/>
<br>
<p><i>Note: CamelBack notation is used for class names</i></p>
+ <div class="issue">The class <code>prov:Role</code> has been
+ renamed to <code>prov:EntityInRole</code>. (A new
+ <code>prov:Role</code> might appear in the rdfs:range of
+ <code>prov:assuming</div>
<section>
<h4>Entity</h4>
<div><b>Class Description</b></div>
@@ -205,11 +222,27 @@
</rdf:Description>
</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>
+ <p>Attributes that are characterising the entity (as defined
+ in PROV-DM) are stated using RDF properties of the asserted
+ entity. Such properties SHOULD be in a declared namespace,
+ and MAY 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>
+ <div><b>Example</b></div>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
+ <cf:hasLocation rdf:resource="http://www.w3.org/PROV/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>
+ </rdf:Description>
+ </pre>
+ </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 in PROV-DM is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
</section> <!-- Classes -->
<section>
@@ -350,6 +383,13 @@
</rdf:Description>
</pre>
</div>
+ <div class='issue'>prov:assumedBy and prov:assumedRole
+ (or equivalent) properties have not yet been defined
+ in this ontology. This is
+ <a href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a>
+ and
+ <a href="http://www.w3.org/2011/prov/track/issues/111">ISSUE-111</a>
+ </div>
</section>
@@ -1387,7 +1427,7 @@
<li><a name="PROV:0013" href="#PROV:0013">PROV:0013</a> "An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <em>only if</em>:
<ol>
- <li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B must be consistent with that mapping</li>
+ <li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B MUST be consistent with that mapping</li>
<li>B has some attribute that A does not have" (<a href="../model/ProvenanceModel.html#PROV:0013">link</a>) </li>
</ol>
</li>