--- a/ontology/ProvenanceFormalModel.html Mon Jan 16 19:49:02 2012 +0000
+++ b/ontology/ProvenanceFormalModel.html Mon Jan 16 19:54:22 2012 +0000
@@ -1,14 +1,22 @@
<!DOCTYPE html>
<html>
<head>
- <title>PROV Ontology Model</title>
+ <title>The PROV Ontology: Model and Formal Semantics</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline,
-->
+<!-- From DM -->
+ <style type="text/css">
+ .note { font-size:small; margin-left:50px }
+ table { text-align: center; vertical-align: middle }
+ </style>
+
<script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ <script src="http://www.w3.org/2007/OWL/toggles.js" class="remove"></script>
+
<script class='remove'>
var addExtraReferences = function() {
for (var k in extraReferences)
@@ -17,36 +25,42 @@
var extraReferences = {
"PROV-DM":
"Luc Moreau, Paolo Missier"+
- "<a href=\"http://www.w3.org/TR/owl2-direct-semantics\"><cite>PROV Conceptual Model</cite></a>. "+
- "2011, Work in progress. "+
- "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html\">http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html</a>",
+ "<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>",
"PROV-PAQ":
"Graham Klyne and Paul Groth "+
- "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html\"><cite>Provenance Access and Query</cite></a>. "+
+ "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html\"><cite>Provenance Access and Query</cite></a>. "+
"2011, Work in progress. "+
- "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html\">http://dvcs.w3.org/hg/prov/tip/paq/provenance-access.html</a>",
+ "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html\">http://dvcs.w3.org/hg/prov/tip/paq/prov-aq.html</a>",
"PROV-Ontology-Namespace":
"TBD"+
- "<a href=\"https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl\"><cite>PROV Ontology Namespace</cite></a>. "+
+ "<a href=\"http://www.w3.org/ns/prov-o/\"><cite>PROV Ontology Namespace</cite></a>. "+
"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>",
+ "URL: <a href=\"http://www.w3.org/ns/prov-o/\">http://www.w3.org/ns/prov-o/</a>",
+
+ "PROV-BestPractices":
+ "Stian Soiland-Reyes "+
+ "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/bestpractices/BestPractices.html\"><cite>PROV Best Practices</cite></a>. "+
+ "2011, Work in progress. "+
+ "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/tip/bestpractices/BestPractices.html\">http://dvcs.w3.org/hg/prov/tip/bestpracties/BestPractices.html</a>",
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "FPWD",
+ specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "PROV-FormalModel",
+ shortName: "prov-o",
// if your specification has a subtitle that goes below the main
// formal title, define it here
//subtitle : "",
// if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
+ publishDate: "2011-12-13",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -54,18 +68,18 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- // previousPublishDate: "1977-03-15",
- // previousMaturity: "WD",
+ previousPublishDate: "2011-12-13",
+ previousMaturity: "FPWD",
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111007/", // http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE",
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html", // http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css", "./extra.css"],
// editors, add as many as you like
// only "name" is required
@@ -73,7 +87,8 @@
{ name: "Satya Sahoo", url: "http://cci.case.edu/cci/index.php/Satya_Sahoo",
company: "Case Western Reserve University, USA" },
{ name: "Deborah McGuinness", url: "http://tw.rpi.edu/instances/Deborah_L_McGuinness",
- company: "Rensselaer Polytechnic Institute, USA" }
+ company: "Rensselaer Polytechnic Institute, USA" },
+ { name: "Mike Lang, Jr.", company: "Revelytix, USA"},
],
// authors, add as many as you like.
@@ -81,10 +96,12 @@
// only "name" is required. Same format as editors.
authors: [
+ { name: "(In alphabetical order)",
+ },
{ name: "Khalid Belhajjame",
url:"http://semanticweb.org/wiki/Khalid_Belhajjame",
company: "University of Manchester, UK" },
- { name: "James Cheney",
+ { name: "James Cheney",
url:"http://homepages.inf.ed.ac.uk/jcheney/",
company: "University of Edinburgh, UK" },
{ name: "Daniel Garijo",
@@ -96,13 +113,16 @@
{ name: "Stian Soiland-Reyes",
url:"http://soiland-reyes.com/stian/",
company: "University of Manchester, UK" },
+ { name: "Stephan Zednik",
+ url:"http://tw.rpi.edu/web/person/StephanZednik",
+ company: "Rensselaer Polytechnic Institute, USA" },
],
// name of the WG
wg: "Provenance Working Group",
// URI of the public WG page
- wgURI: "http://www.w3.org/2011/prov/wiki/Main_Page",
+ wgURI: "http://www.w3.org/2011/prov/",
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-prov-wg",
@@ -112,7 +132,7 @@
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
- wgPatentURI: "",
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46974/status",
// Add extraReferences to bibliography database
preProcess: [addExtraReferences],
@@ -121,40 +141,38 @@
</head>
<body>
- <section id='abstract'>
-<p> The PROV Ontology Model (also PROV ontology) encodes the PROV Data Model [[PROV-DM]] 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>
+ <section id="abstract">
+ <p>
+ The PROV Ontology (also PROV-O) encodes the PROV Data Model [[PROV-DM]] 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 can also be specialized to create new classes and properties for modeling provenance information specific to different domain 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>
+
</section>
-<section id='sotd'>
-<p>TODO: MUST include at least one customized paragraph. This section SHOULD include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs SHOULD explain the publication context, including rationale and relationships to other work. See examples and more discussion in the Manual of Style.<a href="http://www.w3.org/2001/06/manual/#Status">TODO</a></p>
-</section>
-
- <section>
- <a id ="introduction"></a>
+ <section id='sotd'>
+ <p>
+ This specification defines the PROV Ontology as the normative representation of the PROV Data Model using the Web Ontology Language (OWL2). This document is part of a set of specifications being created to address the issue of provenance interchange in Web applications. This document is accompanied by (1) the PROV Data Model, (2) the PROV Access and Query, and (3) the Primer documents.
+ </p>
+ </section>
+
+
+ <section id="introduction">
<h2>Introduction</h2>
<p>
- PROV Ontology 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.
+ PROV Ontology (also PROV-O) 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 domains 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 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://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 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 [[PROV-DM]] 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, [[!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.
</p>
- <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
- NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
- "OPTIONAL" in this document are to be interpreted as described in
- [[!RFC2119]].</p>
-
+ <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 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 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> 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 [[!OWL2-PRIMER]] and [[!RDF-PRIMER]], 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 [[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><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://www.w3.org/TR/2011/WD-prov-dm-20111018/#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>
</section>
@@ -166,104 +184,114 @@
<h2>PROV Ontology</h2>
<p> The PROV Data Model [[PROV-DM]] 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 [[!OWL2-DIRECT-SEMANTICS]] [[!OWL2-RDF-BASED-SEMANTICS]].
</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 [[!XMLSCHEMA-2]].
+ <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 [[!XMLSCHEMA-2]].
</p>
- <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. 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 [[PROV-DM]] 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>
- <section>
+ <section>
+ <h3>Mapping the PROV-DM terms to PROV Ontology</h3>
+ <p>The PROV Data Model [[PROV-DM]] 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."[[RDF-MT]], but the PROV-DM seems to introduce the notion of non-monotonic assertions through "Account" construct [[PROV-DM]]. 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>
+ </section>
+ <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
- namespace for the PROV ontology and is denoted by "PROV" and
- the prefix "prov".
+ <p>This document uses the RDF/XML syntax, which is the mandatory syntax supported by all OWL2 syntax [[!OWL2-PRIMER]] to represent the PROV ontology. Provenance assertions using PROV-O can use any of the RDF syntax defined in the RDF specification [[!RDF-PRIMER]].
</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>
+ <h3>Namespace and OWL2 version</h3>
+ <p>
+ The corresponding OWL2 version of this PROV Ontology is available at [[PROV-Ontology-Namespace]] 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> [[PROV-Ontology-Namespace]] and is in this document denoted by the prefix <code>prov</code>.
+ </p>
+ <div class="issue">
+ It has been suggested that [[PROV-DM]] 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>
</section>
</section> <!-- PROV Ontology -->
<section id="prov-ontology--owl-encoding-of-prov-data-model">
<h2>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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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>
<section>
<h3>Classes</h3>
- <p>The PROV ontology consists of classes that can be organized in a taxonomic structure.
- </p>
- <img src="diagram-history/khalidDiagrams/Ontology_hierarchy.png"
- style="width: 50%; min-width: 25em; max-width: 37em"
- alt="Class hierarchy of the PROV OWL ontology"/>
+ <div class="buttonpanel">
+ <form action=""><p>
+ <input id="hide-examples1" onclick="set_display_by_class('div','anexample','none'); set_display_by_id('hide-examples1','none'); set_display_by_id('show-examples1','');" type="button" value="Hide Examples" />
+ <input id="show-examples1" onclick="set_display_by_class('div','anexample',''); set_display_by_id('hide-examples1',''); set_display_by_id('show-examples1','none');" style="display: none" type="button" value="Show Examples" />
+ </p>
+ </form>
+ </div>
+ <p>The PROV ontology consists of classes that can be organized into a hierarchical structure using the <code>rdfs:subClassOf</code> property.
+
+ <img src="diagrams/Ontology_hierarchy.png"
+ style="width: 70%; min-width: 25em; max-width: 60em"
+ alt="Class hierarchy of the PROV ontology"/>
<br>
+ </p>
<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</code>
- </div>
<section id="entity">
<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> prov:Entity rdfs:subClassOf owl:Thing.
</pre>
+ <div class="anexample">
<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"/>
- </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 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> Example of instances of class Entity from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#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.example.com/crimeFile#e1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ <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 [[PROV-DM]]). The additional attributes SHOULD use an appropriate namespace, and the new sub classes MAY be introduced by application-specific provenance ontologies.
</p>
+ <div class="anexample">
<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>
+ <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>
+ </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 id = "processexecution">
- <h4>ProcessExecution</h4>
+ <section id = "activity">
+ <h4>Activity</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>
+ <p>Activity 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"/>
- </rdf:Description>
- </pre>
+ <pre>prov:Activity rdfs:subClassOf owl:Thing.</pre>
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example instances of the class Activity (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 act2 is an instance of Activity is given below.
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
+ </rdf:Description>
+ </pre>
+ </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 class='note'> act2 is an instance of class <code>:Emailing</code>, which is defined to be sub-class of class <code>prov:Activity</code> in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that act2 is also an instance of <code>prov:Activity</code>.
</div>
</section>
@@ -274,261 +302,538 @@
<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"/>
- </rdf:Description>
- </pre>
+ <pre>prov:Agent rdfs:subClassOf prov:Entity.</pre>
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of instances of class Agent from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#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.example.com/crimeFile#Alice">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Agent"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
+
+
+ <section id ="agent-subclasses">
+ <h5>Person, Organization and SoftwareAgent</h5>
+ <div><b>Classes Description</b></div>
+ <p>The class Agent has three sub-classes: Person, Organization, and SoftwareAgent. Person is used to refer to human agents. This class is equivalent to a "foaf:person".
+ The Organization class is used to represent social institutions such as companies, societies. It is equivalent to "foaf:organization" [FOAF].
+ Finally, SoftwareAgent is used to represent pieces of software, e.g., a workflow engine.
+ </p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Person rdfs:subClassOf prov:Agent ;
+ owl:sameAs foaf:Person . </pre>
+ <pre>prov:Oraganization rdfs:subClassOf prov:Agent ;
+ owl:sameAs foaf:Organization . </pre>
+ <pre>prov:SoftwareAgent rdfs:subClassOf prov:Agent ; </pre>
+ <p>The classes Person, Organization and SoftwareAgent are disjoint. Moreover, they do not cover all kinds of agent. </p>
+ <div class="an_subc_example">
+ <div><b>Example</b></div>
+ <p> The RDF/XML syntax for asserting that Alice is an instance of Person, W3C is an Organization, and TavernaWorkflowSystem is a SoftwareAgent.
+ <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/Person"/>
+ </rdf:Description>
+ <rdf:Description rdf:about="W3C">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Organization"/>
+ </rdf:Description>
+ <rdf:Description rdf:about="TavernaWorkflowSystem">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/SoftwareAgent"/>
+ </rdf:Description>
+ </pre>
+
+
+ </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 id="recipe">
- <h4>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:DM. 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.
- </section>
-
+ </section>
- <section id="time">
- <h4>Time</h4>
+ <section id="temporalentity">
+ <h4>TemporalEntity</h4>
<div><b>Class Description</b></div>
- <p>Time represents temporal information about entities in the Provenance model.</p>
+ <p>TemporalEntity represents temporal information about entities in the Provenance model. This class has been re-used from the OWL Time ontology [[!OWL-TIME]]. 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" [[!OWL-TIME]]. The Interval class represents temporal information that have a non-zero duration [[!OWL-TIME]]</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"/>
- </rdf:Description>
- </pre>
+ <pre>time:TemporalEntity rdfs:subClassOf owl:Thing.</pre>
+ <div class="anexample">
+ <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>. t+1 is associated with the instance of Activity act2. The instances of TemporalEntity are linked to instances of Entity or Activity 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 act2 is given below.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
+ <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>
- </section>
-
-
-
- <section id="revision">
- <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 owl:Thing.</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>
<section id="provenancecontainer">
<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. The ProvenanceContainer class can also be used to model the PROV-DM concept of <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Account">Account</a>.</p>
+ <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>
+ <pre>prov:ProvenanceContainer rdfs:subClassOf owl:Thing.</pre>
+ <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="anexample">
+ <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>
<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'>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>
-
-
+ <div class='issue'>Scope and Identifiers.
+ This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
+ <section>
+ <h5>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>
+ </section>
+ </section>
<section id="location">
<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 owl:Thing.</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">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
- <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
- </rdf:Description>
- </cf:hasLocation>
- </pre>
- </div>
+ <pre>prov:Location rdfs:subClassOf owl:Thing.</pre>
+ <p> Example of instances of class Location from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#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="anexample">
+ <div class="exampleOuter">
+ <pre class="example">
+ <cf:hasLocation>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#sharedDirectoryLocation1">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Location"/>
+ <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
+ </rdf:Description>
+ </cf:hasLocation>
+ </pre>
+ </div>
+ </div>
<div class='note'> Need to clarify whether "geographic" includes "geospatial"?</div>
</section>
- <section id="entityinrole">
- <h4>EntityInRole</h4>
+ <section id="qualifiedinvolvement">
+ <h4>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." [[PROV-DM]]</p>
+ <p>The QualifiedInvolvement 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:EntityInRole rdfs:subClassOf PROV:Entity.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class EntityInRole 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>prov:QualifiedInvolvement rdfs:subClassOf owl:Thing.</pre>
+
+ <section id="usage">
+ <h4>Usage</h4>
+ <div><b>Class Description</b></div>
+ <p>The Usage class represents an n-ary property to capture qualifying information related to the use of Entity by Activity.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Usage rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div class="anexample">
+ <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.
+ <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>
+ </div>
+ </section>
+
+ <section id="participation">
+ <h4>Participation</h4>
+ <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 Activity.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Participation rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div class="anexample">
+ <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.
+ <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>
+ </section>
+
+ <section id="control">
+ <h4>Control</h4>
+ <div><b>Class Description</b></div>
+ <p>The Control class represents an n-ary property to capture qualifying information related to the control of Activity by Agent.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Control rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div class="anexample">
+ <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.
+ <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>
+ </section>
+
+ <section id="generation">
+ <h4>Generation</h4>
+ <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 Activity.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Generation rdfs:subClassOf prov:QualifiedInvolvement.</pre>
+ <div class="anexample">
+ <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.
+ <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>
+ </section>
+ </section>
+
+ <section id="recipe">
+ <h4>Recipe</h4>
+ <div><b>Class Description</b></div>
+ <p>Recipe represents the specification of a <a href="#activity">Activity</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 class="anexample">
+ <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.
+ <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/Activity"/>
+ <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#NewsReportEditingProtocol"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id ="role">
+ <h4>Role</h4>
+ <div><b>Class Description</b></div>
+ <p>Role class models additional information about Entity or Activity class with respect to the QualifiedInvolvement class [[PROV-DM]]</p>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Role rdfs:subClassOf owl:Thing.</pre>
+ <div class="anexample">
+ <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 act1)</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.
+ <div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#AliceAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#EntityInRole"/>
- <prov:assumedBy rdf:resource="http://www.w3.org/PROV/CrimeFile#Alice"/>
- <prov:assumedRole rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#author"/>
+ <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='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>
-
- <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>
+ </div>
+ </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 Activity 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>
+ </section>
+
+ <section>
+ <h4>Classes under Discussion</h4>
+ <p>Temporary section for terms not part of "core" ontology.</p>
+
+ <section id="time">
+ <h4>Time</h4>
+ <div><b>Class Description</b></div>
+ <p><code>Time</code> is subclass of <code>time:Instant</code>
+ from [[!OWL-TIME]] 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 [[PROV-DM]] ASN and other serialisations.
+ c</p>
+ </section>
+
+ </section>
</section>
<section id="object-properties">
<h3>Object Properties</h3>
- <p>The Provenance Model consists of the following object properties. </p>
+ <div class="buttonpanel">
+ <form action=""><p>
+ <input id="hide-examples2" onclick="set_display_by_class('div','anexample','none'); set_display_by_id('hide-examples2','none'); set_display_by_id('show-examples2','');" type="button" value="Hide Examples" />
+ <input id="show-examples2" onclick="set_display_by_class('div','anexample',''); set_display_by_id('hide-examples2',''); set_display_by_id('show-examples2','none');" style="display: none" type="button" value="Show Examples" />
+ </p>
+ </form>
+ </div>
+ <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>
<section id="wasgeneratedby">
<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" alt="wasGeneratedBy links Entity to ProcessExecution" />
- <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/ProvenanceOntology.owl#Entity"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
- <prov:wasGeneratedBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe0">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileCreation"/>
- </rdf:Description>
- <prov:wasGeneratedBy>
- </rdf:Description>
- </pre>
+ <p>The wasGeneratedBy property links the Entity class with the Activity class.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
+ <img src="diagrams/wasGeneratedBy.png"
+ style="height: 3em" alt="wasGeneratedBy links Entity to Activity" />
+ <div class="anexample">
+ <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 act0</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"/>
+ <prov:wasGeneratedBy>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act0">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
+ </rdf:Description>
+ <prov:wasGeneratedBy>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="revision">
+ <h4>wasRevisionOf</h4>
+ <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 class="anexample">
+ <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>
+ <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>
+ </section>
+
+ <section id="wasderivedfrom">
+ <h4>wasDerivedFrom</h4>
+ <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." [[PROV-DM]]</p>
+ <img src="diagrams/wasDerivedFrom.png"
+ style="height: 3em" alt="wasDerivedFrom links Entity to Entity" />
+ <div class="anexample">
+ <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">
+ <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>
+ <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 id="waseventuallyderivedfrom">
+ <h4>wasEventuallyDerivedFrom</h4>
+ <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 Activity class [[PROV-DM]].
+ </p>
+ <img src="diagrams/wasEventuallyDerivedFrom.png"
+ style="height: 3em" alt="wasEventuallyDerivedFrom links Entity to Entity" />
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of wasEventuallyDerivedFrom property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e5 wasEventuallyDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e5">
+ <prov:wasEventuallyDerivedFrom rdf:resource="http://www.example.com/crimeFile#e2"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ <div class='issue'>Is the current definition of wasEventuallyDerivedFrom inconsistent with definition of wasDerivedFrom? This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/126">ISSUE-126</a></div>
+ </section>
+
+ <section id="dependedon">
+ <h4>dependedOn</h4>
+ <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 src="diagrams/dependedOn.png"
+ style="height: 3em" alt="dependedOn links Entity to Entity"/>
+ <div class="anexample">
+ <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">
+ <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>
+ </div>
+ </div>
+ <div class='issue'>Is dependedOn a parent property of
+ wasDerivedFrom? This is <a
+ href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a>
+ </div>
+ </section>
+
+
+
+ <section id="used">
+ <h4>used</h4>
+ <p>The used property links the Activity class to the Entity class, where the Entity instance is "consumed" by a Activity instance.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
+ <img src="diagrams/used.png"
+ style="height: 3em" alt="used links Activity to Entity" />
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of used property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 used 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#act2">
+ <prov:used rdf:resource="http://www.example.com/crimeFile#e2"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+
+ <section id="hadparticipant">
+ <h4>hadParticipant</h4>
+ <p>The hadPariticipant property links Entity class to Activity class, where Entity used or wasGeneratedBy Activity.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
+ <img src="diagrams/hadParticipant.png"
+ style="height: 3em" alt="hadParticipant links Activity to Entity" />
+ <div class="anexample">
+ <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>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
+ <prov:hadParticipant rdf:resource="http://www.example.com/crimeFile#e2"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </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 Activity where it was neither "used" or "generated". For example, a witness in a criminal activity.
</div>
</section>
- <section id="wasderivedfrom">
- <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" alt="wasDerivedFrom links Entity to Entity"/>
- <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">
- <pre class="example">
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e3">
- <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/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 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 id="used">
- <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" alt="prov:used links ProcessExecution to Entity"/>
- <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.</p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
- <prov:used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
- </rdf:Description>
- </pre>
- </div>
+ <section id="alternateOf">
+ <h4>alternateOf</h4>
+ <p>The alternateOf property is used to associate an instance of the class Entity to another instance of the same class, specifying that the two instances provide characterizations of the same entity. [[PROV-DM]]</p>
+ <img src="diagrams/alternateOf.png"
+ style="height: 3em" alt="alternateOf links Entity to Entity" />
</section>
-
-
-
-
- <section id="hadparticipant">
- <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 id="wascomplementof">
- <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 id="specializationOf">
+ <h4>specializationOf</h4>
+ <p>The specialization property is used to associate an instance of the class Entity to another instance of the same class, specifying that the former is a more specific characterization of a given entity than the second. [[PROV-DM]]</p>
+ <img src="diagrams/specializationOf.png"
+ style="height: 3em" alt="specializationOf links Entity to Entity" />
+ </div>
</section>
<section id="wascontrolledby">
<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" alt="wasControlledBy links ProcessExecution to Agent"/>
- <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">
- <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>
- </pre>
+ <p>The wasControlledBy property links Activity class to Agent class, where control represents the involvement of the Agent in modifying the characteristics of the instance of the Activity class"[[PROV-DM]].</p>
+ <img src="diagrams/wasControlledBy.png"
+ style="height: 3em" alt="wasControlledBy links Activity to Agent" />
+ <div class="anexample">
+ <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> (Activity) <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.example.com/crimeFile#act1">
+ <prov:wasControlledBy>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#Bob">
+ <rdf:type rdf:resource="http://www.example.com/crime#Journalist"/>
+ </rdf:Description>
+ </prov:wasControlledBy>
+ </rdf:Description>
+ </pre>
+ </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 id="hadrecipe">
<h4>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 Activity class to the Recipe class, which describes the execution characteristics of the instance of the Activity class. The recipe might or might not have been followed exactly by the Activity.
</p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" alt="prov:hadRecipe links ProcessExecution to Recipe."/>
+ <img src="diagrams/hadRecipe.png"
+ style="height: 3em" alt="hadRecipe links Activity to Agent" />
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <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 act1 (instance of Activity 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#act1">
+ <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#instructions1"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
</section>
<section id="wasinformedby">
<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> This object property links two instances of the Activity 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 src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" alt="prov:wasInformedBy links ProcessExecution to ProcessExecution"/>
+ <img src="diagrams/wasInformedBy.png"
+ style="height: 3em" alt="wasInformedBy links Activity to Activity" />
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of wasInformedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasInformedBy act3</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#act4">
+ <prov:wasInformedBy rdf:resource="http://www.example.com/crimeFile#act3"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
</section>
@@ -536,11 +841,269 @@
<section id="wascheduledafter">
<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.
+ This property links two instances of Activity 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 src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" alt="prov:wasScheduledAfter links ProcessExecution to ProcessExecution"/>
+ <img src="diagrams/wasScheduledAfter.png"
+ style="height: 3em" alt="wasScheduledAfter links Activity to Activity" />
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of wasScheduledAfter property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasScheduledAfter act3</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#act4">
+ <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#act3"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </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>
</section>
+
+ <section id="hadtemporalvalue">
+ <h4>hadTemporalValue</h4>
+ <p> This object property links an instance of <code>Activity</code> or <code>Entity</code> with an <code>time:TemporalEntity</code> from [[!OWL-TIME]], thereby allowing association of time value with instances of the two classes and their subclasses.
+ </p>
+ <img src="diagrams/hadTemporalValue.png"
+ style="height: 3em" alt="hadTemporalValue links Activity or Entity to time:TemporalValue" />
+ <div class="anexample">
+ <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 act3 Activity instanc</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#act3">
+ <prov:hasTemporalValue rdf:resource="http://www.example.com/crimeFile#t+3"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+
+
+ <section id="startedat">
+ <h4>startedAt</h4>
+ <p> This object property defines the time when <code>Activity</code> started. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
+ </p>
+ <img src="diagrams/startedAt.png" style="height: 3em" alt="startedAt links Activity to Instant"/>
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of startedAt property is that a act1 (instance of Activity 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#act1">
+ <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>
+ </section>
+
+ <section id="endedat">
+ <h4>endedAt</h4>
+ <p> This object property defines the time when a <code>Activity</code> ended. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
+ </p>
+ <img src="diagrams/endedAt.png" style="height: 3em" alt="endedAt links Activity to Instant"/>
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p> Example of endedAt property is that a act1 (instance of Activity 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#act1">
+ <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>
+ </section>
+ <section id="wasGeneratedat">
+ <h4>wasGeneratedAt</h4>
+ <p> This object property defines the time when a <code>Entity</code> was generated by Activity.
+ </p>
+ <img src="diagrams/wasGeneratedAt.png" style="height: 3em" alt="wasGeneratedAt links Entity to Instant"/>
+ <div class="anexample">
+ <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>
+ </section>
+ </section>
+
+ <section id="attribution">
+ <h4>wasAttributedTo</h4>
+ <p>The wasAttributedTo property links an instance of the Entity class to an instance of Agent class.</p>
+ <img src="diagrams/wasAttributedTo.png"
+ style="height: 3em" alt="wasAttributedTo links Entity to Agent" />
+ <div class="anexample">
+ <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>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
+ <prov:wasAttributedTo rdf:resource="http://www.example.com/crimeFile#David"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="quotation">
+ <h4>wasQuoteOf</h4>
+ <p>The wasQuoteOf property links an instance of the Entity class to an instance of the Agent class.</p>
+ <img src="diagrams/wasQuoteOf.png"
+ style="height: 3em" alt="wasQuoteOf links Entity to Agent" />
+ <div class="anexample">
+ <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, 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"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="summary">
+ <h4>wasSummaryOf</h4>
+ <p>The wasSummaryOf property links two instances of the Entity class.</p>
+ <img src="diagrams/wasSummaryOf.png"
+ style="height: 3em" alt="wasSummaryOf links Entity to Entity" />
+ <div class="anexample">
+ <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>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
+ <prov:wasSummaryOf rdf:resource="http://www.example.com/crimeFile#statistics"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="originalsource">
+ <h4>hadOriginalSource</h4>
+ <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 src="diagrams/hadOriginalSource.png"
+ style="height: 3em" alt="hadOriginalSource links Entity to Entity" />
+ <div class="anexample">
+ <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>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e6">
+ <prov:hadOriginalSource rdf:resource="http://www.example.com/crimeFile#e1"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ <div>
+ </section>
+
+ <section id="hadqualifiedusage">
+ <h4>hadQualifiedUsage</h4>
+ <p>The hadQualifiedUsage property links the Activity class with the Usage class.</p>
+ <img src="diagrams/hadQualifiedUsage.png"
+ style="height: 3em" alt="hadQualifiedUsage links Activity to Usage" />
+ <div class="anexample">
+ <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> act1 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#act1">
+ <prov:hadQualifiedUsage rdf:resource="http://www.example.com/Usage#u1"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="hadqualifiedparticipation">
+ <h4>hadQualifiedParticipation</h4>
+ <p>The hadQualifiedParticipation property links the Activity class with the Participation class.</p>
+ <img src="diagrams/hadQualifiedParticipation.png"
+ style="height: 3em" alt="hadQualifiedParticipation links Activity to Participation" />
+ <div class="anexample">
+ <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> act1 hadQualifiedParticipation p1</i>, where the hadRole describes the participation of Alice as an "author" in act1. 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#act1">
+ <prov:hadQualifiedParticipation rdf:resource="http://www.example.com/crimeFile#p1"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="hadqualifiedcontrol">
+ <h4>hadQualifiedControl</h4>
+ <p>The hadQualifiedControl property links the Activity class with the Control class.</p>
+ <img src="diagrams/hadQualifiedControl.png"
+ style="height: 3em" alt="hadQualifiedControl links Activity to Control" />
+ <div class="anexample">
+ <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> act0 hadQualifiedControl c1</i>, where the hadRole describes the control of act0 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#act0">
+ <prov:hadQualifiedControl rdf:resource="http://www.example.com/crimeFile#c1"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
+ </section>
+
+ <section id="hadqualifiedgeneration">
+ <h4>hadQualifiedGeneration</h4>
+ <p>The hadQualifiedGeneration property links the Activity class with the Generation class.</p>
+ <img src="diagrams/hadQualifiedGeneration.png"
+ style="height: 3em" alt="hadQualifiedGeneration links Activity to Generation" />
+ <div class="anexample">
+ <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>
+ </div>
+ </section>
+
+ <section id="hadqualifiedentity">
+ <h4>hadQualifiedEntity</h4>
+ <p>The hadQualifiedEntity property links the QualifiedInvolvement class with the Entity class.</p>
+ <img src="diagrams/hadQualifiedEntity.png"
+ style="height: 3em" alt="hadQualifiedInvolvement links QualifiedInvolvement to Entity" />
+ <div class="anexample">
+ <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>
+ </div>
+ </section>
</section>
<section id="characteristics-of-object-properties">
@@ -631,8 +1194,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></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>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.
- </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>
</section>
<section id="annotation-properties">
@@ -653,649 +1215,40 @@
</p>
<div class='note'> Is there a need to define standard provenance-specific annotation properties?
</div>
- </section>
+ </section>
<section id="overview-of-the-ontology">
<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"/>
- <a href="https://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.pdf"><img src="https://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.png" alt="Object properties among all classes in the PROV OWL ontology"/></a>
+ <p>The following diagram illustrates the complete PROV ontology except for <code>QualifiedInvolvement</code> which is detailed in the <a href="#overview-of-qualified-involvement">subsection on Qualified Involvement</a> below. </p>
+ <img src="diagrams/ProvenanceOntology.png"
+ style="min-width: 45em; width: 55em; max-width: 95%"
+ alt="Classes and properties of the PROV ontology"/>
+ </section>
+
+ <section id="overview-of-qualified-involvement">
+ <h3>Overview of Qualified Involvement</h3>
+ <p>The <a href="#qualifiedinvolvement">QualifiedInvolvement</a> class describes qualifying information on the PROV-O properties, namely <a href="#used">used</a>, <a href="#wasgeneratedby">wasGeneratedBy</a>, <a href="#wascontrolledby">wasControlledBy</a>, and <a href="#hadparticipant">hadParticipant</a>. The following figure illustrates the representation of qualifying information using these PROV-O classes and properties.</p>
+ <img src="diagrams/QualifiedInvolvementDiagram.png"
+ style="min-width: 45em; width: 55em; max-width: 95%"
+ alt="Classes and properties of qualified involvement in the PROV ontology"/>
</section>
+
</section>
-
-
- <section id="specializing-provenance-ontology-for-domain-specific-provenance-applications">
- <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:</p>
+ <section class='informative' id="specializing-provenance-ontology-for-domain-specific-provenance-applications">
+ <h2>Specializing the PROV Ontology for Domain-specific Provenance Applications</h2>
+ <p>The PROV Ontology does not include all the provenance terms that are required by different application to model provenance information. For example, the classes and properties to model provenance information in the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a>, such as "Journalist" or "FileEditing", are not part of the PROV ontology. This is a deliberate design choice for PROV ontology, since modeling provenance terms for a variety of domain applications in a single ontology is impractical. Hence, the PROV Ontology is conceived as an 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>
+ <li><i>rdfs:subClassOf</i>: 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 [[!RDF-SCHEMA]]</li>
+ <li><i>rdfs:subPropertyOf</i>: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property" [[!RDF-SCHEMA]]</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 id="moeling-the-crime-file-scenario">
- <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>
- <div class='issue'>insert figure X</div>
- <p><a href = "">Figure X</a> represents the ontology schema that extends the PROV ontology to model the provenance details of the crime file scenario. For example,</p>
- <ul>
- <li>specialization of <a href="#agent">Agent</a> to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
- <li><a href="#processexecution">ProcessExecution</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
- <li>specialization of <a href="#entity">Entity</a> to define a class called CrimeFile, which has individuals such as e1, e2, and e3 </li>
- </ul>
- <p>Example given below describes the provenance of <a href="#entity">Entity</a> e2 using RDF/XML syntax</p>
- <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/ProvenanceOntology.owl#Entity"/>
- <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/ProvenanceOntology.owl#ProcessExecution"/>
- <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">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
- <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
- </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">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
- <prov:used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
- </rdf:Description>
- </rdf:RDF>
- </pre>
- </div>
- <section id="specialization-of-prov-ontology-classes">
- <h4>Specialization of PROV Ontology Classes</h4>
- <p> The following new classes were created in the CrimeFile Ontology by extending the PROV ontology classes:</p>
- <section id="cf-journalist">
- <h5>cf:Journalist</h5>
- <p>The cf:Journalist is a specialization of the PROV ontology <a href="#agent">Agent</a> class and models all individuals that participate in creating, editing, and sharing the crime file.The following RDF/XML code illustrates how cf:Journalist is asserted to be a specialization of <a href="#agent">PROV:Agent.</a></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>
- </pre>
- </div>
- </section>
- <section id="cf-crimefile">
- <h5>cf:CrimeFile</h5>
- <p> The cf:CrimeFile is a specialization of the PROV ontology <a href="#entity">Entity</a> class and it models the the file describing the crime statistics in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>, including the multiple versions of the file. The following RDF/XML code illustrates how cf:Journalist is asserted to be a specialization of <a href="#entity">PROV:Entity</a>.
- </p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <section id="cf-filecreation">
- <h5>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking</h5>
- <p>The classes cf:FileCreation, cf:FileEditing,
- cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking are
- specialization of the PROV ontology <a
- href="#processexecution">ProcessExecution</a> and model the
- different activities in the <a
- href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance
- scenario</a>. The following RDF/XML code illustrates the
- specialization of the <a href="#processexecution">PROV:ProcessExecution</a> to define class cf:FileCreation (other classes can be similarly defined by using the subClassOf property).</p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#FileCreation">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
- </rdf:Description>
- </pre>
- </div>
- <p>The following diagram illustrates the above specialization: </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)."/>
- <a href="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf"><img src="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)."/></a>
- <br>
- <em>Example extension of PROV ontology in order to describe the crime file scenario</em>
- </section>
- </section>
- <section id="specialization-of-prov-ontology-properties">
- <h4>Specialization of PROV Ontology Properties</h4>
- <p> The following new object property was created in the CrimeFile Ontology by extending the PROV ontology object property:</p>
- <section id="cf-hadfilepath">
- <h5>cf:hadFilePath</h5>
- <p>The property cf:hadFilePath is a specialization of the PROV ontology hadLocation object property and links the class CrimeFile to the FileDirectory class. The following RDF/XML code illustrates the use of rdfs:subPropertyOf to create hadFilePath property.</p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#hadFilePath">
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#hadLocation"/>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <p>The following diagram illustrates the above specialization: </p>
- <a href="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.pdf">
- <img src="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.png"
- alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:EmailProcessExecution, extSpellChecking extend prov:ProcessExecution; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location."/>
- </a>
- <br>
- <em>Example extension of PROV ontology in order to describe the crime file scenario</em>
- </section>
- </section>
- <section id="modeling-an-example-scientific-workflow-scenario">
- <h3>Modeling an Example Scientific Workflow Scenario</h3>
- <p>This section describes an example of extending the PROV
- ontology to create a provenance ontology for scientific
- workflows.</p>
-
- <p>Scientific workflow systems allow the specification of a
- pipeline of processes which are linked from outputs to inputs.
- Such workflow definitions are typically created in a graphical
- user interface or interactive web application, and can then be
- <em>enacted</em> using particular inputs or parameters.
- Scientists in fields like bioinformatics, chemistry and
- physics use such workflows to perform repeated analysis by
- connecting together disparate set of domain-specific tools and
- services.
- </p>
-
- <p>
- Capturing the provenance of executions in such a workflow
- system will typically include details of each of the process
- executions, such as its inputs and outputs, start and stop
- time, and should ultimately be able to describe the complete
- data lineage through the workflow for any returned output data.
- </p>
- <p>
- This example is not attempting to be a complete or general
- ontology for asserting workflow provenance, but highlights how
- a particular application like a workflow system can express its
- domain specific attributes based on the PROV ontology.
- </p>
- <p>
- <img
- src="examples/ontology-extensions/workflow/workflowOntology.png"
- style="width: 60%; min-width: 20em; max-width: 40em"
- alt="New classes wf:WorkFlowEngine, wf:Process, wf:ValueAtPort, wf:FileValue, and wf:Value extend prov:Agent, prov:ProcessExecution, prov:EntityInRole. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubProcessExecutionOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom." />
- <br>
- <em>Example extension of PROV ontology in order to describe
- workflow provenance</em>
- </p>
- <section id="workflow-extensions-to-prov-classes">
- <h4>Workflow extensions to PROV classes</h4>
- <p>
- In order to describe workflow executions following the
- model above, the PROV ontology is extended with
- workflow-specific subclasses described below:
- </p>
- <dl>
- <dt>wf:Process</dt>
- <dd>
- A subclass of <i>prov:ProcessExecution</i> to
- signify an execution of a process which
- <i>wf:wasDefinedBy</i> a
- a <i>wf:ProcessDefinition</i>, e.g. a workflow or a
- process in a workflow. A workflow process can also
- act as an <i>prov:Agent</i> when controlling nested
- process executions.
- </dd>
- <dt>wf:WorkflowEngine</dt>
- <dd>
- A subclass of <i>prov:Agent</i> to indicate that a
- workflow process was controlled by a workflow
- engine.
- </dd>
- <dt>wf:Value</dt>
- <dd>
- A subclass of <i>prov:Entity</i>, representing a
- value appearing in the workflow execution, it will
- typically be <i>used</i> or <i>generated</i> by
- <i>wf:Process</i> executions. The actual value can
- be provided with a <i>wf:value</i> property.
- </dd>
- <dt>wf:ValueAtPort</dt>
- <dd>
- A subclass of <i>wf:Value</i> and <i>prov:EntityInRole</i>,
- indicating a value while in the role of being used
- or generated by a <i>wf:Process</i> at a particular
- <i>wf:Port</i>.
- </dd>
- <dt>wf:FileValue</dt>
- <dd>
- A <i>wf:Value</i> which has been read from a file.
- As an <i>prov:Entity</i> this represents
- an entity with both attributes <i>wf:value</i> and
- <i>wf:filename</i> fixed, that is the entity describes
- the point when the given file contained the
- content. As the file might be read a while before
- the <i>wf:Value</i> is used by a <i>wf:Process</i>,
- at which point the file content might have changed,
- those values are declared as being derived from
- this file value using the <i>wf:wasReadFrom</i>
- property.
- </dd>
- </dl>
- </section>
- <section id="workflow-extensions-to-prov-properties">
- <h4>Workflow extensions to PROV properties</h4>
- <p>
- While for most cases subclassing will provide the
- additional expressionality the application needs, this
- example ontology also expands on the PROV ontology
- with more specific subproperties.
- </p>
- <dl>
- <dt>wf:wasDefinedBy</dt>
- <dd>
- This sub-property of <i>prov:hadRecipe</i>
- links a
- <i>wf:Process</i> to the defining
- <i>wf:ProcessDefinition</i>. Thus, if there are
- multiple executions of the same workflow definition,
- each of the separate <i>wf:Process</i>es will link to
- the same definition.
- </dd>
- <dt>wf:ranInWorkflowEngine</dt>
- <dd>
- This subproperty of <i>prov:wasControlledBy</i> links a
- <i>wf:Process</i> to the <i>wf:WorkflowEngine</i> it
- was executed in. The engine instance might contain
- additional details such as which version of the
- workflow system was used.
- </dd>
- <dt>wf:wasLaunchedBy</dt>
- <dd>
- This second subproperty of <i>prov:wasControlledBy</i> links a
- <i>wf:Process</i> to a <i>prov:Agent</i>, indicating
- which person asked to execute the given
- wf:ProcessDefinition in the specified
- <i>wf:WorkflowEngine</i>.
- </dd>
- <dt>wf:wasSubProcessExecutionOf</dt>
- <dd>
- This subproperty of <i>prov:wasControlledBy</i> links a
- <i>wf:Process</i> to another <i>prov:Process</i>, indicating
- this is a child execution
- <div class='issue'>Should there be a general way to state subprocesses? -Stian</div>
- </dd>
- <dt>wf:wasReadFrom</dt>
- <dd>
- <p>
- This subproperty of <i>prov:wasDerivedFrom</i> links a
- <i>wf:Value</i> to the <i>wf:FileValue</i> it was read
- from, typically when used as a workflow input.
- As described for <i>wf:FileValue</i> this distinction
- is done because at the time the workflow input is used
- in the workflow, the file input might be different and
- thus should not be described as an attribute of that
- <i>wf:Value</i>.
- </p>
- <p>
- This property hints of an undescribed "Read file"
- process execution which is not described. This is
- therefore an example of how the provenance asserter
- is limiting the scope of its provenance. The engine
- knows that the file was read, but is not able or
- willing to provide any deeper assertions, because its
- primary scope is at the level of executing workflow
- definitions.
- </p>
- </dd>
- <dt>wf:sawValue</dt>
- <dd>
- A subproperty of <i>prov:wasComplementOf</i> which
- indicates that an <i>wf:Value</i> was
- <i>wf:seenAtPort</i> within an
- <i>wf:ValueAtPort</i>. This ValueAtPort is a complement of the
- pointed at Value because one can consider this
- entity to to have the same attributes, but in
- addition the <i>wf:seenAtPort</i> property is fixed.
- <div class='issue'>Should be subproperty of
- not-yet-existing prov:assumedBy or similar -Stian -
- part of <a
- href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a></div>
- </dd>
-
- <dt>wf:wasSeenAtPort</dt>
- <dd>
- A subproperty of <i>prov:assumedRole</i> (not yet defined in
- PROV ontology) indicating which <i>wf:Port</i> a
- <i>wf:ValueAtPort</i> was seen at. Thus one can see
- at which output port a value was generated, or at
- which input port(s) it was used.
-
- As a functional property this requires a different
- <i>wf:ValueAtPort</i> for each <i>use</i> and
- <i>generation</i> of a value. The
- <i>wf:ValueAtPort</i> is linked to the
- <i>wf:Entity</i> using <i>prov:wasComplementOf</i>
- <div class='issue'>Need
- prov:assumedRole in ontology -Stian</div>
- </dd>
- </dl>
- </section>
- <section id="workflow-structure">
- <h4>Workflow structure</h4>
- <p>
- This ontology includes a simple definition language for
- describing the overall workflow structure. This is not
- meant as a general workflow definition language, but allows
- us to describe <i>process executions</i>, <i>use</i> and
- <i>generation</i> with relation to particular sections of
- the workflow definition.
- </p>
- <dl>
- <dt>wf:ProcessDefinition</dt>
- <dd>A definition of how to execute a process. It will
- typically refer to a command or service which will be
- called. Each process definition also
- <i>wf:definesInput</i>s and <i>wf:definesOutput</i>s.
- </dd>
- <dt>wf:Port</dt>
- <dd>
- A port can be considered as a parameter or return value
- for a process. These are typically given names which are
- unique within a process definition. A value is either
- provided to an input port before execution, or produced
- from an output port after execution.
- </dd>
- <dt>wf:linksTo</dt>
- <dd>
- Ports are connected using links. A link from an output
- port to an input port means that the value received on
- that output will be forwarded to the input of the next
- process. Note that in this simplified ontology links can
- also go from Input to Input and Output to Output, these
- are used to connect workflow ports to processor ports.
- </dd>
- <dt>wf:Input</dt>
- <dd>
- An input port for a process will receive a value which
- will be <i>used</i> by the execution. In a dataflow driven
- workflow model, a process will execute as soon as all its
- defined input ports have been provided with values.
- </dd>
- <dt>wf:Output</dt>
- <dd>
- A process execution might return multiple outputs, for
- instance a table and a diagram. Each of these are declared
- as an output port for that process definition.
- </dd>
- <dt>wf:definesSubProcess</dt>
- <dd>
- <p>
- Scientific workflows can be composed of nested workflows
- which can be shared and reused as components. Some
- workflow systems also allow various execution settings
- on the nested workflow, like looping or parallelisation.
- </p>
- <p>
- In this case a process definition will use
- <i>wf:definesSubProcess</i> to indicate its consistent
- parts, and there will be additional <i>wf:linksTo</i> from
- the input ports of this process definition to the input
- ports of some of its nested sub processes, and vice versa
- for the outputs. The top-level workflow is always such a
- process definition.
- </p>
- </dd>
- </dl>
- </section>
- <section id="example-workflow">
- <h4>Example workflow</h4>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png"
- alt="An example workflow with input, three processes, and two outputs." />
- <p>This is an example workflow which defines a workflow
- input <i>input</i>, three processes <i>String_constant</i>,
- <i>Concatenate_two_strings</i> and <i>sha1</i>, and finally
- two workflow outputs <i>combined</i> and <i>sha1</i>. When
- executed, it will execute from top to bottom, first
- concatenating the provided input with the string constant,
- which is returned on the <i>combined</i> output, but also
- provided to the <i>sha1</i> process, which output is given
- to the other workflow port.
- </p>
- <p>
- Using the definition ontology above this workflow can be
- expressed in RDF/XML as:
- </p>
- <div class="exampleOuter">
- <pre class="example">
-<rdf:RDF xml:base="http://www.example.com/workflow1#"
- xmlns:impl="http://company.example.org/engine-implementation#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:wf="http://www.example.com/scientific-workflow#">
-
- <wf:ProcessDefinition rdf:about="#workflow">
- <rdf:type rdf:resource="http://company.example.org/engine-implementation#Workflow"/>
- <wf:definesInput>
- <wf:Input rdf:about="#inName">
- <wf:linksTo rdf:resource="#catIn2" />
- </wf:Input>
- </wf:definesInput>
- <wf:definesOutput rdf:resource="#combined" />
- <wf:definesOutput rdf:resource="#sha1" />
- <wf:definesSubProcess>
- <impl:Constant rdf:about="#String_constant">
- <impl:constant>Hello, </impl:constant>
- <wf:definesOutput>
- <wf:Output rdf:about="#constantValue">
- <wf:linksTo rdf:resource="#catIn1"/>
- </wf:Output>
- </wf:definesOutput>
- </impl:Constant>
- </wf:definesSubProcess>
- <wf:definesSubProcess>
- <impl:Command rdf:about="#cat">
- <impl:command>cat</impl:command>
- <wf:definesInput rdf:resource="#catIn1" />
- <wf:definesInput rdf:resource="#catIn2" />
- <wf:definesOutput>
- <wf:Output rdf:about="#catOut">
- <wf:linksTo rdf:resource="#shaIn"/>
- </wf:Output>
- </wf:definesOutput>
- </impl:Command>
- </wf:definesSubProcess>
- <wf:definesSubProcess>
- <impl:Command rdf:about="#shasum">
- <impl:command>shasum</impl:command>
- <wf:definesInput rdf:resource="#shaIn" />
- <wf:definesOutput>
- <wf:Output rdf:about="#shaOut">
- <wf:linksTo rdf:resource="#sha1"/>
- </wf:Output>
- </wf:definesOutput>
- </impl:Command>
- </wf:definesSubProcess>
- </wf:ProcessDefinition>
-</rdf:RDF>
- </pre></div>
- </section>
- <section id="example-workflow-run">
- <h4>Example workflow run</h4>
- <p>
- This example shows how using the workflow extensions
- together with PROV can provide the provenance of executing
- the workflow defined above.
- </p>
- <div class="exampleOuter"><pre class="example">
-
-<rdf:RDF xmlns="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#"
- xmlns:cnt="http://www.w3.org/2011/content#"
- xmlns:foaf="http://xmlns.com/foaf/0.1/"
- xmlns:prov="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:wf="http://www.example.com/scientific-workflow#"
- xmlns:base="http://www.example.com/run1#" >
-
- <Agent rdf:about="#aUser">
- <rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Person"/>
- <foaf:name>Stian Soiland-Reyes</foaf:name>
- </Agent>
-
- <wf:WorkflowEngine rdf:about="#workflowEngine" />
-
- <wf:FileValue rdf:about="#inputFile">
- <wf:file>/tmp/myinput.txt</wf:file>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>Steve</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:FileValue>
-
- <wf:Value rdf:about="#input">
- <wf:wasReadFrom rdf:resource="#inputFile"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>Steve</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:Process rdf:about="#workflowRun">
- <used>
- <wf:ValueAtPort>
- <wf:sawValue rdf:resource="#input"/>
- <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#inName"/>
- </wf:ValueAtPort>
- </used>
- <wf:ranInWorkflowEngine rdf:resource="#workflowEngine"/>
- <wf:wasLaunchedBy rdf:resource="#aUser"/>
- <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#workflow"/>
- </wf:Process>
-
- <wf:Process rdf:about="#constant">
- <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
- <wf:wasDefinedBy
- rdf:resource="http://www.example.com/workflow1#String_Constant"/>
- </wf:Process>
-
- <wf:Value rdf:about="#hello">
- <wasGeneratedBy rdf:resource="#constant"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:chars>Hello, </cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:ValueAtPort rdf:about="#helloValue">
- <wasGeneratedBy rdf:resource="#constant"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:chars>Hello, </cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- <wf:sawEntity rdf:resource="#hello"/>
- </wf:ValueAtPort>
-
- <wf:Process rdf:about="#combine">
- <used>
- <wf:ValueAtPort>
- <wf:sawValue rdf:resource="#hello"/>
- <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#catIn1"/>
- </wf:ValueAtPort>
- </used>
- <used>
- <wf:ValueAtPort>
- <wf:sawValue rdf:resource="#input"/>
- <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#catIn2"/>
- </wf:ValueAtPort>
- </used>
- <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
- <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#cat"/>
- </wf:Process>
-
- <wf:Value rdf:about="#combined">
- <wasGeneratedBy rdf:resource="#combine"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:chars>Hello, Steve</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:Process rdf:about="#shasum">
- <used rdf:resource="#combined"/>
- <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
- <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#shasum"/>
- </wf:Process>
-
- <wf:Value rdf:about="#sha1">
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:ValueAtPort rdf:about="#sha1OutputFromShasum">
- <wasGeneratedBy rdf:resource="#shasum"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- <wf:sawValue rdf:resource="#sha1"/>
- <wf:wasSeenAt rdf:resource="http://www.example.com/workflow1#shaOut"/>
- </wf:ValueAtPort>
-
- <wf:ValueAtPort rdf:about="#sha1OutputFromWorkflow">
- <wasGeneratedBy rdf:resource="#workflowRun"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- <wf:sawValue rdf:resource="#sha1"/>
- <wf:wasSeenAt rdf:resource="http://www.example.com/workflow1#sha1"/>
- </wf:ValueAtPort>
-
-</rdf:RDF>
- </pre>
- <em>Example available as
- <a
- href="examples/ontology-extensions/workflow/workflow.rdf">RDF/XML</a>
- and
- <a href="examples/ontology-extensions/workflow/workflow.ttl">Turtle</a>
- </em>
- </div>
- <p> Note that for brevity, the example above does not show the inferred classes
- and properties from the PROV ontology. For interoperability, applications
- should also expressed such inferred statements in its
- serialisations, so that the provenance can be read without using
- OWL2 inferencing and the customized ontologies.
- See the <a
- href="examples/ontology-extensions/workflow/workflow-inferred.rdf">workflow-inferred.rdf</a>
- for the complete example showing both domain-specific and PROV ontology terms
- used side by side.
- </p>
- </section>
- </section>
+ <p>A new provenance ontology can be created to model the classes and properties required by an application to represent its domain-specific provenance terms. The new provenance ontology, for the given application, is also expected to include all the PROV Ontology classes and properties, which will facilitate provenance exchange through a common set of terms.</p>
+ <p>The following are a few example classes from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> that are created by specializing PROV Ontology classes:
+ <ul>
+ <li>The <a href="#agent">Agent</a> class can be specialized to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
+ <li>Similarly, the <a href="#activity">Activity</a> class can be specialized to define classes called FileCreation, FileAppending, and FileEditing </li>
+ </ul>
+ The [[PROV-BestPractices]] document describes in detail the approach used to model provenance information in two domain-specific examples by specializing the PROV Ontology.</p>
</section>
<section id="formal-semantics-of-the-prov-ontology">
<h2>Formal Semantics of the PROV Ontology</h2>
@@ -1320,42 +1273,45 @@
<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>Both the <code>rdfs:subClassOf</code> and <code>rdfs:subPropertyOf</code> 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.
+ <div class="anexample">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>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#Alice">
+ <rdf:type rdf:resource="http://www.example.com/crime#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:about="http://www.example.com/crime#Journalist">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/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 rdf:about="http://www.w3.org/ns/prov-o/Agent">
+ <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.w3.org/PROV/CrimeFile#alice">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#Alice">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/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 rdf:about="http://www.example.com/crimeFile#Alice">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
</rdf:Description>
</pre>
- </div>
+ </div>
+ </div>
</section>
@@ -1367,116 +1323,116 @@
</section>
<section id = "entailments-supported-by-the-provenance-model">
<h3>Provenance-specific Entailments Supported by PROV Ontology</h3>
- <p>The PROV-DM [[PROV-DM]] introduces a set of specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.</p>
- <section id="provenance-constraint-on-processexecution">
- <h4>Provenance constraint on ProcessExecution</h4>
- <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#processexecution">ProcessExecution.</a> </p>
+ <p>The PROV-DM [[PROV-DM]] introduces a set of provenance-specific constraints. These provenance constraints will be modeled in PROV ontology as OWL axioms or as rules using the Rule Interchange Framework (RIF) [[!RIF-OVERVIEW]]. These constraints are expected to be used by provenance applications in addition to the PROV ontology file.</p>
+ <div class='note'> The provenance-specific constraints are currently under review and discussion. Individual constraints will be added to the PROV ontology or as RIF rules after the relevant issues are resolved. The provenance constraints will be progressively added to this section as the related issues are resolved.
+ </div>
+
+ </section>
+ </section>
+
+<!-- <section class="appendix">
+ <h2>Provenance-specific Constraints</h2>
+ <p>This section lists the provenance-specific constraints introduced by the PROV-DM [[PROV-DM]], but are still under discussion.
+ <section id="provenance-constraint-on-activity">
+ <h4>Provenance constraint on Activity</h4>
+ <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#activity">Activity.</a> </p>
<div class='issue'>"From a process execution expression, one can infer that the start event precedes the end event of the represented activity." This is <a href="http://www.w3.org/2011/prov/track/issues/121">ISSUE-121</a></div>
</section>
<section id="provenance-constraint-on-wasgeneratedby-generation-affects-attributes">
<h4>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</h4>
- <p>The PROV-DM describes a constraint on wasGeneratedBy that associates the values of attributes of an Entity with the ProcessExecution that generated the Entity.</p>
- <div class='issue'>"Given a process execution pe, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by pe and the entities used by pe. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ <p>The PROV-DM describes a constraint on wasGeneratedBy that associates the values of attributes of an Entity with the Activity that generated the Entity.</p>
+ <div class='issue'>"Given a process execution act, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by act and the entities used by act. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
</section>
<section id="provenance-constraint-on-wasgeneratedby-generation-pe-ordering">
<h4>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
- <p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of the PE instance.</p>
- <div class='issue'>"Given an assertion wasGeneratedBy(x,pe,r) or wasGeneratedBy(x,pe,r,t), one can infer that the generation of the thing denoted by x precedes the end of pe and follows the beginning of pe." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122</a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ <p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of theActivityinstance.</p>
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#activity">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ </div>
</section>
<section id="provenance-constraint-on-wasgeneratedby-generation-unicity">
<h4>Provenance constraint on wasGeneratedBy (generation-unicity)</h4>
- <p>The PROV-DM describes a constraint on wasGeneratedBy that asserts that given an account, only one PE instance can be associated to an Entity instance by the property wasGeneratedBy.</p>
- <div class='issue'>"Given an entity expression denoted by e, two process execution expressions denoted by pe1 and pe2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then pe1=pe2 and q1=q2." This is <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ <p>The PROV-DM describes a constraint on wasGeneratedBy that asserts that given an account, only oneActivityinstance can be associated to an Entity instance by the property wasGeneratedBy.</p>
+ <div class='issue'>"Given an entity expression denoted by e, two process execution expressions denoted by act1 and act2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then act1=act2 and q1=q2." This is <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
</section>
<section id ="provenance-constraint-on-used-use-attributes">
<h4>Provenance constraint on Used (use-attributes)</h4>
- <p>A constraint is defined for the Used relation in PROV-DM, that makes it necessary for an attribute-value to be true for an Entity instance linked to a ProcessExecution instance by relation Used.
+ <p>A constraint is defined for the Used relation in PROV-DM, that makes it necessary for an attribute-value to be true for an Entity instance linked to a Activity instance by relation Used.
</p>
- <div class='issue'>"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the existence of an attribute-value pair in the entity expression identified by e is a pre-condition for the termination of the activity represented by the process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
+ <div class='issue'>"Given a process execution expression identified by act, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the existence of an attribute-value pair in the entity expression identified by e is a pre-condition for the termination of the activity represented by the process execution expression identified by act." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
</section>
<section id ="provenance-constraint-on-used-pe-ordering">
<h4>Provenance constraint on Used (use-pe-ordering)</h4>
- <p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a ProcessExecution instance pe by Used relation) to be "used" before pe terminates and also the "generation" of e precedes "use" of e.
+ <p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a Activity instance act by Used relation) to be "used" before act terminates and also the "generation" of e precedes "use" of e.
</p>
- <div class='issue'>"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by pe and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
- </section>
- <ul>
-<li><a id="PROV:0006" href="#PROV:0006">PROV:0006</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
- assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds, one can
-infer that the use of the thing denoted by <b>e</b> precedes the end
-of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
-can infer that the generation of the thing denoted by <b>e</b> always precedes
-its use." (<a href="../model/ProvenanceModel.html#PROV:0006">link</a>)
-</li>
-
-<li> <a id="PROV:0007" href="#PROV:0007">PROV:0007</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, if and only if:
- the values of some attributes
-of <b>e2</b> are partly or fully determined by the values of some
-attributes of <b>e1</b>." (<a href="../model/ProvenanceModel.html#PROV:0007">link</a>)
-</li>
-
-<li><a id="PROV:0008" href="#PROV:0008">PROV:0008</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, then
-the use
-of characterized thing denoted by <b>e1</b> precedes the generation of
-the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0008">link</a>)
-</li>
-
-<li><a id="PROV:0009" href="#PROV:0009">PROV:0009</a> "If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
-such that:
- <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b>." (<a href="../model/ProvenanceModel.html#PROV:0009">link</a>)
-</li>
-
-
-<li><a id="PROV:0010" href="#PROV:0010">PROV:0010</a> "If <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also hold." (<a href="../model/ProvenanceModel.html#PROV:0010">link</a>)
-</li>
-
-<li><a id="PROV:0011" href="#PROV:0011">PROV:0011</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, and role <b>r2</b>,
-if <b>wasDerivedFrom(e2,e1)</b> and <b>wasGeneratedBy(e2,pe,r2)</b> hold, then there exists a role <b>r1</b>,
-such that <b>used(pe,e1,r1)</b> also holds." (<a href="../model/ProvenanceModel.html#PROV:0011">link</a>)
-</li>
-
-<li><a id="PROV:0012" href="#PROV:0012">PROV:0012</a> "Given two entities <b>e1</b> and <b>e2</b>, if the assertion <b>isEventuallyDerivedFrom(e2,e1)</b>
- holds, then:
-generation of the characterized thing denoted by <b>e1</b> precedes the generation of
-the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0012">link</a>)
-</li>
-
-<li><a id="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>B has some attribute that A does not have" (<a href="../model/ProvenanceModel.html#PROV:0013">link</a>) </li>
- </ol>
-</li>
-
-<li><a id="PROV:0014" href="#PROV:0014">PROV:0014</a> "Given a process execution <b>pe</b> and entity <b>e</b>, <b>hadPariticipant(pe,e)</b> holds if and only if:
- <ul>
- <li> <b>used(pe,e)</b> holds, or</li>
- <li> <b>wasControlledBy(pe,e)</b> holds, or</li>
- <li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and <b>hadParticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
- </ul>
-</li>
-</ul>
-
-<div class="note">The above constraints are extracted from the
- ProvenanceModel document. The text below should be kept consistent
- with the other document, with bidirectional links. The plan is to
- insert formalizations of these constraints once the OWL
- ontology/vocabulary is mature enough to permit this.
-
- If a constraint is changed in the model document, please copy the
- new version here, and check whether it is still consistent with the
- formalization (if any).
-
- If a constraint is dropped, please mark it as "defunct" - don't
- delete it!
- </div>
- </section>
- </section>
-
-
-
+ <div class='issue'>"Given a process execution expression identified by act, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by act and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-attributes">
+ <h4>Provenance constraint on wasDerivedFrom (derivation-attributes)</h4>
+ <p>The PROV-DM describes a constraint for asserting wasDerivedFrom property between two Entity instances if some attributes of an Entity instance are partially or fully determined by attributes values of the other Entity instance.
+ </p>
+ <div class='issue'>"Given a process execution expression denoted by act, entity expressions denoted by e1 and e2, qualifiers q1 and q2, the assertion wasDerivedFrom(e2,e1,pe,q2,q1) or wasDerivedFrom(e2,e1) holds if and only if the values of some attributes of the entity expression identified by e2 are partly or fully determined by the values of some attributes of the entity expression identified by e1." This is <a href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a></div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-use-generation-ordering">
+ <h4>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1), then the for time instant t1 associated with aActivityinstance that "used" is less than the time instant t2 associated with "generation" of e2.
+ </p>
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#activity">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-events">
+ <h4>Provenance constraint on wasDerivedFrom (derivation-events)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1, act), then wasGeneratedBy(e2, act) and used(pe, e1) can also be asserted.
+ </p>
+ <div class='note'> Since the above constraint defined in PROV-DM does not define how act is linked to the derivation of e2 from e1, this constraint can be supported in the "opposite" direction in PROV-O. In other words, given e2 was generated at time instant t2 by act and act used e1 at time instant t1 and t1 is less than t2, then we can assert that wasDerivedFrom(e2, e1).
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-process-execution">
+ <h4>Provenance constraint on wasDerivedFrom (derivation-events)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, then there exists someActivityinstance such that wasGeneratedBy(e2, act) and used(pe, e1) can also be asserted.
+ </p>
+ <div class='note'> This constraint is a re-statement of the generic Semantic Web "open-world assumption". Hence, it is not mapped to PROV ontology.
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-use">
+ <h4>Provenance constraint on wasDerivedFrom (derivation-use)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, and wasGeneratedBy(e2, act) is also asserted then Used(pe, e1) can also be asserted.
+ </p>
+ <div class='note'> This will be asserted as a rule.
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-generation-generation-ordering">
+ <h4>Provenance constraint on wasEventuallyDerivedFrom (derivation-generation-generation-ordering)</h4>
+ <p>The PROV-DM describes a constraint that if wasEventuallyDerivedFrom property is asserted between two Entity instances e1 and e2, then generation of e1 occurred before generation of e2.
+ </p>
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> (or event) with the <a href="#entity">Entity</a> instance and <a href="#activity">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-derivation-linked-independent">
+ <h4>Provenance constraint on wasEventuallyDerivedFrom (derivation-linked-independent)</h4>
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, then wasEventuallyDerivedFrom property can also be asserted between the two Entity instances.
+ </p>
+ <div class='note'> Is this an equivalence constraint or can we assert a subPropertyOf property between wasDerivedFrom and wasEventuallyFrom?
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-complementof-necessary-cond">
+ <h4>Provenance constraint on wasComplementOf (wasComplementOf-necessary-cond)</h4>
+ <p>The PROV-DM describes a constraint that wasComplementOf property holds between two entities over a temporal intersection of the two entities.
+ </p>
+ <div class='note'> Without an explicit association of time value, this constraint cannot be stated or enforced in PROV ontology.
+ </div>
+ </section>
+ <section id ="provenance-constraint-on-hasParticipant-participant">
+ <h4>Provenance constraint on hadParticipant (participant)</h4>
+ <p>The PROV-DM describes a constraint that hadParticipant property holds between an instance of Entity and instance of Activity if the two instances are linked by "used" of "wasControlledBy" or "wasComplementOf".
+ </p>
+ <div class='issue'> "Given two identifiers act and e, respectively identifying a process execution expression and an entity expression, the expression hadParticipant(pe,e) holds if and only if:
+ *used(pe,e) holds, or
+ *wasControlledBy(pe,e) holds, or
+ *wasComplementOf(e1,e) holds for some entity expression identified by e1, and hadParticipant(pe,e1) holds some process execution expression identified by act." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
+ </div>
+ </section>
+ </section>
+-->
<section class='appendix'>
<h2>Acknowledgements</h2>
<p>