--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/ProvenanceFormalModel.xhtml Wed Oct 12 14:25:03 2011 +0100
@@ -0,0 +1,1822 @@
+<?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">
+<head>
+ <title>PROV Ontology Model</title>
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+
+<!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+
+
+
+ <style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+code {
+ color: #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+ border-top: 1px solid #90b8de;
+ border-bottom: 1px solid #90b8de;
+ padding: 1em;
+ line-height: 120%;
+}
+
+pre.idl::before {
+ content: "WebIDL";
+ display: block;
+ width: 150px;
+ background: #90b8de;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+.idlType {
+ color: #ff4500;
+ font-weight: bold;
+ text-decoration: none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID {
+ font-weight: bold;
+ color: #005a9c;
+}
+
+.idlSuperclass {
+ font-style: italic;
+ color: #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+ color: #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+ color: #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+ color: #005a9c;
+}
+.idlMethName {
+ color: #ff4500;
+}
+.idlMethName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+ color: #005a9c;
+}
+.idlParamName {
+ font-style: italic;
+}
+
+.extAttr {
+ color: #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+ color: #005a9c;
+}
+.idlConstName {
+ color: #ff4500;
+}
+.idlConstName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+ font-weight: bold;
+ color: #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+ color: #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+ color: #c00;
+ font-weight: normal;
+}
+
+.excName a {
+ font-family: monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+ border-bottom: 1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+ width: 45px;
+ text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
+
+.idlImplements a {
+ font-weight: bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+ margin-left: 2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+ font-weight: normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+ font-weight: bold;
+ color: #000;
+ font-family: monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+ background: #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+ color: #005a9c;
+ background: transparent;
+ font-family: inherit;
+ font-weight: normal;
+ font-style: italic;
+}
+
+.methods dt code {
+ background: #d9e6f8;
+}
+
+.constants dt code {
+ background: #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+ margin-bottom: 1em;
+}
+
+table.parameters, table.exceptions {
+ border-spacing: 0;
+ border-collapse: collapse;
+ margin: 0.5em 0;
+ width: 100%;
+}
+table.parameters { border-bottom: 1px solid #90b8de; }
+table.exceptions { border-bottom: 1px solid #deb890; }
+
+.parameters th, .exceptions th {
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+ font-family: initial;
+ font-weight: normal;
+ text-shadow: #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+ vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+ border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+ width: 100px;
+}
+
+.parameters td.prmType {
+ width: 120px;
+}
+
+table.exceptions table {
+ border-spacing: 0;
+ border-collapse: collapse;
+ width: 100%;
+}
+
+/* --- TOC --- */
+.toc a {
+ text-decoration: none;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+ border-top: 1px solid #ff4500;
+ border-bottom: 1px solid #ff4500;
+ padding: 1em;
+ margin-top: 1em;
+}
+
+pre.example::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ background: #ff4500;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.issue::before {
+ content: "Issue";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.note {
+ margin: 1em 0em 0em;
+ padding: 1em;
+ border: 2px solid #cff6d9;
+ background: #e2fff0;
+}
+
+.note::before {
+ content: "Note";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #cff6d9;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+ border: solid #bebebe 1px;
+ margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+ margin: 1.5em 0.5em 1em 1em;
+ font-weight: bold;
+ font-style: italic;
+}
+
+span.practicelab { background: #dfffff; }
+
+span.practicelab {
+ position: relative;
+ padding: 0 0.5em;
+ top: -1.5em;
+}
+
+p.practicedesc {
+ margin: 1.5em 0.5em 1em 1em;
+}
+
+@media screen {
+ p.practicedesc {
+ position: relative;
+ top: -2em;
+ padding: 0;
+ margin: 1.5em 0.5em -1em 1em;
+ }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+ background-color: white;
+ color: black;
+ font-style: normal;
+ font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
+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_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 */
+pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
+</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" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a></p><h1 class="title" id="title">PROV Ontology Model</h1><h2 id="w3c-working-draft-12-october-2011">W3C Working Draft 12 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111012/">http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111012/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/PROV-FormalModel/">http://www.w3.org/TR/PROV-FormalModel/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111007/">http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111007/</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><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester, UK</dd>
+<dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh, UK</dd>
+<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>
+</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. W3C <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>
+<p> The PROV Ontology Model (also PROV ontology) 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 is specialized to create domain-specific provenance ontologies that model the provenance information specific to different applications. The PROV ontology supports a set of entailments based on OWL2 formal semantics and provenance specific inference rules. The PROV ontology is available for download as a separate OWL2 document.</p>
+ </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 W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
+<p>TODO: <em class="rfc2119" title="must">must</em> include at least one customized paragraph. This section <em class="rfc2119" title="should">should</em> include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs <em class="rfc2119" title="should">should</em> explain the publication context, including rationale and relationships to other work. See examples and more discussion in the Manual of Style.<a href="http://www.w3.org/2001/06/manual/#Status">TODO</a></p>
+<p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a W3C 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 W3C 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 W3C Patent Policy</a>. W3C maintains a <a href="" 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 W3C 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="#prov-ontology" class="tocxref"><span class="secno">1. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">1.1 </span>OWL2 Syntax Used in this Document</a></li></ul></li><li class="tocline"><a href="#prov-ontology--classes-and-properties" class="tocxref"><span class="secno">2. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">2.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">2.1.1 </span>Entity</a></li><li class="tocline"><a href="#processexecution" class="tocxref"><span class="secno">2.1.2 </span>ProcessExecution</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">2.1.3 </span>Agent</a></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">2.1.4 </span>Recipe</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.1.5 </span>Time</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">2.1.6 </span>Revision</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">2.1.7 </span>ProvenanceContainer</a></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">2.1.8 </span>Location</a></li><li class="tocline"><a href="#entityinrole" class="tocxref"><span class="secno">2.1.9 </span>EntityInRole</a></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">2.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">2.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">2.2.2 </span>wasDerivedFrom</a></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">2.2.3 </span>Used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">2.2.4 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">2.2.5 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">2.2.6 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">2.2.7 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">2.2.8 </span>wasInformedBy</a></li><li class="tocline"><a href="#wasscheduledafter" class="tocxref"><span class="secno">2.2.9 </span>wasScheduledAfter</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">2.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">2.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">2.5 </span>Overview of the ontology</a></li></ul></li><li class="tocline"><a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications" class="tocxref"><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</a><ul class="toc"><li class="tocline"><a href="#modeling-the-crime-file-scenario" class="tocxref"><span class="secno">3.1 </span>Modeling the Crime File Scenario</a><ul class="toc"><li class="tocline"><a href="#specialization-of-prov-ontology-classes" class="tocxref"><span class="secno">3.1.1 </span>Specialization of PROV Ontology Classes</a><ul class="toc"><li class="tocline"><a href="#cf-journalist" class="tocxref"><span class="secno">3.1.1.1 </span>cf:Journalist</a></li><li class="tocline"><a href="#cf-crimefile" class="tocxref"><span class="secno">3.1.1.2 </span>cf:CrimeFile</a></li><li class="tocline"><a href="#cf-filecreation--cf-fileediting--cf-fileappending--cf-emailprocessexecution--cf-spellchecking" class="tocxref"><span class="secno">3.1.1.3 </span>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking</a></li></ul></li><li class="tocline"><a href="#specialization-of-prov-ontology-properties" class="tocxref"><span class="secno">3.1.2 </span>Specialization of PROV Ontology Properties</a><ul class="toc"><li class="tocline"><a href="#cf-hadfilepath" class="tocxref"><span class="secno">3.1.2.1 </span>cf:hadFilePath</a></li></ul></li></ul></li><li class="tocline"><a href="#modeling-an-example-scientific-workflow-scenario" class="tocxref"><span class="secno">3.2 </span>Modeling an Example Scientific Workflow Scenario</a><ul class="toc"><li class="tocline"><a href="#workflow-extensions-to-prov-classes" class="tocxref"><span class="secno">3.2.1 </span>Workflow extensions to PROV classes</a></li><li class="tocline"><a href="#workflow-extensions-to-prov-properties" class="tocxref"><span class="secno">3.2.2 </span>Workflow extensions to PROV properties</a></li><li class="tocline"><a href="#workflow-structure" class="tocxref"><span class="secno">3.2.3 </span>Workflow structure</a></li><li class="tocline"><a href="#example-workflow" class="tocxref"><span class="secno">3.2.4 </span>Example workflow</a></li><li class="tocline"><a href="#example-workflow-run" class="tocxref"><span class="secno">3.2.5 </span>Example workflow run</a></li></ul></li></ul></li><li class="tocline"><a href="#formal-semantics-of-the-prov-ontology" class="tocxref"><span class="secno">4. </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">4.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">4.2 </span>OWL2 Semantics for PROV Ontology</a></li><li class="tocline"><a href="#provenance-specific-entailments-supported-by-prov-ontology" class="tocxref"><span class="secno">4.3 </span>Provenance-specific Entailments Supported by PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#provenance-constraint-on-processexecution" class="tocxref"><span class="secno">4.3.1 </span>Provenance constraint on ProcessExecution</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby--generation-affects-attributes" class="tocxref"><span class="secno">4.3.2 </span>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby--generation-pe-ordering" class="tocxref"><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby--generation-unicity" class="tocxref"><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</a></li><li class="tocline"><a href="#provenance-constraint-on-used--use-attributes" class="tocxref"><span class="secno">4.3.5 </span>Provenance constraint on Used (use-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-used--use-pe-ordering" class="tocxref"><span class="secno">4.3.6 </span>Provenance constraint on Used (use-pe-ordering)</a></li></ul></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 class="section">
+ <a id="introduction"></a>
+ <h2 id="introduction-1">Introduction</h2>
+ <p>
+ PROV Ontology Model (also PROV ontology) 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 W3C OWL2 Web Ontology Language. This document specification describes the set of classes, properties, and restrictions that constitute the PROV ontology, which have been introduced in the PROV Data Model [<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 applications 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 management in domain-specific Web-based applications.
+ </p>
+ <p>
+ The PROV ontology classes and properties are defined such that they can be specialized for modeling application-specific provenance information in a variety of domains. Thus, the PROV ontology is expected to serve as a <i>reference model</i> for domain-specific provenance ontology and thereby facilitate consistent provenance interchange. This document uses an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] to demonstrate the specialization of PROV ontology.
+ </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 class="section">
+ <h3 id="guide-to-this-document">Guide to this Document</h3>
+ <p> This document is intended for provide an understanding of
+ the PROV ontology and how it can be used by various applications
+ to represent their provenance information. The intended audience
+ of this document include users who are new to provenance
+ modeling as well as experienced users who would like their provenance model compatible with the PROV ontology to facilitate standardization.This document assumes a basic understanding of the W3C OWL2 specification , including modeling of classes, properties, and restrictions in an OWL2 ontology. Readers are referred to the OWL2 documentations, starting with the [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>], for the OWL2 specification.
+ </p>
+ <p><a href="#prov-ontology--owl-encoding-of-prov-data-model">Section 2</a> describes the mapping of the PROV Data Model [<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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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>
+ </div>
+
+ </div>
+<!-- Introduction -->
+
+
+
+
+ <div id="prov-ontology" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">1. </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 is not designed to be used directly in a domain application and its Classes and Properties represent "higher-level" or abstract level concepts that can be specialized further for representing domain-specific provenance information. We briefly introduce some of the OWL2 modeling terms that will be used to describe the PROV ontology. An OWL2 <i>instance</i> is an individual object in a domain of discourse, for example a person named Alice or a car, and a set of individuals sharing a set of common characteristics is called a <i>class</i>. Person and Car are examples of classes representing the set of individual persons and cars respectively. The OWL2 object properties are used to link individuals, classes, or create a property hierarchy. For example, the object property "hasOwner" can be used to link car with person. The OWL2 datatype properties are used to link individuals or classes to data values, including XML Schema datatypes [<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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> describing the creation of crime statistics file stored on a shared file system and edited by journalists Alice, Bob, Charles, David, and Edith. This scenario is used as a running example in this document to describe the PROV ontology classes and properties, the specialization mechanism and entailments supported by the PROV ontology.
+ </p>
+
+
+
+ <div id="owl2-syntax-used-in-this-document" class="section">
+ <h3><span class="secno">1.1 </span>OWL2 Syntax Used in this Document</h3>
+ <p>We use 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. The OWL2 document for the PROV ontology is
+ available at [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>], which is also the
+ namespace for the PROV ontology and is denoted by "PROV" and
+ the prefix "prov".
+ </p>
+ <div class="issue">The namespace URI for the ontology has not
+ yet been decided, and the examples in this document might
+ therefore not be using consistent namespaces. This is <a href="http://www.w3.org/2011/prov/track/issues/90">ISSUE-90</a></div>
+ </div>
+ </div>
+<!-- PROV Ontology -->
+
+
+
+ <div id="prov-ontology--classes-and-properties" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">2. </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 term in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>.
+ </p>
+ <div id="classes" class="section">
+ <h3><span class="secno">2.1 </span>Classes</h3>
+ <p>The PROV ontology consists of classes that can be organized in a taxonomic structure.
+ </p>
+ <img src="diagram-history/khalidDiagrams/Ontology_hierarchy.png" style="width: 50%; min-width: 25em; max-width: 37em" alt="Class hierarchy of the PROV OWL ontology" />
+ <br />
+ <p><i>Note: CamelBack notation is used for class names</i></p>
+ <div class="issue">
+ The class <code>prov:Role</code> has been
+ renamed to <code>prov:EntityInRole</code>. (A new
+ <code>prov:Role</code> might appear in the rdfs:range of
+ <code>prov:assuming</code>
+ </div>
+ <div id="entity" class="section">
+ <h4><span class="secno">2.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><b>Example</b></div>
+ <p> Example of instances of class Entity from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are files with identifiers <i>e1</i> and <i>e2</i>. The RDF/XML syntax for asserting that e1 is an instance of Entity is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+</rdf:Description></pre>
+ </div>
+ <p>Attributes that are characterising the entity (as defined
+ in PROV-DM) are stated using RDF properties of the asserted
+ entity. Such properties <em class="rfc2119" title="should">should</em> be in a declared namespace,
+ and <em class="rfc2119" title="may">may</em> be described by an application-specific vocabulary.
+ Specialisation by subclassing or <code>rdf:type</code> is
+ equivalent to specifying the reserved attribute <code>type</code>
+ in PROV-DM.
+ </p>
+ <div><b>Example</b></div>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
+ <cf:hasLocation rdf:resource="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1"/>
+ <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There was a lot of crime in London last month.</cf:hasFileContent>
+</rdf:Description></pre>
+ </div>
+
+ <div class="issue">Definition of Entity in PROV-DM is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
+ </div>
+<!-- Classes -->
+
+
+ <div id="processexecution" class="section">
+ <h4><span class="secno">2.1.2 </span>ProcessExecution</h4>
+ <div><b>Class Description</b></div>
+ <p>ProcessExecution 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:ProcessExecution rdfs:subClassOf owl:Thing.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class ProcessExecution from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are file creation (<i>pe0</i>) and file editing (<i>pe2</i>) . The RDF/XML syntax for asserting that pe2 is an instance of ProcessExecution is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
+</rdf:Description></pre>
+ </div>
+ <div class="note"> pe2 is an instance of class EmailProcessExecution, which is defined to be "sub-class" of class ProcessExecution in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of ProcessExecution.
+ </div>
+ </div>
+
+
+
+ <div id="agent" class="section">
+ <h4><span class="secno">2.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><b>Example</b></div>
+ <p> Example of instances of class Agent from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>Alice</i> and <i>Edith</i>. The RDF/XML syntax for asserting that Alice is an instance of Agent is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Alice">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
+</rdf:Description></pre>
+ </div>
+ <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="recipe" class="section">
+ <h4><span class="secno">2.1.4 </span>Recipe</h4>
+ <div><b>Class Description</b></div>
+ <p>Recipe represents a process specification. The definition of process specifications is outside the scope of PROV:DM. Therefore, this class acts as a place holder in the ontology that can be extended and specialized by users.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Recipe rdfs:subClassOf owl:Thing.</pre>
+ <div><b>Example</b></div>
+ <p> Recipe examples include backing recipes, programs and workflows.
+ </p></div>
+
+
+
+ <div id="time" class="section">
+ <h4><span class="secno">2.1.5 </span>Time</h4>
+ <div><b>Class Description</b></div>
+ <p>Time represents temporal information about entities in the Provenance model.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Time rdfs:subClassOf owl:Thing.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class Time from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of Time is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#t+1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Time"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+
+
+
+ <div id="revision" class="section">
+ <h4><span class="secno">2.1.6 </span>Revision</h4>
+ <div><b>Class Description</b></div>
+ <p>Revision is defined as a modified version of a Entity.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:Revision rdfs:subClassOf owl:Thing.</pre>
+ <div class="issue">Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
+ </div>
+
+
+
+ <div id="provenancecontainer" class="section">
+ <h4><span class="secno">2.1.7 </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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Account">Account</a>.</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:ProvenanceContainer rdfs:subClassOf owl:Thing.</pre>
+ <p>Examples of instance of class ProvenanceContainer includes a file describing the manufacturing details of a car, such as its batch number, manufacturer, date of manufacture, place of manufacture etc. </p>
+ <div class="note"> According to the definitions of ProvenanceContainer and Account, both contain a set of provenance assertions and have an identifier. Hence, ProvenanceContainer class can also be used to create instances of accounts.
+ </div>
+ <div class="issue">Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
+ <div class="issue">Scope and Identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
+ </div>
+
+
+
+ <div id="location" class="section">
+ <h4><span class="secno">2.1.8 </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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is the location of the crime file in the shared directory <i>/share</i> with file path <i>/shared/crime.txt</i>. The RDF/XML syntax for asserting that the location of the crime file is the shared directory.
+ </p><div class="exampleOuter">
+ <pre class="example"><cf:hasLocation>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
+ <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
+ </rdf:Description>
+</cf:hasLocation></pre>
+ </div>
+ <div class="note"> Need to clarify whether "geographic" includes "geospatial"?</div>
+ </div>
+
+
+
+ <div id="entityinrole" class="section">
+ <h4><span class="secno">2.1.9 </span>EntityInRole</h4>
+ <div><b>Class Description</b></div>
+ <p>EntityInRole is defined to be a "realizable entity" (cite?) "assumed by a Entity or an agent." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
+ <div><b>OWL syntax</b></div>
+ <pre>PROV:EntityInRole rdfs:subClassOf PROV:Entity.</pre>
+ <div><b>Example</b></div>
+ <p> Example of instances of class EntityInRole from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>author</i> role assumed by Bob and <i>file creator</i> role assumed by Alice. The RDF/XML syntax for asserting that Bob assumes the role of an author is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#AliceAsAuthor">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#EntityInRole"/>
+ <prov:assumedBy rdf:resource="http://www.w3.org/PROV/CrimeFile#Alice"/>
+ <prov:assumedRole rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#author"/>
+</rdf:Description></pre>
+ </div>
+ <div class="issue">prov:assumedBy and prov:assumedRole
+ (or equivalent) properties have not yet been defined
+ in this ontology. This is
+ <a href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a>
+ and
+ <a href="http://www.w3.org/2011/prov/track/issues/111">ISSUE-111</a>
+ </div>
+
+ <div class="issue">The PROV-DM defines the term <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a>, which is incorporated implicitly in definition of OWL sub-classes and sub-properties that specialize a parent class or property by defining additional qualifying constraints. Hence, <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a> is not modeled explicitly in PROV ontology.</div>
+ </div>
+ </div>
+
+
+ <div id="object-properties" class="section">
+ <h3><span class="secno">2.2 </span>Object Properties</h3>
+ <p>The Provenance Model consists of the following object properties. </p>
+ <p><i>Note: Names of properties starts with a verb in lower case followed by verb(s) starting with upper case </i></p>
+
+
+
+ <div id="wasgeneratedby" class="section">
+ <h4><span class="secno">2.2.1 </span>wasGeneratedBy</h4>
+ <p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
+ <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" alt="wasGeneratedBy links Entity to ProcessExecution" />
+ <div><b>Example</b></div>
+ <p> Example of wasGeneratedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
+ <prov:wasGeneratedBy>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe0">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileCreation"/>
+ </rdf:Description>
+ <prov:wasGeneratedBy>
+</rdf:Description> </pre>
+ </div>
+ </div>
+
+
+
+ <div id="wasderivedfrom" class="section">
+ <h4><span class="secno">2.2.2 </span>wasDerivedFrom</h4>
+ <p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" alt="wasDerivedFrom links Entity to Entity" />
+ <div><b>Example</b></div>
+ <p> Example of wasDerivedFrom property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e3">
+ <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
+</rdf:Description> </pre>
+ </div>
+ <div class="issue">Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
+ <div class="issue">Should we specifically mention derivation of agents? This is <a href="http://www.w3.org/2011/prov/track/issues/42">ISSUE-42</a>.</div>
+ </div>
+
+
+
+ <div id="used" class="section">
+ <h4><span class="secno">2.2.3 </span>Used</h4>
+ <p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" alt="prov:used links ProcessExecution to Entity" />
+ <div class="issue">Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
+ <div><b>Example</b></div>
+ <p> Example of Used property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 Used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
+ <prov:used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
+ </rdf:Description> </pre>
+ </div>
+ </div>
+
+
+
+
+ <div id="hadparticipant" class="section">
+ <h4><span class="secno">2.2.4 </span>hadParticipant</h4>
+ <p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
+ </p><p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <div class="pending">Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
+ </div>
+
+
+
+ <div id="wascomplementof" class="section">
+ <h4><span class="secno">2.2.5 </span>wasComplementOf</h4>
+ <p>wasComplementOf links two instances of Entity, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." <i>(from the Provenance Conceptual Model)</i></p>
+ </div>
+
+
+
+ <div id="wascontrolledby" class="section">
+ <h4><span class="secno">2.2.6 </span>wasControlledBy</h4>
+ <p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" alt="wasControlledBy links ProcessExecution to Agent" />
+ <div><b>Example</b></div>
+ <p> Example of wasControlledBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
+ </p><div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
+ <prov:wasControlledBy>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Bob">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
+ </rdf:Description>
+ </prov:wasControlledBy>
+</rdf:Description> </pre>
+ </div>
+ <div class="issue">Mutual ivpOf each other should be agreed. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
+ <div class="issue">Do we need a sameAsEntity relation. This is <a href="http://www.w3.org/2011/prov/track/issues/35">ISSUE-35</a></div>
+ <div class="issue">Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
+ <div class="issue"> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
+ </div>
+
+
+
+ <div id="hadrecipe" class="section">
+ <h4><span class="secno">2.2.7 </span>hadRecipe</h4>
+ <p>The ProcessExecution activity performed can be described as
+ having the given recipe resource. It is out of the scope for PROV to
+ define the structure or meaning of the recipe. The recipe
+ might or might not have been followed exactly by the Process
+ Execution.
+ </p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" alt="prov:hadRecipe links ProcessExecution to Recipe." />
+ </div>
+
+
+
+ <div id="wasinformedby" class="section">
+ <h4><span class="secno">2.2.8 </span>wasInformedBy</h4>
+ <p> This object property links two process executions. It is used to express the fact that a given process execution used an entity that was generated by another process execution.
+ </p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" alt="prov:wasInformedBy links ProcessExecution to ProcessExecution" />
+ </div>
+
+
+
+ <div id="wasscheduledafter" class="section">
+ <h4><span class="secno">2.2.9 </span>wasScheduledAfter</h4>
+ <p>
+ This object property links two instances of ProcessExecution to specify the order in which they took place. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
+ </p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" alt="prov:wasScheduledAfter links ProcessExecution to ProcessExecution" />
+ </div>
+
+ </div>
+
+ <div id="characteristics-of-object-properties" class="section">
+ <h3><span class="secno">2.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
+
+ </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
+
+ </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 them may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>isUsedBY</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>isUsedBY</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.
+ </div>
+ </div>
+
+ <div id="annotation-properties" class="section">
+ <h3><span class="secno">2.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>
+
+ <div id="overview-of-the-ontology" class="section">
+ <h3><span class="secno">2.5 </span>Overview of the ontology</h3>
+ <p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" alt="Object properties among all classes in the PROV OWL ontology" />
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.pdf"><img src="http://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.png" alt="Object properties among all classes in the PROV OWL ontology" /></a>
+ </div>
+ </div>
+
+
+
+ <div id="specializing-provenance-ontology-for-domain-specific-provenance-applications" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
+ <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:</p>
+ <ul>
+ <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
+ <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
+ </ul>
+ <p>To illustrate the specialization mechanism, the PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
+
+
+
+ <div id="modeling-the-crime-file-scenario" class="section">
+ <h3><span class="secno">3.1 </span>Modeling the Crime File Scenario</h3>
+ <p>The example scenario can be encoded as a <a href="http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href="">Figure X</a>:</p>
+ <div class="issue">insert figure X</div>
+ <p><a href="">Figure X</a> represents the ontology schema that extends the PROV ontology to model the provenance details of the crime file scenario. For example,</p>
+ <ul>
+ <li>specialization of <a href="#agent">Agent</a> to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
+ <li><a href="#processexecution">ProcessExecution</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
+ <li>specialization of <a href="#entity">Entity</a> to define a class called CrimeFile, which has individuals such as e1, e2, and e3 </li>
+ </ul>
+ <p>Example given below describes the provenance of <a href="#entity">Entity</a> e2 using RDF/XML syntax</p>
+ <div class="exampleOuter">
+ <pre class="example"><?xml version="1.0"?>
+<rdf:RDF
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
+ xmlns:prov="http://www.w3.org/PROV/ProvenanceOntology.owl#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:cf="http://www.w3.org/PROV/CrimeFileOntology.owl#">
+
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
+ <prov:wasGeneratedBy>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileAppending"/>
+ <prov:wasControlledBy>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Bob">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
+ </rdf:Description>
+ </prov:wasControlledBy>
+ </rdf:Description>
+ </prov:wasGeneratedBy>
+ <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/CrimeFile#e1"/>
+ <cf:hasLocation>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
+ <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
+ </rdf:Description>
+ </cf:hasLocation>
+ <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There was a lot of crime in London last month.</cf:hasFileContent>
+ </rdf:Description>
+ <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
+ <prov:used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
+ </rdf:Description>
+ </rdf:RDF></pre>
+ </div>
+ <div id="specialization-of-prov-ontology-classes" class="section">
+ <h4><span class="secno">3.1.1 </span>Specialization of PROV Ontology Classes</h4>
+ <p> The following new classes were created in the CrimeFile Ontology by extending the PROV ontology classes:</p>
+ <div id="cf-journalist" class="section">
+ <h5><span class="secno">3.1.1.1 </span>cf:Journalist</h5>
+ <p>The cf:Journalist is a specialization of the PROV ontology <a href="#agent">Agent</a> class and models all individuals that participate in creating, editing, and sharing the crime file.The following RDF/XML code illustrates how cf:Journalist is asserted to be a specialization of <a href="#agent">PROV:Agent.</a></p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+ <div id="cf-crimefile" class="section">
+ <h5><span class="secno">3.1.1.2 </span>cf:CrimeFile</h5>
+ <p> The cf:CrimeFile is a specialization of the PROV ontology <a href="#entity">Entity</a> class and it models the the file describing the crime statistics in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>, including the multiple versions of the file. The following RDF/XML code illustrates how cf:Journalist is asserted to be a specialization of <a href="#entity">PROV:Entity</a>.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+ <div id="cf-filecreation--cf-fileediting--cf-fileappending--cf-emailprocessexecution--cf-spellchecking" class="section">
+ <h5><span class="secno">3.1.1.3 </span>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking</h5>
+ <p>The classes cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking are specialization of the PROV ontology <a href="processexecution">ProcessExecution</a> and model the different activities in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>. The following RDF/XML code illustrates the specialization of the <a href="processexecution">PROV:ProcessExecution</a> to define class cf:FileCreation (other classes can be similarly defined by using the subClassOf property).</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#FileCreation">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
+</rdf:Description></pre>
+ </div>
+ <p>The following diagram illustrates the above specialization: </p>
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)." />
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf"><img src="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)." /></a>
+ <br />
+ <em>Example extension of PROV ontology in order to describe the crime file scenario</em>
+ </div>
+ </div>
+ <div id="specialization-of-prov-ontology-properties" class="section">
+ <h4><span class="secno">3.1.2 </span>Specialization of PROV Ontology Properties</h4>
+ <p> The following new object property was created in the CrimeFile Ontology by extending the PROV ontology object property:</p>
+ <div id="cf-hadfilepath" class="section">
+ <h5><span class="secno">3.1.2.1 </span>cf:hadFilePath</h5>
+ <p>The property cf:hadFilePath is a specialization of the PROV ontology hadLocation object property and links the class CrimeFile to the FileDirectory class. The following RDF/XML code illustrates the use of rdfs:subPropertyOf to create hadFilePath property.</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#hadFilePath">
+ <rdfs:subPropertyOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#hadLocation"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+ <p>The following diagram illustrates the above specialization: </p>
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.pdf">
+ <img src="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.png" alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:EmailProcessExecution, extSpellChecking extend prov:ProcessExecution; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location." />
+ </a>
+ <br />
+ <em>Example extension of PROV ontology in order to describe the crime file scenario</em>
+ </div>
+ </div>
+ <div id="modeling-an-example-scientific-workflow-scenario" class="section">
+ <h3><span class="secno">3.2 </span>Modeling an Example Scientific Workflow Scenario</h3>
+ <p>This section describes an example of extending the PROV
+ ontology to create a provenance ontology for scientific
+ workflows.</p>
+
+ <p>Scientific workflow systems allow the specification of a
+ pipeline of processes which are linked from outputs to inputs.
+ Such workflow definitions are typically created in a graphical
+ user interface or interactive web application, and can then be
+ <em>enacted</em> using particular inputs or parameters.
+ Scientists in fields like bioinformatics, chemistry and
+ physics use such workflows to perform repeated analysis by
+ connecting together disparate set of domain-specific tools and
+ services.
+ </p>
+
+ <p>
+ Capturing the provenance of executions in such a workflow
+ system will typically include details of each of the process
+ executions, such as its inputs and outputs, start and stop
+ time, and should ultimately be able to describe the complete
+ data lineage through the workflow for any returned output data.
+ </p>
+ <p>
+ This example is not attempting to be a complete or general
+ ontology for asserting workflow provenance, but highlights how
+ a particular application like a workflow system can express its
+ domain specific attributes based on the PROV ontology.
+ </p>
+ <p>
+ <img src="examples/ontology-extensions/workflow/workflowOntology.png" style="width: 60%; min-width: 20em; max-width: 40em" alt="New classes wf:WorkFlowEngine, wf:Process, wf:ValueAtPort, wf:FileValue, and wf:Value extend prov:Agent, prov:ProcessExecution, prov:EntityInRole. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubProcessExecutionOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom." />
+ <br />
+ <em>Example extension of PROV ontology in order to describe
+ workflow provenance</em>
+ </p>
+ <div id="workflow-extensions-to-prov-classes" class="section">
+ <h4><span class="secno">3.2.1 </span>Workflow extensions to PROV classes</h4>
+ <p>
+ In order to describe workflow executions following the
+ model above, the PROV ontology is extended with
+ workflow-specific subclasses described below:
+ </p>
+ <dl>
+ <dt>wf:Process</dt>
+ <dd>
+ A subclass of <i>prov:ProcessExecution</i> to
+ signify an execution of a process which
+ <i>wf:wasDefinedBy</i> a
+ a <i>wf:ProcessDefinition</i>, e.g. a workflow or a
+ process in a workflow. A workflow process can also
+ act as an <i>prov:Agent</i> when controlling nested
+ process executions.
+ </dd>
+ <dt>wf:WorkflowEngine</dt>
+ <dd>
+ A subclass of <i>prov:Agent</i> to indicate that a
+ workflow process was controlled by a workflow
+ engine.
+ </dd>
+ <dt>wf:Value</dt>
+ <dd>
+ A subclass of <i>prov:Entity</i>, representing a
+ value appearing in the workflow execution, it will
+ typically be <i>used</i> or <i>generated</i> by
+ <i>wf:Process</i> executions. The actual value can
+ be provided with a <i>wf:value</i> property.
+ </dd>
+ <dt>wf:ValueAtPort</dt>
+ <dd>
+ A subclass of <i>wf:Value</i> and <i>prov:EntityInRole</i>,
+ indicating a value while in the role of being used
+ or generated by a <i>wf:Process</i> at a particular
+ <i>wf:Port</i>.
+ </dd>
+ <dt>wf:FileValue</dt>
+ <dd>
+ A <i>wf:Value</i> which has been read from a file.
+ As an <i>prov:Entity</i> this represents
+ an entity with both attributes <i>wf:value</i> and
+ <i>wf:filename</i> fixed, that is the entity describes
+ the point when the given file contained the
+ content. As the file might be read a while before
+ the <i>wf:Value</i> is used by a <i>wf:Process</i>,
+ at which point the file content might have changed,
+ those values are declared as being derived from
+ this file value using the <i>wf:wasReadFrom</i>
+ property.
+ </dd>
+ </dl>
+ </div>
+ <div id="workflow-extensions-to-prov-properties" class="section">
+ <h4><span class="secno">3.2.2 </span>Workflow extensions to PROV properties</h4>
+ <p>
+ While for most cases subclassing will provide the
+ additional expressionality the application needs, this
+ example ontology also expands on the PROV ontology
+ with more specific subproperties.
+ </p>
+ <dl>
+ <dt>wf:wasDefinedBy</dt>
+ <dd>
+ This sub-property of <i>prov:hadRecipe</i>
+ links a
+ <i>wf:Process</i> to the defining
+ <i>wf:ProcessDefinition</i>. Thus, if there are
+ multiple executions of the same workflow definition,
+ each of the separate <i>wf:Process</i>es will link to
+ the same definition.
+ </dd>
+ <dt>wf:ranInWorkflowEngine</dt>
+ <dd>
+ This subproperty of <i>prov:wasControlledBy</i> links a
+ <i>wf:Process</i> to the <i>wf:WorkflowEngine</i> it
+ was executed in. The engine instance might contain
+ additional details such as which version of the
+ workflow system was used.
+ </dd>
+ <dt>wf:wasLaunchedBy</dt>
+ <dd>
+ This second subproperty of <i>prov:wasControlledBy</i> links a
+ <i>wf:Process</i> to a <i>prov:Agent</i>, indicating
+ which person asked to execute the given
+ wf:ProcessDefinition in the specified
+ <i>wf:WorkflowEngine</i>.
+ </dd>
+ <dt>wf:wasSubProcessExecutionOf</dt>
+ <dd>
+ This subproperty of <i>prov:wasControlledBy</i> links a
+ <i>wf:Process</i> to another <i>prov:Process</i>, indicating
+ this is a child execution
+ <div class="issue">Should there be a general way to state subprocesses? -Stian</div>
+ </dd>
+ <dt>wf:wasReadFrom</dt>
+ <dd>
+ <p>
+ This subproperty of <i>prov:wasDerivedFrom</i> links a
+ <i>wf:Value</i> to the <i>wf:FileValue</i> it was read
+ from, typically when used as a workflow input.
+ As described for <i>wf:FileValue</i> this distinction
+ is done because at the time the workflow input is used
+ in the workflow, the file input might be different and
+ thus should not be described as an attribute of that
+ <i>wf:Value</i>.
+ </p>
+ <p>
+ This property hints of an undescribed "Read file"
+ process execution which is not described. This is
+ therefore an example of how the provenance asserter
+ is limiting the scope of its provenance. The engine
+ knows that the file was read, but is not able or
+ willing to provide any deeper assertions, because its
+ primary scope is at the level of executing workflow
+ definitions.
+ </p>
+ </dd>
+ <dt>wf:sawValue</dt>
+ <dd>
+ A subproperty of <i>prov:wasComplementOf</i> which
+ indicates that an <i>wf:Value</i> was
+ <i>wf:seenAtPort</i> within an
+ <i>wf:ValueAtPort</i>. This ValueAtPort is a complement of the
+ pointed at Value because one can consider this
+ entity to to have the same attributes, but in
+ addition the <i>wf:seenAtPort</i> property is fixed.
+ <div class="issue">Should be subproperty of
+ not-yet-existing prov:assumedBy or similar -Stian -
+ part of <a href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a></div>
+ </dd>
+
+ <dt>wf:wasSeenAtPort</dt>
+ <dd>
+ A subproperty of <i>prov:assumedRole</i> (not yet defined in
+ PROV ontology) indicating which <i>wf:Port</i> a
+ <i>wf:ValueAtPort</i> was seen at. Thus one can see
+ at which output port a value was generated, or at
+ which input port(s) it was used.
+
+ As a functional property this requires a different
+ <i>wf:ValueAtPort</i> for each <i>use</i> and
+ <i>generation</i> of a value. The
+ <i>wf:ValueAtPort</i> is linked to the
+ <i>wf:Entity</i> using <i>prov:wasComplementOf</i>
+ <div class="issue">Need
+ prov:assumedRole in ontology -Stian</div>
+ </dd>
+ </dl>
+ </div>
+ <div id="workflow-structure" class="section">
+ <h4><span class="secno">3.2.3 </span>Workflow structure</h4>
+ <p>
+ This ontology includes a simple definition language for
+ describing the overall workflow structure. This is not
+ meant as a general workflow definition language, but allows
+ us to describe <i>process executions</i>, <i>use</i> and
+ <i>generation</i> with relation to particular sections of
+ the workflow definition.
+ </p>
+ <dl>
+ <dt>wf:ProcessDefinition</dt>
+ <dd>A definition of how to execute a process. It will
+ typically refer to a command or service which will be
+ called. Each process definition also
+ <i>wf:definesInput</i>s and <i>wf:definesOutput</i>s.
+ </dd>
+ <dt>wf:Port</dt>
+ <dd>
+ A port can be considered as a parameter or return value
+ for a process. These are typically given names which are
+ unique within a process definition. A value is either
+ provided to an input port before execution, or produced
+ from an output port after execution.
+ </dd>
+ <dt>wf:linksTo</dt>
+ <dd>
+ Ports are connected using links. A link from an output
+ port to an input port means that the value received on
+ that output will be forwarded to the input of the next
+ process. Note that in this simplified ontology links can
+ also go from Input to Input and Output to Output, these
+ are used to connect workflow ports to processor ports.
+ </dd>
+ <dt>wf:Input</dt>
+ <dd>
+ An input port for a process will receive a value which
+ will be <i>used</i> by the execution. In a dataflow driven
+ workflow model, a process will execute as soon as all its
+ defined input ports have been provided with values.
+ </dd>
+ <dt>wf:Output</dt>
+ <dd>
+ A process execution might return multiple outputs, for
+ instance a table and a diagram. Each of these are declared
+ as an output port for that process definition.
+ </dd>
+ <dt>wf:definesSubProcess</dt>
+ <dd>
+ <p>
+ Scientific workflows can be composed of nested workflows
+ which can be shared and reused as components. Some
+ workflow systems also allow various execution settings
+ on the nested workflow, like looping or parallelisation.
+ </p>
+ <p>
+ In this case a process definition will use
+ <i>wf:definesSubProcess</i> to indicate its consistent
+ parts, and there will be additional <i>wf:linksTo</i> from
+ the input ports of this process definition to the input
+ ports of some of its nested sub processes, and vice versa
+ for the outputs. The top-level workflow is always such a
+ process definition.
+ </p>
+ </dd>
+ </dl>
+ </div>
+ <div id="example-workflow" class="section">
+ <h4><span class="secno">3.2.4 </span>Example workflow</h4>
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png" alt="An example workflow with input, three processes, and two outputs." />
+ <p>This is an example workflow which defines a workflow
+ input <i>input</i>, three processes <i>String_constant</i>,
+ <i>Concatenate_two_strings</i> and <i>sha1</i>, and finally
+ two workflow outputs <i>combined</i> and <i>sha1</i>. When
+ executed, it will execute from top to bottom, first
+ concatenating the provided input with the string constant,
+ which is returned on the <i>combined</i> output, but also
+ provided to the <i>sha1</i> process, which output is given
+ to the other workflow port.
+ </p>
+ <p>
+ Using the definition ontology above this workflow can be
+ expressed in RDF/XML as:
+ </p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:RDF xml:base="http://www.example.com/workflow1#"
+ xmlns:impl="http://company.example.org/engine-implementation#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:wf="http://www.example.com/scientific-workflow#">
+
+ <wf:ProcessDefinition rdf:about="#workflow">
+ <rdf:type rdf:resource="http://company.example.org/engine-implementation#Workflow"/>
+ <wf:definesInput>
+ <wf:Input rdf:about="#inName">
+ <wf:linksTo rdf:resource="#catIn2" />
+ </wf:Input>
+ </wf:definesInput>
+ <wf:definesOutput rdf:resource="#combined" />
+ <wf:definesOutput rdf:resource="#sha1" />
+ <wf:definesSubProcess>
+ <impl:Constant rdf:about="#String_constant">
+ <impl:constant>Hello, </impl:constant>
+ <wf:definesOutput>
+ <wf:Output rdf:about="#constantValue">
+ <wf:linksTo rdf:resource="#catIn1"/>
+ </wf:Output>
+ </wf:definesOutput>
+ </impl:Constant>
+ </wf:definesSubProcess>
+ <wf:definesSubProcess>
+ <impl:Command rdf:about="#cat">
+ <impl:command>cat</impl:command>
+ <wf:definesInput rdf:resource="#catIn1" />
+ <wf:definesInput rdf:resource="#catIn2" />
+ <wf:definesOutput>
+ <wf:Output rdf:about="#catOut">
+ <wf:linksTo rdf:resource="#shaIn"/>
+ </wf:Output>
+ </wf:definesOutput>
+ </impl:Command>
+ </wf:definesSubProcess>
+ <wf:definesSubProcess>
+ <impl:Command rdf:about="#shasum">
+ <impl:command>shasum</impl:command>
+ <wf:definesInput rdf:resource="#shaIn" />
+ <wf:definesOutput>
+ <wf:Output rdf:about="#shaOut">
+ <wf:linksTo rdf:resource="#sha1"/>
+ </wf:Output>
+ </wf:definesOutput>
+ </impl:Command>
+ </wf:definesSubProcess>
+ </wf:ProcessDefinition>
+</rdf:RDF> </pre></div>
+ </div>
+ <div id="example-workflow-run" class="section">
+ <h4><span class="secno">3.2.5 </span>Example workflow run</h4>
+ <p>
+ This example shows how using the workflow extensions
+ together with PROV can provide the provenance of executing
+ the workflow defined above.
+ </p>
+ <div class="exampleOuter"><pre class="example"><rdf:RDF xmlns="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#"
+ xmlns:cnt="http://www.w3.org/2011/content#"
+ xmlns:foaf="http://xmlns.com/foaf/0.1/"
+ xmlns:prov="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:wf="http://www.example.com/scientific-workflow#"
+ xmlns:base="http://www.example.com/run1#" >
+
+ <Agent rdf:about="#aUser">
+ <rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Person"/>
+ <foaf:name>Stian Soiland-Reyes</foaf:name>
+ </Agent>
+
+ <wf:WorkflowEngine rdf:about="#workflowEngine" />
+
+ <wf:FileValue rdf:about="#inputFile">
+ <wf:file>/tmp/myinput.txt</wf:file>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
+ <cnt:chars>Steve</cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ </wf:FileValue>
+
+ <wf:Value rdf:about="#input">
+ <wf:wasReadFrom rdf:resource="#inputFile"/>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
+ <cnt:chars>Steve</cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ </wf:Value>
+
+ <wf:Process rdf:about="#workflowRun">
+ <used>
+ <wf:ValueAtPort>
+ <wf:sawValue rdf:resource="#input"/>
+ <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#inName"/>
+ </wf:ValueAtPort>
+ </used>
+ <wf:ranInWorkflowEngine rdf:resource="#workflowEngine"/>
+ <wf:wasLaunchedBy rdf:resource="#aUser"/>
+ <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#workflow"/>
+ </wf:Process>
+
+ <wf:Process rdf:about="#constant">
+ <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
+ <wf:wasDefinedBy
+ rdf:resource="http://www.example.com/workflow1#String_Constant"/>
+ </wf:Process>
+
+ <wf:Value rdf:about="#hello">
+ <wasGeneratedBy rdf:resource="#constant"/>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:chars>Hello, </cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ </wf:Value>
+
+ <wf:ValueAtPort rdf:about="#helloValue">
+ <wasGeneratedBy rdf:resource="#constant"/>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:chars>Hello, </cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ <wf:sawEntity rdf:resource="#hello"/>
+ </wf:ValueAtPort>
+
+ <wf:Process rdf:about="#combine">
+ <used>
+ <wf:ValueAtPort>
+ <wf:sawValue rdf:resource="#hello"/>
+ <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#catIn1"/>
+ </wf:ValueAtPort>
+ </used>
+ <used>
+ <wf:ValueAtPort>
+ <wf:sawValue rdf:resource="#input"/>
+ <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#catIn2"/>
+ </wf:ValueAtPort>
+ </used>
+ <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
+ <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#cat"/>
+ </wf:Process>
+
+ <wf:Value rdf:about="#combined">
+ <wasGeneratedBy rdf:resource="#combine"/>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:chars>Hello, Steve</cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ </wf:Value>
+
+ <wf:Process rdf:about="#shasum">
+ <used rdf:resource="#combined"/>
+ <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
+ <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#shasum"/>
+ </wf:Process>
+
+ <wf:Value rdf:about="#sha1">
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
+ <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ </wf:Value>
+
+ <wf:ValueAtPort rdf:about="#sha1OutputFromShasum">
+ <wasGeneratedBy rdf:resource="#shasum"/>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
+ <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ <wf:sawValue rdf:resource="#sha1"/>
+ <wf:wasSeenAt rdf:resource="http://www.example.com/workflow1#shaOut"/>
+ </wf:ValueAtPort>
+
+ <wf:ValueAtPort rdf:about="#sha1OutputFromWorkflow">
+ <wasGeneratedBy rdf:resource="#workflowRun"/>
+ <wf:value>
+ <cnt:ContentAsText>
+ <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
+ <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
+ </cnt:ContentAsText>
+ </wf:value>
+ <wf:sawValue rdf:resource="#sha1"/>
+ <wf:wasSeenAt rdf:resource="http://www.example.com/workflow1#sha1"/>
+ </wf:ValueAtPort>
+
+</rdf:RDF> </pre>
+ <em>Example available as
+ <a href="examples/ontology-extensions/workflow/workflow.rdf">RDF/XML</a>
+ and
+ <a href="examples/ontology-extensions/workflow/workflow.ttl">Turtle</a>
+ </em>
+ </div>
+ <p> Note that for brevity, the example above does not show the inferred classes
+ and properties from the PROV ontology. For interoperability, applications
+ should also expressed such inferred statements in its
+ serialisations, so that the provenance can be read without using
+ OWL2 inferencing and the customized ontologies.
+ See the <a href="examples/ontology-extensions/workflow/workflow-inferred.rdf">workflow-inferred.rdf</a>
+ for the complete example showing both domain-specific and PROV ontology terms
+ used side by side.
+ </p>
+ </div>
+ </div>
+ </div>
+ <div id="formal-semantics-of-the-prov-ontology" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">4. </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>
+
+
+
+ <div id="rdf-semantics-for-prov-ontology" class="section">
+ <h3><span class="secno">4.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 rdfs:subClassOf and rdfsubPropertyOf are transitive properties, hence provenance assertions, in form of RDF triples, using a specialized sub class or sub property can be inferred to be true for their parent class or parent property. For example, in the provenance scenario, though alice and bob are asserted to be individuals of the class Journalist, we can infer that they are also individuals of the PROV ontology class Agent and Entity. Given,
+ </p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#alice">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
+</rdf:Description></pre>
+ </div>
+ <p>and</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
+</rdf:Description>
+<rdf:Description rdf:about="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent">
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+</rdf:Description></pre>
+ </div>
+ <p>we can infer that</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#alice">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
+</rdf:Description></pre>
+ </div>
+ <p>and</p>
+ <div class="exampleOuter">
+ <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#alice">
+ <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
+</rdf:Description></pre>
+ </div>
+ </div>
+
+
+
+ <div id="owl2-semantics-for-prov-ontology" class="section">
+ <h3><span class="secno">4.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="provenance-specific-entailments-supported-by-prov-ontology" class="section">
+ <h3><span class="secno">4.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 specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.</p>
+ <div id="provenance-constraint-on-processexecution" class="section">
+ <h4><span class="secno">4.3.1 </span>Provenance constraint on ProcessExecution</h4>
+ <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#processexecution">ProcessExecution.</a> </p>
+ <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>
+ </div>
+ <div id="provenance-constraint-on-wasgeneratedby--generation-affects-attributes" class="section">
+ <h4><span class="secno">4.3.2 </span>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</h4>
+ <p>The PROV-DM describes a constraint on wasGeneratedBy that associates the values of attributes of an Entity with the ProcessExecution that generated the Entity.</p>
+ <div class="issue">"Given a process execution pe, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by pe and the entities used by pe. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ </div>
+ <div id="provenance-constraint-on-wasgeneratedby--generation-pe-ordering" class="section">
+ <h4><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
+ <p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of the PE instance.</p>
+ <div class="issue">"Given an assertion wasGeneratedBy(x,pe,r) or wasGeneratedBy(x,pe,r,t), one can infer that the generation of the thing denoted by x precedes the end of pe and follows the beginning of pe." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122</a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ </div>
+ <div id="provenance-constraint-on-wasgeneratedby--generation-unicity" class="section">
+ <h4><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</h4>
+ <p>The PROV-DM describes a constraint on wasGeneratedBy that asserts that given an account, only one PE instance can be associated to an Entity instance by the property wasGeneratedBy.</p>
+ <div class="issue">"Given an entity expression denoted by e, two process execution expressions denoted by pe1 and pe2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then pe1=pe2 and q1=q2." This is <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ </div>
+ <div id="provenance-constraint-on-used--use-attributes" class="section">
+ <h4><span class="secno">4.3.5 </span>Provenance constraint on Used (use-attributes)</h4>
+ <p>A constraint is defined for the Used relation in PROV-DM, that makes it necessary for an attribute-value to be true for an Entity instance linked to a ProcessExecution instance by relation Used.
+ </p>
+ <div class="issue">"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the existence of an attribute-value pair in the entity expression identified by e is a pre-condition for the termination of the activity represented by the process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
+ </div>
+ <div id="provenance-constraint-on-used--use-pe-ordering" class="section">
+ <h4><span class="secno">4.3.6 </span>Provenance constraint on Used (use-pe-ordering)</h4>
+ <p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a ProcessExecution instance pe by Used relation) to be "used" before pe terminates and also the "generation" of e precedes "use" of e.
+ </p>
+ <div class="issue">"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by pe and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
+ </div>
+ <ul>
+<li><a id="PROV:0006" href="#PROV:0006">PROV:0006</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
+ assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds, one can
+infer that the use of the thing denoted by <b>e</b> precedes the end
+of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
+can infer that the generation of the thing denoted by <b>e</b> always precedes
+its use." (<a href="../model/ProvenanceModel.html#PROV:0006">link</a>)
+</li>
+
+<li> <a id="PROV:0007" href="#PROV:0007">PROV:0007</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+or <b>wasDerivedFrom(e2,e1)</b> holds, if and only if:
+ the values of some attributes
+of <b>e2</b> are partly or fully determined by the values of some
+attributes of <b>e1</b>." (<a href="../model/ProvenanceModel.html#PROV:0007">link</a>)
+</li>
+
+<li><a id="PROV:0008" href="#PROV:0008">PROV:0008</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+or <b>wasDerivedFrom(e2,e1)</b> holds, then
+the use
+of characterized thing denoted by <b>e1</b> precedes the generation of
+the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0008">link</a>)
+</li>
+
+<li><a id="PROV:0009" href="#PROV:0009">PROV:0009</a> "If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
+such that:
+ <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b>." (<a href="../model/ProvenanceModel.html#PROV:0009">link</a>)
+</li>
+
+
+<li><a id="PROV:0010" href="#PROV:0010">PROV:0010</a> "If <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also hold." (<a href="../model/ProvenanceModel.html#PROV:0010">link</a>)
+</li>
+
+<li><a id="PROV:0011" href="#PROV:0011">PROV:0011</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, and role <b>r2</b>,
+if <b>wasDerivedFrom(e2,e1)</b> and <b>wasGeneratedBy(e2,pe,r2)</b> hold, then there exists a role <b>r1</b>,
+such that <b>used(pe,e1,r1)</b> also holds." (<a href="../model/ProvenanceModel.html#PROV:0011">link</a>)
+</li>
+
+<li><a id="PROV:0012" href="#PROV:0012">PROV:0012</a> "Given two entities <b>e1</b> and <b>e2</b>, if the assertion <b>isEventuallyDerivedFrom(e2,e1)</b>
+ holds, then:
+generation of the characterized thing denoted by <b>e1</b> precedes the generation of
+the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0012">link</a>)
+</li>
+
+<li><a id="PROV:0013" href="#PROV:0013">PROV:0013</a> "An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <em>only if</em>:
+ <ol>
+ <li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B <em class="rfc2119" title="must">must</em> be consistent with that mapping</li>
+ <li>B has some attribute that A does not have" (<a href="../model/ProvenanceModel.html#PROV:0013">link</a>) </li>
+ </ol>
+</li>
+
+<li><a id="PROV:0014" href="#PROV:0014">PROV:0014</a> "Given a process execution <b>pe</b> and entity <b>e</b>, <b>hadPariticipant(pe,e)</b> holds if and only if:
+ <ul>
+ <li> <b>used(pe,e)</b> holds, or</li>
+ <li> <b>wasControlledBy(pe,e)</b> holds, or</li>
+ <li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and <b>hadParticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
+ </ul>
+</li>
+</ul>
+
+<div class="note">The above constraints are extracted from the
+ ProvenanceModel document. The text below should be kept consistent
+ with the other document, with bidirectional links. The plan is to
+ insert formalizations of these constraints once the OWL
+ ontology/vocabulary is mature enough to permit this.
+
+ If a constraint is changed in the model document, please copy the
+ new version here, and check whether it is still consistent with the
+ formalization (if any).
+
+ If a constraint is dropped, please mark it as "defunct" - don't
+ delete it!
+ </div>
+ </div>
+ </div>
+
+
+
+ <div class="appendix section" id="acknowledgements">
+
+<!-- OddPage -->
+<h2><span class="secno">A. </span>Acknowledgements</h2>
+ <p>
+ The Provenance Working Group Members.
+ </p>
+ </div>
+
+
+
+<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-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>
+</dd><dt id="bib-OWL2-SYNTAX">[OWL2-SYNTAX]</dt><dd>Boris Motik; Peter F. Patel-Schneider; Bijan Parsia. <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/"><cite>OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/">http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/</a>
+</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd>Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
+</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-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-DM">[PROV-DM]</dt><dd>Luc Moreau, Paolo Missier<a href="http://www.w3.org/TR/owl2-direct-semantics"><cite>PROV Conceptual Model</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html</a>
+</dd><dt id="bib-PROV-Ontology-Namespace">[PROV-Ontology-Namespace]</dt><dd>TBD<a href="https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl"><cite>PROV Ontology Namespace</cite></a>. 2011, Work in progress. URL: <a href="https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl">https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl</a>
+</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/provenance-access.html"><cite>Provenance Access and Query</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html">http://dvcs.w3.org/hg/prov/tip/paq/provenance-access.html</a>
+</dd></dl></div></div></body><style type="text/css">embed[type*="application/x-shockwave-flash"],embed[src*=".swf"],object[type*="application/x-shockwave-flash"],object[codetype*="application/x-shockwave-flash"],object[src*=".swf"],object[codebase*="swflash.cab"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"],object[classid*="d27cdb6e-ae6d-11cf-96b8-444553540000"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"]{ display: none !important;}</style></html>
--- a/ontology/ProvenanceOntology.html Wed Oct 12 14:23:01 2011 +0100
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,1801 +0,0 @@
-<!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>PROV Ontology Model</title>
- <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
- <!--
- === NOTA BENE ===
- For the three scripts below, if your spec resides on dev.w3 you can check them
- out in the same tree and use relative links so that they'll work offline,
- -->
-
-
- <style type="text/css">
-/*****************************************************************
- * ReSpec CSS
- * Robin Berjon (robin at berjon dot com)
- * v0.05 - 2009-07-31
- *****************************************************************/
-
-
-/* --- INLINES --- */
-em.rfc2119 {
- text-transform: lowercase;
- font-variant: small-caps;
- font-style: normal;
- color: #900;
-}
-
-h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
-h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
- border: none;
-}
-
-dfn {
- font-weight: bold;
-}
-
-a.internalDFN {
- color: inherit;
- border-bottom: 1px solid #99c;
- text-decoration: none;
-}
-
-a.externalDFN {
- color: inherit;
- border-bottom: 1px dotted #ccc;
- text-decoration: none;
-}
-
-a.bibref {
- text-decoration: none;
-}
-
-code {
- color: #ff4500;
-}
-
-
-/* --- WEB IDL --- */
-pre.idl {
- border-top: 1px solid #90b8de;
- border-bottom: 1px solid #90b8de;
- padding: 1em;
- line-height: 120%;
-}
-
-pre.idl::before {
- content: "WebIDL";
- display: block;
- width: 150px;
- background: #90b8de;
- color: #fff;
- font-family: initial;
- padding: 3px;
- font-weight: bold;
- margin: -1em 0 1em -1em;
-}
-
-.idlType {
- color: #ff4500;
- font-weight: bold;
- text-decoration: none;
-}
-
-/*.idlModule*/
-/*.idlModuleID*/
-/*.idlInterface*/
-.idlInterfaceID, .idlDictionaryID {
- font-weight: bold;
- color: #005a9c;
-}
-
-.idlSuperclass {
- font-style: italic;
- color: #005a9c;
-}
-
-/*.idlAttribute*/
-.idlAttrType, .idlFieldType, .idlMemberType {
- color: #005a9c;
-}
-.idlAttrName, .idlFieldName, .idlMemberName {
- color: #ff4500;
-}
-.idlAttrName a, .idlFieldName a, .idlMemberName a {
- color: #ff4500;
- border-bottom: 1px dotted #ff4500;
- text-decoration: none;
-}
-
-/*.idlMethod*/
-.idlMethType {
- color: #005a9c;
-}
-.idlMethName {
- color: #ff4500;
-}
-.idlMethName a {
- color: #ff4500;
- border-bottom: 1px dotted #ff4500;
- text-decoration: none;
-}
-
-/*.idlParam*/
-.idlParamType {
- color: #005a9c;
-}
-.idlParamName {
- font-style: italic;
-}
-
-.extAttr {
- color: #666;
-}
-
-/*.idlConst*/
-.idlConstType {
- color: #005a9c;
-}
-.idlConstName {
- color: #ff4500;
-}
-.idlConstName a {
- color: #ff4500;
- border-bottom: 1px dotted #ff4500;
- text-decoration: none;
-}
-
-/*.idlException*/
-.idlExceptionID {
- font-weight: bold;
- color: #c00;
-}
-
-.idlTypedefID, .idlTypedefType {
- color: #005a9c;
-}
-
-.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
- color: #c00;
- font-weight: normal;
-}
-
-.excName a {
- font-family: monospace;
-}
-
-.idlRaises a.idlType, .excName a.idlType {
- border-bottom: 1px dotted #c00;
-}
-
-.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
- width: 45px;
- text-align: center;
-}
-.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
-.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
-
-.idlImplements a {
- font-weight: bold;
-}
-
-dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
- margin-left: 2em;
-}
-
-.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
- font-weight: normal;
-}
-
-.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
- font-weight: bold;
- color: #000;
- font-family: monospace;
-}
-
-.attributes dt code, .fields dt code, .dictionary-members dt code {
- background: #ffffd2;
-}
-
-.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
- color: #005a9c;
- background: transparent;
- font-family: inherit;
- font-weight: normal;
- font-style: italic;
-}
-
-.methods dt code {
- background: #d9e6f8;
-}
-
-.constants dt code {
- background: #ddffd2;
-}
-
-.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
- margin-bottom: 1em;
-}
-
-table.parameters, table.exceptions {
- border-spacing: 0;
- border-collapse: collapse;
- margin: 0.5em 0;
- width: 100%;
-}
-table.parameters { border-bottom: 1px solid #90b8de; }
-table.exceptions { border-bottom: 1px solid #deb890; }
-
-.parameters th, .exceptions th {
- color: #fff;
- padding: 3px 5px;
- text-align: left;
- font-family: initial;
- font-weight: normal;
- text-shadow: #666 1px 1px 0;
-}
-.parameters th { background: #90b8de; }
-.exceptions th { background: #deb890; }
-
-.parameters td, .exceptions td {
- padding: 3px 10px;
- border-top: 1px solid #ddd;
- vertical-align: top;
-}
-
-.parameters tr:first-child td, .exceptions tr:first-child td {
- border-top: none;
-}
-
-.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
- width: 100px;
-}
-
-.parameters td.prmType {
- width: 120px;
-}
-
-table.exceptions table {
- border-spacing: 0;
- border-collapse: collapse;
- width: 100%;
-}
-
-/* --- TOC --- */
-.toc a {
- text-decoration: none;
-}
-
-a .secno {
- color: #000;
-}
-
-/* --- TABLE --- */
-table.simple {
- border-spacing: 0;
- border-collapse: collapse;
- border-bottom: 3px solid #005a9c;
-}
-
-.simple th {
- background: #005a9c;
- color: #fff;
- padding: 3px 5px;
- text-align: left;
-}
-
-.simple th[scope="row"] {
- background: inherit;
- color: inherit;
- border-top: 1px solid #ddd;
-}
-
-.simple td {
- padding: 3px 10px;
- border-top: 1px solid #ddd;
-}
-
-.simple tr:nth-child(even) {
- background: #f0f6ff;
-}
-
-/* --- DL --- */
-.section dd > p:first-child {
- margin-top: 0;
-}
-
-.section dd > p:last-child {
- margin-bottom: 0;
-}
-
-.section dd {
- margin-bottom: 1em;
-}
-
-.section dl.attrs dd, .section dl.eldef dd {
- margin-bottom: 0;
-}
-
-/* --- EXAMPLES --- */
-pre.example {
- border-top: 1px solid #ff4500;
- border-bottom: 1px solid #ff4500;
- padding: 1em;
- margin-top: 1em;
-}
-
-pre.example::before {
- content: "Example";
- display: block;
- width: 150px;
- background: #ff4500;
- color: #fff;
- font-family: initial;
- padding: 3px;
- font-weight: bold;
- margin: -1em 0 1em -1em;
-}
-
-/* --- EDITORIAL NOTES --- */
-.issue {
- padding: 1em;
- margin: 1em 0em 0em;
- border: 1px solid #f00;
- background: #ffc;
-}
-
-.issue::before {
- content: "Issue";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #f00;
- background: #fff;
- padding: 3px 1em;
-}
-
-.note {
- margin: 1em 0em 0em;
- padding: 1em;
- border: 2px solid #cff6d9;
- background: #e2fff0;
-}
-
-.note::before {
- content: "Note";
- display: block;
- width: 150px;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #cff6d9;
- background: #fff;
- padding: 3px 1em;
-}
-
-/* --- Best Practices --- */
-div.practice {
- border: solid #bebebe 1px;
- margin: 2em 1em 1em 2em;
-}
-
-span.practicelab {
- margin: 1.5em 0.5em 1em 1em;
- font-weight: bold;
- font-style: italic;
-}
-
-span.practicelab { background: #dfffff; }
-
-span.practicelab {
- position: relative;
- padding: 0 0.5em;
- top: -1.5em;
-}
-
-p.practicedesc {
- margin: 1.5em 0.5em 1em 1em;
-}
-
-@media screen {
- p.practicedesc {
- position: relative;
- top: -2em;
- padding: 0;
- margin: 1.5em 0.5em -1em 1em;
- }
-}
-
-/* --- SYNTAX HIGHLIGHTING --- */
-pre.sh_sourceCode {
- background-color: white;
- color: black;
- font-style: normal;
- font-weight: normal;
-}
-
-pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
-pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
-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_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 */
-pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
-pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
-pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
-pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
-
-/* Predefined variables and functions (for instance glsl) */
-pre.sh_sourceCode .sh_predef_var { color: #00008B; }
-pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
-
-/* for OOP */
-pre.sh_sourceCode .sh_classname { color: teal; }
-
-/* line numbers (not yet implemented) */
-pre.sh_sourceCode .sh_linenum { display: none; }
-
-/* Internet related */
-pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
-
-/* for ChangeLog and Log files */
-pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
-pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
-pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
-
-/* for Prolog, Perl... */
-pre.sh_sourceCode .sh_variable { color: #006400; }
-
-/* for LaTeX */
-pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
-pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
-pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
-pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
-pre.sh_sourceCode .sh_argument { color: #006400; }
-pre.sh_sourceCode .sh_optionalargument { color: purple; }
-pre.sh_sourceCode .sh_math { color: orange; }
-pre.sh_sourceCode .sh_bibtex { color: blue; }
-
-/* for diffs */
-pre.sh_sourceCode .sh_oldfile { color: orange; }
-pre.sh_sourceCode .sh_newfile { color: #006400; }
-pre.sh_sourceCode .sh_difflines { color: blue; }
-
-/* for css */
-pre.sh_sourceCode .sh_selector { color: purple; }
-pre.sh_sourceCode .sh_property { color: blue; }
-pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
-
-/* other */
-pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
-pre.sh_sourceCode .sh_paren { color: red; }
-pre.sh_sourceCode .sh_attribute { color: #006400; }
-
-</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" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV Ontology Model</h1><h2 id="w3c-working-draft-12-october-2011">W3C Working Draft 12 October 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111012/">http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111012/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/PROV-FormalModel/">http://www.w3.org/TR/PROV-FormalModel/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111007/">http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111007/</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><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester, UK</dd>
-<dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh, UK</dd>
-<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>
-</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. W3C <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>
-<p> The PROV Ontology Model (also PROV ontology) 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 is specialized to create domain-specific provenance ontologies that model the provenance information specific to different applications. The PROV ontology supports a set of entailments based on OWL2 formal semantics and provenance specific inference rules. The PROV ontology is available for download as a separate OWL2 document.</p>
- </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 W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
-<p>TODO: <em class="rfc2119" title="must">must</em> include at least one customized paragraph. This section <em class="rfc2119" title="should">should</em> include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs <em class="rfc2119" title="should">should</em> explain the publication context, including rationale and relationships to other work. See examples and more discussion in the Manual of Style.<a href="http://www.w3.org/2001/06/manual/#Status">TODO</a></p>
-<p>This document was published by the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">Provenance Working Group</a> as a First Public Working Draft. This document is intended to become a W3C 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 W3C 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 W3C Patent Policy</a>. W3C maintains a <a href="" 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 W3C 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="#prov-ontology" class="tocxref"><span class="secno">1. </span>PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#owl2-syntax-used-in-this-document" class="tocxref"><span class="secno">1.1 </span>OWL2 Syntax Used in this Document</a></li></ul></li><li class="tocline"><a href="#prov-ontology--classes-and-properties" class="tocxref"><span class="secno">2. </span>PROV Ontology: Classes and Properties</a><ul class="toc"><li class="tocline"><a href="#classes" class="tocxref"><span class="secno">2.1 </span>Classes</a><ul class="toc"><li class="tocline"><a href="#entity" class="tocxref"><span class="secno">2.1.1 </span>Entity</a></li><li class="tocline"><a href="#processexecution" class="tocxref"><span class="secno">2.1.2 </span>ProcessExecution</a></li><li class="tocline"><a href="#agent" class="tocxref"><span class="secno">2.1.3 </span>Agent</a></li><li class="tocline"><a href="#recipe" class="tocxref"><span class="secno">2.1.4 </span>Recipe</a></li><li class="tocline"><a href="#time" class="tocxref"><span class="secno">2.1.5 </span>Time</a></li><li class="tocline"><a href="#revision" class="tocxref"><span class="secno">2.1.6 </span>Revision</a></li><li class="tocline"><a href="#provenancecontainer" class="tocxref"><span class="secno">2.1.7 </span>ProvenanceContainer</a></li><li class="tocline"><a href="#location" class="tocxref"><span class="secno">2.1.8 </span>Location</a></li><li class="tocline"><a href="#entityinrole" class="tocxref"><span class="secno">2.1.9 </span>EntityInRole</a></li></ul></li><li class="tocline"><a href="#object-properties" class="tocxref"><span class="secno">2.2 </span>Object Properties</a><ul class="toc"><li class="tocline"><a href="#wasgeneratedby" class="tocxref"><span class="secno">2.2.1 </span>wasGeneratedBy</a></li><li class="tocline"><a href="#wasderivedfrom" class="tocxref"><span class="secno">2.2.2 </span>wasDerivedFrom</a></li><li class="tocline"><a href="#used" class="tocxref"><span class="secno">2.2.3 </span>Used</a></li><li class="tocline"><a href="#hadparticipant" class="tocxref"><span class="secno">2.2.4 </span>hadParticipant</a></li><li class="tocline"><a href="#wascomplementof" class="tocxref"><span class="secno">2.2.5 </span>wasComplementOf</a></li><li class="tocline"><a href="#wascontrolledby" class="tocxref"><span class="secno">2.2.6 </span>wasControlledBy</a></li><li class="tocline"><a href="#hadrecipe" class="tocxref"><span class="secno">2.2.7 </span>hadRecipe</a></li><li class="tocline"><a href="#wasinformedby" class="tocxref"><span class="secno">2.2.8 </span>wasInformedBy</a></li><li class="tocline"><a href="#wasscheduledafter" class="tocxref"><span class="secno">2.2.9 </span>wasScheduledAfter</a></li></ul></li><li class="tocline"><a href="#characteristics-of-object-properties" class="tocxref"><span class="secno">2.3 </span>Characteristics of Object Properties </a></li><li class="tocline"><a href="#annotation-properties" class="tocxref"><span class="secno">2.4 </span>Annotation Properties</a></li><li class="tocline"><a href="#overview-of-the-ontology" class="tocxref"><span class="secno">2.5 </span>Overview of the ontology</a></li></ul></li><li class="tocline"><a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications" class="tocxref"><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</a><ul class="toc"><li class="tocline"><a href="#modeling-the-crime-file-scenario" class="tocxref"><span class="secno">3.1 </span>Modeling the Crime File Scenario</a><ul class="toc"><li class="tocline"><a href="#specialization-of-prov-ontology-classes" class="tocxref"><span class="secno">3.1.1 </span>Specialization of PROV Ontology Classes</a><ul class="toc"><li class="tocline"><a href="#cf-journalist" class="tocxref"><span class="secno">3.1.1.1 </span>cf:Journalist</a></li><li class="tocline"><a href="#cf-crimefile" class="tocxref"><span class="secno">3.1.1.2 </span>cf:CrimeFile</a></li><li class="tocline"><a href="#cf-filecreation--cf-fileediting--cf-fileappending--cf-emailprocessexecution--cf-spellchecking" class="tocxref"><span class="secno">3.1.1.3 </span>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking</a></li></ul></li><li class="tocline"><a href="#specialization-of-prov-ontology-properties" class="tocxref"><span class="secno">3.1.2 </span>Specialization of PROV Ontology Properties</a><ul class="toc"><li class="tocline"><a href="#cf-hadfilepath" class="tocxref"><span class="secno">3.1.2.1 </span>cf:hadFilePath</a></li></ul></li></ul></li><li class="tocline"><a href="#modeling-an-example-scientific-workflow-scenario" class="tocxref"><span class="secno">3.2 </span>Modeling an Example Scientific Workflow Scenario</a><ul class="toc"><li class="tocline"><a href="#workflow-extensions-to-prov-classes" class="tocxref"><span class="secno">3.2.1 </span>Workflow extensions to PROV classes</a></li><li class="tocline"><a href="#workflow-extensions-to-prov-properties" class="tocxref"><span class="secno">3.2.2 </span>Workflow extensions to PROV properties</a></li><li class="tocline"><a href="#workflow-structure" class="tocxref"><span class="secno">3.2.3 </span>Workflow structure</a></li><li class="tocline"><a href="#example-workflow" class="tocxref"><span class="secno">3.2.4 </span>Example workflow</a></li><li class="tocline"><a href="#example-workflow-run" class="tocxref"><span class="secno">3.2.5 </span>Example workflow run</a></li></ul></li></ul></li><li class="tocline"><a href="#formal-semantics-of-the-prov-ontology" class="tocxref"><span class="secno">4. </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">4.1 </span>RDF Semantics for PROV Ontology</a></li><li class="tocline"><a href="#owl2-semantics-for-prov-ontology" class="tocxref"><span class="secno">4.2 </span>OWL2 Semantics for PROV Ontology</a></li><li class="tocline"><a href="#provenance-specific-entailments-supported-by-prov-ontology" class="tocxref"><span class="secno">4.3 </span>Provenance-specific Entailments Supported by PROV Ontology</a><ul class="toc"><li class="tocline"><a href="#provenance-constraint-on-processexecution" class="tocxref"><span class="secno">4.3.1 </span>Provenance constraint on ProcessExecution</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby--generation-affects-attributes" class="tocxref"><span class="secno">4.3.2 </span>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby--generation-pe-ordering" class="tocxref"><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</a></li><li class="tocline"><a href="#provenance-constraint-on-wasgeneratedby--generation-unicity" class="tocxref"><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</a></li><li class="tocline"><a href="#provenance-constraint-on-used--use-attributes" class="tocxref"><span class="secno">4.3.5 </span>Provenance constraint on Used (use-attributes)</a></li><li class="tocline"><a href="#provenance-constraint-on-used--use-pe-ordering" class="tocxref"><span class="secno">4.3.6 </span>Provenance constraint on Used (use-pe-ordering)</a></li></ul></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 class="section">
- <a id="introduction"></a>
- <h2 id="introduction-1">Introduction</h2>
- <p>
- PROV Ontology Model (also PROV ontology) 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 W3C OWL2 Web Ontology Language. This document specification describes the set of classes, properties, and restrictions that constitute the PROV ontology, which have been introduced in the PROV Data Model [<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 applications 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 management in domain-specific Web-based applications.
- </p>
- <p>
- The PROV ontology classes and properties are defined such that they can be specialized for modeling application-specific provenance information in a variety of domains. Thus, the PROV ontology is expected to serve as a <i>reference model</i> for domain-specific provenance ontology and thereby facilitate consistent provenance interchange. This document uses an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> introduced in the PROV Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] to demonstrate the specialization of PROV ontology.
- </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 class="section">
- <h3 id="guide-to-this-document">Guide to this Document</h3>
- <p> This document is intended for provide an understanding of
- the PROV ontology and how it can be used by various applications
- to represent their provenance information. The intended audience
- of this document include users who are new to provenance
- modeling as well as experienced users who would like their provenance model compatible with the PROV ontology to facilitate standardization.This document assumes a basic understanding of the W3C OWL2 specification , including modeling of classes, properties, and restrictions in an OWL2 ontology. Readers are referred to the OWL2 documentations, starting with the [<cite><a class="bibref" rel="biblioentry" href="#bib-OWL2-PRIMER">OWL2-PRIMER</a></cite>], for the OWL2 specification.
- </p>
- <p><a href="#prov-ontology--owl-encoding-of-prov-data-model">Section 2</a> describes the mapping of the PROV Data Model [<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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#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>
- </div>
-
- </div> <!-- Introduction -->
-
-
-
- <div id="prov-ontology" class="section">
- <!--OddPage--><h2><span class="secno">1. </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 is not designed to be used directly in a domain application and its Classes and Properties represent "higher-level" or abstract level concepts that can be specialized further for representing domain-specific provenance information. We briefly introduce some of the OWL2 modeling terms that will be used to describe the PROV ontology. An OWL2 <i>instance</i> is an individual object in a domain of discourse, for example a person named Alice or a car, and a set of individuals sharing a set of common characteristics is called a <i>class</i>. Person and Car are examples of classes representing the set of individual persons and cars respectively. The OWL2 object properties are used to link individuals, classes, or create a property hierarchy. For example, the object property "hasOwner" can be used to link car with person. The OWL2 datatype properties are used to link individuals or classes to data values, including XML Schema datatypes [<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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> describing the creation of crime statistics file stored on a shared file system and edited by journalists Alice, Bob, Charles, David, and Edith. This scenario is used as a running example in this document to describe the PROV ontology classes and properties, the specialization mechanism and entailments supported by the PROV ontology.
- </p>
-
-
-
- <div id="owl2-syntax-used-in-this-document" class="section">
- <h3><span class="secno">1.1 </span>OWL2 Syntax Used in this Document</h3>
- <p>We use 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. The OWL2 document for the PROV ontology is
- available at [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-Ontology-Namespace">PROV-Ontology-Namespace</a></cite>], which is also the
- namespace for the PROV ontology and is denoted by "PROV" and
- the prefix "prov".
- </p>
- <div class="issue">The namespace URI for the ontology has not
- yet been decided, and the examples in this document might
- therefore not be using consistent namespaces. This is <a href="http://www.w3.org/2011/prov/track/issues/90">ISSUE-90</a></div>
- </div>
- </div> <!-- PROV Ontology -->
-
-
- <div id="prov-ontology--classes-and-properties" class="section">
- <!--OddPage--><h2><span class="secno">2. </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 term in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>.
- </p>
- <div id="classes" class="section">
- <h3><span class="secno">2.1 </span>Classes</h3>
- <p>The PROV ontology consists of classes that can be organized in a taxonomic structure.
- </p>
- <img src="diagram-history/khalidDiagrams/Ontology_hierarchy.png" style="width: 50%; min-width: 25em; max-width: 37em" alt="Class hierarchy of the PROV OWL ontology">
- <br>
- <p><i>Note: CamelBack notation is used for class names</i></p>
- <div class="issue">
- The class <code>prov:Role</code> has been
- renamed to <code>prov:EntityInRole</code>. (A new
- <code>prov:Role</code> might appear in the rdfs:range of
- <code>prov:assuming</code>
- </div>
- <div id="entity" class="section">
- <h4><span class="secno">2.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><b>Example</b></div>
- <p> Example of instances of class Entity from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are files with identifiers <i>e1</i> and <i>e2</i>. The RDF/XML syntax for asserting that e1 is an instance of Entity is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
-</rdf:Description></pre>
- </div>
- <p>Attributes that are characterising the entity (as defined
- in PROV-DM) are stated using RDF properties of the asserted
- entity. Such properties <em class="rfc2119" title="should">should</em> be in a declared namespace,
- and <em class="rfc2119" title="may">may</em> be described by an application-specific vocabulary.
- Specialisation by subclassing or <code>rdf:type</code> is
- equivalent to specifying the reserved attribute <code>type</code>
- in PROV-DM.
- </p>
- <div><b>Example</b></div>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
- <cf:hasLocation rdf:resource="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1"/>
- <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There was a lot of crime in London last month.</cf:hasFileContent>
-</rdf:Description></pre>
- </div>
-
- <div class="issue">Definition of Entity in PROV-DM is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
- </div> <!-- Classes -->
-
- <div id="processexecution" class="section">
- <h4><span class="secno">2.1.2 </span>ProcessExecution</h4>
- <div><b>Class Description</b></div>
- <p>ProcessExecution 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:ProcessExecution rdfs:subClassOf owl:Thing.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class ProcessExecution from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are file creation (<i>pe0</i>) and file editing (<i>pe2</i>) . The RDF/XML syntax for asserting that pe2 is an instance of ProcessExecution is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
-</rdf:Description></pre>
- </div>
- <div class="note"> pe2 is an instance of class EmailProcessExecution, which is defined to be "sub-class" of class ProcessExecution in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of ProcessExecution.
- </div>
- </div>
-
-
-
- <div id="agent" class="section">
- <h4><span class="secno">2.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><b>Example</b></div>
- <p> Example of instances of class Agent from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>Alice</i> and <i>Edith</i>. The RDF/XML syntax for asserting that Alice is an instance of Agent is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Alice">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
-</rdf:Description></pre>
- </div>
- <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="recipe" class="section">
- <h4><span class="secno">2.1.4 </span>Recipe</h4>
- <div><b>Class Description</b></div>
- <p>Recipe represents a process specification. The definition of process specifications is outside the scope of PROV:DM. Therefore, this class acts as a place holder in the ontology that can be extended and specialized by users.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Recipe rdfs:subClassOf owl:Thing.</pre>
- <div><b>Example</b></div>
- <p> Recipe examples include backing recipes, programs and workflows.
- </p></div>
-
-
-
- <div id="time" class="section">
- <h4><span class="secno">2.1.5 </span>Time</h4>
- <div><b>Class Description</b></div>
- <p>Time represents temporal information about entities in the Provenance model.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Time rdfs:subClassOf owl:Thing.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class Time from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of Time is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#t+1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Time"/>
-</rdf:Description></pre>
- </div>
- </div>
-
-
-
- <div id="revision" class="section">
- <h4><span class="secno">2.1.6 </span>Revision</h4>
- <div><b>Class Description</b></div>
- <p>Revision is defined as a modified version of a Entity.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:Revision rdfs:subClassOf owl:Thing.</pre>
- <div class="issue">Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
- </div>
-
-
-
- <div id="provenancecontainer" class="section">
- <h4><span class="secno">2.1.7 </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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Account">Account</a>.</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:ProvenanceContainer rdfs:subClassOf owl:Thing.</pre>
- <p>Examples of instance of class ProvenanceContainer includes a file describing the manufacturing details of a car, such as its batch number, manufacturer, date of manufacture, place of manufacture etc. </p>
- <div class="note"> According to the definitions of ProvenanceContainer and Account, both contain a set of provenance assertions and have an identifier. Hence, ProvenanceContainer class can also be used to create instances of accounts.
- </div>
- <div class="issue">Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
- <div class="issue">Scope and Identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
- </div>
-
-
-
- <div id="location" class="section">
- <h4><span class="secno">2.1.8 </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://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is the location of the crime file in the shared directory <i>/share</i> with file path <i>/shared/crime.txt</i>. The RDF/XML syntax for asserting that the location of the crime file is the shared directory.
- </p><div class="exampleOuter">
- <pre class="example"><cf:hasLocation>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
- <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
- </rdf:Description>
-</cf:hasLocation></pre>
- </div>
- <div class="note"> Need to clarify whether "geographic" includes "geospatial"?</div>
- </div>
-
-
-
- <div id="entityinrole" class="section">
- <h4><span class="secno">2.1.9 </span>EntityInRole</h4>
- <div><b>Class Description</b></div>
- <p>EntityInRole is defined to be a "realizable entity" (cite?) "assumed by a Entity or an agent." [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>]</p>
- <div><b>OWL syntax</b></div>
- <pre>PROV:EntityInRole rdfs:subClassOf PROV:Entity.</pre>
- <div><b>Example</b></div>
- <p> Example of instances of class EntityInRole from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>author</i> role assumed by Bob and <i>file creator</i> role assumed by Alice. The RDF/XML syntax for asserting that Bob assumes the role of an author is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#AliceAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#EntityInRole"/>
- <prov:assumedBy rdf:resource="http://www.w3.org/PROV/CrimeFile#Alice"/>
- <prov:assumedRole rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#author"/>
-</rdf:Description></pre>
- </div>
- <div class="issue">prov:assumedBy and prov:assumedRole
- (or equivalent) properties have not yet been defined
- in this ontology. This is
- <a href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a>
- and
- <a href="http://www.w3.org/2011/prov/track/issues/111">ISSUE-111</a>
- </div>
-
- <div class="issue">The PROV-DM defines the term <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a>, which is incorporated implicitly in definition of OWL sub-classes and sub-properties that specialize a parent class or property by defining additional qualifying constraints. Hence, <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a> is not modeled explicitly in PROV ontology.</div>
- </div>
- </div>
-
-
- <div id="object-properties" class="section">
- <h3><span class="secno">2.2 </span>Object Properties</h3>
- <p>The Provenance Model consists of the following object properties. </p>
- <p><i>Note: Names of properties starts with a verb in lower case followed by verb(s) starting with upper case </i></p>
-
-
-
- <div id="wasgeneratedby" class="section">
- <h4><span class="secno">2.2.1 </span>wasGeneratedBy</h4>
- <p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" alt="wasGeneratedBy links Entity to ProcessExecution">
- <div><b>Example</b></div>
- <p> Example of wasGeneratedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
- <prov:wasGeneratedBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe0">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileCreation"/>
- </rdf:Description>
- <prov:wasGeneratedBy>
-</rdf:Description> </pre>
- </div>
- </div>
-
-
-
- <div id="wasderivedfrom" class="section">
- <h4><span class="secno">2.2.2 </span>wasDerivedFrom</h4>
- <p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
- <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" alt="wasDerivedFrom links Entity to Entity">
- <div><b>Example</b></div>
- <p> Example of wasDerivedFrom property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e3">
- <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
-</rdf:Description> </pre>
- </div>
- <div class="issue">Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
- <div class="issue">Should we specifically mention derivation of agents? This is <a href="http://www.w3.org/2011/prov/track/issues/42">ISSUE-42</a>.</div>
- </div>
-
-
-
- <div id="used" class="section">
- <h4><span class="secno">2.2.3 </span>Used</h4>
- <p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" alt="prov:used links ProcessExecution to Entity">
- <div class="issue">Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
- <div><b>Example</b></div>
- <p> Example of Used property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 Used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
- <prov:used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
- </rdf:Description> </pre>
- </div>
- </div>
-
-
-
-
- <div id="hadparticipant" class="section">
- <h4><span class="secno">2.2.4 </span>hadParticipant</h4>
- <p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
- </p><p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <div class="pending">Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
- </div>
-
-
-
- <div id="wascomplementof" class="section">
- <h4><span class="secno">2.2.5 </span>wasComplementOf</h4>
- <p>wasComplementOf links two instances of Entity, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." <i>(from the Provenance Conceptual Model)</i></p>
- </div>
-
-
-
- <div id="wascontrolledby" class="section">
- <h4><span class="secno">2.2.6 </span>wasControlledBy</h4>
- <p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" alt="wasControlledBy links ProcessExecution to Agent">
- <div><b>Example</b></div>
- <p> Example of wasControlledBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
- </p><div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
- <prov:wasControlledBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Bob">
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
- </rdf:Description>
- </prov:wasControlledBy>
-</rdf:Description> </pre>
- </div>
- <div class="issue">Mutual ivpOf each other should be agreed. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
- <div class="issue">Do we need a sameAsEntity relation. This is <a href="http://www.w3.org/2011/prov/track/issues/35">ISSUE-35</a></div>
- <div class="issue">Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
- <div class="issue"> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
- </div>
-
-
-
- <div id="hadrecipe" class="section">
- <h4><span class="secno">2.2.7 </span>hadRecipe</h4>
- <p>The ProcessExecution activity performed can be described as
- having the given recipe resource. It is out of the scope for PROV to
- define the structure or meaning of the recipe. The recipe
- might or might not have been followed exactly by the Process
- Execution.
- </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" alt="prov:hadRecipe links ProcessExecution to Recipe.">
- </div>
-
-
-
- <div id="wasinformedby" class="section">
- <h4><span class="secno">2.2.8 </span>wasInformedBy</h4>
- <p> This object property links two process executions. It is used to express the fact that a given process execution used an entity that was generated by another process execution.
- </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" alt="prov:wasInformedBy links ProcessExecution to ProcessExecution">
- </div>
-
-
-
- <div id="wasscheduledafter" class="section">
- <h4><span class="secno">2.2.9 </span>wasScheduledAfter</h4>
- <p>
- This object property links two instances of ProcessExecution to specify the order in which they took place. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
- </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" alt="prov:wasScheduledAfter links ProcessExecution to ProcessExecution">
- </div>
-
- </div>
-
- <div id="characteristics-of-object-properties" class="section">
- <h3><span class="secno">2.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
-
- </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
-
- </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 them may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>isUsedBY</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>isUsedBY</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.
- </div>
- </div>
-
- <div id="annotation-properties" class="section">
- <h3><span class="secno">2.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>
-
- <div id="overview-of-the-ontology" class="section">
- <h3><span class="secno">2.5 </span>Overview of the ontology</h3>
- <p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" alt="Object properties among all classes in the PROV OWL ontology">
- <a href="http://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.pdf"><img src="http://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.png" alt="Object properties among all classes in the PROV OWL ontology"></a>
- </div>
- </div>
-
-
-
- <div id="specializing-provenance-ontology-for-domain-specific-provenance-applications" class="section">
- <!--OddPage--><h2><span class="secno">3. </span>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
- <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:</p>
- <ul>
- <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
- <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
- </ul>
- <p>To illustrate the specialization mechanism, the PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
-
-
-
- <div id="modeling-the-crime-file-scenario" class="section">
- <h3><span class="secno">3.1 </span>Modeling the Crime File Scenario</h3>
- <p>The example scenario can be encoded as a <a href="http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href="">Figure X</a>:</p>
- <div class="issue">insert figure X</div>
- <p><a href="">Figure X</a> represents the ontology schema that extends the PROV ontology to model the provenance details of the crime file scenario. For example,</p>
- <ul>
- <li>specialization of <a href="#agent">Agent</a> to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
- <li><a href="#processexecution">ProcessExecution</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
- <li>specialization of <a href="#entity">Entity</a> to define a class called CrimeFile, which has individuals such as e1, e2, and e3 </li>
- </ul>
- <p>Example given below describes the provenance of <a href="#entity">Entity</a> e2 using RDF/XML syntax</p>
- <div class="exampleOuter">
- <pre class="example"><?xml version="1.0"?>
-<rdf:RDF
- xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
- xmlns:prov="http://www.w3.org/PROV/ProvenanceOntology.owl#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:cf="http://www.w3.org/PROV/CrimeFileOntology.owl#">
-
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#e2">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile"/>
- <prov:wasGeneratedBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#FileAppending"/>
- <prov:wasControlledBy>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#Bob">
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
- </rdf:Description>
- </prov:wasControlledBy>
- </rdf:Description>
- </prov:wasGeneratedBy>
- <prov:wasDerivedFrom rdf:resource="http://www.w3.org/PROV/CrimeFile#e1"/>
- <cf:hasLocation>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#sharedDirectoryLocation1">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Location"/>
- <cf:hasFilePath rdf:datatype="http://www.w3.org/2001/XMLSchema#string">/share/crime.txt</cf:hasFilePath>
- </rdf:Description>
- </cf:hasLocation>
- <cf:hasFileContent rdf:datatype="http://www.w3.org/2001/XMLSchema#string">There was a lot of crime in London last month.</cf:hasFileContent>
- </rdf:Description>
- <rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#pe2">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
- <prov:used rdf:resource="http://www.w3.org/PROV/CrimeFile#e2"/>
- </rdf:Description>
- </rdf:RDF></pre>
- </div>
- <div id="specialization-of-prov-ontology-classes" class="section">
- <h4><span class="secno">3.1.1 </span>Specialization of PROV Ontology Classes</h4>
- <p> The following new classes were created in the CrimeFile Ontology by extending the PROV ontology classes:</p>
- <div id="cf-journalist" class="section">
- <h5><span class="secno">3.1.1.1 </span>cf:Journalist</h5>
- <p>The cf:Journalist is a specialization of the PROV ontology <a href="#agent">Agent</a> class and models all individuals that participate in creating, editing, and sharing the crime file.The following RDF/XML code illustrates how cf:Journalist is asserted to be a specialization of <a href="#agent">PROV:Agent.</a></p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
-</rdf:Description></pre>
- </div>
- </div>
- <div id="cf-crimefile" class="section">
- <h5><span class="secno">3.1.1.2 </span>cf:CrimeFile</h5>
- <p> The cf:CrimeFile is a specialization of the PROV ontology <a href="#entity">Entity</a> class and it models the the file describing the crime statistics in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>, including the multiple versions of the file. The following RDF/XML code illustrates how cf:Journalist is asserted to be a specialization of <a href="#entity">PROV:Entity</a>.
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#CrimeFile">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
-</rdf:Description></pre>
- </div>
- </div>
- <div id="cf-filecreation--cf-fileediting--cf-fileappending--cf-emailprocessexecution--cf-spellchecking" class="section">
- <h5><span class="secno">3.1.1.3 </span>cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking</h5>
- <p>The classes cf:FileCreation, cf:FileEditing, cf:FileAppending, cf:EmailProcessExecution, cf:SpellChecking are specialization of the PROV ontology <a href="processexecution">ProcessExecution</a> and model the different activities in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>. The following RDF/XML code illustrates the specialization of the <a href="processexecution">PROV:ProcessExecution</a> to define class cf:FileCreation (other classes can be similarly defined by using the subClassOf property).</p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#FileCreation">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#ProcessExecution"/>
-</rdf:Description></pre>
- </div>
- <p>The following diagram illustrates the above specialization: </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution).">
- <a href="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf"><img src="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)."></a>
- <br>
- <em>Example extension of PROV ontology in order to describe the crime file scenario</em>
- </div>
- </div>
- <div id="specialization-of-prov-ontology-properties" class="section">
- <h4><span class="secno">3.1.2 </span>Specialization of PROV Ontology Properties</h4>
- <p> The following new object property was created in the CrimeFile Ontology by extending the PROV ontology object property:</p>
- <div id="cf-hadfilepath" class="section">
- <h5><span class="secno">3.1.2.1 </span>cf:hadFilePath</h5>
- <p>The property cf:hadFilePath is a specialization of the PROV ontology hadLocation object property and links the class CrimeFile to the FileDirectory class. The following RDF/XML code illustrates the use of rdfs:subPropertyOf to create hadFilePath property.</p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#hadFilePath">
- <rdfs:subPropertyOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#hadLocation"/>
-</rdf:Description></pre>
- </div>
- </div>
- <p>The following diagram illustrates the above specialization: </p>
- <a href="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.pdf">
- <img src="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.png" alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:EmailProcessExecution, extSpellChecking extend prov:ProcessExecution; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location.">
- </a>
- <br>
- <em>Example extension of PROV ontology in order to describe the crime file scenario</em>
- </div>
- </div>
- <div id="modeling-an-example-scientific-workflow-scenario" class="section">
- <h3><span class="secno">3.2 </span>Modeling an Example Scientific Workflow Scenario</h3>
- <p>This section describes an example of extending the PROV
- ontology to create a provenance ontology for scientific
- workflows.</p>
-
- <p>Scientific workflow systems allow the specification of a
- pipeline of processes which are linked from outputs to inputs.
- Such workflow definitions are typically created in a graphical
- user interface or interactive web application, and can then be
- <em>enacted</em> using particular inputs or parameters.
- Scientists in fields like bioinformatics, chemistry and
- physics use such workflows to perform repeated analysis by
- connecting together disparate set of domain-specific tools and
- services.
- </p>
-
- <p>
- Capturing the provenance of executions in such a workflow
- system will typically include details of each of the process
- executions, such as its inputs and outputs, start and stop
- time, and should ultimately be able to describe the complete
- data lineage through the workflow for any returned output data.
- </p>
- <p>
- This example is not attempting to be a complete or general
- ontology for asserting workflow provenance, but highlights how
- a particular application like a workflow system can express its
- domain specific attributes based on the PROV ontology.
- </p>
- <p>
- <img src="examples/ontology-extensions/workflow/workflowOntology.png" style="width: 60%; min-width: 20em; max-width: 40em" alt="New classes wf:WorkFlowEngine, wf:Process, wf:ValueAtPort, wf:FileValue, and wf:Value extend prov:Agent, prov:ProcessExecution, prov:EntityInRole. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubProcessExecutionOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom.">
- <br>
- <em>Example extension of PROV ontology in order to describe
- workflow provenance</em>
- </p>
- <div id="workflow-extensions-to-prov-classes" class="section">
- <h4><span class="secno">3.2.1 </span>Workflow extensions to PROV classes</h4>
- <p>
- In order to describe workflow executions following the
- model above, the PROV ontology is extended with
- workflow-specific subclasses described below:
- </p>
- <dl>
- <dt>wf:Process</dt>
- <dd>
- A subclass of <i>prov:ProcessExecution</i> to
- signify an execution of a process which
- <i>wf:wasDefinedBy</i> a
- a <i>wf:ProcessDefinition</i>, e.g. a workflow or a
- process in a workflow. A workflow process can also
- act as an <i>prov:Agent</i> when controlling nested
- process executions.
- </dd>
- <dt>wf:WorkflowEngine</dt>
- <dd>
- A subclass of <i>prov:Agent</i> to indicate that a
- workflow process was controlled by a workflow
- engine.
- </dd>
- <dt>wf:Value</dt>
- <dd>
- A subclass of <i>prov:Entity</i>, representing a
- value appearing in the workflow execution, it will
- typically be <i>used</i> or <i>generated</i> by
- <i>wf:Process</i> executions. The actual value can
- be provided with a <i>wf:value</i> property.
- </dd>
- <dt>wf:ValueAtPort</dt>
- <dd>
- A subclass of <i>wf:Value</i> and <i>prov:EntityInRole</i>,
- indicating a value while in the role of being used
- or generated by a <i>wf:Process</i> at a particular
- <i>wf:Port</i>.
- </dd>
- <dt>wf:FileValue</dt>
- <dd>
- A <i>wf:Value</i> which has been read from a file.
- As an <i>prov:Entity</i> this represents
- an entity with both attributes <i>wf:value</i> and
- <i>wf:filename</i> fixed, that is the entity describes
- the point when the given file contained the
- content. As the file might be read a while before
- the <i>wf:Value</i> is used by a <i>wf:Process</i>,
- at which point the file content might have changed,
- those values are declared as being derived from
- this file value using the <i>wf:wasReadFrom</i>
- property.
- </dd>
- </dl>
- </div>
- <div id="workflow-extensions-to-prov-properties" class="section">
- <h4><span class="secno">3.2.2 </span>Workflow extensions to PROV properties</h4>
- <p>
- While for most cases subclassing will provide the
- additional expressionality the application needs, this
- example ontology also expands on the PROV ontology
- with more specific subproperties.
- </p>
- <dl>
- <dt>wf:wasDefinedBy</dt>
- <dd>
- This sub-property of <i>prov:hadRecipe</i>
- links a
- <i>wf:Process</i> to the defining
- <i>wf:ProcessDefinition</i>. Thus, if there are
- multiple executions of the same workflow definition,
- each of the separate <i>wf:Process</i>es will link to
- the same definition.
- </dd>
- <dt>wf:ranInWorkflowEngine</dt>
- <dd>
- This subproperty of <i>prov:wasControlledBy</i> links a
- <i>wf:Process</i> to the <i>wf:WorkflowEngine</i> it
- was executed in. The engine instance might contain
- additional details such as which version of the
- workflow system was used.
- </dd>
- <dt>wf:wasLaunchedBy</dt>
- <dd>
- This second subproperty of <i>prov:wasControlledBy</i> links a
- <i>wf:Process</i> to a <i>prov:Agent</i>, indicating
- which person asked to execute the given
- wf:ProcessDefinition in the specified
- <i>wf:WorkflowEngine</i>.
- </dd>
- <dt>wf:wasSubProcessExecutionOf</dt>
- <dd>
- This subproperty of <i>prov:wasControlledBy</i> links a
- <i>wf:Process</i> to another <i>prov:Process</i>, indicating
- this is a child execution
- <div class="issue">Should there be a general way to state subprocesses? -Stian</div>
- </dd>
- <dt>wf:wasReadFrom</dt>
- <dd>
- <p>
- This subproperty of <i>prov:wasDerivedFrom</i> links a
- <i>wf:Value</i> to the <i>wf:FileValue</i> it was read
- from, typically when used as a workflow input.
- As described for <i>wf:FileValue</i> this distinction
- is done because at the time the workflow input is used
- in the workflow, the file input might be different and
- thus should not be described as an attribute of that
- <i>wf:Value</i>.
- </p>
- <p>
- This property hints of an undescribed "Read file"
- process execution which is not described. This is
- therefore an example of how the provenance asserter
- is limiting the scope of its provenance. The engine
- knows that the file was read, but is not able or
- willing to provide any deeper assertions, because its
- primary scope is at the level of executing workflow
- definitions.
- </p>
- </dd>
- <dt>wf:sawValue</dt>
- <dd>
- A subproperty of <i>prov:wasComplementOf</i> which
- indicates that an <i>wf:Value</i> was
- <i>wf:seenAtPort</i> within an
- <i>wf:ValueAtPort</i>. This ValueAtPort is a complement of the
- pointed at Value because one can consider this
- entity to to have the same attributes, but in
- addition the <i>wf:seenAtPort</i> property is fixed.
- <div class="issue">Should be subproperty of
- not-yet-existing prov:assumedBy or similar -Stian -
- part of <a href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a></div>
- </dd>
-
- <dt>wf:wasSeenAtPort</dt>
- <dd>
- A subproperty of <i>prov:assumedRole</i> (not yet defined in
- PROV ontology) indicating which <i>wf:Port</i> a
- <i>wf:ValueAtPort</i> was seen at. Thus one can see
- at which output port a value was generated, or at
- which input port(s) it was used.
-
- As a functional property this requires a different
- <i>wf:ValueAtPort</i> for each <i>use</i> and
- <i>generation</i> of a value. The
- <i>wf:ValueAtPort</i> is linked to the
- <i>wf:Entity</i> using <i>prov:wasComplementOf</i>
- <div class="issue">Need
- prov:assumedRole in ontology -Stian</div>
- </dd>
- </dl>
- </div>
- <div id="workflow-structure" class="section">
- <h4><span class="secno">3.2.3 </span>Workflow structure</h4>
- <p>
- This ontology includes a simple definition language for
- describing the overall workflow structure. This is not
- meant as a general workflow definition language, but allows
- us to describe <i>process executions</i>, <i>use</i> and
- <i>generation</i> with relation to particular sections of
- the workflow definition.
- </p>
- <dl>
- <dt>wf:ProcessDefinition</dt>
- <dd>A definition of how to execute a process. It will
- typically refer to a command or service which will be
- called. Each process definition also
- <i>wf:definesInput</i>s and <i>wf:definesOutput</i>s.
- </dd>
- <dt>wf:Port</dt>
- <dd>
- A port can be considered as a parameter or return value
- for a process. These are typically given names which are
- unique within a process definition. A value is either
- provided to an input port before execution, or produced
- from an output port after execution.
- </dd>
- <dt>wf:linksTo</dt>
- <dd>
- Ports are connected using links. A link from an output
- port to an input port means that the value received on
- that output will be forwarded to the input of the next
- process. Note that in this simplified ontology links can
- also go from Input to Input and Output to Output, these
- are used to connect workflow ports to processor ports.
- </dd>
- <dt>wf:Input</dt>
- <dd>
- An input port for a process will receive a value which
- will be <i>used</i> by the execution. In a dataflow driven
- workflow model, a process will execute as soon as all its
- defined input ports have been provided with values.
- </dd>
- <dt>wf:Output</dt>
- <dd>
- A process execution might return multiple outputs, for
- instance a table and a diagram. Each of these are declared
- as an output port for that process definition.
- </dd>
- <dt>wf:definesSubProcess</dt>
- <dd>
- <p>
- Scientific workflows can be composed of nested workflows
- which can be shared and reused as components. Some
- workflow systems also allow various execution settings
- on the nested workflow, like looping or parallelisation.
- </p>
- <p>
- In this case a process definition will use
- <i>wf:definesSubProcess</i> to indicate its consistent
- parts, and there will be additional <i>wf:linksTo</i> from
- the input ports of this process definition to the input
- ports of some of its nested sub processes, and vice versa
- for the outputs. The top-level workflow is always such a
- process definition.
- </p>
- </dd>
- </dl>
- </div>
- <div id="example-workflow" class="section">
- <h4><span class="secno">3.2.4 </span>Example workflow</h4>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png" alt="An example workflow with input, three processes, and two outputs.">
- <p>This is an example workflow which defines a workflow
- input <i>input</i>, three processes <i>String_constant</i>,
- <i>Concatenate_two_strings</i> and <i>sha1</i>, and finally
- two workflow outputs <i>combined</i> and <i>sha1</i>. When
- executed, it will execute from top to bottom, first
- concatenating the provided input with the string constant,
- which is returned on the <i>combined</i> output, but also
- provided to the <i>sha1</i> process, which output is given
- to the other workflow port.
- </p>
- <p>
- Using the definition ontology above this workflow can be
- expressed in RDF/XML as:
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:RDF xml:base="http://www.example.com/workflow1#"
- xmlns:impl="http://company.example.org/engine-implementation#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:wf="http://www.example.com/scientific-workflow#">
-
- <wf:ProcessDefinition rdf:about="#workflow">
- <rdf:type rdf:resource="http://company.example.org/engine-implementation#Workflow"/>
- <wf:definesInput>
- <wf:Input rdf:about="#inName">
- <wf:linksTo rdf:resource="#catIn2" />
- </wf:Input>
- </wf:definesInput>
- <wf:definesOutput rdf:resource="#combined" />
- <wf:definesOutput rdf:resource="#sha1" />
- <wf:definesSubProcess>
- <impl:Constant rdf:about="#String_constant">
- <impl:constant>Hello, </impl:constant>
- <wf:definesOutput>
- <wf:Output rdf:about="#constantValue">
- <wf:linksTo rdf:resource="#catIn1"/>
- </wf:Output>
- </wf:definesOutput>
- </impl:Constant>
- </wf:definesSubProcess>
- <wf:definesSubProcess>
- <impl:Command rdf:about="#cat">
- <impl:command>cat</impl:command>
- <wf:definesInput rdf:resource="#catIn1" />
- <wf:definesInput rdf:resource="#catIn2" />
- <wf:definesOutput>
- <wf:Output rdf:about="#catOut">
- <wf:linksTo rdf:resource="#shaIn"/>
- </wf:Output>
- </wf:definesOutput>
- </impl:Command>
- </wf:definesSubProcess>
- <wf:definesSubProcess>
- <impl:Command rdf:about="#shasum">
- <impl:command>shasum</impl:command>
- <wf:definesInput rdf:resource="#shaIn" />
- <wf:definesOutput>
- <wf:Output rdf:about="#shaOut">
- <wf:linksTo rdf:resource="#sha1"/>
- </wf:Output>
- </wf:definesOutput>
- </impl:Command>
- </wf:definesSubProcess>
- </wf:ProcessDefinition>
-</rdf:RDF> </pre></div>
- </div>
- <div id="example-workflow-run" class="section">
- <h4><span class="secno">3.2.5 </span>Example workflow run</h4>
- <p>
- This example shows how using the workflow extensions
- together with PROV can provide the provenance of executing
- the workflow defined above.
- </p>
- <div class="exampleOuter"><pre class="example"><rdf:RDF xmlns="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#"
- xmlns:cnt="http://www.w3.org/2011/content#"
- xmlns:foaf="http://xmlns.com/foaf/0.1/"
- xmlns:prov="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:wf="http://www.example.com/scientific-workflow#"
- xmlns:base="http://www.example.com/run1#" >
-
- <Agent rdf:about="#aUser">
- <rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Person"/>
- <foaf:name>Stian Soiland-Reyes</foaf:name>
- </Agent>
-
- <wf:WorkflowEngine rdf:about="#workflowEngine" />
-
- <wf:FileValue rdf:about="#inputFile">
- <wf:file>/tmp/myinput.txt</wf:file>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>Steve</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:FileValue>
-
- <wf:Value rdf:about="#input">
- <wf:wasReadFrom rdf:resource="#inputFile"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>Steve</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:Process rdf:about="#workflowRun">
- <used>
- <wf:ValueAtPort>
- <wf:sawValue rdf:resource="#input"/>
- <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#inName"/>
- </wf:ValueAtPort>
- </used>
- <wf:ranInWorkflowEngine rdf:resource="#workflowEngine"/>
- <wf:wasLaunchedBy rdf:resource="#aUser"/>
- <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#workflow"/>
- </wf:Process>
-
- <wf:Process rdf:about="#constant">
- <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
- <wf:wasDefinedBy
- rdf:resource="http://www.example.com/workflow1#String_Constant"/>
- </wf:Process>
-
- <wf:Value rdf:about="#hello">
- <wasGeneratedBy rdf:resource="#constant"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:chars>Hello, </cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:ValueAtPort rdf:about="#helloValue">
- <wasGeneratedBy rdf:resource="#constant"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:chars>Hello, </cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- <wf:sawEntity rdf:resource="#hello"/>
- </wf:ValueAtPort>
-
- <wf:Process rdf:about="#combine">
- <used>
- <wf:ValueAtPort>
- <wf:sawValue rdf:resource="#hello"/>
- <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#catIn1"/>
- </wf:ValueAtPort>
- </used>
- <used>
- <wf:ValueAtPort>
- <wf:sawValue rdf:resource="#input"/>
- <wf:seenAtPort rdf:resource="http://www.example.com/workflow1#catIn2"/>
- </wf:ValueAtPort>
- </used>
- <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
- <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#cat"/>
- </wf:Process>
-
- <wf:Value rdf:about="#combined">
- <wasGeneratedBy rdf:resource="#combine"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:chars>Hello, Steve</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:Process rdf:about="#shasum">
- <used rdf:resource="#combined"/>
- <wf:wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
- <wf:wasDefinedBy rdf:resource="http://www.example.com/workflow1#shasum"/>
- </wf:Process>
-
- <wf:Value rdf:about="#sha1">
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- </wf:Value>
-
- <wf:ValueAtPort rdf:about="#sha1OutputFromShasum">
- <wasGeneratedBy rdf:resource="#shasum"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- <wf:sawValue rdf:resource="#sha1"/>
- <wf:wasSeenAt rdf:resource="http://www.example.com/workflow1#shaOut"/>
- </wf:ValueAtPort>
-
- <wf:ValueAtPort rdf:about="#sha1OutputFromWorkflow">
- <wasGeneratedBy rdf:resource="#workflowRun"/>
- <wf:value>
- <cnt:ContentAsText>
- <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
- <cnt:chars>a33d1fb1658d4fbf017de59ab67437a3eb5ff50d</cnt:chars>
- </cnt:ContentAsText>
- </wf:value>
- <wf:sawValue rdf:resource="#sha1"/>
- <wf:wasSeenAt rdf:resource="http://www.example.com/workflow1#sha1"/>
- </wf:ValueAtPort>
-
-</rdf:RDF> </pre>
- <em>Example available as
- <a href="examples/ontology-extensions/workflow/workflow.rdf">RDF/XML</a>
- and
- <a href="examples/ontology-extensions/workflow/workflow.ttl">Turtle</a>
- </em>
- </div>
- <p> Note that for brevity, the example above does not show the inferred classes
- and properties from the PROV ontology. For interoperability, applications
- should also expressed such inferred statements in its
- serialisations, so that the provenance can be read without using
- OWL2 inferencing and the customized ontologies.
- See the <a href="examples/ontology-extensions/workflow/workflow-inferred.rdf">workflow-inferred.rdf</a>
- for the complete example showing both domain-specific and PROV ontology terms
- used side by side.
- </p>
- </div>
- </div>
- </div>
- <div id="formal-semantics-of-the-prov-ontology" class="section">
- <!--OddPage--><h2><span class="secno">4. </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>
-
-
-
- <div id="rdf-semantics-for-prov-ontology" class="section">
- <h3><span class="secno">4.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 rdfs:subClassOf and rdfsubPropertyOf are transitive properties, hence provenance assertions, in form of RDF triples, using a specialized sub class or sub property can be inferred to be true for their parent class or parent property. For example, in the provenance scenario, though alice and bob are asserted to be individuals of the class Journalist, we can infer that they are also individuals of the PROV ontology class Agent and Entity. Given,
- </p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#alice">
- <rdf:type rdf:resource="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist"/>
-</rdf:Description></pre>
- </div>
- <p>and</p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFileOntology.owl#Journalist">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
-</rdf:Description>
-<rdf:Description rdf:about="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
-</rdf:Description></pre>
- </div>
- <p>we can infer that</p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#alice">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Agent"/>
-</rdf:Description></pre>
- </div>
- <p>and</p>
- <div class="exampleOuter">
- <pre class="example"><rdf:Description rdf:about="http://www.w3.org/PROV/CrimeFile#alice">
- <rdf:type rdf:resource="http://www.w3.org/PROV/ProvenanceOntology.owl#Entity"/>
-</rdf:Description></pre>
- </div>
- </div>
-
-
-
- <div id="owl2-semantics-for-prov-ontology" class="section">
- <h3><span class="secno">4.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="provenance-specific-entailments-supported-by-prov-ontology" class="section">
- <h3><span class="secno">4.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 specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.</p>
- <div id="provenance-constraint-on-processexecution" class="section">
- <h4><span class="secno">4.3.1 </span>Provenance constraint on ProcessExecution</h4>
- <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#processexecution">ProcessExecution.</a> </p>
- <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>
- </div>
- <div id="provenance-constraint-on-wasgeneratedby--generation-affects-attributes" class="section">
- <h4><span class="secno">4.3.2 </span>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</h4>
- <p>The PROV-DM describes a constraint on wasGeneratedBy that associates the values of attributes of an Entity with the ProcessExecution that generated the Entity.</p>
- <div class="issue">"Given a process execution pe, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by pe and the entities used by pe. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
- </div>
- <div id="provenance-constraint-on-wasgeneratedby--generation-pe-ordering" class="section">
- <h4><span class="secno">4.3.3 </span>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
- <p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of the PE instance.</p>
- <div class="issue">"Given an assertion wasGeneratedBy(x,pe,r) or wasGeneratedBy(x,pe,r,t), one can infer that the generation of the thing denoted by x precedes the end of pe and follows the beginning of pe." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122</a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
- </div>
- <div id="provenance-constraint-on-wasgeneratedby--generation-unicity" class="section">
- <h4><span class="secno">4.3.4 </span>Provenance constraint on wasGeneratedBy (generation-unicity)</h4>
- <p>The PROV-DM describes a constraint on wasGeneratedBy that asserts that given an account, only one PE instance can be associated to an Entity instance by the property wasGeneratedBy.</p>
- <div class="issue">"Given an entity expression denoted by e, two process execution expressions denoted by pe1 and pe2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then pe1=pe2 and q1=q2." This is <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
- </div>
- <div id="provenance-constraint-on-used--use-attributes" class="section">
- <h4><span class="secno">4.3.5 </span>Provenance constraint on Used (use-attributes)</h4>
- <p>A constraint is defined for the Used relation in PROV-DM, that makes it necessary for an attribute-value to be true for an Entity instance linked to a ProcessExecution instance by relation Used.
- </p>
- <div class="issue">"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the existence of an attribute-value pair in the entity expression identified by e is a pre-condition for the termination of the activity represented by the process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
- </div>
- <div id="provenance-constraint-on-used--use-pe-ordering" class="section">
- <h4><span class="secno">4.3.6 </span>Provenance constraint on Used (use-pe-ordering)</h4>
- <p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a ProcessExecution instance pe by Used relation) to be "used" before pe terminates and also the "generation" of e precedes "use" of e.
- </p>
- <div class="issue">"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by pe and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
- </div>
- <ul>
-<li><a id="PROV:0006" href="#PROV:0006">PROV:0006</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
- assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds, one can
-infer that the use of the thing denoted by <b>e</b> precedes the end
-of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
-can infer that the generation of the thing denoted by <b>e</b> always precedes
-its use." (<a href="../model/ProvenanceModel.html#PROV:0006">link</a>)
-</li>
-
-<li> <a id="PROV:0007" href="#PROV:0007">PROV:0007</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, if and only if:
- the values of some attributes
-of <b>e2</b> are partly or fully determined by the values of some
-attributes of <b>e1</b>." (<a href="../model/ProvenanceModel.html#PROV:0007">link</a>)
-</li>
-
-<li><a id="PROV:0008" href="#PROV:0008">PROV:0008</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, then
-the use
-of characterized thing denoted by <b>e1</b> precedes the generation of
-the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0008">link</a>)
-</li>
-
-<li><a id="PROV:0009" href="#PROV:0009">PROV:0009</a> "If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
-such that:
- <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b>." (<a href="../model/ProvenanceModel.html#PROV:0009">link</a>)
-</li>
-
-
-<li><a id="PROV:0010" href="#PROV:0010">PROV:0010</a> "If <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also hold." (<a href="../model/ProvenanceModel.html#PROV:0010">link</a>)
-</li>
-
-<li><a id="PROV:0011" href="#PROV:0011">PROV:0011</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, and role <b>r2</b>,
-if <b>wasDerivedFrom(e2,e1)</b> and <b>wasGeneratedBy(e2,pe,r2)</b> hold, then there exists a role <b>r1</b>,
-such that <b>used(pe,e1,r1)</b> also holds." (<a href="../model/ProvenanceModel.html#PROV:0011">link</a>)
-</li>
-
-<li><a id="PROV:0012" href="#PROV:0012">PROV:0012</a> "Given two entities <b>e1</b> and <b>e2</b>, if the assertion <b>isEventuallyDerivedFrom(e2,e1)</b>
- holds, then:
-generation of the characterized thing denoted by <b>e1</b> precedes the generation of
-the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0012">link</a>)
-</li>
-
-<li><a id="PROV:0013" href="#PROV:0013">PROV:0013</a> "An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <em>only if</em>:
- <ol>
- <li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B <em class="rfc2119" title="must">must</em> be consistent with that mapping</li>
- <li>B has some attribute that A does not have" (<a href="../model/ProvenanceModel.html#PROV:0013">link</a>) </li>
- </ol>
-</li>
-
-<li><a id="PROV:0014" href="#PROV:0014">PROV:0014</a> "Given a process execution <b>pe</b> and entity <b>e</b>, <b>hadPariticipant(pe,e)</b> holds if and only if:
- <ul>
- <li> <b>used(pe,e)</b> holds, or</li>
- <li> <b>wasControlledBy(pe,e)</b> holds, or</li>
- <li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and <b>hadParticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
- </ul>
-</li>
-</ul>
-
-<div class="note">The above constraints are extracted from the
- ProvenanceModel document. The text below should be kept consistent
- with the other document, with bidirectional links. The plan is to
- insert formalizations of these constraints once the OWL
- ontology/vocabulary is mature enough to permit this.
-
- If a constraint is changed in the model document, please copy the
- new version here, and check whether it is still consistent with the
- formalization (if any).
-
- If a constraint is dropped, please mark it as "defunct" - don't
- delete it!
- </div>
- </div>
- </div>
-
-
-
- <div class="appendix section" id="acknowledgements">
- <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
- <p>
- The Provenance Working Group Members.
- </p>
- </div>
-
-
-
-<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-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>
-</dd><dt id="bib-OWL2-SYNTAX">[OWL2-SYNTAX]</dt><dd>Boris Motik; Peter F. Patel-Schneider; Bijan Parsia. <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/"><cite>OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/">http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/</a>
-</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd>Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
-</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-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-DM">[PROV-DM]</dt><dd>Luc Moreau, Paolo Missier<a href="http://www.w3.org/TR/owl2-direct-semantics"><cite>PROV Conceptual Model</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html</a>
-</dd><dt id="bib-PROV-Ontology-Namespace">[PROV-Ontology-Namespace]</dt><dd>TBD<a href="https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl"><cite>PROV Ontology Namespace</cite></a>. 2011, Work in progress. URL: <a href="https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl">https://dvcs.w3.org/hg/prov/file/4452648d5a9b/ontology/ProvenanceOntology.owl</a>
-</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/provenance-access.html"><cite>Provenance Access and Query</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/provenance-access.html">http://dvcs.w3.org/hg/prov/tip/paq/provenance-access.html</a>
-</dd></dl></div></div></body><style type="text/css">embed[type*="application/x-shockwave-flash"],embed[src*=".swf"],object[type*="application/x-shockwave-flash"],object[codetype*="application/x-shockwave-flash"],object[src*=".swf"],object[codebase*="swflash.cab"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"],object[classid*="d27cdb6e-ae6d-11cf-96b8-444553540000"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"]{ display: none !important;}</style></html>