--- a/ontology/fpwd/Overview.html Mon Dec 12 18:10:54 2011 -0500
+++ b/ontology/fpwd/Overview.html Mon Dec 12 23:50:37 2011 +0000
@@ -1,28 +1,22 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
-<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml">
+<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
+<html lang="en" dir="ltr">
<head>
<title>The PROV Ontology: Model and Formal Semantics</title>
- <meta content="text/html;charset=utf-8" http-equiv="Content-Type" />
- <script src="toggles.js"></script>
-
-<!--
+ <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">
+ -->
+<!-- From DM -->
+ <style type="text/css">
.note { font-size:small; margin-left:50px }
table { text-align: center; vertical-align: middle }
</style>
-
-
+
+
<style type="text/css">
/*****************************************************************
@@ -79,7 +73,7 @@
}
pre.idl::before {
- content: "WebIDL";
+ content: "WebIDL";
display: block;
width: 150px;
background: #90b8de;
@@ -299,7 +293,7 @@
text-align: left;
}
-.simple th[scope="row"] {
+.simple th[scope="row"] {
background: inherit;
color: inherit;
border-top: 1px solid #ddd;
@@ -315,11 +309,11 @@
}
/* --- DL --- */
-.section dd > p:first-child {
+.section dd > p:first-child {
margin-top: 0;
}
-.section dd > p:last-child {
+.section dd > p:last-child {
margin-bottom: 0;
}
@@ -340,7 +334,7 @@
}
pre.example::before {
- content: "Example";
+ content: "Example";
display: block;
width: 150px;
background: #ff4500;
@@ -360,7 +354,7 @@
}
.issue::before {
- content: "Issue";
+ content: "Issue";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -378,7 +372,7 @@
}
.note::before {
- content: "Note";
+ content: "Note";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -434,7 +428,7 @@
pre.sh_sourceCode .sh_usertype { color: teal; } /* user defined types */
pre.sh_sourceCode .sh_string { color: red; font-family: monospace; } /* strings and chars */
pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; } /* regular expressions */
-pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; } /* comments */
pre.sh_sourceCode .sh_number { color: purple; } /* literal numbers */
pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; } /* e.g., #include, import */
@@ -499,7 +493,7 @@
}
.pending::before {
- content: "Pending Review";
+ content: "Pending Review";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -518,7 +512,7 @@
}
.resolved::before {
- content: "Resolved";
+ content: "Resolved";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -537,7 +531,7 @@
}
.inference::before {
- content: "Inference";
+ content: "Inference";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -556,7 +550,7 @@
.unamedconstraint::before {
- content: "Constraint";
+ content: "Constraint";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -576,13 +570,13 @@
}
.constraint[id]::before {
- content: "Constraint: " attr(id);
- width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
+ content: "Constraint: " attr(id);
+ width: 380px; /* How can we compute the length of "Constraint: " attr(id) */
}
.constraint::before {
- content: "Constraint";
+ content: "Constraint";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -627,7 +621,7 @@
}
.xmpl::before {
- content: "Example";
+ content: "Example";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
@@ -636,8 +630,8 @@
background: #fff;
padding: 3px 1em;
}
-</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8" /></head>
- <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p><h1 id="title" class="title">The PROV Ontology: Model and Formal Semantics</h1><h2 id="w3c-working-draft-13-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 13 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111213/">http://www.w3.org/TR/2011/WD-prov-o-20111213/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
+</style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head>
+ <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1 class="title" id="title">The PROV Ontology: Model and Formal Semantics</h1><h2 id="w3c-working-draft-13-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 13 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111213/">http://www.w3.org/TR/2011/WD-prov-o-20111213/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
<dd><a href="http://tw.rpi.edu/instances/Deborah_L_McGuinness">Deborah McGuinness</a>, Rensselaer Polytechnic Institute, USA</dd>
<dt>Authors:</dt><dd><span>(In alphabetical order)</span></dd>
<dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester, UK</dd>
@@ -645,506 +639,494 @@
<dd><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a>, Universidad Politécnica de Madrid, Spain</dd>
<dd><a href="http://tw.rpi.edu/instances/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute, USA</dd>
<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester, UK</dd>
-<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednick</a>, Rensselaer Polytechnic Institute, USA</dd>
-</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr /></div>
+<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednik</a>, Rensselaer Polytechnic Institute, USA</dd>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
- <div id="abstract" class="introductory section"><h2>Abstract</h2>
+ <div class="introductory section" id="abstract"><h2>Abstract</h2>
<p>
- The PROV Ontology (also PROV-O) encodes the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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>
+ The PROV Ontology (also PROV-O) encodes the PROV Data Model [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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>
- </div><div class="introductory section" id="sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
- <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>
- <p>This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-wg@w3.org">public-prov-wg@w3.org</a> (<a href="mailto:public-prov-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/46974/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#guide-to-this-document" class="tocxref"><span class="secno">1.1 </span>Guide to this Document</a></li></ul></li><li class="tocline"><a href="#prov-ontology" class="tocxref"><span class="secno">2. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#mapping-the-prov-dm-terms-to-prov-ontology" class="tocxref"><span class="secno">2.1 </span>Mapping the PROV-DM terms to PROV Ontology</a></li><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">2.2 </span>OWL2 Syntax Used in this Document</a></li><li class="tocline"><a href="#namespace-and-owl2-version" class="tocxref"><span class="secno">2.3 </span>Namespace and OWL2 version</a></li></ul></li><li class="tocline"><a href="#prov-ontology--owl-encoding-of-prov-data-model" class="tocxref"><span class="secno">3. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">3.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">3.1.3 </span>Agent</a></li><li class="tocline"><a href="#temporalentity" class="tocxref"><span class="secno">3.1.4 </span>TemporalEntity</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">3.1.5 </span>ProvenanceContainer</a><ul class="toc"><li class="tocline"><a href="#modeling-provenancecontainer-and-account-as-rdf-graph" class="tocxref"><span class="secno">3.1.5.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</a></li></ul></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">3.1.6 </span>Location</a></li><li class="tocline"><a href="#qualifiedinvolvement" class="tocxref"><span class="secno">3.1.7 </span>QualifiedInvolvement</a><ul class="toc"><li class="tocline"><a href="#usage" class="tocxref"><span class="secno">3.1.7.1 </span>Usage</a></li><li class="tocline"><a href="#participation" class="tocxref"><span class="secno">3.1.7.2 </span>Participation</a></li><li class="tocline"><a href="#control" class="tocxref"><span class="secno">3.1.7.3 </span>Control</a></li><li class="tocline"><a href="#generation" class="tocxref"><span class="secno">3.1.7.4 </span>Generation</a></li></ul></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">3.1.8 </span>Recipe</a></li><li class="tocline"><a href="#role" class="tocxref"><span class="secno">3.1.9 </span>Role</a></li><li class="tocline"><a href="#classes-under-discussion" class="tocxref"><span class="secno">3.1.10 </span>Classes under Discussion</a><ul class="toc"><li class="tocline"><a href="#time" class="tocxref"><span class="secno">3.1.10.1 </span>Time</a></li></ul></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">3.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">3.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">3.2.2 </span>wasRevisionOf</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">3.2.3 </span>wasDerivedFrom</a></li><li class="tocline"><a href="#waseventuallyderivedfrom" class="tocxref"><span class="secno">3.2.4 </span>wasEventuallyDerivedFrom</a></li><li class="tocline"><a href="#dependedon" class="tocxref"><span class="secno">3.2.5 </span>dependedOn</a></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">3.2.6 </span>used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">3.2.7 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">3.2.8 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">3.2.9 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">3.2.10 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">3.2.11 </span>wasInformedBy</a></li><li class="tocline"><a href="#wascheduledafter" class="tocxref"><span class="secno">3.2.12 </span>wasScheduledAfter</a></li><li class="tocline"><a href="#hadtemporalvalue" class="tocxref"><span class="secno">3.2.13 </span>hadTemporalValue</a><ul class="toc"><li class="tocline"><a href="#startedat" class="tocxref"><span class="secno">3.2.13.1 </span>startedAt</a></li><li class="tocline"><a href="#endedat" class="tocxref"><span class="secno">3.2.13.2 </span>endedAt</a></li><li class="tocline"><a href="#wasGeneratedat" class="tocxref"><span class="secno">3.2.13.3 </span>wasGeneratedAt</a></li></ul></li><li class="tocline"><a href="#attribution" class="tocxref"><span class="secno">3.2.14 </span>wasAttributedTo</a></li><li class="tocline"><a href="#quotation" class="tocxref"><span class="secno">3.2.15 </span>wasQuoteOf</a></li><li class="tocline"><a href="#summary" class="tocxref"><span class="secno">3.2.16 </span>wasSummaryOf</a></li><li class="tocline"><a href="#originalsource" class="tocxref"><span class="secno">3.2.17 </span>hadOriginalSource</a></li><li class="tocline"><a href="#hadqualifiedusage" class="tocxref"><span class="secno">3.2.18 </span>hadQualifiedUsage</a></li><li class="tocline"><a href="#hadqualifiedparticipation" class="tocxref"><span class="secno">3.2.19 </span>hadQualifiedParticipation</a></li><li class="tocline"><a href="#hadqualifiedcontrol" class="tocxref"><span class="secno">3.2.20 </span>hadQualifiedControl</a></li><li class="tocline"><a href="#hadqualifiedgeneration" class="tocxref"><span class="secno">3.2.21 </span>hadQualifiedGeneration</a></li><li class="tocline"><a href="#hadqualifiedentity" class="tocxref"><span class="secno">3.2.22 </span>hadQualifiedEntity</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">3.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">3.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">3.5 </span>Overview of the ontology</a></li><li class="tocline"><a href="#overview-of-qualified-involvement" class="tocxref"><span class="secno">3.6 </span>Overview of Qualified Involvement</a></li></ul></li><li class="tocline"><a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications" class="tocxref"><span class="secno">4. </span>Specializing the PROV Ontology for Domain-specific Provenance Applications</a></li><li class="tocline"><a href="#formal-semantics-of-the-prov-ontology" class="tocxref"><span class="secno">5. </span>Formal Semantics of the PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#rdf-semantics-for-prov-ontology" class="tocxref"><span class="secno">5.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">5.2 </span>OWL2 Semantics for PROV Ontology</a></li><li class="tocline"><a href="#entailments-supported-by-the-provenance-model" class="tocxref"><span class="secno">5.3 </span>Provenance-specific Entailments Supported by PROV Ontology</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
+ </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
+ <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>
+ <p>This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-wg@w3.org">public-prov-wg@w3.org</a> (<a href="mailto:public-prov-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#guide-to-this-document"><span class="secno">1.1 </span>Guide to this Document</a></li></ul></li><li class="tocline"><a class="tocxref" href="#prov-ontology"><span class="secno">2. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#mapping-the-prov-dm-terms-to-prov-ontology"><span class="secno">2.1 </span>Mapping the PROV-DM terms to PROV Ontology</a></li><li class="tocline"><a class="tocxref" href="#owl2-syntax-used-in-this-document"><span class="secno">2.2 </span>OWL2 Syntax Used in this Document</a></li><li class="tocline"><a class="tocxref" href="#namespace-and-owl2-version"><span class="secno">2.3 </span>Namespace and OWL2 version</a></li></ul></li><li class="tocline"><a class="tocxref" href="#prov-ontology--owl-encoding-of-prov-data-model"><span class="secno">3. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#classes"><span class="secno">3.1 </span>Classes</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#entity"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a class="tocxref" href="#activity"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a class="tocxref" href="#agent"><span class="secno">3.1.3 </span>Agent</a></li><li class="tocline"><a class="tocxref" href="#temporalentity"><span class="secno">3.1.4 </span>TemporalEntity</a></li><li class="tocline"><a class="tocxref" href="#provenancecontainer"><span class="secno">3.1.5 </span>ProvenanceContainer</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#modeling-provenancecontainer-and-account-as-rdf-graph"><span class="secno">3.1.5.1 </span>Modeling ProvenanceContainer and Account as RDF Graph</a></li></ul></li><li class="tocline"><a class="tocxref" href="#location"><span class="secno">3.1.6 </span>Location</a></li><li class="tocline"><a class="tocxref" href="#qualifiedinvolvement"><span class="secno">3.1.7 </span>QualifiedInvolvement</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#usage"><span class="secno">3.1.7.1 </span>Usage</a></li><li class="tocline"><a class="tocxref" href="#participation"><span class="secno">3.1.7.2 </span>Participation</a></li><li class="tocline"><a class="tocxref" href="#control"><span class="secno">3.1.7.3 </span>Control</a></li><li class="tocline"><a class="tocxref" href="#generation"><span class="secno">3.1.7.4 </span>Generation</a></li></ul></li><li class="tocline"><a class="tocxref" href="#recipe"><span class="secno">3.1.8 </span>Recipe</a></li><li class="tocline"><a class="tocxref" href="#role"><span class="secno">3.1.9 </span>Role</a></li><li class="tocline"><a class="tocxref" href="#classes-under-discussion"><span class="secno">3.1.10 </span>Classes under Discussion</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#time"><span class="secno">3.1.10.1 </span>Time</a></li></ul></li></ul></li><li class="tocline"><a class="tocxref" href="#object-properties"><span class="secno">3.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#wasgeneratedby"><span class="secno">3.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a class="tocxref" href="#revision"><span class="secno">3.2.2 </span>wasRevisionOf</a></li><li class="tocline"><a class="tocxref" href="#wasderivedfrom"><span class="secno">3.2.3 </span>wasDerivedFrom</a></li><li class="tocline"><a class="tocxref" href="#waseventuallyderivedfrom"><span class="secno">3.2.4 </span>wasEventuallyDerivedFrom</a></li><li class="tocline"><a class="tocxref" href="#dependedon"><span class="secno">3.2.5 </span>dependedOn</a></li><li class="tocline"><a class="tocxref" href="#used"><span class="secno">3.2.6 </span>used</a></li><li class="tocline"><a class="tocxref" href="#hadparticipant"><span class="secno">3.2.7 </span>hadParticipant</a></li><li class="tocline"><a class="tocxref" href="#wascomplementof"><span class="secno">3.2.8 </span>wasComplementOf</a></li><li class="tocline"><a class="tocxref" href="#wascontrolledby"><span class="secno">3.2.9 </span>wasControlledBy</a></li><li class="tocline"><a class="tocxref" href="#hadrecipe"><span class="secno">3.2.10 </span>hadRecipe</a></li><li class="tocline"><a class="tocxref" href="#wasinformedby"><span class="secno">3.2.11 </span>wasInformedBy</a></li><li class="tocline"><a class="tocxref" href="#wascheduledafter"><span class="secno">3.2.12 </span>wasScheduledAfter</a></li><li class="tocline"><a class="tocxref" href="#hadtemporalvalue"><span class="secno">3.2.13 </span>hadTemporalValue</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#startedat"><span class="secno">3.2.13.1 </span>startedAt</a></li><li class="tocline"><a class="tocxref" href="#endedat"><span class="secno">3.2.13.2 </span>endedAt</a></li><li class="tocline"><a class="tocxref" href="#wasGeneratedat"><span class="secno">3.2.13.3 </span>wasGeneratedAt</a></li></ul></li><li class="tocline"><a class="tocxref" href="#attribution"><span class="secno">3.2.14 </span>wasAttributedTo</a></li><li class="tocline"><a class="tocxref" href="#quotation"><span class="secno">3.2.15 </span>wasQuoteOf</a></li><li class="tocline"><a class="tocxref" href="#summary"><span class="secno">3.2.16 </span>wasSummaryOf</a></li><li class="tocline"><a class="tocxref" href="#originalsource"><span class="secno">3.2.17 </span>hadOriginalSource</a></li><li class="tocline"><a class="tocxref" href="#hadqualifiedusage"><span class="secno">3.2.18 </span>hadQualifiedUsage</a></li><li class="tocline"><a class="tocxref" href="#hadqualifiedparticipation"><span class="secno">3.2.19 </span>hadQualifiedParticipation</a></li><li class="tocline"><a class="tocxref" href="#hadqualifiedcontrol"><span class="secno">3.2.20 </span>hadQualifiedControl</a></li><li class="tocline"><a class="tocxref" href="#hadqualifiedgeneration"><span class="secno">3.2.21 </span>hadQualifiedGeneration</a></li><li class="tocline"><a class="tocxref" href="#hadqualifiedentity"><span class="secno">3.2.22 </span>hadQualifiedEntity</a></li></ul></li><li class="tocline"><a class="tocxref" href="#characteristics-of-object-properties"><span class="secno">3.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a class="tocxref" href="#annotation-properties"><span class="secno">3.4 </span>Annotation Properties</a></li><li class="tocline"><a class="tocxref" href="#overview-of-the-ontology"><span class="secno">3.5 </span>Overview of the ontology</a></li><li class="tocline"><a class="tocxref" href="#overview-of-qualified-involvement"><span class="secno">3.6 </span>Overview of Qualified Involvement</a></li></ul></li><li class="tocline"><a class="tocxref" href="#specializing-provenance-ontology-for-domain-specific-provenance-applications"><span class="secno">4. </span>Specializing the PROV Ontology for Domain-specific Provenance Applications</a></li><li class="tocline"><a class="tocxref" href="#formal-semantics-of-the-prov-ontology"><span class="secno">5. </span>Formal Semantics of the PROV Ontology</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#rdf-semantics-for-prov-ontology"><span class="secno">5.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a class="tocxref" href="#owl2-semantics-for-prov-ontology"><span class="secno">5.2 </span>OWL2 Semantics for PROV Ontology</a></li><li class="tocline"><a class="tocxref" href="#entailments-supported-by-the-provenance-model"><span class="secno">5.3 </span>Provenance-specific Entailments Supported by PROV Ontology</a></li></ul></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a class="tocxref" href="#references"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
- <div id="introduction" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">1. </span>Introduction</h2>
+ <div class="section" id="introduction">
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
<p>
- PROV Ontology (also PROV-O) defines the normative modeling of the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] using the <acronym title="World Wide Web Consortium">W3C</acronym> 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-PAQ">PROV-PAQ</a></cite>] and PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>], this document forms a framework for provenance information interchange and management in domain-specific Web-based applications.
+ PROV Ontology (also PROV-O) defines the normative modeling of the PROV Data Model [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] using the <acronym title="World Wide Web Consortium">W3C</acronym> 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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]. 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 [<cite><a href="#bib-PROV-PAQ" rel="biblioentry" class="bibref">PROV-PAQ</a></cite>] and PROV Data Model [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>], 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 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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, [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-DIRECT-SEMANTICS">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>], 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 "<em class="rfc2119" title="must">must</em>", "<em class="rfc2119" title="must not">must not</em>", "<em class="rfc2119" title="required">required</em>", "<em class="rfc2119" title="shall">shall</em>", "<em class="rfc2119" title="shall not">shall not</em>", "<em class="rfc2119" title="should">should</em>", "<em class="rfc2119" title="should not">should not</em>", "<em class="rfc2119" title="recommended">recommended</em>", "<em class="rfc2119" title="may">may</em>", and "<em class="rfc2119" title="optional">optional</em>" in this document are to be interpreted as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
-
- <div id="guide-to-this-document" class="section">
- <h3><span class="secno">1.1 </span>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 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 <acronym title="World Wide Web Consortium">W3C</acronym> RDF(S) and OWL2 specification. Readers are referred to the OWL2 and RDF(S) documentations, starting with the [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>] and [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>], 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. 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>
+ <p>
+ 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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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, [<cite><a href="#bib-OWL2-DIRECT-SEMANTICS" rel="biblioentry" class="bibref">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a href="#bib-OWL2-RDF-BASED-SEMANTICS" rel="biblioentry" class="bibref">OWL2-RDF-BASED-SEMANTICS</a></cite>], 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 "<em title="must" class="rfc2119">must</em>", "<em title="must not" class="rfc2119">must not</em>", "<em title="required" class="rfc2119">required</em>", "<em title="shall" class="rfc2119">shall</em>", "<em title="shall not" class="rfc2119">shall not</em>", "<em title="should" class="rfc2119">should</em>", "<em title="should not" class="rfc2119">should not</em>", "<em title="recommended" class="rfc2119">recommended</em>", "<em title="may" class="rfc2119">may</em>", and "<em title="optional" class="rfc2119">optional</em>" in this document are to be interpreted as described in [<cite><a href="#bib-RFC2119" rel="biblioentry" class="bibref">RFC2119</a></cite>].</p>
+
+ <div class="section" id="guide-to-this-document">
+ <h3><span class="secno">1.1 </span>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 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 <acronym title="World Wide Web Consortium">W3C</acronym> RDF(S) and OWL2 specification. Readers are referred to the OWL2 and RDF(S) documentations, starting with the [<cite><a href="#bib-OWL2-PRIMER" rel="biblioentry" class="bibref">OWL2-PRIMER</a></cite>] and [<cite><a href="#bib-RDF-PRIMER" rel="biblioentry" class="bibref">RDF-PRIMER</a></cite>], 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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]. 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>
</div>
- </div>
-<!-- Introduction -->
-
-
-
-
- <div id="prov-ontology" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">2. </span>PROV Ontology</h2>
- <p> The PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-DIRECT-SEMANTICS">OWL2-DIRECT-SEMANTICS</a></cite>] [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>].
- </p>
- <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 [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a></cite>].
- </p>
- <p>The PROV Data Model document [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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>
-
-
-
- <div id="mapping-the-prov-dm-terms-to-prov-ontology" class="section">
- <h3><span class="secno">2.1 </span>Mapping the PROV-DM terms to PROV Ontology</h3>
- <p>The PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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."[<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>], but the PROV-DM seems to introduce the notion of non-monotonic assertions through "Account" construct [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]. 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>
- </div>
- <div id="owl2-syntax-used-in-this-document" class="section">
- <h3><span class="secno">2.2 </span>OWL2 Syntax Used in this Document</h3>
- <p>This document uses the RDF/XML syntax, which is the mandatory syntax supported by all OWL2 syntax [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>] to represent the PROV ontology. Provenance assertions using PROV-O can use any of the RDF syntax defined in the RDF specification [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>].
- </p>
- </div>
- <div id="namespace-and-owl2-version" class="section">
- <h3><span class="secno">2.3 </span>Namespace and OWL2 version</h3>
- <p>
- The corresponding OWL2 version of this PROV Ontology is available at [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>] 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> [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>] and is in this document denoted by the prefix <code>prov</code>.
- </p>
- <div class="issue">
- It has been suggested that [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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>
- </div>
- </div>
-<!-- PROV Ontology -->
-
-
-
- <div id="prov-ontology--owl-encoding-of-prov-data-model" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">3. </span>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 class in the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a>.
- </p>
- <div id="classes" class="section">
- <h3><span class="secno">3.1 </span>Classes</h3>
- <div class="buttonpanel">
- <form action=""><p>
- <input type="button" value="Hide Examples" onclick="set_display_by_class('div','anexample','none'); set_display_by_id('hide-examples1','none'); set_display_by_id('show-examples1','');" id="hide-examples1" />
- <input type="button" value="Show Examples" style="display: none" onclick="set_display_by_class('div','anexample',''); set_display_by_id('hide-examples1',''); set_display_by_id('show-examples1','none');" id="show-examples1" />
- </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 alt="Class hierarchy of the PROV ontology" style="width: 70%; min-width: 25em; max-width: 60em" src="diagrams/Ontology_hierarchy.png" />
- <br />
- </p>
- <p><i>Note: CamelBack notation is used for class names</i></p>
- <div id="entity" class="section">
- <h4><span class="secno">3.1.1 </span>Entity</h4>
- <div><b>Class Description</b></div>
- <p>Entity is defined to be "An Entity represents an identifiable characterized thing." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
- <div><b>OWL syntax</b></div>
- <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://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.
- </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"/>
-</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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]). The additional attributes <em class="rfc2119" title="should">should</em> use an appropriate namespace, and the new sub classes <em class="rfc2119" title="may">may</em> 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.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>
-<!-- Classes -->
-
-
- <div id="activity" class="section">
- <h4><span class="secno">3.1.2 </span>Activity</h4>
- <div><b>Class Description</b></div>
- <p>Activity is defined to be "an identifiable activity, which performs a piece of work." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
- <div><b>OWL syntax</b></div>
- <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.
- </p><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"> 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>
- </div>
-
-
-
- <div id="agent" class="section">
- <h4><span class="secno">3.1.3 </span>Agent</h4>
- <div><b>Class Description</b></div>
- <p>Agent is defined to be a "characterized entity capable of activity" [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
- <div><b>OWL syntax</b></div>
- <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.
- </p><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>
- </div>
- <div class="note"> Similar to example for Entity, both Alice and Edith are instances of class Journalist, which is defined to be "sub-class" of class Agent in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that both Alice and Edith are also instances of Agent.
- </div>
- </div>
-
-
- <div id="temporalentity" class="section">
- <h4><span class="secno">3.1.4 </span>TemporalEntity</h4>
- <div><b>Class Description</b></div>
- <p>TemporalEntity represents temporal information about entities in the Provenance model. This class has been re-used from the OWL Time ontology [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]. 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" [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]. The Interval class represents temporal information that have a non-zero duration [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>]</p>
- <div><b>OWL syntax</b></div>
- <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>
- </div>
-
- <div id="provenancecontainer" class="section">
- <h4><span class="secno">3.1.5 </span>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://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 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">Scope and Identifiers.
- This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
- <div id="modeling-provenancecontainer-and-account-as-rdf-graph" class="section">
- <h5><span class="secno">3.1.5.1 </span>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>
- </div>
- </div>
-
- <div id="location" class="section">
- <h4><span class="secno">3.1.6 </span>Location</h4>
- <div><b>Class Description</b></div>
- <p>Location is defined to be "is an identifiable geographic place (ISO 19112)." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</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://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.
-
- </p><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>
- </div>
+ </div> <!-- Introduction -->
- <div id="qualifiedinvolvement" class="section">
- <h4><span class="secno">3.1.7 </span>QualifiedInvolvement</h4>
- <div><b>Class Description</b></div>
- <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:QualifiedInvolvement rdfs:subClassOf owl:Thing.</pre>
-
- <div id="usage" class="section">
- <h5><span class="secno">3.1.7.1 </span>Usage</h5>
- <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.
- </p><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"/>
+ <div class="section" id="prov-ontology">
+ <!--OddPage--><h2><span class="secno">2. </span>PROV Ontology</h2>
+ <p> The PROV Data Model [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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 [<cite><a href="#bib-OWL2-DIRECT-SEMANTICS" rel="biblioentry" class="bibref">OWL2-DIRECT-SEMANTICS</a></cite>] [<cite><a href="#bib-OWL2-RDF-BASED-SEMANTICS" rel="biblioentry" class="bibref">OWL2-RDF-BASED-SEMANTICS</a></cite>].
+ </p>
+ <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 [<cite><a href="#bib-XMLSCHEMA-2" rel="biblioentry" class="bibref">XMLSCHEMA-2</a></cite>].
+ </p>
+ <p>The PROV Data Model document [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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>
+
+
+
+ <div class="section" id="mapping-the-prov-dm-terms-to-prov-ontology">
+ <h3><span class="secno">2.1 </span>Mapping the PROV-DM terms to PROV Ontology</h3>
+ <p>The PROV Data Model [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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."[<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>], but the PROV-DM seems to introduce the notion of non-monotonic assertions through "Account" construct [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]. 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>
+ </div>
+ <div class="section" id="owl2-syntax-used-in-this-document">
+ <h3><span class="secno">2.2 </span>OWL2 Syntax Used in this Document</h3>
+ <p>This document uses the RDF/XML syntax, which is the mandatory syntax supported by all OWL2 syntax [<cite><a href="#bib-OWL2-PRIMER" rel="biblioentry" class="bibref">OWL2-PRIMER</a></cite>] to represent the PROV ontology. Provenance assertions using PROV-O can use any of the RDF syntax defined in the RDF specification [<cite><a href="#bib-RDF-PRIMER" rel="biblioentry" class="bibref">RDF-PRIMER</a></cite>].
+ </p>
+ </div>
+ <div class="section" id="namespace-and-owl2-version">
+ <h3><span class="secno">2.3 </span>Namespace and OWL2 version</h3>
+ <p>
+ The corresponding OWL2 version of this PROV Ontology is available at [<cite><a href="#bib-PROV-Ontology-Namespace" rel="biblioentry" class="bibref">PROV-Ontology-Namespace</a></cite>] 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> [<cite><a href="#bib-PROV-Ontology-Namespace" rel="biblioentry" class="bibref">PROV-Ontology-Namespace</a></cite>] and is in this document denoted by the prefix <code>prov</code>.
+ </p>
+ <div class="issue">
+ It has been suggested that [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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>
+ </div>
+ </div> <!-- PROV Ontology -->
+
+
+ <div class="section" id="prov-ontology--owl-encoding-of-prov-data-model">
+ <!--OddPage--><h2><span class="secno">3. </span>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 class in the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a>.
+ </p>
+ <div class="section" id="classes">
+ <h3><span class="secno">3.1 </span>Classes</h3>
+ <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','');" value="Hide Examples" type="button">
+ <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" value="Show Examples" type="button">
+ </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="section" id="entity">
+ <h4><span class="secno">3.1.1 </span>Entity</h4>
+ <div><b>Class Description</b></div>
+ <p>Entity is defined to be "An Entity represents an identifiable characterized thing." [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</p>
+ <div><b>OWL syntax</b></div>
+ <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://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.
+ </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"/>
</rdf:Description></pre>
- </div>
- </div>
- </div>
-
- <div id="participation" class="section">
- <h5><span class="secno">3.1.7.2 </span>Participation</h5>
- <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.
- </p><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"/>
+ </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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]). The additional attributes <em title="should" class="rfc2119">should</em> use an appropriate namespace, and the new sub classes <em title="may" class="rfc2119">may</em> 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.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> <!-- Classes -->
+
+ <div class="section" id="activity">
+ <h4><span class="secno">3.1.2 </span>Activity</h4>
+ <div><b>Class Description</b></div>
+ <p>Activity is defined to be "an identifiable activity, which performs a piece of work." [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</p>
+ <div><b>OWL syntax</b></div>
+ <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.
+ </p><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>
-
- <div id="control" class="section">
- <h5><span class="secno">3.1.7.3 </span>Control</h5>
- <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.
- </p><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"/>
+ </div>
+ </div>
+ <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>
+ </div>
+
+
+
+ <div class="section" id="agent">
+ <h4><span class="secno">3.1.3 </span>Agent</h4>
+ <div><b>Class Description</b></div>
+ <p>Agent is defined to be a "characterized entity capable of activity" [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</p>
+ <div><b>OWL syntax</b></div>
+ <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.
+ </p><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>
- </div>
+ </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>
+ </div>
+
+
+ <div class="section" id="temporalentity">
+ <h4><span class="secno">3.1.4 </span>TemporalEntity</h4>
+ <div><b>Class Description</b></div>
+ <p>TemporalEntity represents temporal information about entities in the Provenance model. This class has been re-used from the OWL Time ontology [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>]. 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" [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>]. The Interval class represents temporal information that have a non-zero duration [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>]</p>
+ <div><b>OWL syntax</b></div>
+ <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>
+ </div>
+
+ <div class="section" id="provenancecontainer">
+ <h4><span class="secno">3.1.5 </span>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://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 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">Scope and Identifiers.
+ This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
+ <div class="section" id="modeling-provenancecontainer-and-account-as-rdf-graph">
+ <h5><span class="secno">3.1.5.1 </span>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>
</div>
-
- <div id="generation" class="section">
- <h5><span class="secno">3.1.7.4 </span>Generation</h5>
- <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.
- </p><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>
- </div>
- </div>
-
- <div id="recipe" class="section">
- <h4><span class="secno">3.1.8 </span>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.
- </p><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"/>
+ </div>
+
+ <div class="section" id="location">
+ <h4><span class="secno">3.1.6 </span>Location</h4>
+ <div><b>Class Description</b></div>
+ <p>Location is defined to be "is an identifiable geographic place (ISO 19112)." [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</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://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.
+
+ </p><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>
+ </div>
+
+
+
+ <div class="section" id="qualifiedinvolvement">
+ <h4><span class="secno">3.1.7 </span>QualifiedInvolvement</h4>
+ <div><b>Class Description</b></div>
+ <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:QualifiedInvolvement rdfs:subClassOf owl:Thing.</pre>
+
+ <div class="section" id="usage">
+ <h5><span class="secno">3.1.7.1 </span>Usage</h5>
+ <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.
+ </p><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>
- </div>
-
- <div id="role" class="section">
- <h4><span class="secno">3.1.9 </span>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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</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.
- </p><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:hadRole rdf:resource="www.example.com/crimeFile#author"/>
+ </div>
+ </div>
+ </div>
+
+ <div class="section" id="participation">
+ <h5><span class="secno">3.1.7.2 </span>Participation</h5>
+ <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.
+ </p><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>
- <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>
- </div>
-
- <div id="classes-under-discussion" class="section">
- <h4><span class="secno">3.1.10 </span>Classes under Discussion</h4>
- <p>Temporary section for terms not part of "core" ontology.</p>
-
- <div id="time" class="section">
- <h5><span class="secno">3.1.10.1 </span>Time</h5>
- <div><b>Class Description</b></div>
- <p><code>Time</code> is subclass of <code>time:Instant</code>
- from [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>] 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] ASN and other serialisations.
- c</p>
- </div>
-
- </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="section" id="control">
+ <h5><span class="secno">3.1.7.3 </span>Control</h5>
+ <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.
+ </p><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>
+ </div>
+
+ <div class="section" id="generation">
+ <h5><span class="secno">3.1.7.4 </span>Generation</h5>
+ <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.
+ </p><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>
+ </div>
+ </div>
+
+ <div class="section" id="recipe">
+ <h4><span class="secno">3.1.8 </span>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.
+ </p><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>
+ </div>
+
+ <div class="section" id="role">
+ <h4><span class="secno">3.1.9 </span>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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</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.
+ </p><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:hadRole rdf:resource="www.example.com/crimeFile#author"/>
+</rdf:Description></pre>
+ </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>
+ </div>
+
+ <div class="section" id="classes-under-discussion">
+ <h4><span class="secno">3.1.10 </span>Classes under Discussion</h4>
+ <p>Temporary section for terms not part of "core" ontology.</p>
+
+ <div class="section" id="time">
+ <h5><span class="secno">3.1.10.1 </span>Time</h5>
+ <div><b>Class Description</b></div>
+ <p><code>Time</code> is subclass of <code>time:Instant</code>
+ from [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>] 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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] ASN and other serialisations.
+ c</p>
+ </div>
+
+ </div>
</div>
- <div id="object-properties" class="section">
- <h3><span class="secno">3.2 </span>Object Properties</h3>
- <div class="buttonpanel">
- <form action=""><p>
- <input type="button" value="Hide Examples" onclick="set_display_by_class('div','anexample','none'); set_display_by_id('hide-examples2','none'); set_display_by_id('show-examples2','');" id="hide-examples2" />
- <input type="button" value="Show Examples" style="display: none" onclick="set_display_by_class('div','anexample',''); set_display_by_id('hide-examples2',''); set_display_by_id('show-examples2','none');" id="show-examples2" />
- </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>
+ <div class="section" id="object-properties">
+ <h3><span class="secno">3.2 </span>Object Properties</h3>
+ <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','');" value="Hide Examples" type="button">
+ <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" value="Show Examples" type="button">
+ </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>
- <div id="wasgeneratedby" class="section">
- <h4><span class="secno">3.2.1 </span>wasGeneratedBy</h4>
- <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 alt="wasGeneratedBy links Entity to Activity" style="height: 3em" src="diagrams/wasGeneratedBy.png" />
- <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>
+ <div class="section" id="wasgeneratedby">
+ <h4><span class="secno">3.2.1 </span>wasGeneratedBy</h4>
+ <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>
- </div>
-
- <div id="revision" class="section">
- <h4><span class="secno">3.2.2 </span>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>
- </div>
+ </div>
+ </div>
+ </div>
- <div id="wasderivedfrom" class="section">
- <h4><span class="secno">3.2.3 </span>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." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
- <img alt="wasDerivedFrom links Entity to Entity" style="height: 3em" src="diagrams/wasDerivedFrom.png" />
- <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>
+ <div class="section" id="revision">
+ <h4><span class="secno">3.2.2 </span>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>
+ </div>
+
+ <div class="section" id="wasderivedfrom">
+ <h4><span class="secno">3.2.3 </span>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." [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</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>
</div>
-
- <div id="waseventuallyderivedfrom" class="section">
- <h4><span class="secno">3.2.4 </span>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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].
- </p>
- <img alt="wasEventuallyDerivedFrom links Entity to Entity" style="height: 3em" src="diagrams/wasEventuallyDerivedFrom.png" />
- <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.
- </p><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>
- </div>
-
- <div id="dependedon" class="section">
- <h4><span class="secno">3.2.5 </span>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 alt="dependedOn links Entity to Entity" style="height: 3em" src="diagrams/dependedOn.png" />
- <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="section" id="waseventuallyderivedfrom">
+ <h4><span class="secno">3.2.4 </span>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 [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>].
+ </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.
+ </p><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>
+ </div>
+
+ <div class="section" id="dependedon">
+ <h4><span class="secno">3.2.5 </span>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>
@@ -1152,665 +1134,657 @@
- <div id="used" class="section">
- <h4><span class="secno">3.2.6 </span>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 alt="used links Activity to Entity" style="height: 3em" src="diagrams/used.png" />
- <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>
- </div>
+ <div class="section" id="used">
+ <h4><span class="secno">3.2.6 </span>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>
+ </div>
- <div id="hadparticipant" class="section">
- <h4><span class="secno">3.2.7 </span>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 alt="hadParticipant links Activity to Entity" style="height: 3em" src="diagrams/hadParticipant.png" />
- <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>
- </div>
+ <div class="section" id="hadparticipant">
+ <h4><span class="secno">3.2.7 </span>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>
+ </div>
- <div id="wascomplementof" class="section">
- <h4><span class="secno">3.2.8 </span>wasComplementOf</h4>
- <p>The wasComplementOf property links two instances of set of assertions about Entity instances, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
- <img alt="wasComplementOf links Entity to Entity" style="height: 3em" src="diagrams/wasComplementOf.png" />
- <div class="note"> Should the wasComplementOf property link two instances of ProvenanceContainer (or Account) classes since they are two classes modeling a set of (one or more) provenance assertions?
- </div>
- </div>
+ <div class="section" id="wascomplementof">
+ <h4><span class="secno">3.2.8 </span>wasComplementOf</h4>
+ <p>The wasComplementOf property links two instances of set of assertions about Entity instances, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>]</p>
+ <img src="diagrams/wasComplementOf.png" style="height: 3em" alt="wasComplementOf links Entity to Entity">
+ <div class="note"> Should the wasComplementOf property link two instances of ProvenanceContainer (or Account) classes since they are two classes modeling a set of (one or more) provenance assertions?
+ </div>
+ </div>
- <div id="wascontrolledby" class="section">
- <h4><span class="secno">3.2.9 </span>wasControlledBy</h4>
- <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"[<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].</p>
- <img alt="wasControlledBy links Activity to Agent" style="height: 3em" src="diagrams/wasControlledBy.png" />
- <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.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
+ <div class="section" id="wascontrolledby">
+ <h4><span class="secno">3.2.9 </span>wasControlledBy</h4>
+ <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"[<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>].</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.
+ </p><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>
+ <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>
+</rdf:Description> </pre>
+ </div>
+ </div>
+ </div>
- <div id="hadrecipe" class="section">
+ <div class="section" id="hadrecipe">
<h4><span class="secno">3.2.10 </span>hadRecipe</h4>
<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 alt="hadRecipe links Activity to Agent" style="height: 3em" src="diagrams/hadRecipe.png" />
- <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>
+ <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>
</div>
- <div id="wasinformedby" class="section">
+ <div class="section" id="wasinformedby">
<h4><span class="secno">3.2.11 </span>wasInformedBy</h4>
<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 alt="wasInformedBy links Activity to Activity" style="height: 3em" src="diagrams/wasInformedBy.png" />
- <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>
+ <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>
</div>
- <div id="wascheduledafter" class="section">
+ <div class="section" id="wascheduledafter">
<h4><span class="secno">3.2.12 </span>wasScheduledAfter</h4>
<p>
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 alt="wasScheduledAfter links Activity to Activity" style="height: 3em" src="diagrams/wasScheduledAfter.png" />
- <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>
+ <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>
</div>
-
- <div id="hadtemporalvalue" class="section">
- <h4><span class="secno">3.2.13 </span>hadTemporalValue</h4>
- <p> This object property links an instance of <code>Activity</code> or <code>Entity</code> with an <code>time:TemporalEntity</code> from [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>], thereby allowing association of time value with instances of the two classes and their subclasses.
- </p>
- <img alt="hadTemporalValue links Activity or Entity to time:TemporalValue" style="height: 3em" src="diagrams/hadTemporalValue.png" />
- <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. 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>
-
-
- <div id="startedat" class="section">
- <h5><span class="secno">3.2.13.1 </span>startedAt</h5>
- <p> This object property defines the time when <code>Activity</code> started. The time is specified as an <code>time:Instant</code> [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>].
- </p>
- <img alt="startedAt links Activity to Instant" style="height: 3em" src="diagrams/startedAt.png" />
- <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>
+
+ <div class="section" id="hadtemporalvalue">
+ <h4><span class="secno">3.2.13 </span>hadTemporalValue</h4>
+ <p> This object property links an instance of <code>Activity</code> or <code>Entity</code> with an <code>time:TemporalEntity</code> from [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>], 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. 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>
+
+
+ <div class="section" id="startedat">
+ <h5><span class="secno">3.2.13.1 </span>startedAt</h5>
+ <p> This object property defines the time when <code>Activity</code> started. The time is specified as an <code>time:Instant</code> [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>].
+ </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>
- </div>
-
- <div id="endedat" class="section">
- <h5><span class="secno">3.2.13.2 </span>endedAt</h5>
- <p> This object property defines the time when a <code>Activity</code> ended. The time is specified as an <code>time:Instant</code> [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL-TIME">OWL-TIME</a></cite>].
- </p>
- <img alt="endedAt links Activity to Instant" style="height: 3em" src="diagrams/endedAt.png" />
- <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>
+ </div>
+
+ <div class="section" id="endedat">
+ <h5><span class="secno">3.2.13.2 </span>endedAt</h5>
+ <p> This object property defines the time when a <code>Activity</code> ended. The time is specified as an <code>time:Instant</code> [<cite><a href="#bib-OWL-TIME" rel="biblioentry" class="bibref">OWL-TIME</a></cite>].
+ </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>
- </div>
- <div id="wasGeneratedat" class="section">
- <h5><span class="secno">3.2.13.3 </span>wasGeneratedAt</h5>
- <p> This object property defines the time when a <code>Entity</code> was generated by Activity.
- </p>
- <img alt="wasGeneratedAt links Entity to Instant" style="height: 3em" src="diagrams/wasGeneratedAt.png" />
- <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>
+ </div>
+ </div>
+ </div>
+ <div class="section" id="wasGeneratedat">
+ <h5><span class="secno">3.2.13.3 </span>wasGeneratedAt</h5>
+ <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>
- </div>
- </div>
+ </div>
+ </div>
+ </div>
+ </div>
- <div id="attribution" class="section">
- <h4><span class="secno">3.2.14 </span>wasAttributedTo</h4>
- <p>The wasAttributedTo property links an instance of the Entity class to an instance of Agent class.</p>
- <img alt="wasAttributedTo links Entity to Agent" style="height: 3em" src="diagrams/wasAttributedTo.png" />
- <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>
- </div>
-
- <div id="quotation" class="section">
- <h4><span class="secno">3.2.15 </span>wasQuoteOf</h4>
- <p>The wasQuoteOf property links an instance of the Entity class to an instance of the Agent class.</p>
- <img alt="wasQuoteOf links Entity to Agent" style="height: 3em" src="diagrams/wasQuoteOf.png" />
- <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>
- </div>
-
- <div id="summary" class="section">
- <h4><span class="secno">3.2.16 </span>wasSummaryOf</h4>
- <p>The wasSummaryOf property links two instances of the Entity class.</p>
- <img alt="wasSummaryOf links Entity to Entity" style="height: 3em" src="diagrams/wasSummaryOf.png" />
- <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>
- </div>
-
- <div id="originalsource" class="section">
- <h4><span class="secno">3.2.17 </span>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 alt="hadOriginalSource links Entity to Entity" style="height: 3em" src="diagrams/hadOriginalSource.png" />
- <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>
- </div></div></div>
-
- <div id="hadqualifiedusage" class="section">
- <h4><span class="secno">3.2.18 </span>hadQualifiedUsage</h4>
- <p>The hadQualifiedUsage property links the Activity class with the Usage class.</p>
- <img alt="hadQualifiedUsage links Activity to Usage" style="height: 3em" src="diagrams/hadQualifiedUsage.png" />
- <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>
- </div>
+ <div class="section" id="attribution">
+ <h4><span class="secno">3.2.14 </span>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>
+ </div>
+
+ <div class="section" id="quotation">
+ <h4><span class="secno">3.2.15 </span>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>
+ </div>
+
+ <div class="section" id="summary">
+ <h4><span class="secno">3.2.16 </span>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>
+ </div>
+
+ <div class="section" id="originalsource">
+ <h4><span class="secno">3.2.17 </span>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>
+ </div></div></div>
+
+ <div class="section" id="hadqualifiedusage">
+ <h4><span class="secno">3.2.18 </span>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>
+ </div>
- <div id="hadqualifiedparticipation" class="section">
- <h4><span class="secno">3.2.19 </span>hadQualifiedParticipation</h4>
- <p>The hadQualifiedParticipation property links the Activity class with the Participation class.</p>
- <img alt="hadQualifiedParticipation links Activity to Participation" style="height: 3em" src="diagrams/hadQualifiedParticipation.png" />
- <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>
- </div>
-
- <div id="hadqualifiedcontrol" class="section">
- <h4><span class="secno">3.2.20 </span>hadQualifiedControl</h4>
- <p>The hadQualifiedControl property links the Activity class with the Control class.</p>
- <img alt="hadQualifiedControl links Activity to Control" style="height: 3em" src="diagrams/hadQualifiedControl.png" />
- <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>
- </div>
-
- <div id="hadqualifiedgeneration" class="section">
- <h4><span class="secno">3.2.21 </span>hadQualifiedGeneration</h4>
- <p>The hadQualifiedGeneration property links the Activity class with the Generation class.</p>
- <img alt="hadQualifiedGeneration links Activity to Generation" style="height: 3em" src="diagrams/hadQualifiedGeneration.png" />
- <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>
- </div>
-
- <div id="hadqualifiedentity" class="section">
- <h4><span class="secno">3.2.22 </span>hadQualifiedEntity</h4>
- <p>The hadQualifiedEntity property links the QualifiedInvolvement class with the Entity class.</p>
- <img alt="hadQualifiedInvolvement links QualifiedInvolvement to Entity" style="height: 3em" src="diagrams/hadQualifiedEntity.png" />
- <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>
- </div>
+ <div class="section" id="hadqualifiedparticipation">
+ <h4><span class="secno">3.2.19 </span>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>
+ </div>
+
+ <div class="section" id="hadqualifiedcontrol">
+ <h4><span class="secno">3.2.20 </span>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>
+ </div>
+
+ <div class="section" id="hadqualifiedgeneration">
+ <h4><span class="secno">3.2.21 </span>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>
+ </div>
+
+ <div class="section" id="hadqualifiedentity">
+ <h4><span class="secno">3.2.22 </span>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>
+ </div>
</div>
- <div id="characteristics-of-object-properties" class="section">
- <h3><span class="secno">3.3 </span>Characteristics of Object Properties </h3>
- <p>The table below summarizes the characteristics of the object properties that are defined in the OWL schema.
- </p>
- <table style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0">
- <tbody><tr>
- <th style="border-style: solid; border-width: 0 1px 1px 0">
- </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Functional
- </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Reverse functional
- </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Transitive
- </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Symmetric
- </th><th style="border-style: solid; border-width: 0 1px 1px 0">Asymmetric
- </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Reflexive
-
- </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Irreflexive
- </th></tr>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> wasControlledBy
- </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">No
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">?
- </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><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>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> wasDerivedFrom
+ <div class="section" id="characteristics-of-object-properties">
+ <h3><span class="secno">3.3 </span>Characteristics of Object Properties </h3>
+ <p>The table below summarizes the characteristics of the object properties that are defined in the OWL schema.
+ </p>
+ <table style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0">
+ <tbody><tr>
+ <th style="border-style: solid; border-width: 0 1px 1px 0">
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Functional
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Reverse functional
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Transitive
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Symmetric
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0">Asymmetric
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Reflexive
- </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">No
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
- </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><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>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> hadParticipant
- </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">No
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">?
- </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><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>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> wasGeneratedBy
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
- </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">?
- </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><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>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> used
- </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">No
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">?
- </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><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>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> wasInformedBy
- </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">No
- </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">No
- </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">No
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">No
- </td></tr>
- <tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> wasScheduledAfter
- </td><td style="border-style: solid; border-width: 0 1px 1px 0">No
+ </th><th style="border-style: solid; border-width: 0 1px 1px 0"> Irreflexive
+ </th></tr>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> wasControlledBy
+ </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">No
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">?
+ </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><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>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> wasDerivedFrom
- </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><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><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></tbody></table>
- <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>
- </div>
+ </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">No
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
+ </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><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>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> hadParticipant
+ </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">No
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">?
+ </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><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>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> wasGeneratedBy
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
+ </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">?
+ </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><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>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> used
+ </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">No
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">?
+ </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><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>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> wasInformedBy
+ </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">No
+ </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">No
+ </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">No
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">No
+ </td></tr>
+ <tr>
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> wasScheduledAfter
+ </td><td style="border-style: solid; border-width: 0 1px 1px 0">No
- <div id="annotation-properties" class="section">
- <h3><span class="secno">3.4 </span>Annotation Properties</h3>
- <p>The PROV ontology uses the OWL2 annotation properties to describe additional information about the PROV ontology classes, properties, individuals, and axioms. OWL2 defines nine annotation properties that are part of the OWL2 structural specification (see OWL2 Syntax document for additional details [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-SYNTAX">OWL2-SYNTAX</a></cite>]):</p>
- <ul>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:label</b></a>- This property is used to associated a "human-readable label" with a term. For example, the class "<a href="#location">Location</a>" can be annotated with "Geo-spatial Location" label using rdfs:label</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:comment</b></a>- This property is used to annotate ontology terms with a readable comment. For example, the class "<a href="#location">Location</a>" can be annotated with "This class represents an identifiable geographic place (ISO 19112)" comment using the rdfs:comment property</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:seeAlso</b></a>- Provenance ontologies can use this property for referring to location of additional information, using an Internationalized Resource Identifier (IRI), associated with a provenance ontology resource. For example, a PROV ontology term can refer users to the PROV Data Model for a descriptive specification</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:isDefinedBy</b></a>- Information related to the definition of a term can be provided by a PROV ontology term using this property</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:deprecated</b></a>- In many cases, domain-specific provenance ontologies will replace or remove certain ontology terms. These terms can be labeled using this property (with value set to be "true^^xsd:boolean")</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>olw:versionInfo</b></a>- This property is used to associate a version information with ontology terms. For example, the current version of the PROV ontology is version "1.0"</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:priorVersion</b></a>- This property allows provenance applications to locate previous version of ontology terms. For example, the PROV ontology can identify a previous version "0.1" using this property</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:backwardCompatibleWith</b></a>- Provenance ontologies can specify previous version of the ontology that are compatible with the current version of the ontology using this property</li>
- <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:incompatibleWith</b></a>- Similar to the previous property, this property allows provenance applications to identify incompatible version of provenance ontologies.</li>
- </ul>
- <p>Additional annotation properties can be defined by provenance ontologies, but unlike the OWL2 annotation properties, these custom annotation properties may not be interpreted in a standard manner across different provenance applications.
- </p>
- <div class="note"> Is there a need to define standard provenance-specific annotation properties?
- </div>
- </div>
+ </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><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><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></tbody></table>
+ <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>
+ </div>
- <div id="overview-of-the-ontology" class="section">
- <h3><span class="secno">3.5 </span>Overview of the ontology</h3>
+ <div class="section" id="annotation-properties">
+ <h3><span class="secno">3.4 </span>Annotation Properties</h3>
+ <p>The PROV ontology uses the OWL2 annotation properties to describe additional information about the PROV ontology classes, properties, individuals, and axioms. OWL2 defines nine annotation properties that are part of the OWL2 structural specification (see OWL2 Syntax document for additional details [<cite><a href="#bib-OWL2-SYNTAX" rel="biblioentry" class="bibref">OWL2-SYNTAX</a></cite>]):</p>
+ <ul>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:label</b></a>- This property is used to associated a "human-readable label" with a term. For example, the class "<a href="#location">Location</a>" can be annotated with "Geo-spatial Location" label using rdfs:label</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:comment</b></a>- This property is used to annotate ontology terms with a readable comment. For example, the class "<a href="#location">Location</a>" can be annotated with "This class represents an identifiable geographic place (ISO 19112)" comment using the rdfs:comment property</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:seeAlso</b></a>- Provenance ontologies can use this property for referring to location of additional information, using an Internationalized Resource Identifier (IRI), associated with a provenance ontology resource. For example, a PROV ontology term can refer users to the PROV Data Model for a descriptive specification</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:isDefinedBy</b></a>- Information related to the definition of a term can be provided by a PROV ontology term using this property</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:deprecated</b></a>- In many cases, domain-specific provenance ontologies will replace or remove certain ontology terms. These terms can be labeled using this property (with value set to be "true^^xsd:boolean")</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>olw:versionInfo</b></a>- This property is used to associate a version information with ontology terms. For example, the current version of the PROV ontology is version "1.0"</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:priorVersion</b></a>- This property allows provenance applications to locate previous version of ontology terms. For example, the PROV ontology can identify a previous version "0.1" using this property</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:backwardCompatibleWith</b></a>- Provenance ontologies can specify previous version of the ontology that are compatible with the current version of the ontology using this property</li>
+ <li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:incompatibleWith</b></a>- Similar to the previous property, this property allows provenance applications to identify incompatible version of provenance ontologies.</li>
+ </ul>
+ <p>Additional annotation properties can be defined by provenance ontologies, but unlike the OWL2 annotation properties, these custom annotation properties may not be interpreted in a standard manner across different provenance applications.
+ </p>
+ <div class="note"> Is there a need to define standard provenance-specific annotation properties?
+ </div>
+ </div>
+
+ <div class="section" id="overview-of-the-ontology">
+ <h3><span class="secno">3.5 </span>Overview of the ontology</h3>
<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 alt="Classes and properties of the PROV ontology" style="min-width: 45em; width: 55em; max-width: 95%" src="diagrams/ProvenanceOntology.png" />
+ <img src="diagrams/ProvenanceOntology.png" style="min-width: 45em; width: 55em; max-width: 95%" alt="Classes and properties of the PROV ontology">
</div>
-
- <div id="overview-of-qualified-involvement" class="section">
+
+ <div class="section" id="overview-of-qualified-involvement">
<h3><span class="secno">3.6 </span>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 alt="Classes and properties of qualified involvement in the PROV ontology" style="min-width: 45em; width: 55em; max-width: 95%" src="diagrams/QualifiedInvolvementDiagram.png" />
+ <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">
</div>
</div>
- <div id="specializing-provenance-ontology-for-domain-specific-provenance-applications" class="informative section">
-
-<!-- OddPage -->
-<h2><span class="secno">4. </span>Specializing the PROV Ontology for Domain-specific Provenance Applications</h2><p><em>This section is non-normative.</em></p>
- <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><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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</li>
- <li><i>rdfs:subPropertyOf</i>: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property" [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]</li>
+ <div class="informative section" id="specializing-provenance-ontology-for-domain-specific-provenance-applications">
+ <!--OddPage--><h2><span class="secno">4. </span>Specializing the PROV Ontology for Domain-specific Provenance Applications</h2><p><em>This section is non-normative.</em></p>
+ <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><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 [<cite><a href="#bib-RDF-SCHEMA" rel="biblioentry" class="bibref">RDF-SCHEMA</a></cite>]</li>
+ <li><i>rdfs:subPropertyOf</i>: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property" [<cite><a href="#bib-RDF-SCHEMA" rel="biblioentry" class="bibref">RDF-SCHEMA</a></cite>]</li>
</ul>
<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:
- </p><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 [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-BestPractices">PROV-BestPractices</a></cite>] document describes in detail the approach used to model provenance information in two domain-specific examples by specializing the PROV Ontology.<p></p>
- </div>
- <div id="formal-semantics-of-the-prov-ontology" class="section">
-
-<!-- OddPage -->
-<h2><span class="secno">5. </span>Formal Semantics of the PROV Ontology</h2>
- <p>The PROV ontology uses OWL2 as the ontology language, hence it supports a set of entailments based on the standard RDF semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>] and OWL2 semantics ([<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-DIRECT-SEMANTICS">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>]). In this section, we describe these set of semantics as applied to the PROV ontology along with a set of constraints introduced in the PROV-DM [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] that are provenance-specific. It is intended that provenance applications can leverage this normative description of the formal semantics of PROV ontology to support:</p>
- <ul>
- <li><b>Automated consistency checking </b>of provenance assertions (in RDF): Any RDF graph generated to represent provenance information using the PROV ontology as schema can be automatically checked for consistency using reasoning tool, such as FaCT++, Pellet, and Racer among others.</li>
- <li><b>Inferencing</b>: Make implicit knowledge explicit from RDF-encoded provenance datasets using valid entailment rules</li>
- </ul>
-
+ </p><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 [<cite><a href="#bib-PROV-BestPractices" rel="biblioentry" class="bibref">PROV-BestPractices</a></cite>] document describes in detail the approach used to model provenance information in two domain-specific examples by specializing the PROV Ontology.<p></p>
+ </div>
+ <div class="section" id="formal-semantics-of-the-prov-ontology">
+ <!--OddPage--><h2><span class="secno">5. </span>Formal Semantics of the PROV Ontology</h2>
+ <p>The PROV ontology uses OWL2 as the ontology language, hence it supports a set of entailments based on the standard RDF semantics [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>] and OWL2 semantics ([<cite><a href="#bib-OWL2-DIRECT-SEMANTICS" rel="biblioentry" class="bibref">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a href="#bib-OWL2-RDF-BASED-SEMANTICS" rel="biblioentry" class="bibref">OWL2-RDF-BASED-SEMANTICS</a></cite>]). In this section, we describe these set of semantics as applied to the PROV ontology along with a set of constraints introduced in the PROV-DM [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] that are provenance-specific. It is intended that provenance applications can leverage this normative description of the formal semantics of PROV ontology to support:</p>
+ <ul>
+ <li><b>Automated consistency checking </b>of provenance assertions (in RDF): Any RDF graph generated to represent provenance information using the PROV ontology as schema can be automatically checked for consistency using reasoning tool, such as FaCT++, Pellet, and Racer among others.</li>
+ <li><b>Inferencing</b>: Make implicit knowledge explicit from RDF-encoded provenance datasets using valid entailment rules</li>
+ </ul>
+
- <div id="rdf-semantics-for-prov-ontology" class="section">
- <h3><span class="secno">5.1 </span>RDF Semantics for PROV Ontology</h3>
- <p> We briefly summarize the essential features of the RDF Semantics and refer to the RDF semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>] for the normative specification. The RDF Semantics uses model theory, with a notion of interpretation I defined over RDF (rdf-interpretation) or RDFS (rdfs-interpretation) vocabulary, for specifying the formal semantics of a RDF or RDFS graph [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>]. The rdf-interpretation is an interpretation that satisfies a set of constraints called "<i>RDF semantic conditions</i>" and a set of "<i>RDF axiomatic triples</i>" (see Section 3.1 of RDF Semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>]). The rdfs-interpretation is defined over the additional terms in the RDFS vocabulary, including <i>rdfs:domain</i>, <i>rdfs:range</i>, <i>rdfs:Class</i>, <i>rdfs:subClassOf</i>, and <i>rdfs:subPropertyOf</i>. An rdfs-interpretation satisfies a set of constraints called "<i>RDFS semantic conditions</i>" and "<i>RDFS axiomatic triples</i>" (see Section 4.1 of RDFS Semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>]).
- </p>
- <p>The rdfs-interpretation supports the following set of the entailment rules that are applicable to the PROV ontology (we do not discuss the simple RDF entailments):
- </p>
- <h4 id="rule-1">Rule 1</h4>
- <p>If a PROV ontology class X is defined to be <i>domain</i> of a PROV property, then an individual asserted as "subject" of that property in a RDF triple is an instance of the class X. (from rdf2 Rule defined in RDF Semantics)
- </p>
- <h4 id="rule-2">Rule 2</h4>
- <p>Similar to Rule 1, if a PROV ontology class Y is defined to be <i>range</i> of a PROV object property, then an individual asserted as "object" of that property in a RDF triple is an instance of the class Y. (from rdf3 Rule defined in RDF Semantics)
- </p>
- <h4 id="rule-3">Rule 3</h4>
- <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.
- </p><div class="anexample">Given,
- <p></p>
- <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"/>
+ <div class="section" id="rdf-semantics-for-prov-ontology">
+ <h3><span class="secno">5.1 </span>RDF Semantics for PROV Ontology</h3>
+ <p> We briefly summarize the essential features of the RDF Semantics and refer to the RDF semantics [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>] for the normative specification. The RDF Semantics uses model theory, with a notion of interpretation I defined over RDF (rdf-interpretation) or RDFS (rdfs-interpretation) vocabulary, for specifying the formal semantics of a RDF or RDFS graph [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>]. The rdf-interpretation is an interpretation that satisfies a set of constraints called "<i>RDF semantic conditions</i>" and a set of "<i>RDF axiomatic triples</i>" (see Section 3.1 of RDF Semantics [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>]). The rdfs-interpretation is defined over the additional terms in the RDFS vocabulary, including <i>rdfs:domain</i>, <i>rdfs:range</i>, <i>rdfs:Class</i>, <i>rdfs:subClassOf</i>, and <i>rdfs:subPropertyOf</i>. An rdfs-interpretation satisfies a set of constraints called "<i>RDFS semantic conditions</i>" and "<i>RDFS axiomatic triples</i>" (see Section 4.1 of RDFS Semantics [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>]).
+ </p>
+ <p>The rdfs-interpretation supports the following set of the entailment rules that are applicable to the PROV ontology (we do not discuss the simple RDF entailments):
+ </p>
+ <h4 id="rule-1">Rule 1</h4>
+ <p>If a PROV ontology class X is defined to be <i>domain</i> of a PROV property, then an individual asserted as "subject" of that property in a RDF triple is an instance of the class X. (from rdf2 Rule defined in RDF Semantics)
+ </p>
+ <h4 id="rule-2">Rule 2</h4>
+ <p>Similar to Rule 1, if a PROV ontology class Y is defined to be <i>range</i> of a PROV object property, then an individual asserted as "object" of that property in a RDF triple is an instance of the class Y. (from rdf3 Rule defined in RDF Semantics)
+ </p>
+ <h4 id="rule-3">Rule 3</h4>
+ <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.
+ </p><div class="anexample">Given,
+ <p></p>
+ <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.example.com/crime#Journalist">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/Agent"/>
+ </div>
+
+ <p>and</p>
+ <div class="exampleOuter">
+ <pre class="example"><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/ns/prov-o/Agent">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/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 the following</p>
- <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"/>
+ </div>
+ <p>we can infer the following</p>
+ <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>
- <p>and</p>
- <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/Entity"/>
+ </div>
+ <p>and</p>
+ <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/Entity"/>
</rdf:Description></pre>
- </div>
- </div>
- </div>
+ </div>
+ </div>
+ </div>
- <div id="owl2-semantics-for-prov-ontology" class="section">
- <h3><span class="secno">5.2 </span>OWL2 Semantics for PROV Ontology</h3>
- <p>In addition to RDF Semantics, the OWL2 semantics as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-DIRECT-SEMANTICS">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>] are also applicable to PROV ontology. We consider the OWL2 RDF-Based Semantics (since it is a semantics superset of OWL2 Direct Semantics) and specifically the extension of the D-interpretation, which satisfies the constraints for rdf-interpretation, rdfs-interpretation (as defined in previous section), graphs with blank nodes, and interpretation defined for RDF datatypes (see Section 5.1 in RDF Semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>]). The OWL2 RDF-based semantics introduces the notion of "facets" to constrain datatypes, both the rdf:XMLLiteral defined in the RDF Semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-MT">RDF-MT</a></cite>] and datatypes defined in the OWL2 Structural Specifications [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-SYNTAX">OWL2-SYNTAX</a></cite>]. The OWL2 RDF-based interpretation, also called <b>D-interpretation with facets</b> is a D-interpretation that also satisfies the OWL2 RDF-based semantics called "semantic constraints" (see Section 5 in OWL2 RDF-Based Semantics [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-RDF-BASED-SEMANTICS">OWL2-RDF-BASED-SEMANTICS</a></cite>]).
- </p>
- </div>
- <div id="entailments-supported-by-the-provenance-model" class="section">
- <h3><span class="secno">5.3 </span>Provenance-specific Entailments Supported by PROV Ontology</h3>
- <p>The PROV-DM [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] 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) [<cite><a class="bibref" rel="biblioentry" href="#bib-RIF-OVERVIEW">RIF-OVERVIEW</a></cite>]. 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>
-
- </div>
- </div>
-
+ <div class="section" id="owl2-semantics-for-prov-ontology">
+ <h3><span class="secno">5.2 </span>OWL2 Semantics for PROV Ontology</h3>
+ <p>In addition to RDF Semantics, the OWL2 semantics as described in [<cite><a href="#bib-OWL2-DIRECT-SEMANTICS" rel="biblioentry" class="bibref">OWL2-DIRECT-SEMANTICS</a></cite>], [<cite><a href="#bib-OWL2-RDF-BASED-SEMANTICS" rel="biblioentry" class="bibref">OWL2-RDF-BASED-SEMANTICS</a></cite>] are also applicable to PROV ontology. We consider the OWL2 RDF-Based Semantics (since it is a semantics superset of OWL2 Direct Semantics) and specifically the extension of the D-interpretation, which satisfies the constraints for rdf-interpretation, rdfs-interpretation (as defined in previous section), graphs with blank nodes, and interpretation defined for RDF datatypes (see Section 5.1 in RDF Semantics [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>]). The OWL2 RDF-based semantics introduces the notion of "facets" to constrain datatypes, both the rdf:XMLLiteral defined in the RDF Semantics [<cite><a href="#bib-RDF-MT" rel="biblioentry" class="bibref">RDF-MT</a></cite>] and datatypes defined in the OWL2 Structural Specifications [<cite><a href="#bib-OWL2-SYNTAX" rel="biblioentry" class="bibref">OWL2-SYNTAX</a></cite>]. The OWL2 RDF-based interpretation, also called <b>D-interpretation with facets</b> is a D-interpretation that also satisfies the OWL2 RDF-based semantics called "semantic constraints" (see Section 5 in OWL2 RDF-Based Semantics [<cite><a href="#bib-OWL2-RDF-BASED-SEMANTICS" rel="biblioentry" class="bibref">OWL2-RDF-BASED-SEMANTICS</a></cite>]).
+ </p>
+ </div>
+ <div class="section" id="entailments-supported-by-the-provenance-model">
+ <h3><span class="secno">5.3 </span>Provenance-specific Entailments Supported by PROV Ontology</h3>
+ <p>The PROV-DM [<cite><a href="#bib-PROV-DM" rel="biblioentry" class="bibref">PROV-DM</a></cite>] 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) [<cite><a href="#bib-RIF-OVERVIEW" rel="biblioentry" class="bibref">RIF-OVERVIEW</a></cite>]. 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>
+
+ </div>
+ </div>
-<!-- <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 Activity that generated the Entity.</p>
+<!-- <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 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 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 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 Activity instance by relation Used.
- </p>
- <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>
+ <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 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 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 Activity instance by relation Used.
+ </p>
+ <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 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 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>
- -->
-
- <div class="appendix section" id="acknowledgements">
-
-<!-- OddPage -->
-<h2><span class="secno">A. </span>Acknowledgements</h2>
+ <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 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 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>
+-->
+ <div id="acknowledgements" class="appendix section">
+ <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
The Provenance Working Group Members.
</p>
@@ -1818,9 +1792,7 @@
-<div id="references" class="appendix section">
-<!-- OddPage -->
-<h2><span class="secno">B. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL-TIME">[OWL-TIME]</dt><dd>Feng Pan; Jerry R. Hobbs. <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927"><cite>Time Ontology in OWL.</cite></a> 27 September 2006. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927">http://www.w3.org/TR/2006/WD-owl-time-20060927</a>
+<div class="appendix section" id="references"><!--OddPage--><h2><span class="secno">B. </span>References</h2><div class="section" id="normative-references"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-OWL-TIME">[OWL-TIME]</dt><dd>Feng Pan; Jerry R. Hobbs. <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927"><cite>Time Ontology in OWL.</cite></a> 27 September 2006. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2006/WD-owl-time-20060927">http://www.w3.org/TR/2006/WD-owl-time-20060927</a>
</dd><dt id="bib-OWL2-DIRECT-SEMANTICS">[OWL2-DIRECT-SEMANTICS]</dt><dd>Boris Motik; Peter F. Patel-Schneider; Bernardo Cuenca Grau. <a href="http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/"><cite>OWL 2 Web Ontology Language:Direct Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/">http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/</a>
</dd><dt id="bib-OWL2-PRIMER">[OWL2-PRIMER]</dt><dd>Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-primer-20091027/">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a>
</dd><dt id="bib-OWL2-RDF-BASED-SEMANTICS">[OWL2-RDF-BASED-SEMANTICS]</dt><dd>Michael Schneider. <a href="http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/"><cite>OWL 2 Web Ontology Language:RDF-Based Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/">http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/</a>
@@ -1831,7 +1803,7 @@
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
</dd><dt id="bib-RIF-OVERVIEW">[RIF-OVERVIEW]</dt><dd>Michael Kifer; Harold Boley. <a href="http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/"><cite>RIF Overview.</cite></a> 22 June 2010. W3C Working Group Note. URL: <a href="http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/">http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/</a>
</dd><dt id="bib-XMLSCHEMA-2">[XMLSCHEMA-2]</dt><dd>Paul V. Biron; Ashok Malhotra. <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML Schema Part 2: Datatypes Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>
-</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-BestPractices">[PROV-BestPractices]</dt><dd>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>
+</dd></dl></div><div class="section" id="informative-references"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-BestPractices">[PROV-BestPractices]</dt><dd>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>
</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau, Paolo Missier<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>
</dd><dt id="bib-PROV-Ontology-Namespace">[PROV-Ontology-Namespace]</dt><dd>TBD<a href="http://www.w3.org/ns/prov-o/"><cite>PROV Ontology Namespace</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/ns/prov-o/">http://www.w3.org/ns/prov-o/</a>
</dd><dt id="bib-PROV-PAQ">[PROV-PAQ]</dt><dd>Graham Klyne and Paul Groth <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/prov-aq.html">http://dvcs.w3.org/hg/prov/tip/paq/prov-aq.html</a>