--- a/model/diff.html Mon Jul 09 16:34:06 2012 -0400
+++ b/model/diff.html Mon Jul 09 16:35:36 2012 -0400
@@ -520,7 +520,7 @@
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
-</style><style type="text/css"><span class="insert">
+</style><style type="text/css">
/* --- EDITORIAL NOTES --- */
.component1-color {
background-color: rgba(255,42,42,0.2);
@@ -970,17 +970,17 @@
font-size:120%;
font-family: monospace;
}
-</span></style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" 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-DM: The PROV Data Model</h1><h2 id="subtitle"><span class="delete">For internal release</span><span class="insert">Final review before Last Call Vote</span> (WD6) (<a href="diff.html">Diffs since last release</a>)</h2><h2 id="w3c-editor-s-draft-28-june-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft <span class="delete">14</span><span class="insert">28</span> June 2012</h2><dl><dt>This version:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120503/">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" 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-DM: The PROV Data Model</h1><h2 id="subtitle">Final review before Last Call Vote (WD6) (<a href="diff.html">Diffs since last release</a>)</h2><h2 id="w3c-editor-s-draft-09-july-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft <span class="delete">28 June</span><span class="insert">09 July</span> 2012</h2><dl><dt>This version:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120503/">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
<dt>Authors:</dt><dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
<dd><span>Reza B'Far</span>, Oracle Corporation</dd>
<dd><span>Stephen Cresswell</span>, legislation.gov.uk</dd>
-<dd><span class="delete">Tom De Nies</span><a href="http://users.ugent.be/~scoppens/"><span class="insert">Sam Coppens</span></a>, IBBT - Ghent University</dd>
+<dd><span>Sam Coppens</span>, IBBT - Ghent University</dd>
<dd><a href="http://www.isi.edu/~gil/">Yolanda Gil</a>, Invited Expert</dd>
<dd><a href="http://www.few.vu.nl/~pgroth/">Paul Groth</a>, VU University of Amsterdam</dd>
<dd><span>Graham Klyne</span>, University of Oxford</dd>
-<dd><span class="delete">Tim</span><a href="http://tw.rpi.edu/instances/TimLebo"><span class="insert">Timothy</span> Lebo</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://tw.rpi.edu/instances/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute</dd>
<dd><a href="http://tw.rpi.edu/web/person/JamesMcCusker">Jim McCusker</a>, Rensselaer Polytechnic Institute</dd>
<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, Invited Expert</dd>
<dd><a href="http://www.rpi.edu/research/ccni/">James Myers</a>, Rensselaer Polytechnic Institute</dd>
@@ -990,7 +990,7 @@
<div id="abstract" class="introductory section"><h2>Abstract</h2>
<p>
-Provenance is information about entities, activities, and <span class="delete">people,</span><span class="insert">people</span>
+Provenance is information about entities, activities, and people
involved in producing a piece of data or thing, which can be used
to form assessments about its quality, reliability or trustworthiness.
PROV-DM is the conceptual data model that forms a basis for the <acronym title="World Wide Web Consortium">W3C</acronym>
@@ -999,12 +999,11 @@
extended structures catering for more specific uses of provenance.
PROV-DM is organized in six components, respectively dealing with:
(1) entities and activities, and the time at which they were created, used, or ended;
-(2) <span class="insert">derivations of entities from entities;
-(3) </span>agents bearing responsibility for entities that were generated and activities that happened;
-<span class="delete">(3) derivations of</span><span class="insert">(4) a notion of bundle, a mechanism to support provenance of provenance; and,
-(5) properties to link</span> entities <span class="delete">from entities;
-(4) properties</span><span class="insert">that refer</span> to <span class="delete">link entities that refer to </span>the same thing;<span class="delete">
-(5) a notion of bundle, a mechanism to support provenance of provenance; and,</span>
+(2) derivations of entities from entities;
+(3) agents bearing responsibility for entities that were generated and activities that happened;
+(4) a notion of bundle, a mechanism to support provenance of provenance;<span class="insert">
+(5) properties to link entities that refer to the same thing;</span> and,<span class="delete">
+(5) properties to link entities that refer to the same thing;</span>
(6) collections forming a logical structure for its members.
</p>
@@ -1024,10 +1023,15 @@
<h4 id="intended-to-be-last-call--tbc">Intended to be Last Call (TBC)</h4>
<p>This is the fifth public release of the PROV-DM document.
Publication as Last Call working draft means that
-the Working Group believes that it has satisfied the relevant technical requirements outlined in its charter on this document. The design is not expected to change significantly, going forward, and now is the key time for external review, before the implementation phase.</p>
-<h4 id="please-comment-by--date-tbd">Please Comment By (date TBD)</h4>
+the Working Group believes that it has satisfied the relevant technical requirements outlined in its charter on this document. The design is not expected to change significantly, going forward, and now is the key time for external <span class="delete">review, before the</span><span class="insert">review.</span></p>
+
+<p><span class="insert">This specification identifies one </span><a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi"><span class="insert">feature at risk</span></a><span class="insert">: </span><a href="#term-mention"><span class="insert">Mention</span></a><span class="insert"> might be removed from PROV if</span> implementation <span class="delete">phase.</span><span class="insert">experience reveals problems with supporting this construct.</span></p>
+
+
+
+<h4 id="please-comment-by-2012-09-13--date-tbc">Please Comment By <span class="insert">2012-09-13 </span>(date <span class="delete">TBD)</span><span class="insert">TBC)</span></h4>
<p>The PROV Working group seeks public feedback on this Working Draft.
-The end date of the Last Call review period is TBD, and we would appreciate comments by that date to public-prov-comments@w3.org
+The end date of the Last Call review period is <span class="delete">TBD,</span><b><span class="insert">2012-09-13 (TBC)</span></b><span class="insert">,</span> and we would appreciate comments by that date to public-prov-comments@w3.org
</p>
<h4 id="prov-family-of-specifications">PROV Family of Specifications</h4>
@@ -1037,7 +1041,7 @@
<li> PROV-DM, the PROV data model for provenance (this document);</li>
<li> PROV-CONSTRAINTS, a set of constraints applying to the PROV data model;</li>
<li> PROV-N, a notation for provenance aimed at human consumption;</li>
-<li> PROV-O, the PROV ontology, an <span class="delete">OWL-RL</span><span class="insert">OWL2</span> ontology allowing the mapping of PROV to RDF;</li>
+<li> PROV-O, the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF;</li>
<li> PROV-AQ, the mechanisms for accessing and querying provenance; </li>
<li> PROV-PRIMER, a primer for the PROV data model;</li>
<li> PROV-SEM, a formal semantics for the PROV data model;</li>
@@ -1046,14 +1050,14 @@
<h4 id="how-to-read-the-prov-family-of-specifications">How to read the PROV Family of Specifications</h4>
<ul>
<li>The primer is the entry point to PROV offering an introduction to the provenance model.</li>
-<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an OWL-RL ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. PROV-SEM provides a mathematical semantics.</li>
+<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an <span class="delete">OWL-RL</span><span class="insert">OWL2</span> ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. PROV-SEM provides a mathematical semantics.</li>
<li>The XML community should focus on PROV-XML defining an XML schema for PROV. Further details can also be found in PROV-DM, PROV-CONSTRAINTS, and PROV-SEM.</li>
<li>Developers seeking to retrieve or publish provenance should focus on PROV-AQ.</li>
<li>Readers seeking to implement other PROV serializations
should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
</ul>
<p>This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction<br>
-</a><ul class="toc"><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.1 </span>Structure of this Document</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Notational Conventions</a></li></ul></li><li class="tocline"><a href="#section-prov-overview" class="tocxref"><span class="secno">2. </span>PROV Overview</a><ul class="toc"><li class="tocline"><a href="#core-structures" class="tocxref"><span class="secno">2.1 </span>PROV Core Structures</a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno">2.1.1 </span>Entity and Activity</a></li><li class="tocline"><a href="#section-derivation" class="tocxref"><span class="secno">2.1.2 </span>Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-delegation" class="tocxref"><span class="secno">2.1.3 </span>Agents and Responsibility</a></li></ul></li><li class="tocline"><a href="#section-extended-structures" class="tocxref"><span class="secno">2.2 </span>PROV Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-mechanisms" class="tocxref"><span class="secno">2.2.1 </span>Mechanisms to Define Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-approach-subtyping" class="tocxref"><span class="secno">2.2.1.1 </span>Subtyping</a></li><li class="tocline"><a href="#section-prov-extended-approach-expanded-relation" class="tocxref"><span class="secno">2.2.1.2 </span>Expanded Relations</a></li><li class="tocline"><a href="#section-prov-extended-approach-optional-identification" class="tocxref"><span class="secno">2.2.1.3 </span>Optional Identification</a></li><li class="tocline"><a href="#section-prov-extended-approach-further-relations" class="tocxref"><span class="secno">2.2.1.4 </span>Further Relations</a></li></ul></li><li class="tocline"><a href="#section-provenance-of-provnance" class="tocxref"><span class="secno">2.2.2 </span>Provenance of Provenance</a></li><li class="tocline"><a href="#section-collections" class="tocxref"><span class="secno">2.2.3 </span>Collections</a></li></ul></li><li class="tocline"><a href="#section-overview-components" class="tocxref"><span class="secno">2.3 </span>Modular Organization</a></li></ul></li><li class="tocline"><a href="#prov-notation" class="tocxref"><span class="secno">3. </span>The Provenance Notation</a></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno">4. </span>Illustration of PROV-DM by an Example</a><ul class="toc"><li class="tocline"><a href="#section-example-one" class="tocxref"><span class="secno">4.1 </span><span class="insert">Example: </span>The Authors View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno">4.2 </span><span class="insert">Example: </span>The Process View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno">4.3 </span><span class="insert">Example: </span>Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno">5. </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">5.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-entity" class="tocxref"><span class="secno">5.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">5.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">5.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">5.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">5.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">5.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">5.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">5.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">5.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">5.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-revision" class="tocxref"><span class="secno">5.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno">5.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-primary-source" class="tocxref"><span class="secno">5.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">5.3 </span>Component 3: <span class="delete">Agents</span><span class="insert">Agents, Responsibility,</span> and <span class="delete">Responsibility</span><span class="insert">Influence</span></a><ul class="toc"><li class="tocline"><a href="#term-agent" class="tocxref"><span class="secno">5.3.1 </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno">5.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">5.3.3 </span>Association</a></li><li class="tocline"><a href="#term-delegation" class="tocxref"><span class="secno">5.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-influence" class="tocxref"><span class="secno">5.3.5 </span><span class="delete">Trace</span><span class="insert">Influence</span></a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">5.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-bundle" class="tocxref"><span class="secno">5.4.1 </span>Bundle constructor</a></li><li class="tocline"><a href="#term-bundle-entity" class="tocxref"><span class="secno">5.4.2 </span>Bundle Type</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">5.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno">5.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno">5.5.2 </span>Alternate</a></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">5.5.3 </span><span class="delete">Contextualization</span><span class="insert">Mention</span></a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">5.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno">5.6.1 </span>Collection</a></li><li class="tocline"><a href="#term-collection-membership" class="tocxref"><span class="secno">5.6.2 </span>Collection Memberhsip<span class="delete">5.6.3 </span><span class="delete">Dictionary</span><span class="delete">5.6.4 </span><span class="delete">Dictionary Membership</span><span class="delete">5.6.5 </span><span class="delete">Dictionary Insertion</span><span class="delete">5.6.6 </span><span class="delete">Dictionary Removal</span></a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno">5.7 </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno">5.7.1 </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno">5.7.2 </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno">5.7.2.1 </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno">5.7.2.2 </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno">5.7.2.3 </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno">5.7.2.4 </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno">5.7.2.5 </span>prov:value</a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno">5.7.3 </span>Value</a></li><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno">5.7.4 </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno">5.7.5 </span>Qualified Name</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno">6. </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno">7. </span>Creating Valid Provenance</a></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>
+</a><ul class="toc"><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.1 </span>Structure of this Document</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Notational Conventions</a></li><li class="tocline"><a href="#namespaces" class="tocxref"><span class="secno"><span class="insert">1.3 </span></span><span class="insert">Namespaces</span></a></li></ul></li><li class="tocline"><a href="#section-prov-overview" class="tocxref"><span class="secno">2. </span>PROV Overview</a><ul class="toc"><li class="tocline"><a href="#core-structures" class="tocxref"><span class="secno">2.1 </span>PROV Core Structures</a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno">2.1.1 </span>Entity and Activity</a></li><li class="tocline"><a href="#section-derivation" class="tocxref"><span class="secno">2.1.2 </span>Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-delegation" class="tocxref"><span class="secno">2.1.3 </span>Agents and Responsibility</a></li></ul></li><li class="tocline"><a href="#section-extended-structures" class="tocxref"><span class="secno">2.2 </span>PROV Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-mechanisms" class="tocxref"><span class="secno">2.2.1 </span>Mechanisms to Define Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-approach-subtyping" class="tocxref"><span class="secno">2.2.1.1 </span>Subtyping</a></li><li class="tocline"><a href="#section-prov-extended-approach-expanded-relation" class="tocxref"><span class="secno">2.2.1.2 </span>Expanded Relations</a></li><li class="tocline"><a href="#section-prov-extended-approach-optional-identification" class="tocxref"><span class="secno">2.2.1.3 </span>Optional Identification</a></li><li class="tocline"><a href="#section-prov-extended-approach-further-relations" class="tocxref"><span class="secno">2.2.1.4 </span>Further Relations</a></li></ul></li><li class="tocline"><a href="#section-provenance-of-provnance" class="tocxref"><span class="secno">2.2.2 </span>Provenance of Provenance</a></li><li class="tocline"><a href="#section-collections" class="tocxref"><span class="secno">2.2.3 </span>Collections</a></li></ul></li><li class="tocline"><a href="#section-overview-components" class="tocxref"><span class="secno">2.3 </span>Modular Organization</a></li></ul></li><li class="tocline"><a href="#prov-notation" class="tocxref"><span class="secno">3. </span>The Provenance Notation</a></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno">4. </span>Illustration of PROV-DM by an Example</a><ul class="toc"><li class="tocline"><a href="#section-example-one" class="tocxref"><span class="secno">4.1 </span>Example: The Authors View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno">4.2 </span>Example: The Process View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno">4.3 </span>Example: Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno">5. </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">5.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-entity" class="tocxref"><span class="secno">5.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">5.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">5.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">5.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">5.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">5.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">5.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">5.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">5.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">5.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-revision" class="tocxref"><span class="secno">5.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno">5.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-primary-source" class="tocxref"><span class="secno">5.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">5.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-agent" class="tocxref"><span class="secno">5.3.1 </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno">5.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">5.3.3 </span>Association</a></li><li class="tocline"><a href="#term-delegation" class="tocxref"><span class="secno">5.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-influence" class="tocxref"><span class="secno">5.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">5.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-bundle" class="tocxref"><span class="secno">5.4.1 </span>Bundle constructor</a></li><li class="tocline"><a href="#term-bundle-entity" class="tocxref"><span class="secno">5.4.2 </span>Bundle Type</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">5.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno">5.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno">5.5.2 </span>Alternate</a></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">5.5.3 </span>Mention</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">5.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno">5.6.1 </span>Collection</a></li><li class="tocline"><a href="#term-collection-membership" class="tocxref"><span class="secno">5.6.2 </span>Collection <span class="delete">Memberhsip</span><span class="insert">Membership</span></a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno">5.7 </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno">5.7.1 </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno">5.7.2 </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno">5.7.2.1 </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno">5.7.2.2 </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno">5.7.2.3 </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno">5.7.2.4 </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno">5.7.2.5 </span>prov:value</a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno">5.7.3 </span>Value</a></li><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno">5.7.4 </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno">5.7.5 </span>Qualified Name</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno">6. </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno">7. </span>Creating Valid Provenance</a></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>
@@ -1110,10 +1114,10 @@
The PROV data model has a modular design and is structured according to six components covering various facets of provenance:</p>
<ul>
<li> component 1: entities and activities, and the time at which they were created, used, or ended;
-</li><li> component 2: <span class="delete">agents bearing responsibility for</span><span class="insert">derivations of</span> entities <span class="delete">that were generated and activities that happened;</span><span class="insert">from others;</span>
-</li><li> component 3: <span class="delete">derivations of</span><span class="insert">agents bearing responsibility for</span> entities <span class="delete">from others;</span><span class="insert">that were generated and activities that happened;</span>
-</li><li> component 4: <span class="delete">properties</span><span class="insert">bundles, a mechanism</span> to <span class="delete">link entities that refer to a same thing;</span><span class="insert">support provenance of provenance;</span>
-</li><li> component 5: <span class="delete">bundles,</span><span class="insert">properties to link entities that refer to</span> a <span class="delete">mechanism to support provenance of provenance;</span><span class="insert">same thing;</span>
+</li><li> component 2: derivations of entities from others;
+</li><li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
+</li><li> component 4: bundles, a mechanism to support provenance of provenance;
+</li><li> component 5: properties to link entities that refer to a same thing;
</li><li> component 6: collections forming a logical structure for its members.
</li></ul>
@@ -1167,6 +1171,19 @@
[<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
+
+
+<p><span class="insert">
+ Examples throughout this document use the PROV-N Provenance
+ Notation, briefly introduced in </span><a href="#prov-notation"><span class="insert">Section 3</span></a><span class="insert"> and specified fully in a separate document [</span><cite><a class="bibref" rel="biblioentry" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite><span class="insert">].</span></p>
+
+
+
+</div>
+
+<div id="namespaces" class="section">
+<h3><span class="secno"><span class="insert">1.3 </span></span><span class="insert">Namespaces</span></h3>
+
<p>
The following namespaces prefixes are used throughout this document.
@@ -1181,9 +1198,9 @@
</tbody></table>
</div>
-<p>
+<span class="delete">
Examples throughout this document use the PROV-N Provenance
- Notation, briefly introduced in <a href="#prov-notation">Section 3</a> and specified fully in a separate document [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-N">PROV-N</a></cite>].</p>
+ Notation, briefly introduced in </span><span class="delete">Section 3</span><span class="delete"> and specified fully in a separate document [</span><span class="delete">PROV-N</span><span class="delete">].</span>
</div>
@@ -1196,7 +1213,7 @@
<h2><span class="secno">2. </span>PROV Overview</h2>
<p>This section introduces provenance concepts with informal explanations and illustrative
-examples. PROV distinguishes <em>core structures</em>, forming the essence of provenance, from <em>extended structures</em> catering for more advanced uses of provenance. Core and extended structures are respectively presented in <a href="#core-structures">Section 2.1</a> and <a href="#section-extended-structures">Section 2.2</a>. Furthermore, the PROV data model is organized according to components, which form thematic groupings of concepts (see <a href="#section-overview-components">Section 2.3</a>). A <em>provenance description</em> is an instance of a core and extended provenance structure described below.
+examples. PROV distinguishes <em>core structures</em>, forming the essence of provenance, from <em>extended structures</em> catering for more <span class="delete">advanced</span><span class="insert">specific</span> uses of provenance. Core and extended structures are respectively presented in <a href="#core-structures">Section 2.1</a> and <a href="#section-extended-structures">Section 2.2</a>. Furthermore, the PROV data model is organized according to components, which form thematic groupings of concepts (see <a href="#section-overview-components">Section 2.3</a>). A <em>provenance description</em> is an instance of a core and extended provenance structure described below.
</p>
@@ -1213,17 +1230,18 @@
<div style="text-align: center; ">
- <span class="figure" id="prov-core-structures-top" style="max-width: 70%; ">
-
-<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; ">
-<p><span class="figcaption" id="prov-core-structures">Figure 1: PROV Core Structures</span></p>
+
+ <span class="figure" id="prov-core-structures-top" style="max-width: 70%; ">
+
+<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; "><br>
+<span class="figcaption" id="prov-core-structures">Figure 1: PROV Core Structures</span>
</span>
</div>
<p>The concepts found in the core of PROV are introduced in the rest of this section.
They are summarized in <a href="#overview-types-and-relations">Table 2</a>, where they are categorized as
type or relation.
- The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen. In the core of PROV, all relations are binary.
+ The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding <span class="delete">name.</span><span class="insert">name, as it appears in Figure 1.</span> Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen. In the core of PROV, all relations are binary.
</p>
@@ -1240,7 +1258,7 @@
<tr><td><a href="#concept-activity" class="internalDFN">Activity</a></td><td><a title="dfn-Activity" href="#dfn-activity" class="internalDFN">Activity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
<tr><td><a href="#concept-agent" class="internalDFN">Agent</a></td><td><a title="dfn-agent" href="#dfn-agent" class="internalDFN">Agent</a></td><td style="text-align: center;"><a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a></td></tr>
<tr>
-<td><a href="#concept-generation" class="internalDFN">Generation</a></td><td rowspan="7" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy" href="#dfn-wasgeneratedby" class="internalDFN">wasGeneratedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
+<td><a href="#concept-generation" class="internalDFN">Generation</a></td><td rowspan="7" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy" href="#dfn-wasgeneratedby" class="internalDFN"><span class="delete">wasGeneratedBy</span><span class="insert">WasGeneratedBy</span></a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
<tr><td><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a title="used" href="#dfn-used" class="internalDFN">Used</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
<tr><td><a href="#concept-communication" class="internalDFN">Communication</a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN">WasInformedBy</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
<tr><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td><td><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN">WasDerivedFrom</a></td><td style="text-align: center;"><a class="section-ref" href="#section-derivation"><span>Section 2.1.2</span></a></td></tr>
@@ -1273,7 +1291,7 @@
<h4><span class="secno">2.1.1 </span>Entity and Activity</h4>
-<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed aspect. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
+<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed <span class="delete">aspect.</span><span class="insert">aspects.</span> The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
physical things such as a mountain, a building, a printed book, or a car as well as abstract concepts and ideas.
</p>
@@ -1360,7 +1378,7 @@
<p>
<span class="glossary-ref">
- <span class="dfn">Communication</span> is the exchange of <span class="delete">an</span><span class="insert">some</span> unspecified entity by two activities, one activity using some entity generated by the other. </span> [<a href="#term-Communication">Detailed specification</a>]</p>
+ <span class="dfn">Communication</span> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </span> [<a href="#term-Communication">Detailed specification</a>]</p>
@@ -1385,7 +1403,7 @@
</p>
<p>
-<span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a <span class="delete">pre-exisiting</span><span class="insert">pre-existing</span> entity.</span>
+<span class="glossary-ref"> A <span class="dfn">derivation</span> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</span>
[<a href="#term-Derivation">Detailed specification</a>]</p>
@@ -1427,7 +1445,7 @@
for deciding whether something is reliable and/or trustworthy is
knowing who or what <em>was reponsible</em> for its production. Data published by
a respected independent organization may be considered more
- trustworthy <span class="delete">that</span><span class="insert">than</span> that from a lobby organization; a claim by a
+ trustworthy than that from a lobby organization; a claim by a
well-known scientist with an established track record may be more
believed than a claim by a new student; a calculation performed by an
established software library may be more reliable than by a one-off
@@ -1435,7 +1453,7 @@
<p>
<span class="glossary-ref">
- An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking <span class="delete">place</span><span class="insert">place, for the existence of an entity,</span> or for <span class="delete">the existence of an entity.</span><span class="insert">another agent's activity.</span> </span> [<a href="#term-agent">Detailed specification</a>]
+ An <span class="dfn">agent</span> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </span> [<a href="#term-agent">Detailed specification</a>]
An agent <em class="rfc2119" title="may">may</em> be a particular type of entity or activity. This means that the model can be
used to express provenance of the agents themselves.
</p>
@@ -1608,7 +1626,7 @@
<div id="section-prov-extended-approach-further-relations" class="section">
<h5><span class="secno">2.2.1.4 </span>Further Relations</h5>
-<p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations.</p>
+<p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing <span class="delete">relations.</span><span class="insert">relations (such as </span><a href="#concept-specialization" class="internalDFN"><span class="insert">specialization</span></a><span class="insert">, </span><a href="#concept-alternate" class="internalDFN"><span class="insert">alternate</span></a><span class="insert">).</span></p>
</div>
@@ -1626,7 +1644,7 @@
<span class="glossary-ref">
A <span class="dfn">bundle</span> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span>
-</p><p><span class="insert">
+</p><p>
For users to decide whether they can place their trust in
something, they may want to analyze its provenance, but also determine
the agent its provenance is attributed to, and when it was
@@ -1634,17 +1652,11 @@
Hence, provenance is also
regarded as an entity (of type Bundle), by which provenance of provenance can then be
expressed.
-</span></p>
+</p>
<div class="anexample conceptexample" id="bundle-example"><div class="anexampleTitle">Example 13<sup><a class="internalDFN" href="#bundle-example"><span class="diamond"> ◊</span></a></sup></div>
<p>
-<span class="delete">For users</span><span class="insert">In a decision making situation, decision makers may be presented with the same piece of knowledge, issued by multiple sources. In order</span> to <span class="delete">decide</span><span class="insert">validate this piece of knowledge, decision makers can consider its provenance, but also the provenance of their provenance, which may help determine</span> whether <span class="delete">they</span><span class="insert">it</span> can <span class="delete">place their trust in
-a resource, they may want to analyze the resource's provenance, but also determine
-who its provenance is attributed to, and when it was
-generated. In other words, users need to </span>be <span class="delete">able to determine the provenance of provenance.
-Hence, provenance is also
-regarded as an entity (of type Bundle), by which provenance of provenance can then be
-expressed.</span><span class="insert">trusted.</span>
+In a decision making situation, decision makers may be presented with the same piece of knowledge, issued by multiple sources. In order to validate this piece of knowledge, decision makers can consider its provenance, but also the provenance of their provenance, which may help determine whether it can be trusted.
</p>
</div>
</div>
@@ -1653,8 +1665,8 @@
<h4><span class="secno">2.2.3 </span>Collections</h4>
<p>
-<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> Many different types of collections exist, such as a <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
-Using Collections, one can express the provenance of the collection itself in addition to that of the members.<span class="delete"> The provenance of the collection is the history of all insertions into and deletions from the collection. This may be complemented by explicit membership statements which enumerate the contents of the collection. </span> </p>
+<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> Many different types of collections exist, such as<span class="delete"> a</span> <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
+Using Collections, one can express the provenance of the collection itself in addition to that of the members. </p>
<div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example 14<sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
<p>
@@ -1677,7 +1689,7 @@
is further organized according to components, grouping concepts in a
thematic manner. </p>
-<p> <a href="#components-overview">Table 3</a> enumerates the six components, five of which have already been implicitly overviewed in this section. All components specify extended structures, whereas only the first three define core structures.
+<p> <a href="#components-overview">Table 3</a> enumerates the six components, five of which have already been implicitly overviewed in this section. All components <span class="delete">specify</span><span class="insert">contain</span> extended structures, whereas only the first three<span class="delete"> define</span><span class="insert"> contain</span> core structures.
</p><div id="components-overview-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
@@ -1687,10 +1699,9 @@
<tr><td style=" padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr>
<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about derivations and its subtypes</td></tr>
<tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component2">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr>
-<tr><td>4</td><td style="text-align: left;"><span class="insert">Bundles</span></td><td></td><td><a href="#section-provenance-of-provnance"><span class="insert">2.2.2</span></a></td><td><a href="#component4"><span class="insert">5.4</span></a></td><td style="text-align: left;"><span class="insert">about bundles, a mechanism to support provenance of provenance</span></td></tr>
-<tr><td><span class="insert">5</span></td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><span class="delete">5.4</span><a href="#component5"><span class="insert">5.5</span></a></td><td style="text-align: left;">about relations linking entities referring the same thing
-<span class="delete">5</span><span class="delete">Bundles</span><span class="delete">2.2.2</span><span class="delete">5.5</span><span class="delete">about bundles, a mechanism to support provenance of provenance</span></td></tr>
-<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td><a href="#section-collections">2.2.3</a></td><td><a href="#component6">5.6</a></td><td style="text-align: left;">about collections<span class="delete"> and concepts capturing their transformation, such as insertion and removal</span></td></tr>
+<tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr>
+<tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr>
+<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td><a href="#section-collections">2.2.3</a></td><td><a href="#component6">5.6</a></td><td style="text-align: left;">about collections</td></tr>
</tbody></table>
</div>
@@ -1700,6 +1711,7 @@
<div id="prov-notation" class="section">
+
<h2><span class="secno">3. </span>The Provenance Notation</h2>
@@ -1712,6 +1724,10 @@
<li>The interpretation of PROV-N arguments is defined according to their <em>position</em> in the list of arguments. This convention allows for a compact notation. </li>
+<li><span class="insert">The PROV data model defines </span><em><span class="insert">identifiers</span></em><span class="insert"> as qualified names; in PROV-N, they are expressed as a local name optionally preceded of a prefix and a colon. </span></li>
+
+
+
<li>
PROV-N <em>optional arguments</em> need not be specified:
the general rule for optional arguments is that, if none of them are used in the expression, then they are simply omitted, resulting in a simpler expression. However, it may be the case that only some of the optional arguments need to be specified. Because the position of the arguments in the expression matters, in this case, an additional marker must be used to indicate that a particular term is not available. The syntactic marker '<span class="name">-</span>' is used for this purpose.
@@ -1720,7 +1736,7 @@
<li>Most expressions
include an identifier
and a set of attribute-value pairs; both are optional unless otherwise specified. By convention, the identifier occurs in the <em>first position</em>, and the set of attribute-value pairs in the <em>last position</em>.
-Consistent with the convention on arguments, the marker '<span class="name">-</span>' can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising. To further disambiguate expressions that contains an optional identifier, the optional identifier or marker must be followed by '<span class="name">;</span>'.
+Consistent with the convention on arguments, the marker '<span class="name">-</span>' can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising. To further disambiguate expressions that <span class="delete">contains</span><span class="insert">contain</span> an optional identifier, the optional identifier or marker must be followed by '<span class="name">;</span>'.
</li>
</ul>
@@ -1761,7 +1777,7 @@
<div id="section-example-one" class="section">
-<h3><span class="secno">4.1 </span><span class="insert">Example: </span>The Authors View</h3>
+<h3><span class="secno">4.1 </span>Example: The Authors View</h3>
<p style="font-style:italic; "><b>Description:</b> A document
@@ -1782,8 +1798,8 @@
<div style="text-align: center; ">
<span class="figure" id="prov-a-document1-top">
- <img src="images/w3-publication3.png" alt="Provenance of a Document (1)" style="max-width: 98%; ">
-<p><span class="figcaption" id="prov-a-document1">Figure 2: Provenance of a Document (1)</span></p>
+ <img src="images/w3-publication3.png" alt="Provenance of a Document (1)" style="max-width: 98%; "><br>
+<span class="figcaption" id="prov-a-document1">Figure 2: Provenance of a Document (1)</span>
</span>
</div>
@@ -1806,8 +1822,8 @@
<li>There were some agents.
-<pre>agent(ex:Paolo, [ <span class="delete">prov:type="Person"</span><span class="insert">prov:type='prov:Person'</span> ])
-agent(ex:Simon, [ <span class="delete">prov:type="Person"</span><span class="insert">prov:type='prov:Person'</span> ])
+<pre>agent(ex:Paolo, [ prov:type='prov:Person' ])
+agent(ex:Simon, [ prov:type='prov:Person' ])
</pre>
</li>
@@ -1833,7 +1849,7 @@
</div>
<div id="section-example-two" class="section">
-<h3><span class="secno">4.2 </span><span class="insert">Example: </span>The Process View</h3>
+<h3><span class="secno">4.2 </span>Example: The Process View</h3>
<p style="font-style:italic; "><b>Description:</b> The World Wide Web
@@ -1868,8 +1884,8 @@
</p><div style="text-align: center;">
<span class="figure" id="prov-a-document2-top">
- <img src="images/w3-publication1.png" alt="Provenance of a Document (2)" style="max-width: 90%; ">
-<p><span class="figcaption" id="prov-a-document2">Figure 3: Provenance of a Document (2)</span></p>
+ <img src="images/w3-publication1.png" alt="Provenance of a Document (2)" style="max-width: 90%; "><br>
+<span class="figcaption" id="prov-a-document2">Figure 3: Provenance of a Document (2)</span>
</span>
</div>
@@ -1921,7 +1937,7 @@
<div id="section-example-c" class="section">
-<h3><span class="secno">4.3 </span><span class="insert">Example: </span>Attribution of Provenance</h3>
+<h3><span class="secno">4.3 </span>Example: Attribution of Provenance</h3>
<p>The two previous sections offer two different perspectives on the provenance of a document. PROV allows for multiple sources to provide the provenance of a subject. For users to decide whether they can place their trust in the document, they may want to analyze its provenance, but also determine who the provenance is attributed to, and when it was
generated, etc. In other words, we need to be able to express the provenance of provenance.</p>
@@ -1968,25 +1984,24 @@
<h2><span class="secno">5. </span>PROV-DM Types and Relations</h2>
<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.
-The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another is displayed above it in the figure. So, for example, component <span class="delete">6 (collections)</span><span class="insert">5 (alternate)</span> depends on concepts defined in component <span class="delete">3 (derivation),</span><span class="insert">4 (bundles),</span> itself dependen on concepts defined in component 1 (entity and activity).
+The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another is displayed above it in the figure. So, for example, component 5 (alternate) depends on concepts defined in component 4 (bundles), itself <span class="delete">dependen</span><span class="insert">dependent</span> on concepts defined in component 1 (entity and activity).
</p>
<div id="prov-dm-components-ul">
<ul>
<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
-<li><b>Component 2:<span class="delete"> agents and responsibility.</span><span class="delete"> The second component consists of agents and concepts ascribing responsibility to agents.</span>
-<span class="delete">Component 3:</span> derivations.</b> The <span class="delete">third</span><span class="insert">second</span> component is formed with derivations and derivation subtypes.</li>
-<li><b>Component <span class="delete">4: alternate.</span><span class="insert">3: agents, responsibility, and influence.</span></b> The <span class="delete">fourth</span><span class="insert">third</span> component consists of <span class="delete">relations linking entities referring</span><span class="insert">agents and concepts ascribing responsibility</span> to <span class="delete">the same thing. </span><span class="insert">agents.</span></li>
-<li><b>Component <span class="delete">5:</span><span class="insert">4:</span> bundles.</b> The <span class="delete">fifth</span><span class="insert">fourth</span> component is concerned with bundles, a mechanism to support provenance of provenance.</li>
-<li><b>Component <span class="insert">5: alternate.</span></b><span class="insert"> The fifth component consists of relations linking entities referring to the same thing. </span></li>
-<li><b><span class="insert">Component </span>6: collections.</b> The sixth component is about <span class="delete">collections and concepts capturing their transformation, such as insertion and removal.</span><span class="insert">collections.</span> </li>
+<li><b>Component 2: derivations.</b> The second component is formed with derivations and derivation subtypes.</li>
+<li><b>Component 3: agents, responsibility, and influence.</b> The third component consists of agents and concepts ascribing responsibility to agents.</li>
+<li><b>Component 4: bundles.</b> The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</li>
+<li><b>Component 5: alternate.</b> The fifth component consists of relations linking entities referring to the same thing. </li>
+<li><b>Component 6: collections.</b> The sixth component is about collections. </li>
</ul>
</div>
<div style="text-align: center;">
-<span class="figure" style="max-width: 90%; ">
+<span class="figure" style="max-width: 95%; ">
<img usemap="#componentMap" src="images/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; ">
<map id="componentMap" name="componentMap">
<area title="collections" href="#component5" coords="220,0,440,70" alt="collections" shape="rect">
@@ -1995,8 +2010,8 @@
<area title="activities/entities" href="#component1" coords="80,150,510,220" alt="activities/entities" shape="rect">
<area title="derivations" href="#component3" coords="80,0,210,70" alt="derivations" shape="rect">
<area title="agents/responsibility" href="#component2" coords="0,0,70,220" alt="agents/responsibility" shape="rect">
-</map>
-<p><span class="figcaption" id="prov-dm-components">Figure 4: PROV-DM Components</span></p>
+</map><br>
+<span class="figcaption" id="prov-dm-components">Figure 4: PROV-DM Components</span>
</span>
</div>
@@ -2012,19 +2027,19 @@
<caption id="relations-at-a-glance">Table 4: PROV-DM Relations At a Glance</caption>
<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6">Object</td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="2">Entity</td><td colspan="2">Activity</td><td colspan="2">Agent</td></tr>
-<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential internalDFN" href="#dfn-wasderivedfrom">WasDerivedFrom</a><br><span class="delete">WasRevisionOf</span><a href="#concept-revision" class="internalDFN"><span class="insert">Revision</span></a><br><span class="delete">WasQuotedFrom</span><a href="#concept-quotation" class="internalDFN"><span class="insert">Quotation</span></a><br><span class="delete">HadPrimarySource</span><a href="#dfn-primarysource" class="internalDFN"><span class="insert">PrimarySource</span></a></div><div class="component5-color"><a href="#dfn-alternateof" class="internalDFN">AlternateOf</a><br><a href="#dfn-specializationof" class="internalDFN">SpecializationOf</a><br><span class="delete">ContextualizationOf</span><a><span class="insert">MentionOf</span></a></div></td><td class="component1-color"><a class="essential internalDFN" title="wasGeneratedBy" href="#dfn-wasgeneratedby">WasGeneratedBy</a><br><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN"><span class="insert">R</span></a><br><a title="time" href="#dfn-time" class="internalDFN"><span class="insert">T</span></a><br><a title="location" href="#concept-location" class="internalDFN"><span class="insert">L</span></a><br></td><td class="component3-color" colspan="2"><a class="essential internalDFN" href="#dfn-wasattributedto">WasAttributedTo</a></td></tr>
-<tr><td>Activity</td><td class="component1-color"><a class="essential internalDFN" href="#dfn-used">Used</a><br><a href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a><br><a href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN"><span class="insert">R</span></a><br><a title="time" href="#dfn-time" class="internalDFN"><span class="insert">T</span></a><br><a title="location" href="#concept-location" class="internalDFN"><span class="insert">L</span></a><br></td><td colspan="2" class="component1-color"><a class="essential internalDFN" href="#dfn-wasinformedby">WasInformedBy</a></td><td class="component3-color"><a class="essential internalDFN" href="#dfn-wasassociatedwith">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN"><span class="insert">R</span></a><br></td></tr>
+<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential internalDFN" href="#dfn-wasderivedfrom">WasDerivedFrom</a><br><a href="#concept-revision" class="internalDFN">Revision</a><br><a href="#concept-quotation" class="internalDFN">Quotation</a><br><a href="#dfn-primarysource" class="internalDFN">PrimarySource</a></div><div class="component5-color"><a href="#dfn-alternateof" class="internalDFN">AlternateOf</a><br><a href="#dfn-specializationof" class="internalDFN">SpecializationOf</a><br><a href="#dfn-mentionof" class="internalDFN">MentionOf</a></div></td><td class="component1-color"><a class="essential internalDFN" title="wasGeneratedBy" href="#dfn-wasgeneratedby">WasGeneratedBy</a><br><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br><a title="time" href="#dfn-time" class="internalDFN">T</a><br><a title="location" href="#concept-location" class="internalDFN">L</a><br></td><td class="component3-color" colspan="2"><a class="essential internalDFN" href="#dfn-wasattributedto">WasAttributedTo</a></td></tr>
+<tr><td>Activity</td><td class="component1-color"><a class="essential internalDFN" href="#dfn-used">Used</a><br><a href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a><br><a href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br><a title="time" href="#dfn-time" class="internalDFN">T</a><br><a title="location" href="#concept-location" class="internalDFN">L</a><br></td><td colspan="2" class="component1-color"><a class="essential internalDFN" href="#dfn-wasinformedby">WasInformedBy</a></td><td class="component3-color"><a class="essential internalDFN" href="#dfn-wasassociatedwith">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br></td></tr>
<tr><td>Agent</td><td colspan="2">—</td><td colspan="2">—</td><td class="component3-color" colspan="2"><a class="essential internalDFN" href="#dfn-actedonbehalfof">ActedOnBehalfOf</a></td></tr>
</tbody></table>
</div>
-<p><span class="insert">The letters 'R' and 'L' appearing in the right-hand side of some cells of </span><a href="#relations-at-a-glance"><span class="insert">Table 4</span></a><span class="insert"> indicate that attributes
-</span><a title="role" href="#concept-role" class="internalDFN"><span class="insert">prov:role</span></a><span class="insert"> (</span><a class="section-ref" href="#term-attribute-role"><span><span class="insert">Section 5.7.2.3</span></span></a><span class="insert">)
+<p>The letters 'R' and 'L' appearing in the right-hand side of some cells of <a href="#relations-at-a-glance">Table 4</a> indicate that attributes
+<a title="role" href="#concept-role" class="internalDFN">prov:role</a> (<a class="section-ref" href="#term-attribute-role"><span>Section 5.7.2.3</span></a>)
and
-</span><a title="location" href="#concept-location" class="internalDFN"><span class="insert">prov:location</span></a><span class="insert"> (</span><a class="section-ref" href="#term-attribute-location"><span><span class="insert">Section 5.7.2.2</span></span></a><span class="insert">)
+<a title="location" href="#concept-location" class="internalDFN">prov:location</a> (<a class="section-ref" href="#term-attribute-location"><span>Section 5.7.2.2</span></a>)
are permitted for these relations.
-The letter 'T' indicates an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em> <a title="time" href="#dfn-time" class="internalDFN"><span class="insert">time</span></a><span class="insert"> is also permitted.
-</span></p>
+The letter 'T' indicates an <em class="rfc2119" title="optional">optional</em> <a title="time" href="#dfn-time" class="internalDFN">time</a> is also permitted.
+</p>
<p><a href="#prov-dm-types-and-relations">Table 5</a> is a complete index of all the types and relations of PROV-DM, color-coded according to the component they belong to. In the first column, concept names link to their informal definition, whereas, in the second column, representations link to the information used to represent the concept. Concept names appearing in bold are the core structures introduced in <a href="#core-structures">Section 2.1</a>.</p>
@@ -2039,7 +2054,7 @@
<tr class="component1-color"><td class="essential"><a href="#concept-activity" class="internalDFN">Activity</a></td><td><a title="dfn-Activity" class="essential internalDFN" href="#dfn-activity">activity(id, st, et, [ attr1=val1, ...])</a></td></tr>
<tr class="component1-color"><td class="essential"><a href="#concept-generation" class="internalDFN">Generation</a></td><td><a title="WasGeneratedBy" href="#dfn-wasgeneratedby" class="internalDFN"><span class="essential">wasGeneratedBy(</span>id;<span class="essential">e,a</span>,t,attrs<span class="essential">)</span></a></td></tr>
<tr class="component1-color"><td class="essential"><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a title="used" href="#dfn-used" class="internalDFN"><span class="essential">used(</span>id;<span class="essential">a,e</span>,t,attrs<span class="essential">)</span></a></td></tr>
-<tr class="component1-color"><td class="essential"><a href="#concept-communication" class="internalDFN">Communication</a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN"><span class="delete">wasInformedBy(id;a2,a1,attrs)</span><span class="essential"><span class="insert">wasInformedBy(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">a2,a1</span></span><span class="insert">,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-communication" class="internalDFN">Communication</a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN"><span class="essential">wasInformedBy(</span>id;<span class="essential">a2,a1</span>,attrs<span class="essential">)</span></a></td></tr>
<tr class="component1-color"><td><a href="#concept-start" class="internalDFN">Start</a></td><td><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">wasStartedBy(id;a2,e,a1,t,attrs)</a></td></tr>
<tr class="component1-color"><td><a href="#concept-end" class="internalDFN">End</a></td><td><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">wasEndedBy(id;a2,e,a1,t,attrs)</a></td></tr>
<tr class="component1-color"><td><a href="#concept-invalidation" class="internalDFN">Invalidation</a></td><td><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">wasInvalidatedBy(id;e,a,t,attrs)</a></td></tr>
@@ -2047,13 +2062,13 @@
<tr class="component2-color"><td class="essential"><a href="#concept-derivation" class="internalDFN">Derivation</a></td><td><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN"><span class="essential">wasDerivedFrom(</span>id; <span class="essential">e2, e1</span>, a, g2, u1, attrs<span class="essential">)</span></a></td><td rowspan="5"><a href="#component2">Component 2: Derivations</a></td></tr>
-<tr class="component2-color"><td class="provType"><a href="#concept-revision" class="internalDFN">Revision</a></td><td><a title="Revision" href="#concept-revision" class="internalDFN">... <span class="delete">prov:type='prov:WasRevisionOf'</span><span class="insert">prov:type='prov:Revision'</span> ...</a></td></tr>
-<tr class="component2-color"><td class="provType"><a href="#concept-quotation" class="internalDFN">Quotation</a></td><td><a title="Quotation" href="#concept-quotation" class="internalDFN">... <span class="delete">prov:type='prov:WasQuotedFrom'</span><span class="insert">prov:type='prov:Quotation'</span> ...</a></td></tr>
-<tr class="component2-color"><td class="provType"><a href="#concept-primary-source" class="internalDFN">Primary Source</a></td><td><a title="PrimarySource" href="#dfn-primarysource" class="internalDFN">... <span class="delete">prov:type='prov:HadPrimarySource'</span><span class="insert">prov:type='prov:PrimarySource'</span> ...</a></td></tr>
-<tr class="component2-color"><td><span class="delete">Trace</span><a href="#concept-influence" class="internalDFN"><span class="insert">Influence</span></a></td><td><span class="delete">tracedTo(id;e2,e1,attrs)</span><a title="wasInfluencedBy" href="#dfn-wasinfluencedby" class="internalDFN"><span class="insert">wasInfluencedBy(id;e2,e1,attrs)</span></a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-revision" class="internalDFN">Revision</a></td><td><a title="Revision" href="#concept-revision" class="internalDFN">... prov:type='prov:Revision' ...</a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-quotation" class="internalDFN">Quotation</a></td><td><a title="Quotation" href="#concept-quotation" class="internalDFN">... prov:type='prov:Quotation' ...</a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-primary-source" class="internalDFN">Primary Source</a></td><td><a title="PrimarySource" href="#dfn-primarysource" class="internalDFN">... prov:type='prov:PrimarySource' ...</a></td></tr>
+<tr class="component2-color"><td><a href="#concept-influence" class="internalDFN">Influence</a></td><td><a title="wasInfluencedBy" href="#dfn-wasinfluencedby" class="internalDFN">wasInfluencedBy(id;e2,e1,attrs)</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component3-color" style="border-collapse: collapse; "><td class="essential"><a href="#concept-agent" class="internalDFN">Agent</a></td><td><a title="dfn-agent" class="essential internalDFN" href="#dfn-agent">agent(id, [ attr1=val1, ...])</a></td><td rowspan="8"><a href="#component3">Component 3: <span class="delete">Agents/Responsibility</span><span class="insert">Agents, Responsibility, Influence</span></a></td></tr>
+<tr class="component3-color" style="border-collapse: collapse; "><td class="essential"><a href="#concept-agent" class="internalDFN">Agent</a></td><td><a title="dfn-agent" class="essential internalDFN" href="#dfn-agent">agent(id, [ attr1=val1, ...])</a></td><td rowspan="8"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td></tr>
<tr class="component3-color"><td class="essential"><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a title="wasAttributedTo" href="#dfn-wasattributedto" class="internalDFN"><span class="essential">wasAttributedTo(</span>id;<span class="essential">e,ag</span>,attr<span class="essential">)</span></a></td></tr>
<tr class="component3-color"><td class="essential"><a href="#concept-activityAssociation" class="internalDFN">Association</a></td><td><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN"><span class="essential">wasAssociatedWith(</span>id;<span class="essential">a,ag</span>,pl,attrs<span class="essential">)</span></a></td></tr>
<tr class="component3-color"><td class="essential"><a href="#concept-delegation" class="internalDFN">Delegation</a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN"><span class="essential">actedOnBehalfOf(</span>id;<span class="essential">ag2,ag1</span>,a,attrs<span class="essential">)</span></a></td></tr>
@@ -2069,20 +2084,14 @@
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr class="component5-color"><td><a href="#concept-alternate" class="internalDFN">Alternate</a></td><td><a title="alternateOf" href="#dfn-alternateof" class="internalDFN">alternateOf(alt1, alt2)</a></td><td rowspan="3"><a href="#component4">Component 5: Alternate</a></td></tr>
-<tr class="component5-color"><td><a href="#concept-specialization" class="internalDFN">Specialization</a></td><td><a title="specializationOf" href="#dfn-specializationof" class="internalDFN"><span class="delete">specializationOf(sub, super)</span><span class="insert">specializationOf(infra, supra)</span></a></td></tr>
-<tr class="component5-color"><td><span class="delete">Contextualization</span><a href="#concept-mention" class="internalDFN"><span class="insert">Mention</span></a></td><td><span class="delete">contextualizationOf(i2, i1,bundle)</span><a title="mentionOf" href="#dfn-mentionof" class="internalDFN"><span class="insert">mentionOf(infra, supra,bundle)</span></a></td></tr>
-
+<tr class="component5-color"><td><a href="#concept-specialization" class="internalDFN">Specialization</a></td><td><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">specializationOf(infra, supra)</a></td></tr>
+<tr class="component5-color"><td><a href="#concept-mention" class="internalDFN">Mention</a></td><td><a title="mentionOf" href="#dfn-mentionof" class="internalDFN">mentionOf(infra, supra,bundle)</a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr class="component6-color"><td class="provType"><a href="#concept-collection" class="internalDFN">Collection</a></td><td><a title="collection" href="#concept-collection" class="internalDFN">... prov:type='prov:Collection' ...</a></td><td rowspan="3"><a href="#component6">Component 6: Collections</a></td></tr>
-<tr class="component6-color"><td class="provType"><a title="empty collection" href="#concept-empty-collection" class="internalDFN"><span class="insert">EmptyCollection</span></a></td><td><a title="empty collection" href="#concept-empty-collection" class="internalDFN"><span class="insert">... prov:type='prov:EmptyCollection' ...</span></a></td></tr>
-<tr class="component6-color"><td><a href="#concept-collection-membership" class="internalDFN">Collection Membership</a></td><td><a title="memberOf" href="#dfn-memberof" class="internalDFN"><span class="delete">memberOf(c,</span><span class="insert">memberOf(id; c,</span> {e_1, ..., <span class="delete">e_n})</span>
-<span class="delete">Dictionary</span><span class="delete">... prov:type='prov:Dictionary' ...</span>
-<span class="delete">EmptyDictionary</span><span class="delete">... prov:type='prov:EmptyDictionary' ...</span>
-<span class="delete">Insertion</span><span class="delete">derivedByInsertionFrom(id; c2, c1, {(key_1, e_1), ..., (key_n, e_n)},</span><span class="insert">e_n}, cplt,</span> attrs)
-<span class="delete">Removal</span><span class="delete">derivedByRemovalFrom(id; c2, c1, {key_1, ... key_n}, attrs)</span>
-<span class="delete">Dictionary Membership</span><span class="delete">memberOf(d, {(key_1, e_1), ..., (key_n, e_n)})</span></a></td></tr>
+<tr class="component6-color"><td class="provType"><a title="empty collection" href="#concept-empty-collection" class="internalDFN">EmptyCollection</a></td><td><a title="empty collection" href="#concept-empty-collection" class="internalDFN">... prov:type='prov:EmptyCollection' ...</a></td></tr>
+<tr class="component6-color"><td><a href="#concept-collection-membership" class="internalDFN">Collection Membership</a></td><td><a title="memberOf" href="#dfn-memberof" class="internalDFN">memberOf(id; c, {e_1, ..., e_n}, cplt, attrs)</a></td></tr>
</tbody></table>
</div>
@@ -2100,10 +2109,10 @@
</p>
<div style="text-align: center;">
-<span class="figure">
-
-<img src="uml/component1.png" alt="entities and activities">
-<p><span class="figcaption" id="figure-component1">Figure 5: Entities and Activities Component Overview</span></p>
+<span class="figure" style="max-width: 95%; ">
+
+<img src="uml/component1.png" alt="entities and activities"><br>
+<span class="figcaption" id="figure-component1">Figure 5: Entities and Activities Component Overview</span>
</span>
</div>
@@ -2262,7 +2271,7 @@
<div id="term-Communication" class="section">
<h4><span class="secno">5.1.5 </span>Communication</h4>
-<div class="glossary-ref"> <dfn id="concept-communication" class="internalDFN">Communication</dfn><sup><a class="internalDFN" href="#concept-communication"><span class="diamond"> ◊</span></a></sup> is the exchange of <span class="delete">an</span><span class="insert">some</span> unspecified entity by two activities, one activity using some entity generated by the other. </div>
+<div class="glossary-ref"> <dfn id="concept-communication" class="internalDFN">Communication</dfn><sup><a class="internalDFN" href="#concept-communication"><span class="diamond"> ◊</span></a></sup> is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. </div>
<p>A communication implies that activity <span class="name">a2</span> is dependent on another <span class="name">a1</span>, by way of some unspecified entity that is generated by <span class="name">a1</span> and used by <span class="name">a2</span>.</p>
@@ -2329,7 +2338,7 @@
wasGeneratedBy(e1, a0)
wasStartedBy(a1, e1, a0, 2011-11-16T16:05:00)
</pre>
-<p>If <span class="name">e1</span> is not known, it would also have valid to write:
+<p>If <span class="name">e1</span> is not known, it would also <span class="delete">have</span><span class="insert">be</span> valid to write:
</p><pre class="codeexample">wasStartedBy(a1, -, a0, 2011-11-16T16:05:00)
</pre>
</div>
@@ -2445,7 +2454,7 @@
agent(ex:Picasso)
wasAttributedTo(ex:The-Painter, ex:Picasso)
activity(ex:crash)
-wasInvalidatedBy(ex:The-Painter, ex:crash, <span class="delete">1998-09-02,</span><span class="insert">1998-09-03T01:31:00,</span> [ ex:circumstances="plane accident" ])
+wasInvalidatedBy(ex:The-Painter, ex:crash, 1998-09-03T01:31:00, [ ex:circumstances="plane accident" ])
</pre>
</div>
@@ -2456,14 +2465,14 @@
<a href="http://www.bbc.co.uk/news/uk-17595024">bbc:news/uk-17595024</a>,
but the BBC news home page on the next day did not.
</p><pre class="codeexample">entity(ex:bbcNews2012-04-03)
-memberOf(ex:bbcNews2012-04-03, <span class="delete">{("item1", bbc:news/uk-17595024)})</span><span class="insert">{bbc:news/uk-17595024})</span>
+memberOf(ex:bbcNews2012-04-03, {bbc:news/uk-17595024})
wasGeneratedBy (ex:bbcNews2012-04-03, -, 2012-04-03T00:00:01)
wasInvalidatedBy(ex:bbcNews2012-04-03, -, 2012-04-03T23:59:59)
</pre>
We refer to example
<a href="#anexample-specialization" class="anexample-ref"><span>Example 42</span></a>
- for further descriptions of the BBC Web site, and to <a href="#term-dictionary-membership">Section 5.6.5</a> for a description of the relation <a title="memberOf" href="#dfn-memberof" class="internalDFN">memberOf</a>.
+ for further descriptions of the BBC Web site, and to <a href="#term-collection-membership">Section 5.6.2</a> for a description of the relation <a title="memberOf" href="#dfn-memberof" class="internalDFN">memberOf</a>.
</div>
@@ -2507,22 +2516,21 @@
-<p>The <span class="delete">third</span><span class="insert">second</span> component of PROV-DM is concerned with: <a title="derivation" href="#concept-derivation" class="internalDFN">derivations</a> of <a title="entity" href="#concept-entity" class="internalDFN">entities</a> from <span class="delete">others;</span><span class="insert">other entities and</span> derivation subtypes <a href="#concept-revision" class="internalDFN">Revision</a>, <a href="#concept-quotation" class="internalDFN">Quotation</a>, and <a href="#concept-primary-source" class="internalDFN">Primary Source</a><span class="delete">; derivation-related </span><span class="delete">Trace</span>.
-
+<p>The <span class="delete">second</span><span class="insert">third</span> component of PROV-DM is concerned with: <a title="derivation" href="#concept-derivation" class="internalDFN">derivations</a> of <a title="entity" href="#concept-entity" class="internalDFN">entities</a> from other entities and derivation subtypes <a href="#concept-revision" class="internalDFN">Revision</a>, <a href="#concept-quotation" class="internalDFN">Quotation</a>, and <a href="#concept-primary-source" class="internalDFN">Primary Source</a>.
<a href="#figure-component2">Figure 6</a> depicts the third component
with PROV core structures in the yellow area, including two classes
(<a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>) and binary association
(<a href="#concept-derivation" class="internalDFN">Derivation</a>). PROV extended structures are found outside this
area. UML association classes express expanded n-ary relations.
-<span class="insert">The subclasses are marked by the UML stereotype "prov:type" to indicate that the corresponding types are valid values for the attribute </span><a href="#term-attribute-type"><span class="insert">prov:type</span></a><span class="insert">.
-</span></p>
+The subclasses are marked by the UML stereotype "prov:type" to indicate that the corresponding types are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
+</p>
<div style="text-align: center;">
-<span class="figure">
-
-<img src="uml/component2.png" alt="derivation">
-<p><span class="figcaption" id="figure-component2">Figure 6: Derivation Component Overview</span></p>
+<span class="figure" style="max-width: 95%; ">
+
+<img src="uml/component2.png" alt="derivation"><br>
+<span class="figcaption" id="figure-component2">Figure 6: Derivation Component Overview</span>
</span>
</div>
@@ -2533,7 +2541,7 @@
-<div class="glossary-ref"> A <dfn id="concept-derivation" class="internalDFN">derivation</dfn><sup><a class="internalDFN" href="#concept-derivation"><span class="diamond"> ◊</span></a></sup> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a <span class="delete">pre-exisiting</span><span class="insert">pre-existing</span> entity.</div>
+<div class="glossary-ref"> A <dfn id="concept-derivation" class="internalDFN">derivation</dfn><sup><a class="internalDFN" href="#concept-derivation"><span class="diamond"> ◊</span></a></sup> is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.</div>
@@ -2591,7 +2599,7 @@
original.
Revision is a particular case of <a href="#concept-derivation" class="internalDFN">derivation</a> of an entity into its revised version.
The type is of a revision derivation is denoted by:
-<dfn title="Revision" id="dfn-revision" class="internalDFN"><span class="name"><span class="delete">prov:WasRevisionOf</span><span class="insert">prov:Revision</span></span></dfn><sup><a class="internalDFN" href="#dfn-revision"><span class="diamond"> ◊</span></a></sup>.
+<dfn title="Revision" id="dfn-revision" class="internalDFN"><span class="name">prov:Revision</span></dfn><sup><a class="internalDFN" href="#dfn-revision"><span class="diamond"> ◊</span></a></sup>.
</p>
@@ -2605,9 +2613,9 @@
the report <span class="name">tr:WD-prov-dm-20111018</span>.
</p><pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
entity(tr:WD-prov-dm-20111018, [ prov:type='rec54:WD' ])
-wasDerivedFrom(tr:WD-prov-dm-20111215,
- tr:WD-prov-dm-20111018,
- [ <span class="delete">prov:type='prov:WasRevisionOf'</span><span class="insert">prov:type='prov:Revision'</span> ])
+wasDerivedFrom(tr:WD-prov-dm-20111215,
+ tr:WD-prov-dm-20111018,
+ [ prov:type='prov:Revision' ])
</pre>
</div>
@@ -2625,7 +2633,7 @@
<p>Quotation
is a particular case of <a href="#concept-derivation" class="internalDFN">derivation</a> in which an entity is derived from an original entity by copying, or "quoting", some or all of it.
The type is of a quotation derivation is denoted by:
-<dfn title="Quotation" id="dfn-quotation" class="internalDFN"><span class="name"><span class="delete">prov:WasQuotedFrom</span><span class="insert">prov:Quotation</span></span></dfn><sup><a class="internalDFN" href="#dfn-quotation"><span class="diamond"> ◊</span></a></sup>.
+<dfn title="Quotation" id="dfn-quotation" class="internalDFN"><span class="name">prov:Quotation</span></dfn><sup><a class="internalDFN" href="#dfn-quotation"><span class="diamond"> ◊</span></a></sup>.
</p>
@@ -2645,7 +2653,7 @@
agent(ex:Paul)
wasDerivedFrom(dm:bl-dagstuhl,
wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/,
- [ <span class="delete">prov:type='prov:WasQuotedFrom'</span><span class="insert">prov:type='prov:Quotation'</span> ])
+ [ prov:type='prov:Quotation' ])
wasAttributedTo(dm:bl-dagstuhl, ex:Luc)
wasAttributedTo(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/, ex:Paul)
</pre>
@@ -2663,16 +2671,12 @@
<span class="glossary-ref"> A <dfn id="concept-primary-source" class="internalDFN">primary source</dfn><sup><a class="internalDFN" href="#concept-primary-source"><span class="diamond"> ◊</span></a></sup> for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. </span>
</p>
-<p>Because of the directness<span class="delete"> of </span><span class="insert">
-of </span><a href="http://en.wikipedia.org/wiki/Primary_source">primary<span class="delete"> sources,</span><span class="insert">
-sources</span></a><span class="insert">,</span> they "speak for
- themselves" in ways that cannot be
-captured through the filter of
- secondary sources. As such, it is
-important for secondary sources to
- reference those primary sources
-from which they were derived, so that
- their reliability can be
+<p>Because of the directness
+of <a href="http://en.wikipedia.org/wiki/Primary_source">primary
+sources</a>, they "speak for themselves" in ways that cannot be
+captured through the filter of secondary sources. As such, it is
+important for secondary sources to reference those primary sources
+from which they were derived, so that their reliability can be
investigated.</p>
@@ -2682,7 +2686,7 @@
should be done according to conventions accepted within the
application's domain.
The type is of a primary source derivation is denoted by:
-<dfn title="PrimarySource" id="dfn-primarysource" class="internalDFN"><span class="name"><span class="delete">prov:HadPrimarySource</span><span class="insert">prov:PrimarySource</span></span></dfn><sup><a class="internalDFN" href="#dfn-primarysource"><span class="diamond"> ◊</span></a></sup>.
+<dfn title="PrimarySource" id="dfn-primarysource" class="internalDFN"><span class="name">prov:PrimarySource</span></dfn><sup><a class="internalDFN" href="#dfn-primarysource"><span class="diamond"> ◊</span></a></sup>.
</p>
@@ -2695,12 +2699,11 @@
to Napoleon's army during the Russian campaign. This primary source relation
can be encoded as follows.</p>
-<pre class="codeexample"><span class="delete">entity(ex:la-campagne-de-Russie-1812-1813)
-entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII)</span><span class="insert">entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type="map" ])
-entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type="journal" ])</span>
+<pre class="codeexample">entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type="map" ])
+entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type="journal" ])
wasDerivedFrom(ex:la-campagne-de-Russie-1812-1813,
ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII,
- [ <span class="delete">prov:type='prov:HadPrimarySource'</span><span class="insert">prov:type='prov:PrimarySource'</span> ])
+ [ prov:type='prov:PrimarySource' ])
</pre>
</div>
@@ -2712,36 +2715,36 @@
</div>
<div id="component3" class="section">
-<h3><span class="secno">5.3 </span>Component 3: <span class="delete">Agents</span><span class="insert">Agents, Responsibility,</span> and <span class="delete">Responsibility</span><span class="insert">Influence</span></h3>
+<h3><span class="secno">5.3 </span>Component 3: Agents, Responsibility, and Influence</h3>
<p>The second component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent" href="#concept-agent" class="internalDFN">agents</a> and the notions of
<a href="#concept-attribution" class="internalDFN">Attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">Association</a>, <a href="#concept-delegation" class="internalDFN">Delegation</a>, relating agents to entities, activities, and agents, respectively.
- Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise and UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">SofwareAgent</a>, and <a href="#concept-organization" class="internalDFN">Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>
+ Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise <span class="delete">and </span>UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">SofwareAgent</a>, and <a href="#concept-organization" class="internalDFN">Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>
</p>
<div style="text-align: center;">
-<span class="figure">
-
-<img src="uml/component3.png" alt="agents and responsibilities">
-<p><span class="figcaption" id="figure-component3">Figure 7: Agents and Responsibility <span class="insert">Overview</span></span></p>
+<span class="figure" style="max-width: 95%; ">
+
+<img src="uml/component3.png" alt="agents and responsibilities"><br>
+<span class="figcaption" id="figure-component3">Figure 7: Agents and Responsibility Overview</span>
</span>
</div>
-<p>Component <span class="delete">Overview</span><span class="insert">3 further defines a general notion of </span><a href="#concept-influence" class="internalDFN"><span class="insert">influence</span></a><span class="insert">, as a super-relation of all relations defined so far. </span><a href="#figure-component3b"><span class="insert">Figure 7b</span></a><span class="insert"> displays one new association class, generalizing previously introduced associations.</span></p>
+<p>Component 3 further defines a general notion of <a href="#concept-influence" class="internalDFN">influence</a>, as a super-relation of all relations defined so far. <a href="#figure-component3b">Figure <span class="delete">7b</span><span class="insert">8</span></a> displays one new association class, generalizing previously introduced associations.</p>
<div style="text-align: center;">
-<span class="figure">
-<img src="uml/Component3b.png" alt="Influence">
-<p><span class="figcaption" id="figure-component3b"><span class="insert">Figure 7b: Influence</span></span></p>
+<span class="figure" style="max-width: 95%; ">
+<img src="uml/Component3b.png" alt="Influence"><br>
+<span class="figcaption" id="figure-component3b">Figure <span class="delete">7b:</span><span class="insert">8:</span> Influence</span>
</span>
</div>
<div id="term-agent" class="section">
<h4><span class="secno">5.3.1 </span>Agent</h4>
-<div class="glossary-ref"> An <dfn id="concept-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#concept-agent"><span class="diamond"> ◊</span></a></sup> is something that bears some form of responsibility for an activity taking <span class="delete">place</span><span class="insert">place, for the existence of an entity,</span> or for <span class="delete">the existence of an entity.</span><span class="insert">another agent's activity.</span> </div>
+<div class="glossary-ref"> An <dfn id="concept-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#concept-agent"><span class="diamond"> ◊</span></a></sup> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </div>
<p></p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent" id="dfn-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#dfn-agent"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
@@ -2807,8 +2810,8 @@
Revisiting the example of
<a class="section-ref" href="#section-example-one"><span>Section 4.1</span></a>,
we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity. The reserved attribute <span class="name">role</span> (see <a class="section-ref" href="#term-attribute-role"><span>Section 5.7.2.3</span></a>) allows for role of the agent in the attribution to be specified.
-</p><pre class="codeexample">agent(ex:Paolo, [ <span class="delete">prov:type="Person"</span><span class="insert">prov:type='prov:Person'</span> ])
-agent(ex:Simon, [ <span class="delete">prov:type="Person"</span><span class="insert">prov:type='prov:Person'</span> ])
+</p><pre class="codeexample">agent(ex:Paolo, [ prov:type='prov:Person' ])
+agent(ex:Simon, [ prov:type='prov:Person' ])
entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [ prov:type="editorship" ])
wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [ prov:type="authorship" ])
@@ -2848,7 +2851,7 @@
wasAssociatedWith(ex:a, ex:ag2, ex:wf, [ prov:role="designer", ex:context="project1" ])
entity(ex:wf, [ prov:type='prov:Plan' ,
ex:label="Workflow 1",
- <span class="delete">ex:url="http://example.org/workflow1.bpel"</span><span class="insert">prov:location="http://example.org/workflow1.bpel"</span> %% xsd:anyURI ])
+ prov:location="http://example.org/workflow1.bpel" %% xsd:anyURI ])
</pre>
Since the workflow <span class="name">ex:wf</span> is itself an entity, its provenance can also be expressed in PROV-DM: it can be generated by some activity and derived from other entities,
for instance.
@@ -2918,43 +2921,38 @@
</div>
<div id="term-influence" class="section">
-<h4><span class="secno">5.3.5 </span><span class="delete">Trace</span><span class="insert">Influence</span></h4>
+<h4><span class="secno">5.3.5 </span>Influence</h4>
<p>
-<span class="glossary-ref"> <span class="delete">Trace</span><dfn id="concept-influence" class="internalDFN"><span class="insert">Influence</span></dfn><sup><a class="internalDFN" href="#concept-influence"><span class="diamond"> ◊</span></a></sup> is the <span class="delete">ability</span><span class="insert">capacity an entity, activity, or agent</span> to <span class="delete">link back</span><span class="insert">have</span> an <span class="delete">entity to</span><span class="insert">effect on the character, development, or behavior of</span> another by means of <span class="delete">derivation</span><span class="insert">usage, start, end, generation, invalidation, communication, derivation, attribution, association,</span> or <span class="delete">responsibility relations, possibly repeatedly traversed.</span><span class="insert">delegation.</span> </span>
+<span class="glossary-ref"> <dfn id="concept-influence" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#concept-influence"><span class="diamond"> ◊</span></a></sup> is the capacity <span class="insert">of </span>an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. </span>
</p>
-<p> <span class="delete">A trace</span><span class="insert">An influence</span> relation between two <span class="delete">entities </span><span class="insert">objects </span><span class="name"><span class="delete">e2</span><span class="insert">o2</span></span> and <span class="name"><span class="delete">e1</span><span class="insert">o1</span></span> is a generic dependency of <span class="name"><span class="delete">e2</span><span class="insert">o2</span></span>
-on <span class="name"><span class="delete">e1</span><span class="insert">o1</span></span> that <span class="delete">indicates either that</span><span class="insert">signifies some form of influence of</span> <span class="name"><span class="delete">e1</span><span class="delete"> may have been necessary for</span><span class="insert">o1</span></span><span class="insert"> on</span> <span class="name"><span class="delete">e2</span><span class="delete"> to be created, or that </span><span class="delete">e1</span><span class="delete"> bears
-some responsibility for </span><span class="delete">e2</span><span class="delete">'s existence.</span><span class="insert">o2</span></span><span class="insert">.</span></p>
-
-
-<p>A <span class="delete">Trace</span><dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN"><span class="insert">Influence</span></dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression"><span class="delete">tracedTo(id; e2, e1,</span><span class="insert">wasInfluencedBy(id; o2, o1,</span> attrs)</span> in PROV-N,</span> has:</p>
+<p> An influence relation between two objects <span class="name">o2</span> and <span class="name">o1</span> is a generic dependency of <span class="name">o2</span>
+on <span class="name">o1</span> that signifies some form of influence of <span class="name">o1</span> on <span class="name">o2</span>.</p>
+
+
+<p>A <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class="attribute" id="influence.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier identifying the relation;</li>
-<li><span class="delete">entity</span><span class="attribute" id="influence.influencee"><span class="insert">influencee</span></span>: an identifier (<span class="name"><span class="delete">e2</span><span class="insert">o2</span></span>) for an <span class="delete">entity;</span><span class="insert">entity, activity, or agent;</span>
-</li><li><span class="delete">ancestor</span><span class="attribute" id="influence.influencer"><span class="insert">influencer</span></span>: an identifier (<span class="name"><span class="delete">e1</span><span class="insert">o1</span></span>) for an ancestor <span class="delete">entity</span><span class="insert">entity, activity, or agent</span> that the former depends on;
+<li><span class="attribute" id="influence.influencee">influencee</span>: an identifier (<span class="name">o2</span>) for an entity, activity, or agent;
+</li><li><span class="attribute" id="influence.influencer">influencer</span>: an identifier (<span class="name">o1</span>) for an ancestor entity, activity, or agent that the former depends on;
</li><li><span class="attribute" id="influence.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
</ul>
-<span class="delete">We note that the ancestor </span><span class="delete">may</span><span class="delete"> be an agent since agents may be entities. </span>
<p>
-<a href="#concept-usage" class="internalDFN"><span class="insert">Usage</span></a><span class="insert">, </span><a href="#concept-start" class="internalDFN"><span class="insert">start</span></a><span class="insert">, </span><a href="#concept-end" class="internalDFN"><span class="insert">end</span></a><span class="insert">, </span><a href="#concept-generation" class="internalDFN"><span class="insert">generation</span></a><span class="insert">, </span><a href="#concept-invalidation" class="internalDFN"><span class="insert">invalidation</span></a><span class="insert">, </span><a href="#concept-communication" class="internalDFN"><span class="insert">communication</span></a><span class="insert">, </span><a href="#concept-derivation" class="internalDFN"><span class="delete">Derivation</span><span class="delete"> and</span><span class="insert">derivation</span></a><span class="insert">,</span> <a href="#concept-attribution" class="internalDFN">attribution</a><span class="insert">, </span><a href="#concept-activityAssociation" class="internalDFN"><span class="insert">association</span></a><span class="insert">, and </span><a href="#concept-delegation" class="internalDFN"><span class="insert">delegation</span></a> are particular cases of <span class="delete">trace.</span><span class="insert">influence. It is </span><em class="rfc2119" title="recommended"><span class="insert">recommended</span></em><span class="insert"> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the </span><a href="#concept-influence" class="internalDFN"><span class="insert">Influence</span></a><span class="insert"> relation may be useful to express queries over provenance information.</span>
+<a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-start" class="internalDFN">start</a>, <a href="#concept-end" class="internalDFN">end</a>, <a href="#concept-generation" class="internalDFN">generation</a>, <a href="#concept-invalidation" class="internalDFN">invalidation</a>, <a href="#concept-communication" class="internalDFN">communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a href="#concept-attribution" class="internalDFN">attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">association</a>, and <a href="#concept-delegation" class="internalDFN">delegation</a> are particular cases of influence. It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
</p>
<div class="anexample" id="example_38"><div class="anexampleTitle">Example 38<sup><a class="internalDFN" href="#example_38"><span class="diamond"> ◊</span></a></sup></div>
-<p>We refer to the example of <a class="section-ref" href="#section-example-two"><span>Section 4.2</span></a>, and specifically to <a href="#prov-a-document2-top">Figure 3</a>.
-We <span class="delete">can see</span><span class="insert">could have expressed</span> that <span class="delete">there is a path from</span><span class="insert">the influence of
-</span><span class="name"><span class="insert">w3:Consortium</span></span>
-<span class="insert">on </span><span class="name">tr:WD-prov-dm-20111215</span><span class="delete"> to
-</span><span class="delete">w3:Consortium</span><span class="delete"> and to
-</span><span class="delete">process:rec-advance</span>.<span class="delete"> This is expressed as follows.</span>
-</p><pre class="codeexample"> <span class="delete">tracedTo(tr:WD-prov-dm-20111215,</span><span class="insert">wasInfluencedBy(tr:WD-prov-dm-20111215,</span> w3:Consortium)<span class="delete">
- tracedTo(tr:WD-prov-dm-20111215, process:rec-advance)</span>
-</pre><span class="insert">
-Instead, it is </span><em class="rfc2119" title="recommended"><span class="insert">recommended</span></em><span class="insert"> to express the more specific description:
-</span><pre class="codeexample"><span class="insert"> wasAttributedTo(tr:WD-prov-dm-20111215, w3:Consortium)</span>
+<p>We refer to the example of <a class="section-ref" href="#section-example-two"><span>Section 4.2</span></a>, and specifically to <a href="#prov-a-document2-top">Figure 3</a>.
+We could have expressed that the influence of
+<span class="name">w3:Consortium</span>
+on <span class="name">tr:WD-prov-dm-20111215</span>.
+</p><pre class="codeexample"> wasInfluencedBy(tr:WD-prov-dm-20111215, w3:Consortium)
+</pre>
+Instead, it is <em class="rfc2119" title="recommended">recommended</em> to express the more specific description:
+<pre class="codeexample"> wasAttributedTo(tr:WD-prov-dm-20111215, w3:Consortium)
</pre>
</div>
@@ -2973,14 +2971,14 @@
<p>The fourth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance.
-<a href="#figure-component4">Figure 8</a> depicts a UML class diagram for the fourth component. It comprises a <a href="#concept-bundle" class="internalDFN">Bundle</a> class <span class="delete">and</span><span class="insert">defined as</span> a subclass of <a href="#concept-entity" class="internalDFN">Entity</a>.
+<a href="#figure-component4">Figure <span class="delete">8</span><span class="insert">9</span></a> depicts a UML class diagram for the fourth component. It comprises a <a href="#concept-bundle" class="internalDFN">Bundle</a> class defined as a subclass of <a href="#concept-entity" class="internalDFN">Entity</a>.
</p>
<div style="text-align: center;">
-<span class="figure">
-
-<img src="uml/component4.png" alt="bundles">
-<p><span class="figcaption" id="figure-component4">Figure 8: Bundle Component Overview</span></p>
+<span class="figure" style="max-width: 95%; ">
+
+<img src="uml/component4.png" alt="bundles"><br>
+<span class="figcaption" id="figure-component4">Figure <span class="delete">8:</span><span class="insert">9:</span> Bundle Component Overview</span>
</span>
</div>
@@ -3010,7 +3008,7 @@
<p>A bundle's identifier <span class="name">id</span> identifies a unique set of descriptions.</p>
</div>
-<p><span class="insert">There may be other kinds of bundles not directly expressible by this constructor, such as napkin, whiteboard, etc. What ever the means by which bundles are expressed, all can be described, as in the following section.</span></p>
+<p>There may be other kinds of bundles not directly expressible by this constructor, such as <span class="delete">napkin,</span><span class="insert">provenance descriptions handwritten on a letter or a</span> whiteboard, etc. What ever the means by which bundles are expressed, all can be described, as in the following section.</p>
</div>
@@ -3123,17 +3121,17 @@
<p>The fifth component of PROV-DM is concerned with
-relations <a href="#concept-specialization" class="internalDFN">specialization</a><span class="delete">,</span><span class="insert"> and</span> <a href="#concept-alternate" class="internalDFN">alternate<span class="delete"> and </span><span class="delete">contextualization</span></a> between entities.
- <a href="#figure-component5">Figure 9</a> depicts
+relations <a href="#concept-specialization" class="internalDFN">specialization</a><span class="delete"> and</span><span class="insert">,</span> <a href="#concept-alternate" class="internalDFN">alternate</a><span class="insert">, and </span><a href="#concept-mention" class="internalDFN"><span class="insert">mention</span></a> between entities.
+ <a href="#figure-component5">Figure <span class="delete">9</span><span class="insert">10</span></a> depicts
the fifth component with a single class, two binary associations, and a ternary association.
</p>
<div style="text-align: center;">
-<span class="figure">
-
-<img src="uml/component5.png" alt="alternates">
-<p><span class="figcaption" id="figure-component5">Figure 9: Alternates Component Overview</span></p>
+<span class="figure" style="max-width: 95%; ">
+
+<img src="uml/component5.png" alt="alternates"><br>
+<span class="figcaption" id="figure-component5">Figure <span class="delete">9:</span><span class="insert">10:</span> Alternates Component Overview</span>
</span>
</div>
@@ -3143,7 +3141,7 @@
<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific IRI, as she might edit the article later. Alternatively, user Bob refers to the article in general, independently of its variants over time.</p>
</div>
<p>
-The PROV data model introduces relations, called <span class="delete">specialization, alternate,</span><span class="insert">specialization</span> and <span class="delete">contextualization,</span><span class="insert">alternate</span>
+The PROV data model introduces relations, called <span class="delete">specialization</span><span class="insert">specialization, alternate,</span> and <span class="delete">alternate</span><span class="insert">mention</span>
that allow entities to be linked together. They are defined as follows. </p>
@@ -3152,7 +3150,7 @@
<h4><span class="secno">5.5.1 </span>Specialization</h4>
-<span class="glossary-ref"> An entity that is a <dfn id="concept-specialization" class="internalDFN">specialization</dfn><sup><a class="internalDFN" href="#concept-specialization"><span class="diamond"> ◊</span></a></sup> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the <span class="insert">entity being </span>specialized<span class="delete"> entity </span> contains that of any specialization. </span>
+<span class="glossary-ref"> An entity that is a <dfn id="concept-specialization" class="internalDFN">specialization</dfn><sup><a class="internalDFN" href="#concept-specialization"><span class="diamond"> ◊</span></a></sup> of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. </span>
<p>
@@ -3165,15 +3163,13 @@
</p><div class="attributes" id="attributes-specialization">A <dfn title="specializationOf" id="dfn-specializationof" class="internalDFN">specialization</dfn><sup><a class="internalDFN" href="#dfn-specializationof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">specializationOf(infra, supra)</span> in PROV-N,</span> has:
<ul>
-<li><span class="attribute" id="specialization.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)<span class="delete"> of the specialized entity;</span><span class="insert">
-of the entity that is a specialization of the general entity (</span><span class="name"><span class="insert">supra</span></span><span class="insert">);</span></li>
+<li><span class="attribute" id="specialization.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
+of the entity that is a specialization of the general entity (<span class="name">supra</span>);</li>
<li><span class="attribute" id="specialization.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being specialized.</li>
</ul>
</div>
-
-
<div class="anexample" id="anexample-specialization"><div class="anexampleTitle">Example 42<sup><a class="internalDFN" href="#anexample-specialization"><span class="diamond"> ◊</span></a></sup></div>
<p>
The BBC news home page on 2012-03-23 <span class="name">ex:bbcNews2012-03-23</span>
@@ -3190,15 +3186,6 @@
-
-
-
-
-
-
-
-
-
</div>
<div id="term-alternate" class="section">
@@ -3224,11 +3211,11 @@
<a href="http://www.bbc.co.uk/news/science-environment-17526723">bbc:news/science-environment-17526723</a> for desktop
is an alternate of a
<a href="http://www.bbc.co.uk/news/mobile/science-environment-17526723">bbc:news/mobile/science-environment-17526723</a> for mobile devices.</p>
-<pre class="codeexample">entity(bbc:news/science-environment-17526723,
+<pre class="codeexample">entity(bbc:news/science-environment-17526723,
[ prov:type="a news item for desktop"])
-entity(bbc:news/mobile/science-environment-17526723,
+entity(bbc:news/mobile/science-environment-17526723,
[ prov:type="a news item for mobile devices"])
-alternateOf(bbc:news/science-environment-17526723,
+alternateOf(bbc:news/science-environment-17526723,
bbc:news/mobile/science-environment-17526723)
</pre>
</div>
@@ -3247,82 +3234,80 @@
</div>
-
-
<div id="term-mention" class="section">
-<h4><span class="secno">5.5.3 </span><span class="delete">Contextualization</span><span class="insert">Mention</span></h4>
-
-<div class="note"><span class="insert">
-This construct is a </span><b><span class="insert">FEATURE AT RISK</span></b><span class="insert">.
-</span></div>
-
-
-<p>The following notion is a relation between two entities with regard to a <span class="delete">bundle (referred to as remote bundle). In contrast, the bundle in which this relation occurs is referred to as local </span>bundle. </p>
-
-
-<span class="glossary-ref"><span class="delete"> An entity that is a </span><span class="delete">contextualization</span><span class="insert"> The </span><dfn id="concept-mention" class="internalDFN"><span class="insert">mention</span></dfn><sup><a class="internalDFN" href="#concept-mention"><span class="diamond"> ◊</span></a></sup> of <span class="insert">an entity in a bundle (containing a description of this entity) is </span>another entity <span class="insert">that is a specialization of the former and that </span>presents <span class="delete">all aspects of the latter</span><span class="insert">the bundle</span> as <span class="delete">per the latter's</span><span class="insert">a further additional aspect. </span></span>
-
-
-
-<p><span class="insert">
-An entity is interpreted with respect to a bundle's</span> description in <span class="delete">another</span><span class="insert">a
+<h4><span class="secno">5.5.3 </span>Mention</h4>
+
+
+
+
+<div class="note">
+<p><span class="insert">Note: </span>This <span class="insert">feature is "</span><a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi"><span class="insert">at risk</span></a><span class="insert">" and may be removed from this specification based on feedback. Please send feedback to public-prov-comments@w3.org.</span></p>
+<p><span class="insert">The "Mention" </span>construct <span class="delete">is a </span><span class="delete">FEATURE AT RISK</span><span class="delete">.
+</span><span class="insert">might be removed from PROV if implementation experience reveals problems with supporting this construct.</span></p>
+</div>
+
+
+<p><span class="delete">The</span><span class="insert">An entity </span><span class="name"><span class="insert">e1</span></span><span class="insert"> may be mentioned in a bundle </span><span class="name"><span class="insert">b</span></span><span class="insert">, which contains some
+ descriptions about this entity </span><span class="name"><span class="insert">e1</span></span><span class="insert">: how </span><span class="name"><span class="insert">e1</span></span><span class="insert"> was generated and used, which activities </span><span class="name"><span class="insert">e1</span></span><span class="insert"> is involved with, the agents </span><span class="name"><span class="insert">e1</span></span><span class="insert"> is attributed to, etc. Other bundles may contain other descriptions about the same entity </span><span class="name"><span class="insert">e1</span></span><span class="insert">.
+Some applications may want to interpret
+this entity </span><span class="name"><span class="insert">e1</span></span><span class="insert"> with respect to the descriptions found in the bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> it occurs in. To this end, PROV allows a new entity </span><span class="name"><span class="insert">e2</span></span><span class="insert"> to be created, which is a specialization of the original entity </span><span class="name"><span class="insert">e1</span></span><span class="insert">, and which presents an additional aspect: the bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> containing some descriptions of </span><span class="name"><span class="insert">e1</span></span><span class="insert">. With this relation, applications that process </span><span class="name"><span class="insert">e2</span></span><span class="insert">
+can know that the attributes of </span><span class="name"><span class="insert">e2</span></span><span class="insert"> may have been computed according to the descriptions of </span><span class="name"><span class="insert">e1</span></span><span class="insert"> in </span><span class="name"><span class="insert">b</span></span><span class="insert">.</span></p>
+
+
+
+<p><span class="insert">Thus, the</span> following notion is a relation between two entities with regard to a bundle. <span class="insert">
+It is a special case of specialization.</span></p>
+
+
+<span class="glossary-ref"> The <dfn id="concept-mention" class="internalDFN">mention</dfn><sup><a class="internalDFN" href="#concept-mention"><span class="diamond"> ◊</span></a></sup> of an entity in a bundle (containing a description of this entity) is another entity that is a specialization of the former and that presents the bundle as a further additional aspect. </span>
+
+
+
+<p>
+An entity is interpreted with respect to a bundle's description in a
domain specific manner. The mention of this entity with respect to
-this</span> bundle <span class="delete">(referred</span><span class="insert">offers the opportunity</span> to <span class="delete">as remote bundle), and therefore constitutes a particular case of </span><span class="delete">specialization</span><span class="delete"> of the latter entity. </span><span class="insert">specialize it according to some
+this bundle offers the opportunity to specialize it according to some
domain-specific interpretation.
-</span></p>
-
-
-<p>A <span class="delete">bundle's
-descriptions provide</span><span class="insert">mention of an entity in</span> a <span class="delete">context</span><span class="insert">bundle results</span> in <span class="delete">which to interpret an</span><span class="insert">a specialization of this</span> entity <span class="delete">in a
-domain-specific manner.</span><span class="insert">with extra fixed aspects, including the</span> <span class="delete">The contextualization of this entity with respect to this bundle offers the opportunity to specialize it according to some domain-specific interpretation.
-</span>
-
-
-
-
-<span class="delete">A contextualization of an entity in a remote bundle results in a specialization of this entity with extra fixed aspects, including the remote </span>bundle that it is described in.
</p>
-
-
-
-<p></p><div class="attributes" id="attributes-mention">A <span class="delete">contextualization</span><dfn title="mentionOf" id="dfn-mentionof" class="internalDFN"><span class="insert">mention</span></dfn><sup><a class="internalDFN" href="#dfn-mentionof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression"><span class="delete">contextualizationOf(l, e,</span><span class="insert">mentionOf(infra, supra,</span> b)</span> in PROV-N,</span> has:
+<p>A mention of an entity in a bundle results in a specialization of this entity with extra fixed aspects, including the bundle that it is described in.
+</p>
+
+
+
+<p></p><div class="attributes" id="attributes-mention">A <dfn title="mentionOf" id="dfn-mentionof" class="internalDFN">mention</dfn><sup><a class="internalDFN" href="#dfn-mentionof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">mentionOf(infra, supra, b)</span> in PROV-N,</span> has:
<ul>
-<li><span class="delete">local</span><span class="attribute" id="mention.specificEntity"><span class="insert">specificEntity</span></span>: an identifier (<span class="name"><span class="delete">l</span><span class="insert">infra</span></span>)<span class="delete"> for an</span><span class="insert">
-of the</span> entity <span class="delete">in the local bundle (not explicitly identified) presenting the aspects of </span><span class="delete">e</span><span class="delete"> in remote bundle </span><span class="delete">b</span><span class="delete"> ;</span>
-<span class="delete">contextualized</span><span class="delete">: an identifier</span><span class="insert">that is a mention of the general entity</span> (<span class="name"><span class="delete">e</span><span class="insert">supra</span></span><span class="insert">);</span></li>
-<li><span class="attribute" id="mention.generalEntity"><span class="insert">generalEntity</span></span><span class="insert">: an identifier (</span><span class="name"><span class="insert">supra</span></span>) of <span class="insert">the entity that is being mentioned.</span></li>
-<li><span class="attribute" id="mention.bundle"><span class="insert">bundle</span></span><span class="insert">: </span>an <span class="delete">entity in some remote bundle </span><span class="delete">b</span><span class="delete">;</span>
-<span class="delete">bundle</span><span class="delete">: an</span><em class="rfc2119" title="optional"><span class="insert">optional</span></em> identifier (<span class="name">b</span>) <span class="delete">for</span><span class="insert">of</span> a <span class="delete">remote bundle.</span><span class="insert">bundle that contains a description of </span><span class="name"><span class="insert">supra</span></span><span class="insert"> and further constitutes one additional aspect presented by </span><span class="name"><span class="insert">infra</span></span><span class="insert">.</span></li>
+<li><span class="attribute" id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
+of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
+<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being mentioned.</li>
+<li><span class="attribute" id="mention.bundle">bundle</span>: an <span class="delete">optional</span> identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>
-
-
-
<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example 45<sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
-<p>In the following example, two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+<p><span class="delete">In the following example,</span><span class="insert">This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </span></p>
+<p><span class="insert">As an illustration, we consider that</span> two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
<pre class="codeexample">bundle ex:run1
- activity(ex:a1, 2011-11-16T16:00:00,2011-11-16T17:00:00) //duration: 1hour
- wasAssociatedWith(ex:a1,ex:Bob,[prov:role="controller"])
+ activity(ex:a1, <span class="delete">2011-11-16T16:00:00,2011-11-16T17:00:00)</span><span class="insert">2011-11-16T16:00:00, 2011-11-16T17:00:00)</span> //duration: 1hour
+ <span class="delete">wasAssociatedWith(ex:a1,ex:Bob,[prov:role="controller"])</span><span class="insert">wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])</span>
endBundle
bundle ex:run2
- activity(ex:a2, 2011-11-17T10:00:00,2011-11-17T17:00:00) //duration: 7hours
- wasAssociatedWith(ex:a2,ex:Bob,[prov:role="controller"])
+ activity(ex:a2, <span class="delete">2011-11-17T10:00:00,2011-11-17T17:00:00)</span><span class="insert">2011-11-17T10:00:00, 2011-11-17T17:00:00)</span> //duration: 7hours
+ <span class="delete">wasAssociatedWith(ex:a2,ex:Bob,[prov:role="controller"])</span><span class="insert">wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])</span>
endBundle
</pre>
-<p>A performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a <span class="delete">contextualization</span><span class="insert">mention</span> of <span class="name">ex:Bob</span> as described in<span class="delete"> remote </span> bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours.
+<p><span class="delete">A</span><span class="insert">The</span> performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours.
</p><pre class="codeexample">bundle tool:analysis01
agent(tool:Bob-2011-11-16, [perf:rating="good"])
- <span class="delete">contextualizationOf(tool:Bob-2011-11-16,</span><span class="insert">mentionOf(tool:Bob-2011-11-16,</span> ex:Bob, ex:run1)
+ mentionOf(tool:Bob-2011-11-16, ex:Bob, ex:run1)
agent(tool:Bob-2011-11-17, [perf:rating="bad"])
- <span class="delete">contextualizationOf(tool:Bob-2011-11-17,</span><span class="insert">mentionOf(tool:Bob-2011-11-17,</span> ex:Bob, ex:run2)
+ mentionOf(tool:Bob-2011-11-17, ex:Bob, ex:run2)
endBundle
</pre>
</div>
@@ -3341,17 +3326,17 @@
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
wasAttributedTo(obs:bundle1, ex:observer01)
</pre>
-Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool. It may useful for the tool configuration for this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool. It may useful for the <span class="delete">tool configuration for</span><span class="insert">visualization layout of</span> this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
<pre class="codeexample">
bundle tool:bundle2
entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
wasAttributedTo(tool:bundle2, viz:Visualizer)
entity(tool:report1, [viz:color="orange"])
- <span class="delete">contextualizationOf(tool:report1,</span><span class="insert">mentionOf(tool:report1,</span> obs:bundle1, ex:report1)
+ mentionOf(tool:report1, <span class="delete">obs:bundle1, ex:report1)</span><span class="insert">ex:report1, obs:bundle1)</span>
entity(tool:report2, [viz:color="blue"])
- <span class="delete">contextualizationOf(tool:report2,</span><span class="insert">mentionOf(tool:report2,</span> obs:bundle1, ex:report2)
+ mentionOf(tool:report2, <span class="delete">obs:bundle1, ex:report2)</span><span class="insert">ex:report2, obs:bundle1)</span>
endBundle
</pre>
@@ -3375,43 +3360,32 @@
-
-
</div>
<div id="component6" class="section">
<h3><span class="secno">5.6 </span>Component 6: Collections</h3>
<p>The sixth component of PROV-DM is concerned with the notion of collections.
-A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection (attribution), which members it contains as it evolves, and how it was assembled. The purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections.<span class="delete"> In PROV, the concept of Collection is implemented by means of dictionaries, which we introduce in this section. </span> </p>
-
-<p><a href="#figure-component6">Figure 10</a> depicts
-the sixth component with <span class="delete">four </span><span class="insert">two </span>new classes (Collection, <span class="delete">Dictionary, EmptyDictionary,</span><span class="insert">Empty Collection)</span> and <span class="delete">Pair) and three associations (insertion, removal, and memberOf).</span><span class="insert">one association (MemberOf).</span>
+A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection (attribution), which members it contains as it evolves, and how it was assembled. The purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections. </p>
+
+<p><a href="#figure-component6">Figure <span class="delete">10</span><span class="insert">11</span></a> depicts
+the sixth component with two new classes (Collection, Empty Collection) and one association (MemberOf).
</p>
<div style="text-align: center;">
<span class="figure" style="max-width: 95%; ">
-<img src="uml/component6.png" alt="collection">
-
-
-
-<p><span class="figcaption" id="figure-component6">Figure 10: Collections Component Overview</span></p>
+<img src="uml/component6.png" alt="collection"><br>
+<span class="figcaption" id="figure-component6">Figure <span class="delete">10:</span><span class="insert">11:</span> Collections Component Overview</span>
</span>
</div>
-<span class="delete">The intent of these relations and types is to express the </span><span class="delete">history of changes that occurred to a collection</span><span class="delete">.
-Changes to collections are about the insertion of entities into, and the removal of entities from the collection.
-Indirectly, such history provides a way to reconstruct the contents of the collection.</span>
-
<div id="term-collection" class="section">
<h4><span class="secno">5.6.1 </span>Collection</h4>
<span class="glossary-ref"> A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections. </span>
-<span class="delete">A collection is a multiset of entities (it is a multiset, rather than a set, because it may not be possible to verify that two distinct entity identitifiers do not denote, in fact, the same entity).</span>
-
<span class="glossary-ref"> An <dfn id="concept-empty-collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members. </span>
@@ -3430,15 +3404,11 @@
</pre>
</div>
-<span class="delete">In PROV, the concept of Collection is provided as an extensibility point for specialized kinds of collections. One of these, Dictionary, is defined next. </span>
-
-
-
</div>
<div id="term-collection-membership" class="section">
-<h4><span class="secno">5.6.2 </span>Collection Memberhsip</h4>
+<h4><span class="secno">5.6.2 </span>Collection <span class="delete">Memberhsip</span><span class="insert">Membership</span></h4>
<p>A <strong>collection membership</strong> relation is defined, to allow stating the members of a Collection. </p>
@@ -3455,9 +3425,10 @@
<li><span class="attribute" id="membership.complete">complete</span>: an <em class="rfc2119" title="optional">optional</em> boolean
<a title="value" href="#concept-value" class="internalDFN">Value</a> (<span class="name">cplt</span>). It is interpreted as follows:
<ul>
-<li>if it is present and set to true, then c is believed to include all and only the members specified in the entity-set;
-</li><li>if it is present and set to false, then c is believed to include more members in addition to those specified in the entity-set;
-</li><li>if it is not present, then c is believed to include all the members specified in the entity-set, and it <em class="rfc2119" title="may">may</em> include more.
+<li>if it is present and set to true, then
+<span class="name">c</span> is believed to include all and only the members specified in the entity-set;
+</li><li>if it is present and set to <span class="delete">false,</span><span class="insert">false or if it is not present,</span> then <span class="name">c</span> is believed to include more members in addition to those specified in the <span class="delete">entity-set;
+</span><span class="delete">if it is not present, then c is believed to include all the members specified in the entity-set, and it </span><span class="delete">may</span><span class="delete"> include more.</span><span class="insert">entity-set.</span>
</li></ul>
</li><li><span class="attribute" id="membership.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this relation.</li>
@@ -3472,221 +3443,6 @@
</div>
-<span class="delete">5.6.3 </span><span class="delete">Dictionary</span>
-
-<span class="delete">PROV-DM defines a specific type of collection, specified as follows.</span>
-
-
-<span class="delete"> A </span><span class="delete">dictionary</span><span class="delete"> ◊</span><span class="delete"> is a collection whose members are indexed by keys. </span>
-
-<span class="delete">Conceptually, a dictionary has a logical structure consisting of key-entity pairs. This structure is often referred to as a </span><span class="delete">map</span><span class="delete">, and is a generic indexing mechanism that can abstract commonly used data structures, including associative lists, relational tables, ordered lists, and more. The specification of such specialized structures in terms of key-value pairs is out of the scope of this document.</span>
-
-<span class="delete">A given dictionary forms a given structure for its members. A different structure (obtained either by insertion or removal of members) constitutes a different dictionary. Hence,
- for the purpose of provenance, a dictionary entity is viewed as a snapshot of a structure. Insertion and removal operations result in new snapshots, each snapshot forming an identifiable dictionary entity.</span>
-
-
-
-
-<span class="delete">Following the earlier definitions for generic collections, PROV-DM defines the following types related to dictionaries:</span>
-
-
- <span class="delete">prov:Dictionary</span><span class="delete"> is a subtype of </span><span class="delete">prov:Collection</span><span class="delete">. It denotes an entity of type dictionary, i.e. an entity that can participate in relations amongst dictionaries;
-
- </span><span class="delete">prov:EmptyDictionary</span><span class="delete"> is a subtype of </span><span class="delete">prov:EmptyCollection</span><span class="delete">. It denotes an empty dictionary.
-</span>
-
-
-<span class="delete">Example 48</span><span class="delete"> ◊</span>
-<span class="delete">entity(d0, [prov:type='prov:EmptyDictionary' ]) // d0 is an empty dictionary
-entity(d1, [prov:type='prov:Dictionary' ]) // d1 is a dictionary, with unknown content
-</span>
-
-
-
-
-
-<span class="delete">5.6.4 </span><span class="delete">Dictionary Membership</span>
-
-
- <span class="delete">Membership</span><span class="delete"> ◊</span><span class="delete"> is the belonging of a key-entity pair to a dictionary. </span><span class="delete">
-
-The </span><span class="delete">dictionary membership</span><span class="delete"> has the same purpose as the </span><span class="delete">collection membership</span><span class="delete"> relation, but it applies to entities having </span><span class="delete">prov:type = 'prov:Dictionary'</span><span class="delete">. It allows stating the members of a Dictionary.
-
-
-
-</span>
-<span class="delete">
- A </span><span class="delete">membership</span><span class="delete"> ◊</span><span class="delete"> relation, written </span><span class="delete">memberOf(id; c, {(key_1, e_1), ..., (key_n, e_n)}, cplt, attrs)</span><span class="delete">, has:
-</span>
-<span class="delete">id</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> identifier identifying the relation;</span>
-<span class="delete">dictionary</span><span class="delete">: an identifier (</span><span class="delete">c</span><span class="delete">) for the dictionary whose members are asserted; </span>
-<span class="delete">key-entity-set</span><span class="delete">: a set of key-entity pairs </span><span class="delete">(key_1, e_1)</span><span class="delete">, ..., </span><span class="delete">(key_n, e_n)</span><span class="delete"> that are members of the dictionary;</span>
-<span class="delete">complete</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> boolean
-</span><span class="delete">Value</span><span class="delete"> (</span><span class="delete">cplt</span><span class="delete">). It is interpreted as follows:
-</span>
-<span class="delete">if it is present and set to true, then c is believed to include all and only the members specified in the key-entity-set;
-</span><span class="delete">if it is present and set to false, then c is believed to include more members in addition to those specified in the key-entity-set;
-</span><span class="delete">if it is not present, then c is believed to include all the members specified in the key-entity-set, and it </span><span class="delete">may</span><span class="delete"> include more.
-</span>
-
-
-<span class="delete">attributes</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> set (</span><span class="delete">attrs</span><span class="delete">) of attribute-value pairs representing additional information about this relation.</span>
-
-
-
-
-<span class="delete">
-The attribute </span><span class="delete">complete</span><span class="delete"> is interpreted as for the general </span><span class="delete">collection membership</span><span class="delete"> relation.
-
-</span><span class="delete">Example 49</span><span class="delete"> ◊</span>
-<span class="delete">entity(d1, [prov:type='prov:Dictionary' ]) // d1 is a dictionary, with unknown content
-entity(d2, [prov:type='prov:Dictionary' ]) // d2 is a dictionary, with unknown content
-
-entity(e1)
-entity(e2)
-
-memberOf(d1, {("k1", e1), ("k2", e2)} )
-memberOf(d2, {("k1", e1), ("k2", e2)}, true)
-
-</span><span class="delete">
-From these descriptions, we conclude:
-</span>
- <span class="delete">d1</span><span class="delete"> has the following pairs as members: </span><span class="delete">("k1", e1), ("k2", e2)</span><span class="delete">, and may contain others.
-</span> <span class="delete">d2</span><span class="delete"> exactly has the following pairs as members: </span><span class="delete">("k1", e1), ("k2", e2)</span><span class="delete">, and does not contain any other.
-</span>
-<span class="delete"> Thus, the membership of </span><span class="delete">d1</span><span class="delete"> is only partially known.</span>
-
-
-
-
-
-
-<span class="delete">5.6.5 </span><span class="delete">Dictionary Insertion</span>
-
- <span class="delete">Insertion</span><span class="delete"> ◊</span><span class="delete"> is a derivation that transforms a dictionary into another, by insertion of one or more key-entity pairs. </span>
-
-
-<span class="delete">An </span><span class="delete">Insertion</span><span class="delete"> ◊</span><span class="delete"> relation</span><span class="delete">, written </span><span class="delete">derivedByInsertionFrom(id; d2, d1, {(key_1, e_1), ..., (key_n, e_n)}, attrs)</span><span class="delete">,</span><span class="delete"> has:</span>
-
-<span class="delete">id</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> identifier identifying the relation;</span>
-<span class="delete">after</span><span class="delete">: an identifier (</span><span class="delete">d2</span><span class="delete">) for the dictionary </span><span class="delete">after</span><span class="delete"> insertion; </span>
-<span class="delete">before</span><span class="delete">: an identifier (</span><span class="delete">d1</span><span class="delete">) for the dictionary </span><span class="delete">before</span><span class="delete"> insertion;</span>
-<span class="delete">key-entity-set</span><span class="delete">: the inserted key-entity pairs </span><span class="delete">(key_1, e_1)</span><span class="delete">, ..., </span><span class="delete">(key_n, e_n)</span><span class="delete"> in which each </span><span class="delete">key_i</span><span class="delete"> is a </span><span class="delete">value</span><span class="delete">, and </span><span class="delete">e_i</span><span class="delete"> is an identifier for the entity that has been inserted with the key;
- each </span><span class="delete">key_i</span><span class="delete"> is expected to be unique for the key-entity-set;
-</span>
-<span class="delete">attributes</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> set (</span><span class="delete">attrs</span><span class="delete">) of attribute-value pairs representing additional information about this relation.</span>
-
-
-
-<span class="delete">
-An Insertion relation </span><span class="delete">derivedByInsertionFrom(id; d2, d1, {(key_1, e_1), ..., (key_n, e_n)})</span><span class="delete"> states that </span><span class="delete">d2</span><span class="delete"> is the dictionary
-following the insertion of pairs </span><span class="delete">(key_1, e_1)</span><span class="delete">, ..., </span><span class="delete">(key_n, e_n)</span><span class="delete"> into dictionary </span><span class="delete">d1</span><span class="delete">.</span>
-
-
-<span class="delete">Example 50</span><span class="delete"> ◊</span>
-<span class="delete">entity(d0, [prov:type='prov:EmptyDictionary' ]) // d0 is an empty dictionary
-entity(e1)
-entity(e2)
-entity(e3)
-entity(d1, [prov:type='prov:Dictionary' ])
-entity(d2, [prov:type='prov:Dictionary' ])
-
-derivedByInsertionFrom(d1, d0, {("k1", e1), ("k2", e2)})
-derivedByInsertionFrom(d2, d1, {("k3", e3)})
-</span><span class="delete">
-From this set of descriptions, we conclude:
-</span>
- <span class="delete">d0</span><span class="delete"> is the set </span><span class="delete">{ }</span>
- <span class="delete">d1</span><span class="delete"> is the set </span><span class="delete">{ ("k1", e1), ("k2", e2) }</span>
- <span class="delete">d2</span><span class="delete"> is the set </span><span class="delete">{ ("k1", e1), ("k2", e2), ("k3", e3) }</span>
-
-
-
-<span class="delete">Insertion provides an "update semantics" for the keys that are already present in a dictionary,
-since a new pair replaces an existing pair with the same key in the new dictionary. This is illustrated by the following example.</span>
-
-<span class="delete">Example 51</span><span class="delete"> ◊</span>
-<span class="delete">entity(d0, [prov:type='prov:EmptyDictionary' ]) // d0 is an empty dictionary
-entity(e1)
-entity(e2)
-entity(e3)
-entity(d1, [prov:type='prov:Dictionary' ])
-entity(d2, [prov:type='prov:Dictionary' ])
-
-derivedByInsertionFrom(d1, d0, {("k1", e1), ("k2", e2)})
-derivedByInsertionFrom(d2, d1, {("k1", e3)})
-</span><span class="delete">
- This is a case of </span><span class="delete">update</span><span class="delete"> of </span><span class="delete">e1</span><span class="delete"> to </span><span class="delete">e3</span><span class="delete"> for the same key, </span><span class="delete">"k1"</span><span class="delete">. </span><span class="delete">
- From this set of descriptions, we conclude:
-</span>
- <span class="delete">d0</span><span class="delete"> is the set </span><span class="delete">{ }</span>
- <span class="delete">d1</span><span class="delete"> is the set </span><span class="delete">{ ("k1", e1), ("k2", e2) }</span>
- <span class="delete">d2</span><span class="delete"> is the set </span><span class="delete">{ ("k1", e3), ("k2", e2) }</span>
-
-
-
-
-
-
-
-<span class="delete">5.6.6 </span><span class="delete">Dictionary Removal</span>
-
- <span class="delete">Removal</span><span class="delete"> ◊</span><span class="delete"> is a derivation that transforms a dictionary into another, by removing one or more key-entity pairs. </span>
-
-
-
-
-<span class="delete"> A </span><span class="delete">Removal</span><span class="delete"> ◊</span><span class="delete"> relation, written </span><span class="delete">derivedByRemovalFrom(id; d2, d1, {key_1, ... key_n}, attrs)</span><span class="delete">, has:</span>
-
-<span class="delete">id</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> identifier identifying the relation;</span>
-<span class="delete">after</span><span class="delete">: an identifier (</span><span class="delete">d2</span><span class="delete">) for the dictionary </span><span class="delete">after</span><span class="delete"> the deletion; </span>
-<span class="delete">before</span><span class="delete">: an identifier (</span><span class="delete">d1</span><span class="delete">) for the dictionary </span><span class="delete">before</span><span class="delete"> the deletion;</span>
-<span class="delete">key-set</span><span class="delete">: a set of deleted keys </span><span class="delete">key_1</span><span class="delete">, ..., </span><span class="delete">key_n</span><span class="delete">, for which each </span><span class="delete">key_i</span><span class="delete"> is a </span><span class="delete">value</span><span class="delete">;</span>
-<span class="delete">attributes</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> set (</span><span class="delete">attrs</span><span class="delete">) of attribute-value pairs representing additional information about this relation.</span>
-
-
-
-<span class="delete">A Removal relation </span><span class="delete">derivedByRemovalFrom(id; d2,d1, {key_1, ..., key_n})</span><span class="delete"> states that </span><span class="delete">d2</span><span class="delete"> is the dictionary following the removal of the set of pairs corresponding to keys </span><span class="delete">key_1...key_n</span><span class="delete"> from </span><span class="delete">d1</span><span class="delete">.
-
-</span><span class="delete">Example 52</span><span class="delete"> ◊</span>
-<span class="delete">entity(d0, [prov:type="prov:EmptyDictionary"]) // d0 is an empty dictionary
-entity(e1)
-entity(e2)
-entity(e3)
-entity(d1, [prov:type="prov:Dictionary"])
-entity(d2, [prov:type="prov:Dictionary"])
-
-derivedByInsertionFrom(d1, d0, {("k1", e1), ("k2",e2)})
-derivedByInsertionFrom(d2, d1, {("k3", e3)})
-derivedByRemovalFrom(d3, d2, {"k1", "k3"})
-</span><span class="delete">
-From this set of descriptions, we conclude:
-</span>
-<span class="delete">d0</span><span class="delete"> is the set </span><span class="delete">{ }</span>
-<span class="delete">d1</span><span class="delete"> is the set </span><span class="delete">{ ("k1", e1), ("k2", e2) }</span>
-<span class="delete">d2</span><span class="delete"> is the set </span><span class="delete">{ ("k1", e1), ("k2", e2), ("k3", e3) }</span>
-<span class="delete">d3</span><span class="delete"> is the set </span><span class="delete">{ ("k2", e2) }</span>
-
-
-
-
-
-
-
-
-<span class="delete">Further considerations: </span>
-
-
-
-
-
-<span class="delete">The representation of a dictionary through these relations makes no assumption regarding the underlying data structure used to store and manage dictionaries. In particular, no assumptions are needed regarding the mutability of a data structure that is subject to updates. Entities, however, are immutable and this applies to those entities that represent dictionaries. This is reflected in the constraints listed in [</span><span class="delete">PROV-CONSTRAINTS</span><span class="delete">]. </span>
-
-
-
-
-
-
</div>
@@ -3728,7 +3484,7 @@
<tbody><tr><td><b>Attribute</b></td><td><b>Allowed In</b></td><td><b>value</b></td><td><b>Section</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr><td><a title="label" href="#concept-label" class="internalDFN">prov:label</a></td><td><em>any construct</em></td><td>A <a href="#concept-value" class="internalDFN">Value</a> of type <a class="section-ref" href="http://www.w3.org/TR/xmlschema11-2/#string">xsd:string</a></td><td><a class="section-ref" href="#term-attribute-label"><span>Section 5.7.2.1</span></a> </td></tr>
-<tr><td><a title="location" href="#concept-location" class="internalDFN">prov:location</a></td><td><a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, <a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a><span class="insert">, </span><a href="#concept-usage" class="internalDFN">Usage</a>, <span class="delete">and </span><a href="#concept-generation" class="internalDFN">Generation</a><span class="delete">.</span><span class="insert">, </span><a href="#concept-invalidation" class="internalDFN"><span class="insert">Invalidation</span></a><span class="insert">, </span><a href="#concept-start" class="internalDFN"><span class="insert">Start</span></a><span class="insert">, and </span><a href="#concept-end" class="internalDFN"><span class="insert">End</span></a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-location"><span>Section 5.7.2.2</span></a> </td></tr>
+<tr><td><a title="location" href="#concept-location" class="internalDFN">prov:location</a></td><td><a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, <a href="#concept-agent" class="internalDFN">Agent</a>, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-location"><span>Section 5.7.2.2</span></a> </td></tr>
<tr><td><a title="role" href="#concept-role" class="internalDFN">prov:role</a></td><td><a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-activityAssociation" class="internalDFN">Association</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-role"><span>Section 5.7.2.3</span></a> </td></tr>
<tr><td><a title="type" href="#concept-type" class="internalDFN">prov:type</a></td><td><em>any construct</em></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-type"><span>Section 5.7.2.4</span></a> </td></tr>
<tr><td><a title="value-attribute" href="#concept-value-attribute" class="internalDFN">prov:value</a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a></td><td><a class="section-ref" href="#term-attribute-value"><span>Section 5.7.2.5</span></a> </td></tr>
@@ -3747,10 +3503,14 @@
<span class="glossary-ref"> The attribute <dfn id="concept-label" title="label" class="internalDFN"><span class="name">prov:label</span></dfn><sup><a class="internalDFN" href="#concept-label"><span class="diamond"> ◊</span></a></sup> provides a human-readable representation of an instance of a PROV-DM type or relation. </span>
The value associated with the attribute <span class="name">prov:label</span> <em class="rfc2119" title="must">must</em> be a string.</p>
-<div class="anexample" id="example_48"><div class="anexampleTitle">Example <span class="delete">53</span><span class="insert">48</span><sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_48"><div class="anexampleTitle">Example 48<sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
<p>The following entity is provided with a label attribute.</p>
<pre class="codeexample"> entity(ex:e1, [ prov:label="This is a human-readable label" ])
</pre>
+
+<p><span class="insert">The following entity has two label attributes, in French and English.</span></p>
+<pre class="codeexample"><span class="insert"> entity(ex:car01, [ prov:label="Voiture 01"@fr, prov:label="Car 01"@en ])
+</span></pre>
</div>
</div>
@@ -3764,12 +3524,12 @@
<p>
-The attribute <span class="name">prov:location</span> is an <em class="rfc2119" title="optional">optional</em> attribute of <span class="delete">entity, activity, usage,</span><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a><span class="insert">, </span><a href="#concept-activity" class="internalDFN"><span class="insert">Activity</span></a><span class="insert">, </span><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a><span class="insert">, </span><a href="#concept-usage" class="internalDFN"><span class="insert">Usage</span></a><span class="insert">, </span><a href="#concept-generation" class="internalDFN"><span class="insert">Generation</span></a><span class="insert">, </span><a href="#concept-invalidation" class="internalDFN"><span class="insert">Invalidation</span></a><span class="insert">, </span><a href="#concept-start" class="internalDFN"><span class="insert">Start</span></a><span class="insert">,</span> and <span class="delete">generation.</span><a href="#concept-end" class="internalDFN"><span class="insert">End</span></a><span class="insert">.</span> The value associated with the attribute <span class="name">prov:location</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>, expected to denote a location.
+The attribute <span class="name">prov:location</span> is an <em class="rfc2119" title="optional">optional</em> attribute of <a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, <a href="#concept-agent" class="internalDFN">Agent</a>, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a>. The value associated with the attribute <span class="name">prov:location</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>, expected to denote a location.
</p>
-<div class="anexample" id="example-location"><div class="anexampleTitle">Example <span class="delete">54</span><span class="insert">49</span><sup><a class="internalDFN" href="#example-location"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example-location"><div class="anexampleTitle">Example 49<sup><a class="internalDFN" href="#example-location"><span class="diamond"> ◊</span></a></sup></div>
<p>The following expression describes entity Mona Lisa, a painting, with a location attribute. </p>
-<pre class="codeexample"> entity(ex:MonaLisa, [ prov:location="Le <span class="delete">Louvres,</span><span class="insert">Louvre,</span> Paris", prov:type="StillImage" ])
+<pre class="codeexample"> entity(ex:MonaLisa, [ prov:location="Le Louvre, Paris", prov:type="StillImage" ])
</pre>
<p>The following expression describes a cell, at coordinates (5,5), with value 10. </p>
<pre class="codeexample"> entity(ex:cell, [ prov:location="(5,5)", prov:value="10" %% xsd:integer ])
@@ -3788,7 +3548,7 @@
<p>
The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span class="name">prov:role</span> attribute <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>.</p>
-<div class="anexample" id="anexample-role"><div class="anexampleTitle">Example <span class="delete">55</span><span class="insert">50</span><sup><a class="internalDFN" href="#anexample-role"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-role"><div class="anexampleTitle">Example 50<sup><a class="internalDFN" href="#anexample-role"><span class="diamond"> ◊</span></a></sup></div>
<p>The following activity is associated with an agent acting as the operator. </p>
<pre class="codeexample"> wasAssociatedWith(a, ag, [ prov:role="operator" ])
</pre>
@@ -3809,7 +3569,7 @@
the value associated with a <span class="name">prov:type</span> attribute <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value.</a> The attribute <span class="name">prov:type</span>
is allowed to occur multiple times.</p>
-<div class="anexample" id="example_51"><div class="anexampleTitle">Example <span class="delete">56</span><span class="insert">51</span><sup><a class="internalDFN" href="#example_51"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_51"><div class="anexampleTitle">Example 51<sup><a class="internalDFN" href="#example_51"><span class="diamond"> ◊</span></a></sup></div>
<p>The following describes an agent of type software agent.</p>
<pre class="codeexample"> agent(ag, [ prov:type='prov:SoftwareAgent' ])
</pre>
@@ -3824,15 +3584,19 @@
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr><td><a title="bundle" href="#concept-bundle" class="internalDFN"><span class="name">prov:Bundle</span></a></td><td><a class="section-ref" href="#term-bundle"><span>Section 5.4.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
<tr><td><a title="collection" href="#concept-collection" class="internalDFN"><span class="name">prov:Collection</span></a></td><td><a class="section-ref" href="#term-collection"><span>Section 5.6.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
-<tr><td><a title="dictionary" href="#concept-dictionary" class="internalDFN"><span class="name">prov:Dictionary</span></a></td><td><a class="section-ref" href="#term-dictionary"><span>Section <span class="delete">5.6.3</span></span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
-<tr><td><a title="empty dictionary" href="#concept-empty-dictionary" class="internalDFN"><span class="name">prov:EmptyDictionary</span></a></td><td><a class="section-ref" href="#term-dictionary"><span>Section <span class="delete">5.6.3</span></span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
-<tr><td><a title="primary source" href="#concept-primary-source" class="internalDFN"><span class="name"><span class="delete">prov:HadPrimarySource</span><span class="insert">prov:PrimarySource</span></span></a></td><td><a class="section-ref" href="#term-primary-source"><span>Section 5.2.4</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
-<tr><td><a title="organization" href="#concept-organization" class="internalDFN"><span class="name">prov:Organization</span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent</a></td></tr>
-<tr><td><a title="person" href="#concept-person" class="internalDFN"><span class="name">prov:Person</span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent</a></td></tr>
-<tr><td><a title="plan" href="#concept-plan" class="internalDFN"><span class="name">prov:Plan</span></a></td> <td><a class="section-ref" href="#term-entity"><span>Section 5.1.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
-<tr><td><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="name">prov:SoftwareAgent</span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent</a></td></tr>
-<tr><td><a title="Quotation" href="#concept-quotation" class="internalDFN"><span class="name"><span class="delete">prov:WasQuotedFrom</span><span class="insert">prov:Quotation</span></span></a></td><td><a class="section-ref" href="#term-quotation"><span>Section 5.2.3</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
-<tr><td><a title="Revision" href="#concept-revision" class="internalDFN"><span class="name"><span class="delete">prov:WasRevisionOf</span><span class="insert">prov:Revision</span></span></a></td><td><a class="section-ref" href="#term-revision"><span>Section 5.2.2</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
+<tr><td><a title="empty collection" href="#concept-empty-collection" class="internalDFN"><span class="name"><span class="insert">prov:EmptyCollection</span></span></a></td><td><a class="section-ref" href="#term-collection"><span><span class="insert">Section 5.6.1</span></span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a></td></tr>
+<tr><td><a title="organization" href="#concept-organization" class="internalDFN"><span class="name"><span class="insert">prov:Organization</span></span></a></td><td><a class="section-ref" href="#term-agent"><span><span class="insert">Section 5.3.1</span></span></a></td><td><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a></td></tr>
+<tr><td><a title="person" href="#concept-person" class="internalDFN"><span class="name"><span class="insert">prov:Person</span></span></a></td><td><a class="section-ref" href="#term-agent"><span><span class="insert">Section 5.3.1</span></span></a></td><td><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a></td></tr>
+<tr><td><a title="plan" href="#concept-plan" class="internalDFN"><span class="name"><span class="insert">prov:Plan</span></span></a></td> <td><a class="section-ref" href="#term-entity"><span><span class="insert">Section 5.1.1</span></span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a></td></tr>
+<tr><td><a title="primary source" href="#concept-primary-source" class="internalDFN"><span class="name">prov:PrimarySource</span></a></td><td><a class="section-ref" href="#term-primary-source"><span>Section 5.2.4</span></a></td><td><a href="#concept-derivation" class="internalDFN">Derivation</a></td></tr>
+<tr><td><a title="Quotation" href="#concept-quotation" class="internalDFN"><span class="name"><span class="delete">prov:Organization</span><span class="insert">prov:Quotation</span></span></a></td><td><a class="section-ref" href="#term-quotation"><span><span class="insert">Section 5.2.3</span></span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td></tr>
+<tr><td><a title="Revision" href="#concept-revision" class="internalDFN"><span class="name"><span class="insert">prov:Revision</span></span></a></td><td><a class="section-ref" href="#term-revision"><span><span class="insert">Section 5.2.2</span></span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td></tr>
+<tr><td><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="name"><span class="insert">prov:SoftwareAgent</span></span></a></td><td><a class="section-ref" href="#term-agent"><span>Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN">Agent
+<span class="delete">prov:Person</span><span class="delete">Section 5.3.1</span><span class="delete">Agent</span>
+<span class="delete">prov:Plan</span> <span class="delete">Section 5.1.1</span><span class="delete">Entity</span>
+<span class="delete">prov:SoftwareAgent</span><span class="delete">Section 5.3.1</span><span class="delete">Agent</span>
+<span class="delete">prov:Quotation</span><span class="delete">Section 5.2.3</span><span class="delete">Derivation</span>
+<span class="delete">prov:Revision</span><span class="delete">Section 5.2.2</span><span class="delete">Derivation</span></a></td></tr>
</tbody></table>
</div>
@@ -3847,7 +3611,7 @@
<p>The attribute <span class="name">prov:value</span> is an <em class="rfc2119" title="optional">optional</em> attribute of entity. The value associated with the attribute <span class="name">prov:value</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <em class="rfc2119" title="may">may</em> occur at most once in a set of attribute-value pairs.</p>
-<div class="anexample" id="example_52"><div class="anexampleTitle">Example <span class="delete">57</span><span class="insert">52</span><sup><a class="internalDFN" href="#example_52"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_52"><div class="anexampleTitle">Example 52<sup><a class="internalDFN" href="#example_52"><span class="diamond"> ◊</span></a></sup></div>
<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
</p>
@@ -3860,10 +3624,6 @@
</pre>
</div>
-<span class="delete">Should we also have prov:encoding?</span>
-
-
-
</div>
@@ -3881,124 +3641,39 @@
<p>Each kind of such values is called a <em>datatype</em>.
Use of the following data types is <em class="rfc2119" title="recommended">recommended</em>. </p>
<ul>
-<li> The RDF-compatible [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]<span class="delete"> built-in types</span><span class="insert"> types, including those</span> taken from
+<li> The RDF-compatible [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>] types, including those taken from
the set of XML Schema Datatypes [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>];</li>
-<li> Qualified names introduced in this <span class="delete">specification;</span><span class="insert">specification.</span></li>
+<li> Qualified names introduced in this specification.</li>
</ul>
-<p><span class="insert">
+<p>
The normative definitions of these datatypes are provided by their respective specifications.
-</span></p>
-
-
-
-
-
-<p id="conformance-to-rdf-datatypes"><b><span class="insert">Conformance to RDF Datatypes</span></b><span class="insert"> As of the publication of this document, RDF 1.1 Concepts and Abstract Syntax [</span><cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS11"><span class="insert">RDF-CONCEPTS11</span></a></cite><span class="insert">] is not yet a </span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert"> Recommendation (see </span><a href="http://www.w3.org/TR/rdf11-concepts/"><span class="insert">http://www.w3.org/TR/rdf11-concepts/</span></a><span class="insert"> for the latest version).
-Both the PROV Working Group and the RDF Working Group are confident that there will be only minor changes before it becomes a </span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert"> Recommendation. In order to take advantage of the anticipated corrections and new features sooner, while also providing stability in case the specification does not advance as expected, conformance to PROV as it relates to RDF Datatypes is defined as follows:</span></p>
+</p>
+
+
+
+
+
+<p id="conformance-to-rdf-datatypes"><b>Conformance to RDF Datatypes</b> As of the publication of this document, RDF 1.1 Concepts and Abstract Syntax [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS11">RDF-CONCEPTS11</a></cite>] is not yet a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation (see <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a> for the latest version).
+Both the PROV Working Group and the RDF Working Group are confident that there will be only minor changes before it becomes a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. In order to take advantage of the anticipated corrections and new features sooner, while also providing stability in case the specification does not advance as expected, conformance to PROV as it relates to RDF Datatypes is defined as follows:</p>
<ul>
-<li><span class="insert">If</span> RDF <span class="delete">literal types for html</span><span class="insert">1.1 Concepts</span> and <span class="delete">xml</span><span class="insert">Abstract Syntax becomes a </span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert"> Recommendation, all references in PROV to
+<li>If RDF 1.1 Concepts and Abstract Syntax becomes a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation, all references in PROV to
RDF Concepts and Abstract Syntax will be normative references to the 1.1 Recommendation.
-</span></li><li><span class="insert">Until that time, references in PROV to RDF Concepts and Abstract Syntax features operate as follows:
-</span><ul>
-<li><span class="insert"> If RDF 1.0 defines the features, then the reference is normative to the 1.0 definition</span> [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite><span class="delete">].</span><span class="insert">];</span></li>
-<li><span class="insert">otherwise, the feature is optional in PROV and the reference is informative only.</span></li>
+</li><li>Until that time, references in PROV to RDF Concepts and Abstract Syntax features operate as follows:
+<ul>
+<li> If RDF 1.0 defines the features, then the reference is normative to the 1.0 definition [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>];</li>
+<li>otherwise, the feature is optional in PROV and the reference is informative only.</li>
</ul>
</li></ul>
-<p><span class="delete">
-The</span><span class="insert">This "change in</span> normative <span class="delete">definitions of these datatypes are provided by their respective specifications. An informative list of these datatypes appears in Table 8.
-</span><span class="insert">reference" is effective as of the publication of RDF 1.1 as a </span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert"> Recommendation. However, </span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert"> expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</span></p>
-
-<span class="delete">PROV accepts the RDF-Compatible XSD types that RDF enumerates in
-its own specification [</span><span class="delete">RDF-CONCEPTS</span><span class="delete">]. New RDF releases
-[</span><span class="delete">RDF-CONCEPTS11</span><span class="delete">] may extend the list of datatypes, and PROV would
-naturally accept those too.</span>
-
-
-
-
-
-
-
-<span class="delete">Table 8: Informative List of PROV-DM Data Types</span>
-
-
- <span class="delete">Datatype</span><span class="delete">Value space</span>
-
- <span class="delete">Core types</span><span class="delete">xsd:string</span><span class="delete">Character strings</span>
- <span class="delete">xsd:boolean</span><span class="delete">true, false</span>
- <span class="delete">xsd:decimal</span><span class="delete">Arbitrary-precision decimal numbers</span>
- <span class="delete">xsd:integer</span><span class="delete">Arbitrary-size integer numbers</span>
-
- <span class="delete">IEEE floating-point</span><span class="delete">numbers</span>
- <span class="delete">xsd:double</span><span class="delete">64-bit floating point numbers incl. ±Inf, ±0, NaN</span>
- <span class="delete">xsd:float</span><span class="delete">32-bit floating point numbers incl. ±Inf, ±0, NaN</span>
-
- <span class="delete">Time and date</span>
- <span class="delete">xsd:date</span><span class="delete">Dates (yyyy-mm-dd) with or without timezone</span>
- <span class="delete">xsd:time</span><span class="delete">Times (hh:mm:ss.sss…) with or without timezone</span>
- <span class="delete">xsd:dateTime</span><span class="delete">Date and time with or without timezone</span>
- <span class="delete">xsd:dateTimeStamp</span><span class="delete">Date and time with required timezone</span>
-
- <span class="delete">Recurring and</span><span class="delete">partial dates</span>
- <span class="delete">xsd:gYear</span><span class="delete">Gregorian calendar year</span>
- <span class="delete">xsd:gMonth</span><span class="delete">Gregorian calendar month</span>
- <span class="delete">xsd:gDay</span><span class="delete">Gregorian calendar day of the month</span>
- <span class="delete">xsd:gYearMonth</span><span class="delete">Gregorian calendar year and month</span>
- <span class="delete">xsd:gMonthDay</span><span class="delete">Gregorian calendar month and day</span>
- <span class="delete">xsd:duration</span><span class="delete">Duration of time</span>
- <span class="delete">xsd:yearMonthDuration</span><span class="delete">Duration of time (months and years only)</span>
- <span class="delete">xsd:dayTimeDuration</span><span class="delete">Duration of time (days, hours, minutes, seconds only)</span>
-
- <span class="delete">Limited-range</span><span class="delete">integer numbers</span>
- <span class="delete">xsd:byte</span><span class="delete">-128…+127 (8 bit)</span>
- <span class="delete">xsd:short</span><span class="delete">-32768…+32767 (16 bit)</span>
- <span class="delete">xsd:int</span><span class="delete">-2147483648…+2147483647 (32 bit)</span>
- <span class="delete">xsd:long</span><span class="delete">-9223372036854775808…+9223372036854775807 (64 bit)</span>
-
- <span class="delete">xsd:unsignedByte</span><span class="delete">0…255 (8 bit)</span>
- <span class="delete">xsd:unsignedShort</span><span class="delete">0…65535 (16 bit)</span>
- <span class="delete">xsd:unsignedInt</span><span class="delete">0…4294967295 (32 bit)</span>
- <span class="delete">xsd:unsignedLong</span><span class="delete">0…18446744073709551615 (64 bit)</span>
-
- <span class="delete">xsd:positiveInteger</span><span class="delete">Integer numbers >0</span>
- <span class="delete">xsd:nonNegativeInteger</span><span class="delete">Integer numbers ≥0</span>
- <span class="delete">xsd:negativeInteger</span><span class="delete">Integer numbers <0</span>
- <span class="delete">xsd:nonPositiveInteger</span><span class="delete">Integer numbers ≤0</span>
-
- <span class="delete">Encoded binary data</span>
- <span class="delete">xsd:hexBinary</span><span class="delete">Hex-encoded binary data</span>
- <span class="delete">xsd:base64Binary</span><span class="delete">Base64-encoded binary data</span>
-
- <span class="delete">Miscellaneous</span><span class="delete">XSD types</span>
- <span class="delete">xsd:language</span><span class="delete">Language tags per [</span><span class="delete">BCP47</span><span class="delete">]</span>
- <span class="delete">xsd:normalizedString</span><span class="delete">Whitespace-normalized strings</span>
- <span class="delete">xsd:token</span><span class="delete">Tokenized strings</span>
- <span class="delete">xsd:NMTOKEN</span><span class="delete">XML NMTOKENs</span>
- <span class="delete">xsd:Name</span><span class="delete">XML Names</span>
- <span class="delete">xsd:NCName</span><span class="delete">XML NCNames</span>
-
- <span class="delete">Qualified</span><span class="delete">Names or URIs</span>
- <span class="delete">xsd:anyURI</span><span class="delete">Absolute or relative URIs and IRIs</span>
- <span class="delete">prov:QUALIFIED_NAME</span><span class="delete">PROV qualified name</span>
-
- <span class="delete">RDF XML/HTML Literals</span>
- <span class="delete">rdf:XMLLiteral</span><span class="delete">XML content as a value</span>
- <span class="delete">rdf:HTML</span><span class="delete">HTML content as a value</span>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example <span class="delete">58</span><span class="insert">53</span><sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
+<p>This "change in normative reference" is effective as of the publication of RDF 1.1 as a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. However, <acronym title="World Wide Web Consortium">W3C</acronym> expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</p>
+
+
+
+
+
+
+
+<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example 53<sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
</p><pre class="codeexample"> "abc"
@@ -4020,7 +3695,7 @@
<p>We note that PROV-DM <dfn title="time" id="dfn-time" class="internalDFN">time instants</dfn><sup><a class="internalDFN" href="#dfn-time"><span class="diamond"> ◊</span></a></sup> are defined according to xsd:dateTime [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
-<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example <span class="delete">59</span><span class="insert">54</span><sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example 54<sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, the generation time of entity <span class="name">e1</span> is expressed according to
<a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
@@ -4084,7 +3759,7 @@
<li>Sub-types and sub-relations can be expressed by means of the reserved attribute
<a href="#term-attribute-type"><span class="name">prov:type</span></a>.
-<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example <span class="delete">60</span><span class="insert">55</span><sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example 55<sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e2</span> is a translation of <span class="name">e1</span>,
expressed as a sub-type of derivation.
@@ -4093,7 +3768,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example <span class="delete">61</span><span class="insert">56</span><sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example 56<sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e</span> is described as a Car, a type of entity.
</p><pre class="codeexample">
@@ -4109,7 +3784,7 @@
<li>Application and domain specific roles can be expressed by means of the reserved attribute
<a href="#term-attribute-role"><span class="name">prov:role</span></a>.
-<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example <span class="delete">62</span><span class="insert">57</span><sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example 57<sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, two computers <span class="name">ex:laptop4</span> and <span class="name">ex:desktop9</span> are used in different roles in a work activity.
</p><pre class="codeexample">
@@ -4184,14 +3859,12 @@
<div class="appendix section" id="acknowledgements">
<h2><span class="secno">A. </span>Acknowledgements</h2>
- <p><span class="delete">
- WG membership</span><span class="insert">
-
-This document has been produced by the PROV Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks</span> to<span class="delete"> be listed here.</span><span class="insert"> Sandro Hawke (</span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert">/</span><acronym title="Massachusetts Institute of Technology"><span class="insert">MIT</span></acronym><span class="insert">), Ivan Herman (</span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert">/</span><acronym title="European Research Consortium for Informatics and Mathematics"><span class="insert">ERCIM</span></acronym><span class="insert">), Tom Baker for their thorough reviews.</span>
+ <p>
+
+This document has been produced by the PROV Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to Sandro Hawke (<acronym title="World Wide Web Consortium">W3C</acronym>/<acronym title="Massachusetts Institute of Technology">MIT</acronym>), Ivan Herman (<acronym title="World Wide Web Consortium">W3C</acronym>/<acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym>), Tom Baker for their thorough reviews.
</p>
-
-
-<p><span class="insert">
+
+<p>
Members of the PROV Working Group at the time of publication of this document were:
Ilkay Altintas (Invited expert),
@@ -4215,9 +3888,9 @@
Paul Groth (Vrije Universiteit),
Olaf Hartig (Invited expert),
David Hau (National Cancer Institute, NCI),
-Sandro Hawke (</span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert">/</span><acronym title="Massachusetts Institute of Technology"><span class="insert">MIT</span></acronym><span class="insert">),
+Sandro Hawke (<acronym title="World Wide Web Consortium">W3C</acronym>/<acronym title="Massachusetts Institute of Technology">MIT</acronym>),
Jörn Hees (German Research Center for Artificial Intelligence (DFKI) Gmbh),
-Ivan Herman, (</span><acronym title="World Wide Web Consortium"><span class="insert">W3C</span></acronym><span class="insert">/</span><acronym title="European Research Consortium for Informatics and Mathematics"><span class="insert">ERCIM</span></acronym><span class="insert">),
+Ivan Herman, (<acronym title="World Wide Web Consortium">W3C</acronym>/<acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym>),
Ralph Hodgson (TopQuadrant),
Hook Hua (Invited expert),
Trung Dong Huynh (University of Southampton),
@@ -4251,13 +3924,9 @@
Stephan Zednik (Rensselaer Polytechnic Institute),
Jun Zhao (University of Oxford),
Yuting Zhao (University of Aberdeen, Computing Science).
-</span></p>
+</p>
</div>
-
-
-
-