--- a/ontology/ProvenanceFormalModel.html Wed Oct 05 23:05:57 2011 +0100
+++ b/ontology/ProvenanceFormalModel.html Wed Oct 05 21:43:56 2011 -0400
@@ -33,6 +33,7 @@
"2011, Work in progress. "+
"URL: <a href=\"https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl\">https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl</a>",
};
+
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
@@ -79,11 +80,22 @@
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
- Contributors: [
- { name: "Stian Soiland-Reyes",
- url:"http://soiland-reyes.com/stian/",
- company: "University of Manchester, UK" },
- { name: "TBD" },
+ authors: [
+ { name: "Khalid Belhajjame",
+ url:"http://semanticweb.org/wiki/Khalid_Belhajjame",
+ company: "University of Manchester, UK" },
+ { name: "James Cheney",
+ url:"http://homepages.inf.ed.ac.uk/jcheney/",
+ company: "University of Edinburgh, UK" },
+ { name: "Daniel Garijo",
+ url:"http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo",
+ company: "Universidad Politécnica de Madrid, Spain" },
+ { name: "Tim Lebo",
+ url:"http://tw.rpi.edu/web/person/TimLebo",
+ company: "Rensselaer Polytechnic Institute, USA" },
+ { name: "Stian Soiland-Reyes",
+ url:"http://soiland-reyes.com/stian/",
+ company: "University of Manchester, UK" },
],
// name of the WG
@@ -103,7 +115,7 @@
wgPatentURI: "",
// Add extraReferences to bibliography database
- preProcess: [addExtraReferences],
+ preProcess: [addExtraReferences],
};
</script>
</head>
@@ -1163,22 +1175,69 @@
</section>
<section>
<h2>Formal Semantics of the PROV Ontology</h2>
- <p>The PROV ontology uses OWL2 as the ontology language, hence it supports a set of entailments based on the standard RDFS semantics [[!RDF-MT]] and OWL2 semantics ([[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]]). In this section, we describe these set of semantics as applied to the PROV ontology along with a set of constraints introduced in the PROV-DM [[PROV-DM]] that are provenance-specific. It is intended that provenance applications can leverage this normative description of the formal semantics of PROV ontology to support:
+ <p>The PROV ontology uses OWL2 as the ontology language, hence it supports a set of entailments based on the standard RDF semantics [[!RDF-MT]] and OWL2 semantics ([[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]]). In this section, we describe these set of semantics as applied to the PROV ontology along with a set of constraints introduced in the PROV-DM [[PROV-DM]] that are provenance-specific. It is intended that provenance applications can leverage this normative description of the formal semantics of PROV ontology to support:
<ul>
- <li>Automated consistency checking of provenance assertions (in RDF) that use the PROV ontology as reference model</li>
- <li>Make explicit knowledge that is implicit in RDF-encoded provenance datasets using valid entailment</li>
- </ul>
+ <li><b>Automated consistency checking </b>of provenance assertions (in RDF): Any RDF graph generated to represent provenance information using the PROV ontology as schema can be automatically checked for consistency using reasoning tool, such as FaCT++, Pellet, and Racer among others.</li>
+ <li><b>Inferencing</b>: Make implicit knowledge explicit from RDF-encoded provenance datasets using valid entailment rules</li>
+ </ul>
</p>
<section>
- <h3>RDFS Semantics for PROV Ontology</h3>
+ <h3>RDF Semantics for PROV Ontology</h3>
+ <p> We briefly summarize the essential features of the RDF Semantics and refer to the RDF semantics [[!RDF-MT]] for the normative specification. The RDF Semantics uses model theory, with a notion of interpretation I defined over RDF (rdf-interpretation) or RDFS (rdfs-interpretation) vocabulary, for specifying the formal semantics of a RDF or RDFS graph [[!RDF-MT]]. The rdf-interpretation is an interpretation that satisfies a set of constraints called "<i>RDF semantic conditions</i>" and a set of "<i>RDF axiomatic triples</i>" (see Section 3.1 of RDF Semantics [[!RDF-MT]]). The rdfs-interpretation is defined over the additional terms in the RDFS vocabulary, including <i>rdfs:domain</i>, <i>rdfs:range</i>, <i>rdfs:Class</i>, <i>rdfs:subClassOf</i>, and <i>rdfs:subPropertyOf</i>. An rdfs-interpretation satisfies a set of constraints called "<i>RDFS semantic conditions</i>" and "<i>RDFS axiomatic triples</i>" (see Section 4.1 of RDFS Semantics [[!RDF-MT]]).
+ </p>
+ <p>The rdfs-interpretation supports the following set of the entailment rules that are applicable to the PROV ontology (we do not discuss the simple RDF entailments):
+ </p>
+ <h4>Rule 1</h4>
+ <p>If a PROV ontology class X is defined to be <i>domain</i> of a PROV property, then an individual asserted as "subject" of that property in a RDF triple is an instance of the class X. (from rdf2 Rule defined in RDF Semantics)
+ </p>
+ <h4>Rule 2</h4>
+ <p>Similar to Rule 1, if a PROV ontology class Y is defined to be <i>range</i> of a PROV object property, then an individual asserted as "object" of that property in a RDF triple is an instance of the class Y. (from rdf3 Rule defined in RDF Semantics)
+ </p>
+ <h4>Rule 3</h4>
+ <p>Both the rdfs:subClassOf and rdfsubPropertyOf are transitive properties, hence provenance assertions, in form of RDF triples, using a specialized sub class or sub property can be inferred to be true for their parent class or parent property. For example, in the provenance scenario, though alice and bob are asserted to be individuals of the class Journalist, we can infer that they are also individuals of the PROV ontology class Agent and Entity. Given,
+ </p>
+ <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/CrimeFileOntology.owl#Journalist"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ <p>and</p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
+ </rdf:Description>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ <p>we can infer that</p>
+ <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"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ <p>and</p>
+ <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#Entity"/>
+ </rdf:Description>
+ </pre>
+ </div>
</section>
<section>
- <h3>OWL2 RDF-Based Semantics for PROV Ontology</h3>
+ <h3>OWL2 Semantics for PROV Ontology</h3>
+ <p>In addition to RDF Semantics, the OWL2 semantics as described in [[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]] are also applicable to PROV ontology. We consider the OWL2 RDF-Based Semantics (since it is a semantics superset of OWL2 Direct Semantics) and specifically the extension of the D-interpretation, which satisfies the constraints for rdf-interpretation, rdfs-interpretation (as defined in previous section), graphs with blank nodes, and interpretation defined for RDF datatypes (see Section 5.1 in RDF Semantics [[!RDF-MT]]). The OWL2 RDF-based semantics introduces the notion of "facets" to constrain datatypes, both the rdf:XMLLiteral defined in the RDF Semantics [[!RDF-MT]] and datatypes defined in the OWL2 Structural Specifications [[!OWL2-SYNTAX]]. The OWL2 RDF-based interpretation, also called <b>D-interpretation with facets</b> is a D-interpretation that also satisfies the OWL2 RDF-based semantics called "semantic constraints" (see Section 5 in OWL2 RDF-Based Semantics [[!OWL2-RDF-BASED-SEMANTICS]]).
+ </p>
</section>
<section>
<h3>Provenance-specific Entailments Supported by PROV Ontology</h3>
- </section>
- <section>
<h4>Additional properties </h4>
<div class="note">The following constraints are extracted from the
ProvenanceModel document. The text below should be kept consistent
@@ -1258,31 +1317,9 @@
<li> <b>wasControlledBy(pe,e)</b> holds, or</li>
<li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and
<b>hadPariticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
-</ul>" (<a href="../model/ProvenanceModel.html#PROV:0014">link</a>)
-</li>
-<li><a name="PROV:XXXX" href="#PROV:XXXX">PROV:XXXX</a> "Template
- for more constraints" (<a href="../model/ProvenanceModel.html#PROV:XXXX">link</a>)
-</li>
-<li><div class='constraint'>
- <p>
- <a name="PROV:XXXX">Template for constraints in ConceptualModel</a>
- [<a href="../ontology/ProvenanceFormalModel.html#PROV:XXXX">PROV:XXXX</a>]
-</p>
- </div>
-<li> Various things involving IVP-of
-</li></ul>
+</ul>
</section>
- </section>
- <h3>PROV Data Model Terms Currently not Modeled in PROV Ontology</h3>
- <p>
- The following terms, which are defined in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">PROV data model</a>, are still to be encoded within the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">PROV ontology</a>: </br>
- <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-RecipeLink">Recipe Link</a>,
- <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#process-execution-independent-derivation-expression">wasEventuallyDerivedFrom</a>,
- <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-complement-of">wasComplementOf</a>.
- </p>
- <p>
- In the PROV ontology, the object property wasPrecededBy is using to specify the order of process executions. PROV-DM, however, uses instead two relationships: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-OrderingOfProcessExecutions">wasInformedBy</a> and <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-OrderingOfProcessExecutions">wasScheduledAfter</a>. The ontology needs to be updated to cater for these two relationships.
- </p>
+ </section>
<section class='appendix'>
<h2>Acknowledgements</h2>
<p>