--- a/model/diff.html Tue May 29 13:13:18 2012 -0400
+++ b/model/diff.html Tue May 29 13:13:52 2012 -0400
@@ -955,7 +955,7 @@
font-weight: bold;
}
</span></style><link href="./extra-dm.css" rel="stylesheet" type="text/css" charset="utf-8"><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="insert">working towards WD6 (</span><a href="diff.html"><span class="insert">Diffs since last release</span></a><span class="insert">)</span></h2><h2 id="w3c-editor-s-draft-28-may-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">03</span><span class="insert">28</span> May 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></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><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120202/</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120503/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+ <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="insert">working towards WD6 (</span><a href="diff.html"><span class="insert">Diffs since last release</span></a><span class="insert">)</span></h2><h2 id="w3c-editor-s-draft-29-may-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">03</span><span class="insert">29</span> May 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></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><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120202/</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120503/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span></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><span class="delete">Contributors:</span><span class="insert">Authors:</span></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>
@@ -979,8 +979,8 @@
provenance <span class="delete">that describes
the entities, people and activities involved in
producing a piece of data or thing.</span><span class="insert">(PROV) family of specifications.
-PROV-DM distinguishes core structures, forming the essence of provenance descriptions, from
-extended structures catering for more advanced uses of provenance.</span>
+PROV-DM distinguishes core structures, forming the essence of provenance information, from
+extended structures catering for more specific uses of provenance.</span>
PROV-DM is <span class="delete">structured</span><span class="insert">organized</span> in six components,<span class="insert"> respectively</span> dealing with:
(1) entities and activities, and the time at which they were created, used, or ended;
(2) agents bearing responsibility for entities that were generated and activities that happened;
@@ -998,7 +998,7 @@
<p>Two further documents complete the specification of PROV-DM.
First, a companion document specifies the set of constraints that
-provenance descriptions should follow. Second,
+provenance<span class="delete"> descriptions</span> should follow. Second,
a separate document describes a provenance notation for expressing
instances of provenance for human consumption; this notation is used in examples in
this document. </p>
@@ -1040,7 +1040,7 @@
<span class="delete">Fourth Public Working Draft</span>
<p>This <span class="delete">is the fourth public release of the PROV-DM document. Following feedback, the Working Group has decided to reorganize this document substantially, separating the data model from its contraints and the notation used to illustrate it. The PROV-DM release is synchronized with the release of the PROV-O, PROV-PRIMER, PROV-N, and PROV-CONSTRAINTS documents. We are now clarifying the entry path to the PROV family of specifications.</span>
<span class="delete">This </span>document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as <span class="delete">a Working</span><span class="insert">an Editor's</span> Draft. <span class="delete">This document is intended</span><span class="insert">If you wish</span> to <span class="delete">become a </span><span class="delete">W3C</span><span class="delete"> Recommendation. If you wish</span><span class="insert">make comments regarding this document, please send them</span> to <span class="delete">make comments regarding this document, please send them to </span><span class="delete">public-prov-wg@w3.org</span><a href="mailto:public-prov-comments@w3.org"><span class="insert">public-prov-comments@w3.org</span></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 <span class="delete">a Working</span><span class="insert">an Editor's</span> 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 <span class="delete">Starting Points</span><span class="insert">Overview</span></a><ul class="toc"><li class="tocline"><a href="#core-structures" class="tocxref"><span class="secno"><span class="insert">2.1 </span></span><span class="insert">PROV Core Structures</span></a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno"><span class="delete">2.1</span><span class="insert">2.1.1</span> </span>Entity and Activity</a></li><li class="tocline"><a href="#section-agents-attribution-association-delegation" class="tocxref"><span class="secno"><span class="delete">2.2 </span><span class="delete">Generation, Usage, Derivation</span><span class="insert">2.1.2 </span></span><span class="insert">Agents and Responsibility</span></a></li><li class="tocline"><a href="#section-derivation" class="tocxref"><span class="secno"><span class="delete">2.3 </span><span class="delete">Agents, Attribution, Association, and Responsibility</span><span class="delete">2.4 </span><span class="delete">Further Entities: Collections and Accounts</span><span class="delete">2.5 </span><span class="delete">Simplified Overview Diagram</span><span class="delete">2.6 </span><span class="delete">PROV-N: The Provenance Notation</span><span class="insert">2.1.3 </span></span><span class="insert">Derivation</span></a></li></ul></li><li class="tocline"><a href="#section-extended-structures" class="tocxref"><span class="secno"><span class="insert">2.2 </span></span><span class="insert">PROV Extended Structures</span></a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-mechanisms" class="tocxref"><span class="secno"><span class="insert">2.2.1 </span></span><span class="insert">Mechanisms to Define Extended Structures</span></a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-approach-subtyping" class="tocxref"><span class="secno"><span class="insert">2.2.1.1 </span></span><span class="insert">Subtyping</span></a></li><li class="tocline"><a href="#section-prov-extended-approach-expanded-relation" class="tocxref"><span class="secno"><span class="insert">2.2.1.2 </span></span><span class="insert">Expanded Relations</span></a></li><li class="tocline"><a href="#section-prov-extended-approach-optional-identification-new-relation" class="tocxref"><span class="secno"><span class="insert">2.2.1.3 </span></span><span class="insert">Optional Identification and New Relations</span></a></li></ul></li><li class="tocline"><a href="#section-provenance-of-provnance" class="tocxref"><span class="secno"><span class="insert">2.2.2 </span></span><span class="insert">Provenance of Provenance</span></a></li><li class="tocline"><a href="#section-collections" class="tocxref"><span class="secno"><span class="insert">2.2.3 </span></span><span class="insert">Collections</span></a></li></ul></li><li class="tocline"><a href="#section-overview-components" class="tocxref"><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Modular Organization</span></a></li></ul></li><li class="tocline"><a href="#prov-notation" class="tocxref"><span class="secno"><span class="insert">3. </span></span><span class="insert">The Provenance Notation</span></a></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno"><span class="delete">3.</span><span class="insert">4.</span> </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"><span class="delete">3.1</span><span class="insert">4.1</span> </span>The Authors View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno"><span class="delete">3.2</span><span class="insert">4.2</span> </span>The Process View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno"><span class="delete">3.3</span><span class="insert">4.3</span> </span>Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno"><span class="delete">4.</span><span class="insert">5.</span> </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno"><span class="delete">4.1</span><span class="insert">5.1</span> </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-entity" class="tocxref"><span class="secno"><span class="delete">4.1.1</span><span class="insert">5.1.1</span> </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno"><span class="delete">4.1.2</span><span class="insert">5.1.2</span> </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno"><span class="delete">4.1.3</span><span class="insert">5.1.3</span> </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno"><span class="delete">4.1.4</span><span class="insert">5.1.4</span> </span>Usage</a></li><li class="tocline"><a href="#term-wasInformedBy" class="tocxref"><span class="secno"><span class="insert">5.1.5 </span></span><span class="insert">Communication</span></a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno"><span class="delete">4.1.5</span><span class="insert">5.1.6</span> </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno"><span class="delete">4.1.6</span><span class="insert">5.1.7</span> </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno"><span class="delete">4.1.7</span><span class="insert">5.1.8</span> </span>Invalidation<span class="delete">4.1.8 </span><span class="delete">Communication</span><span class="delete">4.1.9 </span><span class="delete">Start by Activity</span></a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno"><span class="delete">4.2</span><span class="insert">5.2</span> </span>Component 2: Agents and Responsibility</a><ul class="toc"><li class="tocline"><a href="#term-agent" class="tocxref"><span class="secno"><span class="delete">4.2.1</span><span class="insert">5.2.1</span> </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno"><span class="delete">4.2.2</span><span class="insert">5.2.2</span> </span>Attribution</a></li><li class="tocline"><a href="#term-ActivityAssociation" class="tocxref"><span class="secno"><span class="delete">4.2.3</span><span class="insert">5.2.3</span> </span>Association</a></li><li class="tocline"><a href="#term-delegation" class="tocxref"><span class="secno"><span class="delete">4.2.4 </span><span class="delete">Responsibility</span><span class="insert">5.2.4 </span></span><span class="insert">Delegation</span></a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno"><span class="delete">4.3</span><span class="insert">5.3</span> </span>Component 3: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-derivation" class="tocxref"><span class="secno"><span class="delete">4.3.1</span><span class="insert">5.3.1</span> </span>Derivation</a></li><li class="tocline"><a href="#term-revision" class="tocxref"><span class="secno"><span class="delete">4.3.2</span><span class="insert">5.3.2</span> </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno"><span class="delete">4.3.3</span><span class="insert">5.3.3</span> </span>Quotation</a></li><li class="tocline"><a href="#term-original-source" class="tocxref"><span class="secno"><span class="delete">4.3.4</span><span class="insert">5.3.4</span> </span>Original Source</a></li><li class="tocline"><a href="#term-trace" class="tocxref"><span class="secno"><span class="delete">4.3.5</span><span class="insert">5.3.5</span> </span>Trace</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno"><span class="delete">4.4</span><span class="insert">5.4</span> </span>Component 4: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno"><span class="delete">4.4.1</span><span class="insert">5.4.1</span> </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno"><span class="delete">4.4.2</span><span class="insert">5.4.2</span> </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno"><span class="delete">4.5</span><span class="insert">5.5</span> </span>Component 5: <span class="delete">Collections</span><span class="insert">Bundles</span></a><ul class="toc"><li class="tocline"><a href="#term-bundle" class="tocxref"><span class="secno"><span class="delete">4.5.1 </span><span class="delete">Collection</span><span class="insert">5.5.1 </span></span><span class="insert">Bundle constructor</span></a></li><li class="tocline"><a href="#term-bundle-entity" class="tocxref"><span class="secno"><span class="delete">4.5.2 </span><span class="delete">Dictionary</span><span class="insert">5.5.2 </span></span><span class="insert">Bundle Description</span></a></li><li class="tocline"><a href="#term-hasProvenanceIn" class="tocxref"><span class="secno"><span class="delete">4.5.3 </span><span class="delete">Insertion</span><span class="delete">4.5.4 </span><span class="delete">Removal</span><span class="delete">4.5.5 </span><span class="delete">Membership</span><span class="insert">5.5.3 </span></span><span class="insert">Provenance Locator</span></a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno"><span class="delete">4.6</span><span class="insert">5.6</span> </span>Component 6: <span class="delete">Annotations</span><span class="insert">Collections</span></a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno"><span class="delete">4.6.1 </span><span class="delete">Note</span><span class="insert">5.6.1 </span></span><span class="insert">Collection</span></a></li><li class="tocline"><a href="#term-dictionary" class="tocxref"><span class="secno"><span class="delete">4.6.2 </span><span class="delete">Annotation</span><span class="insert">5.6.2 </span></span><span class="insert">Dictionary</span></a></li><li class="tocline"><a href="#term-dictionary-insertion" class="tocxref"><span class="secno"><span class="insert">5.6.3 </span></span><span class="insert">Insertion</span></a></li><li class="tocline"><a href="#term-dictionary-removal" class="tocxref"><span class="secno"><span class="insert">5.6.4 </span></span><span class="insert">Removal</span></a></li><li class="tocline"><a href="#term-dictionary-membership" class="tocxref"><span class="secno"><span class="insert">5.6.5 </span></span><span class="insert">Membership</span></a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno"><span class="delete">4.7</span><span class="insert">5.7</span> </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno"><span class="delete">4.7.1</span><span class="insert">5.7.1</span> </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno"><span class="delete">4.7.2</span><span class="insert">5.7.2</span> </span>Qualified Name</a></li><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno"><span class="delete">4.7.3</span><span class="insert">5.7.3</span> </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno"><span class="delete">4.7.4</span><span class="insert">5.7.4</span> </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno"><span class="delete">4.7.4.1</span><span class="insert">5.7.4.1</span> </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno"><span class="delete">4.7.4.2</span><span class="insert">5.7.4.2</span> </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno"><span class="delete">4.7.4.3</span><span class="insert">5.7.4.3</span> </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno"><span class="delete">4.7.4.4</span><span class="insert">5.7.4.4</span> </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno"><span class="delete">4.7.4.5</span><span class="insert">5.7.4.5</span> </span>prov:value</a></li><li class="tocline"><a href="#term-attribute-provenance-uri" class="tocxref"><span class="secno"><span class="insert">5.7.4.6 </span></span><span class="insert">prov:provenance-uri</span></a></li><li class="tocline"><a href="#term-attribute-service-uri" class="tocxref"><span class="secno"><span class="insert">5.7.4.7 </span></span><span class="insert">prov:service-uri</span></a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno"><span class="delete">4.7.5</span><span class="insert">5.7.5</span> </span>Value</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno"><span class="delete">5.</span><span class="insert">6.</span> </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno"><span class="delete">6.</span><span class="insert">7.</span> </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></ul></li><li class="tocline"><a href="#section-prov-overview" class="tocxref"><span class="secno">2. </span>PROV <span class="delete">Starting Points</span><span class="insert">Overview</span></a><ul class="toc"><li class="tocline"><a href="#core-structures" class="tocxref"><span class="secno"><span class="insert">2.1 </span></span><span class="insert">PROV Core Structures</span></a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno"><span class="delete">2.1</span><span class="insert">2.1.1</span> </span>Entity and Activity</a></li><li class="tocline"><a href="#section-derivation" class="tocxref"><span class="secno"><span class="delete">2.2 </span><span class="delete">Generation, Usage, </span><span class="insert">2.1.2 </span></span>Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-delegation" class="tocxref"><span class="secno"><span class="delete">2.3 </span><span class="delete">Agents, Attribution, Association,</span><span class="insert">2.1.3 </span></span><span class="insert">Agents</span> and Responsibility<span class="delete">2.4 </span><span class="delete">Further Entities: Collections and Accounts</span><span class="delete">2.5 </span><span class="delete">Simplified Overview Diagram</span><span class="delete">2.6 </span><span class="delete">PROV-N: The Provenance Notation</span></a></li></ul></li><li class="tocline"><a href="#section-extended-structures" class="tocxref"><span class="secno"><span class="insert">2.2 </span></span><span class="insert">PROV Extended Structures</span></a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-mechanisms" class="tocxref"><span class="secno"><span class="insert">2.2.1 </span></span><span class="insert">Mechanisms to Define Extended Structures</span></a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-approach-subtyping" class="tocxref"><span class="secno"><span class="insert">2.2.1.1 </span></span><span class="insert">Subtyping</span></a></li><li class="tocline"><a href="#section-prov-extended-approach-expanded-relation" class="tocxref"><span class="secno"><span class="insert">2.2.1.2 </span></span><span class="insert">Expanded Relations</span></a></li><li class="tocline"><a href="#section-prov-extended-approach-optional-identification-new-relation" class="tocxref"><span class="secno"><span class="insert">2.2.1.3 </span></span><span class="insert">Optional Identification and New Relations</span></a></li></ul></li><li class="tocline"><a href="#section-provenance-of-provnance" class="tocxref"><span class="secno"><span class="insert">2.2.2 </span></span><span class="insert">Provenance of Provenance</span></a></li><li class="tocline"><a href="#section-collections" class="tocxref"><span class="secno"><span class="insert">2.2.3 </span></span><span class="insert">Collections</span></a></li></ul></li><li class="tocline"><a href="#section-overview-components" class="tocxref"><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Modular Organization</span></a></li></ul></li><li class="tocline"><a href="#prov-notation" class="tocxref"><span class="secno"><span class="insert">3. </span></span><span class="insert">The Provenance Notation</span></a></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno"><span class="delete">3.</span><span class="insert">4.</span> </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"><span class="delete">3.1</span><span class="insert">4.1</span> </span>The Authors View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno"><span class="delete">3.2</span><span class="insert">4.2</span> </span>The Process View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno"><span class="delete">3.3</span><span class="insert">4.3</span> </span>Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno"><span class="delete">4.</span><span class="insert">5.</span> </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno"><span class="delete">4.1</span><span class="insert">5.1</span> </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-entity" class="tocxref"><span class="secno"><span class="delete">4.1.1</span><span class="insert">5.1.1</span> </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno"><span class="delete">4.1.2</span><span class="insert">5.1.2</span> </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno"><span class="delete">4.1.3</span><span class="insert">5.1.3</span> </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno"><span class="delete">4.1.4</span><span class="insert">5.1.4</span> </span>Usage</a></li><li class="tocline"><a href="#term-wasInformedBy" class="tocxref"><span class="secno"><span class="insert">5.1.5 </span></span><span class="insert">Communication</span></a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno"><span class="delete">4.1.5</span><span class="insert">5.1.6</span> </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno"><span class="delete">4.1.6</span><span class="insert">5.1.7</span> </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno"><span class="delete">4.1.7</span><span class="insert">5.1.8</span> </span>Invalidation<span class="delete">4.1.8 </span><span class="delete">Communication</span><span class="delete">4.1.9 </span><span class="delete">Start by Activity</span></a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno"><span class="delete">4.2</span><span class="insert">5.2</span> </span>Component 2: <span class="delete">Agents and Responsibility</span><span class="insert">Derivations</span></a><ul class="toc"><li class="tocline"><a href="#term-derivation" class="tocxref"><span class="secno"><span class="delete">4.2.1 </span><span class="delete">Agent</span><span class="insert">5.2.1 </span></span><span class="insert">Derivation</span></a></li><li class="tocline"><a href="#term-revision" class="tocxref"><span class="secno"><span class="delete">4.2.2 </span><span class="delete">Attribution</span><span class="insert">5.2.2 </span></span><span class="insert">Revision</span></a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno"><span class="delete">4.2.3 </span><span class="delete">Association</span><span class="insert">5.2.3 </span></span><span class="insert">Quotation</span></a></li><li class="tocline"><a href="#term-original-source" class="tocxref"><span class="secno"><span class="delete">4.2.4 </span><span class="delete">Responsibility</span><span class="insert">5.2.4 </span></span><span class="insert">Original Source</span></a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno"><span class="delete">4.3</span><span class="insert">5.3</span> </span>Component 3: <span class="delete">Derivations</span><span class="insert">Agents and Responsibility</span></a><ul class="toc"><li class="tocline"><a href="#term-agent" class="tocxref"><span class="secno"><span class="delete">4.3.1 </span><span class="delete">Derivation</span><span class="insert">5.3.1 </span></span><span class="insert">Agent</span></a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno"><span class="delete">4.3.2 </span><span class="delete">Revision</span><span class="insert">5.3.2 </span></span><span class="insert">Attribution</span></a></li><li class="tocline"><a href="#term-ActivityAssociation" class="tocxref"><span class="secno"><span class="delete">4.3.3 </span><span class="delete">Quotation</span><span class="insert">5.3.3 </span></span><span class="insert">Association</span></a></li><li class="tocline"><a href="#term-delegation" class="tocxref"><span class="secno"><span class="delete">4.3.4 </span><span class="delete">Original Source</span><span class="insert">5.3.4 </span></span><span class="insert">Delegation</span></a></li><li class="tocline"><a href="#term-trace" class="tocxref"><span class="secno"><span class="delete">4.3.5</span><span class="insert">5.3.5</span> </span>Trace</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno"><span class="delete">4.4</span><span class="insert">5.4</span> </span>Component 4: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno"><span class="delete">4.4.1</span><span class="insert">5.4.1</span> </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno"><span class="delete">4.4.2</span><span class="insert">5.4.2</span> </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno"><span class="delete">4.5</span><span class="insert">5.5</span> </span>Component 5: <span class="delete">Collections</span><span class="insert">Bundles</span></a><ul class="toc"><li class="tocline"><a href="#term-bundle" class="tocxref"><span class="secno"><span class="delete">4.5.1 </span><span class="delete">Collection</span><span class="insert">5.5.1 </span></span><span class="insert">Bundle constructor</span></a></li><li class="tocline"><a href="#term-bundle-entity" class="tocxref"><span class="secno"><span class="delete">4.5.2 </span><span class="delete">Dictionary</span><span class="insert">5.5.2 </span></span><span class="insert">Bundle Description</span></a></li><li class="tocline"><a href="#term-hasProvenanceIn" class="tocxref"><span class="secno"><span class="delete">4.5.3 </span><span class="delete">Insertion</span><span class="delete">4.5.4 </span><span class="delete">Removal</span><span class="delete">4.5.5 </span><span class="delete">Membership</span><span class="insert">5.5.3 </span></span><span class="insert">Provenance Locator</span></a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno"><span class="delete">4.6</span><span class="insert">5.6</span> </span>Component 6: <span class="delete">Annotations</span><span class="insert">Collections</span></a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno"><span class="delete">4.6.1 </span><span class="delete">Note</span><span class="insert">5.6.1 </span></span><span class="insert">Collection</span></a></li><li class="tocline"><a href="#term-dictionary" class="tocxref"><span class="secno"><span class="delete">4.6.2 </span><span class="delete">Annotation</span><span class="insert">5.6.2 </span></span><span class="insert">Dictionary</span></a></li><li class="tocline"><a href="#term-dictionary-insertion" class="tocxref"><span class="secno"><span class="insert">5.6.3 </span></span><span class="insert">Insertion</span></a></li><li class="tocline"><a href="#term-dictionary-removal" class="tocxref"><span class="secno"><span class="insert">5.6.4 </span></span><span class="insert">Removal</span></a></li><li class="tocline"><a href="#term-dictionary-membership" class="tocxref"><span class="secno"><span class="insert">5.6.5 </span></span><span class="insert">Membership</span></a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno"><span class="delete">4.7</span><span class="insert">5.7</span> </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno"><span class="delete">4.7.1</span><span class="insert">5.7.1</span> </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno"><span class="delete">4.7.2</span><span class="insert">5.7.2</span> </span>Qualified Name</a></li><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno"><span class="delete">4.7.3</span><span class="insert">5.7.3</span> </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno"><span class="delete">4.7.4</span><span class="insert">5.7.4</span> </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno"><span class="delete">4.7.4.1</span><span class="insert">5.7.4.1</span> </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno"><span class="delete">4.7.4.2</span><span class="insert">5.7.4.2</span> </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno"><span class="delete">4.7.4.3</span><span class="insert">5.7.4.3</span> </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno"><span class="delete">4.7.4.4</span><span class="insert">5.7.4.4</span> </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno"><span class="delete">4.7.4.5</span><span class="insert">5.7.4.5</span> </span>prov:value</a></li><li class="tocline"><a href="#term-attribute-provenance-uri" class="tocxref"><span class="secno"><span class="insert">5.7.4.6 </span></span><span class="insert">prov:provenance-uri</span></a></li><li class="tocline"><a href="#term-attribute-service-uri" class="tocxref"><span class="secno"><span class="insert">5.7.4.7 </span></span><span class="insert">prov:service-uri</span></a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno"><span class="delete">4.7.5</span><span class="insert">5.7.5</span> </span>Value</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno"><span class="delete">5.</span><span class="insert">6.</span> </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno"><span class="delete">6.</span><span class="insert">7.</span> </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>
@@ -1085,7 +1085,7 @@
<p><span class="delete">A set of specifications, referred to as the</span><span class="insert">
The</span> PROV <span class="delete">family of specifications, define the</span><span class="insert">data model distinguishes </span><em><span class="insert">core structures</span></em><span class="insert"> from
</span><em><span class="insert">extended structures</span></em><span class="insert">: core structures form the essence of
-provenance descriptions, and are commonly found in</span> various<span class="delete"> aspects
+provenance information, and are commonly found in</span> various<span class="delete"> aspects
</span><span class="insert">
domain-specific vocabularies </span>that <span class="delete">are necessary to achieve this vision in an interoperable
way:</span>
@@ -1131,13 +1131,13 @@
<p>This specification presents the <span class="delete">key </span>concepts of the PROV Data Model, and
provenance types and relations, without specific concern for how they are applied.
-With these, it becomes possible to write useful provenance descriptions, and publish or embed them <span class="delete">along side</span><span class="insert">alongside</span> the data they relate to. </p>
+With these, it becomes possible to write useful <span class="delete">provenance descriptions,</span><span class="insert">provenance,</span> and publish or embed <span class="delete">them along side</span><span class="insert">it alongside</span> the data <span class="delete">they relate</span><span class="insert">it relates</span> to. </p>
<p>However, if something about which provenance is expressed is subject to change, then it is challenging to express its provenance precisely (e.g. the data from which a daily weather report is derived changes from day to day).<span class="insert">
This is addressed in a companion</span>
<span class="delete">To address this challenge, a </span><span class="delete">refinement</span><span class="delete"> is proposed to enrich simple provenance, with extra descriptions that help qualify the specific subject of provenance and provenance itself, with attributes and temporal information, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion </span>specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite><span class="delete">].</span><span class="insert">] by proposing formal constraints on
- the way that provenance descriptions are related to the things they
- describe (such as the use of attributes, temporal information and
+ the way that provenance is related to the things it
+ describes (such as the use of attributes, temporal information and
specialization of entities), and additional conclusions that are valid
to infer.</span>
</p>
@@ -1146,9 +1146,9 @@
<div id="structure-of-this-document" class="section">
<h3><span class="secno">1.1 </span>Structure of this Document</h3>
-<p><a href="#section-prov-overview">Section 2</a> provides<span class="insert"> an overview of the PROV Data Model,</span> <span class="delete">starting points for the PROV Data Model, listing a</span><span class="insert">distinguishing a core</span> set of types and relations, <span class="delete">which allows users to make initial</span><span class="insert">commonly found in</span> provenance <span class="delete">descriptions.</span><span class="insert">descriptions, from extended structures catering for more specific uses. It also introduces a modular organization of the data model in components. </span></p>
-
-<p><a href="#prov-notation"><span class="insert">Section 3</span></a><span class="insert"> overviews the Provenance Notation used to illustrate examples of provenance descriptions.</span></p>
+<p><a href="#section-prov-overview">Section 2</a> provides<span class="insert"> an overview of the PROV Data Model,</span> <span class="delete">starting points for the PROV Data Model, listing a</span><span class="insert">distinguishing a core</span> set of types and relations, <span class="delete">which allows users to make initial provenance descriptions.</span><span class="insert">commonly found in provenance, from extended structures catering for more specific uses. It also introduces a modular organization of the data model in components. </span></p>
+
+<p><a href="#prov-notation"><span class="insert">Section 3</span></a><span class="insert"> overviews the Provenance Notation used to illustrate examples of provenance.</span></p>
<p><a href="#prov-dm-example">Section <span class="delete">3</span><span class="insert">4</span></a> illustrates how the PROV data model can be used
@@ -1165,7 +1165,7 @@
<p><a href="#extensibility-section">Section <span class="delete">5</span><span class="insert">6</span></a> summarizes PROV-DM extensibility points.</p>
-<p><a href="#valid-provenance">Section <span class="delete">6</span><span class="insert">7</span></a> introduces the idea that constraints can be applied to the PROV data model to <span class="delete">refine</span><span class="insert">validate</span> provenance descriptions; these are covered in the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
+<p><a href="#valid-provenance">Section <span class="delete">6</span><span class="insert">7</span></a> introduces the idea that constraints can be applied to the PROV data model to <span class="delete">refine provenance descriptions;</span><span class="insert">validate provenance;</span> these are covered in the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
</div>
@@ -1211,13 +1211,13 @@
<h2><span class="secno">2. </span>PROV <span class="delete">Starting Points</span><span class="insert">Overview</span></h2>
<p>
-This section introduces provenance concepts with informal descriptions and illustrative
-examples.<span class="insert"> PROV distinguishes</span> <span class="delete">Since PROV-DM</span><em><span class="insert">core structures</span></em><span class="insert">, forming the essence of provenance descriptions, from </span><em><span class="insert">extended structures</span></em><span class="insert"> catering for more advanced uses of provenance. Core and extended structures are respectively presented in </span><a href="#core-structures"><span class="insert">Section 2.1</span></a><span class="insert"> and </span><a href="#section-extended-structures"><span class="insert">Section 2.2</span></a><span class="insert">. Furthermore, the PROV data model</span> is <span class="delete">a conceptual data
-model, </span><span class="insert">organized according to components, which form thematic groupings of concepts (see </span><a href="#section-overview-components">Section <span class="delete">2.5 maps the concepts to various types and relations,
+This section introduces provenance concepts with informal <span class="delete">descriptions</span><span class="insert">explanations</span> and illustrative
+examples.<span class="insert"> PROV distinguishes</span> <span class="delete">Since PROV-DM</span><em><span class="insert">core structures</span></em><span class="insert">, forming the essence of provenance, from </span><em><span class="insert">extended structures</span></em><span class="insert"> catering for more advanced uses of provenance. Core and extended structures are respectively presented in </span><a href="#core-structures"><span class="insert">Section 2.1</span></a><span class="insert"> and </span><a href="#section-extended-structures"><span class="insert">Section 2.2</span></a><span class="insert">. Furthermore, the PROV data model</span> is <span class="delete">a conceptual data
+model, </span><span class="insert">organized according to components, which form thematic groupings of concepts (see </span><a href="#section-overview-components">Section <span class="delete">2.5 maps the concepts to various types</span><span class="insert">2.3</span></a><span class="insert">). A </span><em><span class="insert">provenance description</span></em><span class="insert"> is an instance of a core</span> and <span class="delete">relations,
which are illustrated graphically in
a simplified UML diagram in </span><span class="delete">Figure 1</span><span class="delete">. Section 2.6
then summarizes the PROV notation allowing instances of PROV-DM to be
-written down.</span><span class="insert">2.3</span></a><span class="insert">).</span>
+written down.</span><span class="insert">extended provenance structure described below.</span>
</p>
@@ -1241,7 +1241,7 @@
<span class="delete">Things we want to describe the provenance of are called </span><span class="insert">production of
</span><em>entities</em> <span class="insert">by </span><em><span class="insert">activities</span></em><span class="insert">, which may be
-controlled or influenced </span>in<span class="delete"> PROV. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
+influenced </span>in<span class="delete"> PROV. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page,
physical things such as a building or a printed book, or a car as well as abstract concepts</span><span class="insert">
various ways by </span><em><span class="insert">agents</span></em><span class="insert">. These core types</span> and <span class="delete">ideas. </span><span class="insert">their relationships
are illustrated
@@ -1482,17 +1482,18 @@
<caption id="overview-types-and-relations">Table 2: Mapping of <span class="delete">Provenance</span><span class="insert">PROV core</span> concepts to types and relations</caption>
<tbody><tr><td><a><b>PROV Concepts</b></a></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td><td><b><span class="insert">Overview</span></b></td></tr>
<tr>
-<td><a href="#concept-entity" class="internalDFN">Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity" href="#dfn-entity" class="internalDFN">entity</a></td><td style="text-align: center;"><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td></tr>
-<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 href="#section-entity-activity"><span class="insert">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 href="#section-agents-attribution-association-delegation"><span class="insert">2.1.2</span></a></td></tr>
+<td><a href="#concept-entity" class="internalDFN">Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity" href="#dfn-entity" class="internalDFN"><span class="delete">entity</span><span class="insert">Entity</span></a></td><td style="text-align: center;"><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-activity" class="internalDFN">Activity</a></td><td><a title="dfn-Activity" href="#dfn-activity" class="internalDFN"><span class="delete">activity</span><span class="insert">Activity</span></a></td><td style="text-align: center;"><a href="#section-entity-activity"><span class="insert">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"><span class="delete">agent</span><span class="insert">Agent</span></a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.2</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 href="#section-entity-activity"><span class="insert">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 href="#section-entity-activity"><span class="insert">2.1.1</span></a></td></tr>
-<tr><td><a href="#concept-communication" class="internalDFN"><span class="insert">Communication</span></a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN"><span class="insert">wasInformedBy</span></a></td><td style="text-align: center;"><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td></tr>
-<tr><td><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a title="wasAttributedTo" href="#dfn-wasattributedto" class="internalDFN">wasAttributedTo</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.2</span></a></td></tr>
-<tr><td><a href="#concept-activityAssociation" class="internalDFN">Association</a></td><td><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN">wasAssociatedWith</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.2</span></a></td></tr>
-<tr><td><span class="delete">Responsibility</span><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN">actedOnBehalfOf</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.2</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 href="#section-derivation"><span class="insert">2.1.3</span></a></td></tr>
+<tr><td><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a title="used" href="#dfn-used" class="internalDFN"><span class="delete">used</span><span class="insert">Used</span></a></td><td style="text-align: center;"><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-communication" class="internalDFN"><span class="insert">Communication</span></a></td><td><a title="wasInformedBy" href="#dfn-wasinformedby" class="internalDFN"><span class="insert">WasInformedBy</span></a></td><td style="text-align: center;"><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td></tr>
+<tr><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td><td><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN"><span class="insert">WasDerivedFrom</span></a></td><td style="text-align: center;"><a href="#section-derivation"><span class="insert">2.1.2</span></a></td></tr>
+<tr><td><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a title="wasAttributedTo" href="#dfn-wasattributedto" class="internalDFN"><span class="delete">wasAttributedTo</span><span class="insert">WasAttributedTo</span></a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.3</span></a></td></tr>
+<tr><td><a href="#concept-activityAssociation" class="internalDFN">Association</a></td><td><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN"><span class="delete">wasAssociatedWith</span><span class="insert">WasAssociatedWith</span></a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.3</span></a></td></tr>
+<tr><td><span class="delete">Responsibility</span><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN"><span class="delete">actedOnBehalfOf</span><span class="insert">ActedOnBehalfOf</span></a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.3</span></a></td></tr>
+<span class="delete">Derivation</span><span class="delete">wasDerivedFrom</span>
</tbody></table>
</div>
@@ -1529,14 +1530,14 @@
-<div class="anexample conceptexample" id="entity-example" count="1">
+<div class="anexample conceptexample" id="entity-example" data-count="1"><div class="anexampleTitle"><span class="insert">Example 1</span></div>
<p><span class="insert">An entity may be the document at URI </span><a href="http://www.bbc.co.uk/news/science-environment-17526723"><span class="insert">http://www.bbc.co.uk/news/science-environment-17526723</span></a><span class="insert">, a file in a file system, a car, or an idea.</span></p>
</div>
<p>
-<span class="glossary-ref"><span class="insert"> An </span><span class="dfn"><span class="insert">activity</span></span><span class="insert"> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities. </span></span><span class="insert">
+<span class="glossary-ref"><span class="insert"> An </span><span class="dfn"><span class="insert">activity</span></span><span class="insert"> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. </span></span><span class="insert">
Just as entities cover a broad range of notions,
activities can cover a broad range of
notions:
@@ -1548,7 +1549,7 @@
-<div class="anexample conceptexample" id="activity-example" count="2">
+<div class="anexample conceptexample" id="activity-example" data-count="2"><div class="anexampleTitle"><span class="insert">Example 2</span></div>
<p><span class="insert">An activity may be the publishing of a document on the Web, sending a twitter message, extracting metadata embedded in a file, driving a car from Boston to Cambridge, assembling a data set based on a set of measurements, performing a statistical analysis over a data set, sorting news items according to some criteria, running a SPARQL query over a triple store, or editing a file.</span></p>
</div>
@@ -1567,7 +1568,7 @@
-<div class="anexample conceptexample" id="generation-example" count="3">
+<div class="anexample conceptexample" id="generation-example" data-count="3"><div class="anexampleTitle"><span class="insert">Example 3</span></div>
<p><span class="insert">Examples of generation</span> are <span class="delete">shown to be binary. Definitions of </span><span class="delete">Section 4</span><span class="delete"> reveal that some relations, while involving two primary elements, are n-ary. </span><span class="insert">the completed creation of a file by a
program, the completed creation of a linked data set, and the completed
publication of a new version of a document.
@@ -1604,7 +1605,7 @@
-<div class="anexample conceptexample" id="usage-example" count="4">
+<div class="anexample conceptexample" id="usage-example" data-count="4"><div class="anexampleTitle"><span class="insert">Example 4</span></div>
<p><span class="insert">Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
the mix); in contrast, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
@@ -1615,28 +1616,67 @@
<p>
</p><div class="glossary-ref">
- <span class="dfn"><span class="insert">Communication</span></span><span class="insert"> is the exchange of an entity by two activities, one activity using the entity generated by the other. </span></div>
-
-
-
-
-
-<div class="anexample conceptexample" id="communication-example" count="5">
+ <span class="dfn"><span class="insert">Communication</span></span><span class="insert"> is the exchange of an unspecified entity by two activities, one activity using some entity generated by the other. </span></div>
+
+
+
+
+
+<div class="anexample conceptexample" id="communication-example" data-count="5"><div class="anexampleTitle"><span class="insert">Example 5</span></div>
<p><span class="insert">
The activity of writing a celebrity article was informed by (a
communication instance) the activity of intercepting voicemails.
- The activity of purchasing a
- car in Boston can be informed by the the activity of its being
- designed in Japan.
</span></p></div>
</div>
+ <div id="section-derivation" class="section">
+<h4><span class="secno"><span class="insert">2.1.2 </span></span><span class="insert">Derivation</span></h4>
+
+
+
+<p><span class="insert">Activities utilize entities and produce entities. In some cases, utilizing an entity influences the creation of another in some way. This notion of 'influence' is captured by derivations, defined as follows.
+</span></p>
+
+<p>
+<span class="glossary-ref"><span class="insert"> A </span><span class="dfn"><span class="insert">derivation</span></span><span class="insert"> is a transformation of an entity into another, an update of an entity, resulting in a new one, or based on an entity, the construction of another.</span></span>
+
+
+
+
+
+</p><div class="anexample conceptexample" id="derivation-example" data-count="6"><div class="anexampleTitle"><span class="insert">Example 6</span></div>
+<p><span class="insert">Examples of derivation include the transformation of a relational table into a
+linked data set, the transformation of a canvas into a painting, the transportation of a work of art from London to New York, and a physical transformation such as the melting of ice into water.</span></p>
+</div>
+
+
+<p><span class="insert">
+While the basic idea is simple, the concept of derivation can be quite
+subtle: implicit is the notion that the generated entity was affected
+in some way by the used entity.
+
+If an artifact
+was used by an activity that also generated a new artifact, it does not always follow
+that the second artifact was derived from the first. In the activity
+of creating a painting, an artist may have mixed some paint that was
+never actually applied to the canvas: the painting would typically
+not be considered a derivation from the unused paint.
+
+PROV does not attempt to specify the conditions under which derivations
+exist; rather, derivation is considered to have been determined by unspecified means.
+Thus, while a chain of usage and generation is necessary for a
+derivation to hold between entities, it is not sufficient; some
+form of influence occurring during the activities involved is also needed.
+</span></p>
+</div>
+
+
<div id="section-agents-attribution-association-delegation" class="section">
-<h4><span class="secno"><span class="insert">2.1.2 </span></span><span class="insert">Agents and Responsibility</span></h4>
+<h4><span class="secno"><span class="insert">2.1.3 </span></span><span class="insert">Agents and Responsibility</span></h4>
<p><span class="insert">For many purposes, a key consideration
for deciding whether something is reliable and/or trustworthy is
@@ -1659,7 +1699,7 @@
-<div class="anexample conceptexample" id="agent-example" count="6">
+<div class="anexample conceptexample" id="agent-example" data-count="7"><div class="anexampleTitle"><span class="insert">Example 7</span></div>
<p><span class="insert">
Software for checking the use of grammar in a document may be defined as an agent of a document preparation activity; one can also describe its provenance, including for instance the vendor and the version history.
A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
@@ -1673,7 +1713,7 @@
<div class="glossary-ref"> <span class="dfn"><span class="insert">Attribution</span></span><span class="insert"> is the ascribing of an entity to an agent. </span></div>
-<div class="anexample conceptexample" id="attribution-example" count="7">
+<div class="anexample conceptexample" id="attribution-example" data-count="8"><div class="anexampleTitle"><span class="insert">Example 8</span></div>
<p><span class="insert">A blog post can be attributed to an author, a mobile phone to its manufacturer.</span></p>
</div>
@@ -1687,7 +1727,7 @@
<span class="glossary-ref"><span class="insert"> An activity </span><span class="dfn"><span class="insert">association</span></span><span class="insert"> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. </span></span>
</p>
-<div class="anexample conceptexample" id="association-example" count="8">
+<div class="anexample conceptexample" id="association-example" data-count="9"><div class="anexampleTitle"><span class="insert">Example 9</span></div>
<p><span class="insert">Examples of association between an activity and an agent are:
</span></p><ul>
<li><span class="insert">creation of a web page under the guidance of a designer;</span></li>
@@ -1705,65 +1745,23 @@
-<div class="anexample conceptexample" id="responsibility-example" count="9">
+<div class="anexample conceptexample" id="responsibility-example" data-count="10"><div class="anexampleTitle"><span class="insert">Example 10</span></div>
<p><span class="insert">A student publishing a web page describing an academic
department could result in both the student and the department being
agents associated with the activity. It may not matter which actual
-student published a web page, but</span> it <span class="delete">only illustrates</span><span class="insert">may matter significantly that the department
-told the student to put up the web page.
+student published a web page, but</span> it <span class="delete">only illustrates types and relations introduced in this section (</span><span class="delete">Section 2</span><span class="delete">), exploited in the example discussed in </span><span class="delete">Section 3</span><span class="delete">, and explained in detail in </span><span class="delete">Section 4</span><span class="delete">.
+Names of relations depicted in </span><span class="delete">Figure 1</span><span class="delete">
+are listed in
+the third column of </span><span class="delete">Table 2</span><span class="delete">. These names are part of a textual notation</span><span class="insert">may matter significantly that the department
+told the student</span> to <span class="delete">write instances of the PROV data model, which we introduce in the next section. </span><span class="insert">put up the web page.
</span></p>
</div>
</div>
- <div id="section-derivation" class="section">
-<h4><span class="secno"><span class="insert">2.1.3 </span></span><span class="insert">Derivation</span></h4>
-
-
-
-<p><span class="insert">Activities utilize entities and produce entities. In some cases, utilizing an entity influences the creation of another in some way. This notion of 'influence' is captured by derivations, defined as follows.
-</span></p>
-
-<p>
-<span class="glossary-ref"><span class="insert"> A </span><span class="dfn"><span class="insert">derivation</span></span> <span class="delete">types</span><span class="insert">is a transformation of an entity into another, an update of an entity, resulting in a new one, or based on an entity, the construction of another.</span></span>
-
-
-
-
-
-</p><div class="anexample conceptexample" id="derivation-example" count="10">
-<p><span class="insert">Examples of derivation include the transformation of a relational table into a
-linked data set, the transformation of a canvas into a painting, the transportation of a work of art from London to New York,</span> and <span class="delete">relations introduced </span><span class="insert">a physical transformation such as the melting of ice into water.</span></p>
-</div>
-
-
-<p><span class="insert">
-While the basic idea is simple, the concept of derivation can be quite
-subtle: implicit is the notion that the generated entity was affected
-</span>in <span class="delete">this section (</span><span class="delete">Section 2</span><span class="delete">), exploited in the example discussed in </span><span class="delete">Section 3</span><span class="delete">,</span><span class="insert">some way by the used entity.
-
-If an artifact
-was used by an activity that also generated a new artifact, it does not always follow
-that the second artifact was derived from the first. In the activity
-of creating a painting, an artist may have mixed some paint that was
-never actually applied to the canvas: the painting would typically
-not be considered a derivation from the unused paint.
-
-PROV does not attempt to specify the conditions under which derivations
-exist; rather, derivation is considered to have been determined by unspecified means.
-Thus, while a chain of usage</span> and <span class="delete">explained in detail in </span><span class="delete">Section 4</span><span class="delete">.
-Names of relations depicted in </span><span class="delete">Figure 1</span><span class="insert">generation is necessary for a
-derivation to hold between entities, it is not sufficient; some
-form of influence occurring during the activities involved is also needed.</span>
-<span class="delete">are listed in
-the third column of </span><span class="delete">Table 2</span><span class="delete">. These names are part of a textual notation to write instances of the PROV data model, which we introduce in the next section. </span></p>
-
-
-
-</div>
-
</div>
+
<div id="section-extended-structures" class="section">
<h3><span class="secno"><span class="delete">2.6 </span><span class="delete">PROV-N: </span><span class="insert">2.2 </span></span><span class="insert">PROV Extended Structures</span></h3>
@@ -1804,34 +1802,51 @@
<p><a href="#core-structures"><span class="insert">Section 2.1</span></a><span class="insert"> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</span></p>
-<p>To illustrate <span class="delete">the application of PROV</span><span class="insert">expanded relations, we consider the concept of
+<p>To illustrate <span class="delete">the application of PROV concepts to a concrete example (see </span><span class="delete">Section 3</span><span class="delete">) and to provide examples of concepts (see </span><span class="delete">Section 4</span><span class="delete">),
+</span><span class="insert">expanded relations, </span>we <span class="delete">introduce PROV-N, a notation for writing instances of the PROV data model. For full details, the reader is referred to the companion specification [</span><span class="delete">PROV-N</span><span class="delete">].
+PROV-N is a notation</span><span class="insert">consider the concept of
association, described
in </span><a href="#section-agents-attribution-association-delegation"><span class="insert">section
-2.1.2</span></a><span class="insert">. Agents may adopt sets of actions or steps to achieve their
-goals in the context of an activity: this is captured by the notion of
-a plan. Thus, an activity may reflect the execution of a plan that was
-designed in advance to guide the execution. Hence, an expanded
-association relation allows a plan be linked to an
-activity. Plan is defined by subtyping and full association by an expanded relation, as follows. </span></p>
+2.1.3</span></a><span class="insert">.</span> <span class="delete">aimed at human consumption, with the following characteristics:</span>
+
+<span class="delete">PROV-N expressions</span><span class="insert">Agents may</span> adopt <span class="delete">a </span><em><span class="delete">functional notation</span><span class="delete"> consisting
+of a name and a list of arguments in parentheses.</span>
+
+<span class="delete">The interpretation of PROV-N arguments is defined according to their </span><span class="delete">position</span><span class="delete"> in the list of arguments. This convention allows for a compact notation. </span>
+
+<span class="delete">
+PROV-N </span><span class="delete">optional arguments</span><span class="delete"> 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><span class="delete">-</span><span class="delete"> is used for this purpose.
+</span>
+
+<span class="delete">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 </span><span class="delete">first position</span><span class="insert">plans</span></em>, <span class="insert">i.e. sets of actions or steps, to achieve their
+goals in the context of an activity.
+Hence, an expanded form of
+association relation allows for a plan to be specified. Plan is defined by subtyping </span>and<span class="delete"> the the</span><span class="insert">
+full association by an expanded relation, as follows. </span></p>
<p>
<span class="glossary-ref"><span class="insert">
- A </span><span class="dfn"><span class="insert">plan</span></span><span class="insert"> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. </span></span><span class="insert">
-There exist no
+ A </span><span class="dfn"><span class="insert">plan</span></span><span class="insert"> is an entity that represents a</span> set of <span class="delete">attribute-value pairs</span><span class="insert">actions or steps intended by one or more agents to achieve some goals. </span></span>
+</p>
+
+
+<p>
+<span class="glossary-ref"><span class="insert"> An activity </span><span class="dfn"><span class="insert">association</span></span><span class="insert"> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role</span> in the <span class="insert">activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span></span>
+</p>
+
+<p><span class="insert">There exist no
prescriptive requirement on the nature of plans, their representation, the
actions or steps they consist of, or their intended goals. Since plans may evolve over time,
it may become necessary to track their provenance, so plans themselves are
entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to
validate the execution as represented in the provenance record, to
-manage expectation failures, or to provide explanations.</span></p>
-
-
-<p>
-<span class="glossary-ref"><span class="insert"> An activity </span><span class="dfn"><span class="insert">association</span></span><span class="insert"> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </span></span>
-</p>
-
-
-<div class="anexample conceptexample" id="association-example2" count="11">
+manage expectation failures, or to provide explanations.</span></p>
+
+
+<div class="anexample conceptexample" id="association-example2" data-count="11"><div class="anexampleTitle"><span class="insert">Example 11</span></div>
<p><span class="insert">An example of association between an activity and an agent involving a plan is:
an XSLT transform (an activity) launched by a user (an agent) based on an XSL style sheet (a plan).
@@ -1842,9 +1857,9 @@
<div id="section-prov-extended-approach-optional-identification-new-relation" class="section">
<h5><span class="secno"><span class="insert">2.2.1.3 </span></span><span class="insert">Optional Identification and New Relations</span></h5>
-<p><span class="insert">Some</span> concepts <span class="insert">exhibit both a core use, expressed as
+<p><span class="insert">Some concepts exhibit both a core use, expressed as
binary relation, and an extended use, expressed as n-ary relation. In
-some cases, mapping the concept </span>to a <span class="delete">concrete example (see </span><span class="delete">Section 3</span><span class="delete">)</span><span class="insert">relation, whether binary or
+some cases, mapping the concept to a relation, whether binary or
n-ary, is not sufficient: instead, it may be required to
identify an instance of such concept. In those cases, PROV-DM allows for
an optional identifier to be
@@ -1852,7 +1867,7 @@
more elements. This optional identifier can then be used to refer to
an instance as part of other concepts.</span></p>
-<div class="anexample conceptexample" id="identifier-example" count="12">
+<div class="anexample conceptexample" id="identifier-example" data-count="12"><div class="anexampleTitle"><span class="insert">Example 12</span></div>
<p><span class="insert">A service may read a same configuration file on two different occasions. Each usage can be identifed by its own identifier, allowing them to be distinguished.
</span></p></div>
@@ -1877,10 +1892,9 @@
<p>
<span class="glossary-ref"><span class="insert">
- A </span><span class="dfn"><span class="insert">bundle</span></span><span class="insert"> is a named set of provenance descriptions,</span> and <span class="insert">is itself an entity, so allowing provenance of provenance </span>to <span class="delete">provide examples of concepts (see </span><span class="delete">Section 4</span><span class="delete">),
-we introduce PROV-N, a notation</span><span class="insert">be expressed. </span></span>
-
-</p><div class="anexample conceptexample" id="bundle-example" count="13">
+ A </span><span class="dfn"><span class="insert">bundle</span></span><span class="insert"> is a named set of provenance descriptions, and is itself an entity, so allowing provenance of provenance to be expressed. </span></span>
+
+</p><div class="anexample conceptexample" id="bundle-example" data-count="13"><div class="anexampleTitle"><span class="insert">Example 13</span></div>
<p><span class="insert">
For users to decide whether they can place their trust in
a resource, they may want to analyze the resource's provenance, but also determine
@@ -1897,27 +1911,12 @@
<h4><span class="secno"><span class="insert">2.2.3 </span></span><span class="insert">Collections</span></h4>
<p>
-<span class="glossary-ref"><span class="insert"> A </span><span class="dfn"><span class="insert">collection</span></span><span class="insert"> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be </span><span class="dfn"><span class="insert">member of</span></span><span class="insert"> the collections. </span></span><span class="insert"> This concept allows</span> for <span class="delete">writing instances of the PROV data model. For full details, the reader is referred</span><span class="insert">the provenance of the collection itself</span> to <span class="delete">the companion specification [</span><span class="delete">PROV-N</span><span class="delete">].
-PROV-N is a notation</span><span class="insert">be expressed in addition to that of the members.</span> <span class="delete">aimed at human consumption, with the following characteristics:</span>
-
-<span class="delete">PROV-N expressions adopt</span><span class="insert">Many different types of collections exist, such as</span> a <em><span class="delete">functional notation</span><span class="delete"> consisting
-of a name and a list of arguments in parentheses.</span>
-
-<span class="delete">The interpretation of PROV-N arguments is defined according to their </span><span class="delete">position</span><span class="delete"> in the list of arguments. This convention allows for a compact notation. </span>
-
-<span class="delete">
-PROV-N </span><span class="delete">optional arguments</span><span class="delete"> 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><span class="delete">-</span><span class="delete"> is used for this purpose.
-</span>
-
-<span class="delete">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 </span><span class="delete">first position</span><span class="insert">sets</span></em>, <em><span class="insert">dictionaries</span></em><span class="insert">, or </span><em><span class="insert">lists</span></em><span class="insert">, all of which involve a membership relationship between the constituents </span>and the <span class="delete">the set of attribute-value pairs</span><span class="insert">collection. </span></p>
-
-<div class="anexample conceptexample" id="collection-example" count="14">
+<span class="glossary-ref"><span class="insert"> A </span><span class="dfn"><span class="insert">collection</span></span><span class="insert"> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be </span><span class="dfn"><span class="insert">member of</span></span><span class="insert"> the collections. </span></span><span class="insert"> This concept allows for the provenance of the collection itself to be expressed in addition to that of the members. Many different types of collections exist, such as a </span><em><span class="delete">last position</span><span class="insert">sets</span></em><span class="delete">.
+Consistent with the convention on arguments, the marker</span><span class="insert">, </span><em><span class="insert">dictionaries</span></em><span class="insert">, or </span><em><span class="insert">lists</span></em><span class="insert">, all of which involve a membership relationship between the constituents and the collection. </span></p>
+
+<div class="anexample conceptexample" id="collection-example" data-count="14"><div class="anexampleTitle"><span class="insert">Example 14</span></div>
<p><span class="insert">
-An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point</span> in <span class="delete">the </span><span class="delete">last position</span><span class="delete">.
-Consistent with the convention on arguments, the marker</span><span class="insert">time, how it was assembled, etc.
+An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point in time, how it was assembled, etc.
</span></p></div>
@@ -1959,8 +1958,8 @@
wasGeneratedBy(e2,a1)
</span><span class="delete">
The</span><span class="insert">their interrelations</span></td></tr>
-<tr><td><span class="insert">2</span></td><td style="text-align: left;"><span class="insert">Agent and Responsibility</span></td><td><span class="insert">✔</span></td><td><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.2</span></a></td><td><a href="#component2"><span class="insert">5.2</span></a></td><td style="text-align: left;"><span class="insert">about agents and concepts ascribing responsibility to them</span></td></tr>
-<tr><td><span class="insert">3</span></td><td style="text-align: left;"><span class="insert">Derivation</span></td><td><span class="insert">✔</span></td><td><a href="#section-derivation"><span class="insert">2.1.3</span></a></td><td><a href="#component3"><span class="insert">5.3</span></a></td><td style="text-align: left;"><span class="insert">about derivations and its subtypes</span></td></tr>
+<tr><td><span class="insert">2</span></td><td style="text-align: left;"><span class="insert">Derivation</span></td><td><span class="insert">✔</span></td><td><a href="#section-derivation"><span class="insert">2.1.2</span></a></td><td><a href="#component3"><span class="insert">5.2</span></a></td><td style="text-align: left;"><span class="insert">about derivations and its subtypes</span></td></tr>
+<tr><td><span class="insert">3</span></td><td style="text-align: left;"><span class="insert">Agent and Responsibility</span></td><td><span class="insert">✔</span></td><td><a href="#section-agents-attribution-association-delegation"><span class="insert">2.1.3</span></a></td><td><a href="#component2"><span class="insert">5.3</span></a></td><td style="text-align: left;"><span class="insert">about agents and concepts ascribing responsibility to them</span></td></tr>
<tr><td><span class="insert">4</span></td><td style="text-align: left;"><span class="insert">Alternate</span></td><td></td><td><span class="insert">—</span></td><td><a href="#component4"><span class="insert">5.4</span></a></td><td style="text-align: left;"><span class="insert">about relations linking entities referring the</span> same <span class="delete">description, but with an explicit identifier </span><span class="delete">u1</span><span class="delete"> for the usage,</span><span class="insert">thing</span></td></tr>
<tr><td><span class="insert">5</span></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="#component5"><span class="insert">5.5</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">6</span></td><td style="text-align: left;"><span class="insert">Collections</span></td><td></td><td><a href="#section-collections"><span class="insert">2.2.3</span></a></td><td><a href="#component6"><span class="insert">5.6</span></a></td><td style="text-align: left;"><span class="insert">about collections</span> and <span class="delete">the syntactic marker </span><span class="delete">-</span><span class="delete"> to mark the absence of identifier in the generation.
@@ -2000,7 +1999,7 @@
</span></li>
</ul>
-<div class="anexample" count="15">
+<div class="anexample" data-count="15"><div class="anexampleTitle"><span class="insert">Example 15</span></div>
<p><span class="insert">
An activity with identifier </span><span class="name"><span class="insert">a1</span></span><span class="insert"> and an attribute </span><span class="name"><span class="insert">type</span></span><span class="insert"> with value </span><span class="name"><span class="insert">createFile</span></span><span class="insert">.
</span></p><pre class="codeexample"><span class="insert">activity(a1, [prov:type="createFile"])
@@ -2327,10 +2326,10 @@
<caption id="relations-at-a-glance">Table <span class="delete">3:</span><span class="insert">4:</span> PROV-DM Relations At a Glance</caption>
<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="3"><span class="insert">Object</span></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td>Entity</td><td>Activity</td><td>Agent</td><span class="delete">Note</span></tr>
-<tr><td rowspan="3"><span class="insert">Subject</span></td><td>Entity</td><td><div class="component3-color"><a class="essential internalDFN" href="#dfn-wasderivedfrom">wasDerivedFrom</a><br><a>wasRevisionOf</a><br><a>wasQuotedFrom</a><br><a>hadOriginalSource</a></div><div class="component4-color"><a href="#dfn-alternateof" class="internalDFN">alternateOf</a><br><a href="#dfn-specializationof" class="internalDFN">specializationOf</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="component2-color"><a class="essential internalDFN" href="#dfn-wasattributedto">wasAttributedTo<span class="delete">hasAnnotation</span></a></td></tr>
-<tr><td>Activity</td><td><div 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></div></td><td class="component1-color"><span class="delete">wasStartedByActivity</span><a class="essential internalDFN" href="#dfn-wasinformedby">wasInformedBy</a></td><td class="component2-color"><a class="essential internalDFN" href="#dfn-wasassociatedwith">wasAssociatedWith<span class="delete">hasAnnotation</span></a></td></tr>
-<tr><td>Agent</td><td>—</td><td>—</td><td class="component2-color"><a class="essential internalDFN" href="#dfn-actedonbehalfof">actedOnBehalfOf<span class="delete">hasAnnotation</span>
-<span class="delete">Note</span><span class="delete">—</span><span class="delete">—</span><span class="delete">—</span><span class="delete">hasAnnotation</span></a></td></tr>
+<tr><td rowspan="3"><span class="insert">Subject</span></td><td>Entity</td><td><div class="component3-color"><span class="delete">wasDerivedFrom</span><a class="essential internalDFN" href="#dfn-wasderivedfrom"><span class="insert">WasDerivedFrom</span></a><br><span class="delete">wasRevisionOf</span><a><span class="insert">WasRevisionOf</span></a><br><span class="delete">wasQuotedFrom</span><a><span class="insert">WasQuotedFrom</span></a><br><span class="delete">hadOriginalSource</span><a><span class="insert">HadOriginalSource</span></a></div><div class="component4-color"><a href="#dfn-alternateof" class="internalDFN"><span class="delete">alternateOf</span><span class="insert">AlternateOf</span></a><br><a href="#dfn-specializationof" class="internalDFN"><span class="delete">specializationOf</span><span class="insert">SpecializationOf</span></a></div></td><td class="component1-color"><span class="delete">wasGeneratedBy</span><a class="essential internalDFN" title="wasGeneratedBy" href="#dfn-wasgeneratedby"><span class="insert">WasGeneratedBy</span></a><br><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN"><span class="delete">wasInvalidatedBy</span><span class="insert">WasInvalidatedBy</span></a></td><td class="component2-color"><span class="delete">wasAttributedTo</span><span class="delete">hasAnnotation</span><a class="essential internalDFN" href="#dfn-wasattributedto"><span class="insert">WasAttributedTo</span></a></td></tr>
+<tr><td>Activity</td><td><div class="component1-color"><span class="delete">used</span><a class="essential internalDFN" href="#dfn-used"><span class="insert">Used</span></a><br><a href="#dfn-wasstartedby" class="internalDFN"><span class="delete">wasStartedBy</span><span class="insert">WasStartedBy</span></a><br><a href="#dfn-wasendedby" class="internalDFN"><span class="delete">wasEndedBy</span><span class="insert">WasEndedBy</span></a></div></td><td class="component1-color"><span class="delete">wasStartedByActivity</span><span class="delete">wasInformedBy</span><a class="essential internalDFN" href="#dfn-wasinformedby"><span class="insert">WasInformedBy</span></a></td><td class="component2-color"><span class="delete">wasAssociatedWith</span><span class="delete">hasAnnotation</span><a class="essential internalDFN" href="#dfn-wasassociatedwith"><span class="insert">WasAssociatedWith</span></a></td></tr>
+<tr><td>Agent</td><td>—</td><td>—</td><td class="component2-color"><span class="delete">actedOnBehalfOf</span><span class="delete">hasAnnotation</span>
+<span class="delete">Note</span><span class="delete">—</span><span class="delete">—</span><span class="delete">—</span><span class="delete">hasAnnotation</span><a class="essential internalDFN" href="#dfn-actedonbehalfof"><span class="insert">ActedOnBehalfOf</span></a></td></tr>
</tbody></table>
</div>
@@ -2353,24 +2352,29 @@
<tr class="component1-color"><td><a href="#concept-invalidation" class="internalDFN">Invalidation</a></td><td><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN"><span class="delete">wasInvalidatedBy(id,e,a,t,attrs)</span><span class="insert">wasInvalidatedBy(id;e,a,t,attrs)</span></a></td></tr>
<span class="delete">Communication</span><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component2-color" style="border-collapse: collapse; "><td class="essential"><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a></td><td><span class="delete">wasInformedBy(id,a2,a1,attrs)</span><a title="dfn-agent" class="essential internalDFN" href="#dfn-agent"><span class="insert">agent(id, [ attr1=val1, ...])</span></a></td><td rowspan="8"><a href="#component2"><span class="insert">Component 2: agents/responsibility</span></a></td></tr>
-<span class="delete">Start by Activity</span><span class="delete">wasStartedByActivity(id, a2, a1, attrs)</span>
-<tr class="component2-color"><span class="delete">Agent</span><span class="delete">agent(id, [ attr1=val1, ...])</span>
-<td class="essential"><a href="#concept-attribution" class="internalDFN">Attribution</a></td><td><a title="wasAttributedTo" href="#dfn-wasattributedto" class="internalDFN"><span class="delete">wasAttributedTo(id,e,ag,attr)</span><span class="essential"><span class="insert">wasAttributedTo(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">e,ag</span></span><span class="insert">,attr</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
-<tr class="component2-color"><td class="essential"><a href="#concept-activityAssociation" class="internalDFN">Association</a></td><td><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN"><span class="delete">wasAssociatedWith(id,a,ag,pl,attrs)</span><span class="essential"><span class="insert">wasAssociatedWith(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">a,ag</span></span><span class="insert">,pl,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
-<tr class="component2-color"><span class="delete">Responsibility</span><td class="essential"><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN"><span class="delete">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span><span class="essential"><span class="insert">actedOnBehalfOf(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">ag2,ag1</span></span><span class="insert">,a,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
-<tr class="component2-color"><td class="provType"><a href="#concept-plan" class="internalDFN"><span class="insert">Plan</span></a></td><td><a title="plan" href="#concept-plan" class="internalDFN"><span class="insert">... prov:type='prov:Plan' ...</span></a></td>
-</tr><tr class="component2-color"><td class="provType"><a href="#concept-person" class="internalDFN"><span class="insert">Person</span></a></td><td><a title="person" href="#concept-person" class="internalDFN"><span class="insert">... prov:type='prov:Person' ...</span></a></td>
-</tr><tr class="component2-color"><td class="provType"><a href="#concept-organization" class="internalDFN"><span class="insert">Organization</span></a></td><td><a title="organization" href="#concept-organization" class="internalDFN"><span class="insert">... prov:type='prov:Organization' ...</span></a></td>
-</tr><tr class="component2-color"><td class="provType"><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="insert">SoftwareAgent</span></a></td><td><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="insert">... prov:type='prov:SoftwareAgent' ...</span></a></td>
+
+<tr class="component2-color"><td class="essential"><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td><td><span class="delete">wasInformedBy(id,a2,a1,attrs)</span><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN"><span class="essential"><span class="insert">wasDerivedFrom(</span></span><span class="insert">id; </span><span class="essential"><span class="insert">e2, e1</span></span><span class="insert">, a, g2, u1, attrs</span><span class="essential"><span class="insert">)</span></span></a></td><td rowspan="5"><a href="#component2"><span class="insert">Component 2: derivation</span></a></td></tr>
+<span class="delete">Start by Activity</span><tr class="component2-color"><td class="provType"><a href="#concept-revision" class="internalDFN"><span class="insert">Revision</span></a></td><td><span class="delete">wasStartedByActivity(id, a2, a1, attrs)</span><a title="revision" href="#concept-revision" class="internalDFN"><span class="insert">... prov:type='prov:WasRevisionOf' ...</span></a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-quotation" class="internalDFN"><span class="insert">Quotation</span></a></td><td><a title="quotation" href="#concept-quotation" class="internalDFN"><span class="insert">... prov:type='prov:WasQuotedFrom' ...</span></a></td></tr>
+<tr class="component2-color"><td class="provType"><a href="#concept-original-source" class="internalDFN"><span class="insert">Original Source</span></a></td><td><a title="Original Source" href="#concept-original-source" class="internalDFN"><span class="insert">... prov:type='prov:HadOriginalSource' ...</span></a></td></tr>
+<tr class="component2-color"><td><a href="#concept-trace" class="internalDFN"><span class="insert">Trace</span></a></td><td><a title="tracedTo" href="#dfn-tracedto" class="internalDFN"><span class="insert">tracedTo(id;e2,e1,attrs)</span></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"><span class="insert">Component 3: agents/responsibility</span></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="delete">wasAttributedTo(id,e,ag,attr)</span><span class="essential"><span class="insert">wasAttributedTo(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">e,ag</span></span><span class="insert">,attr</span><span class="essential"><span class="insert">)</span></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="delete">wasAssociatedWith(id,a,ag,pl,attrs)</span><span class="essential"><span class="insert">wasAssociatedWith(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">a,ag</span></span><span class="insert">,pl,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
+<span class="delete">Responsibility</span><tr class="component3-color"><td class="essential"><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a></td><td><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN"><span class="delete">actedOnBehalfOf(id,ag2,ag1,a,attrs)</span><span class="essential"><span class="insert">actedOnBehalfOf(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">ag2,ag1</span></span><span class="insert">,a,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
+<tr class="component3-color"><span class="delete">Derivation</span><td class="provType"><a href="#concept-plan" class="internalDFN"><span class="insert">Plan</span></a></td><td><span class="delete">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span><a title="plan" href="#concept-plan" class="internalDFN"><span class="insert">... prov:type='prov:Plan' ...</span></a></td>
+</tr><tr class="component3-color"><td class="provType"><a href="#concept-person" class="internalDFN"><span class="insert">Person</span></a></td><td><a title="person" href="#concept-person" class="internalDFN"><span class="insert">... prov:type='prov:Person' ...</span></a></td>
+</tr><tr class="component3-color"><td class="provType"><a href="#concept-organization" class="internalDFN"><span class="insert">Organization</span></a></td><td><a title="organization" href="#concept-organization" class="internalDFN"><span class="insert">... prov:type='prov:Organization' ...</span></a></td>
+</tr><tr class="component3-color"><td class="provType"><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="insert">SoftwareAgent</span></a></td><td><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="insert">... prov:type='prov:SoftwareAgent' ...</span></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"><td class="essential"><a href="#concept-derivation" class="internalDFN">Derivation</a></td><td><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN"><span class="delete">wasDerivedFrom(id, </span><span class="essential"><span class="insert">wasDerivedFrom(</span></span><span class="insert">id; </span><span class="essential">e2, <span class="delete">e1,</span><span class="insert">e1</span></span><span class="insert">,</span> a, g2, u1, <span class="delete">attrs)</span><span class="insert">attrs</span><span class="essential"><span class="insert">)</span></span></a></td><td rowspan="5"><a href="#component3"><span class="insert">Component 3: derivation</span></a></td></tr>
-<tr class="component3-color"><td class="provType"><a href="#concept-revision" class="internalDFN">Revision</a></td><td><span class="delete">wasRevisionOf(id,e2,e1,ag,attrs)</span><a title="revision" href="#concept-revision" class="internalDFN"><span class="insert">... prov:type='prov:WasRevisionOf' ...</span></a></td></tr>
-<tr class="component3-color"><td class="provType"><a href="#concept-quotation" class="internalDFN">Quotation</a></td><td><span class="delete">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span><a title="quotation" href="#concept-quotation" class="internalDFN"><span class="insert">... prov:type='prov:WasQuotedFrom' ...</span></a></td></tr>
-<tr class="component3-color"><td class="provType"><a href="#concept-original-source" class="internalDFN">Original Source</a></td><td><span class="delete">hadOriginalSource(id,e2,e1,attrs)</span><a title="Original Source" href="#concept-original-source" class="internalDFN"><span class="insert">... prov:type='prov:HadOriginalSource' ...</span></a></td></tr>
-<tr class="component3-color"><td><a href="#concept-trace" class="internalDFN">Trace</a></td><td><a title="tracedTo" href="#dfn-tracedto" class="internalDFN"><span class="delete">tracedTo(id,e2,e1,attrs)</span><span class="insert">tracedTo(id;e2,e1,attrs)</span></a></td></tr>
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
+<span class="delete">Revision</span><span class="delete">wasRevisionOf(id,e2,e1,ag,attrs)</span>
+<span class="delete">Quotation</span><span class="delete">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span>
+<span class="delete">Original Source</span><span class="delete">hadOriginalSource(id,e2,e1,attrs)</span>
+<span class="delete">Trace</span><span class="delete">tracedTo(id,e2,e1,attrs)</span>
+
+
<tr class="component4-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="2"><a href="#component4"><span class="insert">Component 4: alternate</span></a></td></tr>
<tr class="component4-color"><td><a href="#concept-specialization" class="internalDFN">Specialization</a></td><td><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">specializationOf(sub, super)</a></td></tr>
@@ -2432,7 +2436,7 @@
<li><span class="attribute" id="entity.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this entity.</li>
</ul></div>
-<div class="anexample" count="16">
+<div class="anexample" data-count="16"><div class="anexampleTitle"><span class="insert">Example 16</span></div>
<p>
The following expression</p>
<pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
@@ -2450,7 +2454,7 @@
<h4><span class="secno"><span class="delete">4.1.2</span><span class="insert">5.1.2</span> </span>Activity</h4>
-<div class="glossary-ref"> An <dfn id="concept-activity">activity</dfn> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, generating, or being associated with entities. </div>
+<div class="glossary-ref"> An <dfn id="concept-activity">activity</dfn> is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, <span class="delete">generating, </span>or <span class="delete">being associated with</span><span class="insert">generating</span> entities. </div>
<p></p><div class="attributes" id="attributes-activity"> An <dfn title="dfn-Activity" id="dfn-activity">activity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-activity">activity(id, st, et, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
@@ -2460,7 +2464,7 @@
<li><span class="attribute" id="activity.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this activity.</li>
</ul></div>
-<div class="anexample" count="17">
+<div class="anexample" data-count="17"><div class="anexampleTitle"><span class="insert">Example 17</span></div>
<p>
The following expression</p>
<pre class="codeexample">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
@@ -2503,7 +2507,7 @@
-<div class="anexample" count="18">
+<div class="anexample" data-count="18"><div class="anexampleTitle"><span class="insert">Example 18</span></div>
<p>
The following expressions</p>
<pre class="codeexample"> <span class="delete">wasGeneratedBy(e1,a1,</span><span class="insert">wasGeneratedBy(e1, a1,</span> 2001-10-26T21:32:52, <span class="delete">[ex:port="p1"])</span><span class="insert">[ ex:port="p1" ])</span>
@@ -2516,7 +2520,7 @@
</div>
-<div class="anexample" count="19">
+<div class="anexample" data-count="19"><div class="anexampleTitle"><span class="insert">Example 19</span></div>
<p>
In some cases, we may want to record the time at which an entity was generated without having to specify the activity that generated it. To support this requirement, the activity element in generation is optional. Hence, the following expression indicates the time at which an entity is generated, without naming the activity that did it.</p>
<pre class="codeexample"> <span class="delete">wasGeneratedBy(e,-,2001-10-26T21:32:52)</span><span class="insert">wasGeneratedBy(e, -, 2001-10-26T21:32:52)</span>
@@ -2550,7 +2554,7 @@
</p>
-<div class="anexample" count="20">
+<div class="anexample" data-count="20"><div class="anexampleTitle"><span class="insert">Example 20</span></div>
<p>The following usages</p>
<pre class="codeexample"> <span class="delete">used(a1,e1,2011-11-16T16:00:00,[ex:parameter="p1"])</span><span class="insert">used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter="p1" ])</span>
<span class="delete">used(a1,e2,2011-11-16T16:00:01,[ex:parameter="p2"])</span><span class="insert">used(a1, e2, 2011-11-16T16:00:01, [ ex:parameter="p2" ])</span>
@@ -2572,7 +2576,7 @@
<div id="term-wasInformedBy" class="section">
<h4><span class="secno"><span class="delete">4.1.5</span><span class="insert">5.1.5 </span></span><span class="insert">Communication</span></h4>
-<div class="glossary-ref"> <dfn id="concept-communication"><span class="insert">Communication</span></dfn><span class="insert"> is the exchange of an entity by two activities, one activity using the entity generated by the other. </span></div>
+<div class="glossary-ref"> <dfn id="concept-communication"><span class="insert">Communication</span></dfn><span class="insert"> is the exchange of an unspecified entity by two activities, one activity using some entity generated by the other. </span></div>
<p><span class="insert">A communication implies that activity </span><span class="name"><span class="insert">a2</span></span><span class="insert"> is dependent on another </span><span class="name"><span class="insert">a1</span></span><span class="insert">, by way of some unspecified entity that is generated by </span><span class="name"><span class="insert">a1</span></span><span class="insert"> and used by </span><span class="name"><span class="insert">a2</span></span><span class="insert">.</span></p>
@@ -2593,7 +2597,7 @@
-<div class="anexample" count="21">
+<div class="anexample" data-count="21"><div class="anexampleTitle"><span class="insert">Example 21</span></div>
<p><span class="insert">
Consider two activities </span><span class="name"><span class="insert">a1</span></span><span class="insert"> and </span><span class="name"><span class="insert">a2</span></span><span class="insert">, the former performed by a government agency, and the latter by a driver caught speeding.
</span></p><pre class="codeexample"><span class="insert">activity(a1, [ prov:type="traffic regulations enforcing" ])
@@ -2624,7 +2628,7 @@
<p><span class="insert">While each of </span><a href="#start.id"><span class="attribute"><span class="insert">id</span></span></a><span class="insert">, </span><a href="#start.trigger"><span class="attribute"><span class="insert">trigger</span></span></a><span class="insert">, </span><a href="#start.starter"><span class="attribute"><span class="insert">starter</span></span></a><span class="insert">, </span><a href="#start.time"><span class="attribute"><span class="insert">time</span></span></a><span class="insert">, and </span><a href="#start.attributes"><span class="attribute"><span class="insert">attributes</span></span></a><span class="insert"> is </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert">, at least one of them </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be present.</span></p>
-<div class="anexample" count="22">
+<div class="anexample" data-count="22"><div class="anexampleTitle"><span class="insert">Example 22</span></div>
<p>
The following example contains the description of an activity <span class="name">a1</span> (a discussion), which was started at a specific time, and was triggered by an email message <span class="name">e1</span>.</p>
<pre class="codeexample"><span class="delete">entity(e1,[prov:type="email message"])
@@ -2646,7 +2650,7 @@
</pre>
</div>
-<div class="anexample" count="23">
+<div class="anexample" data-count="23"><div class="anexampleTitle"><span class="insert">Example 23</span></div>
<p>
In the following example, a race is started by a bang, and responsibility for this trigger is attributed to an agent
<span class="name">ex:Bob</span>.
@@ -2659,7 +2663,7 @@
</pre>
</div>
-<div class="anexample" count="24">
+<div class="anexample" data-count="24"><div class="anexampleTitle"><span class="insert">Example 24</span></div>
<p><span class="insert">
In this example, filling fuel was started as a consequence of
observing low fuel. The trigger entity is unspecified, it could
@@ -2702,7 +2706,7 @@
<p><span class="insert">While each of </span><a href="#end.id"><span class="attribute"><span class="insert">id</span></span></a><span class="insert">, </span><a href="#end.trigger"><span class="attribute"><span class="insert">trigger</span></span></a><span class="insert">, </span><a href="#end.ender"><span class="attribute"><span class="insert">ender</span></span></a><span class="insert">, </span><a href="#end.time"><span class="attribute"><span class="insert">time</span></span></a><span class="insert">, and </span><a href="#end.attributes"><span class="attribute"><span class="insert">attributes</span></span></a><span class="insert"> is </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert">, at least one of them </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be present.</span></p>
-<div class="anexample" count="25">
+<div class="anexample" data-count="25"><div class="anexampleTitle"><span class="insert">Example 25</span></div>
<p>
The following example is a description of an activity <span class="name">a1</span> (editing) that was ended following an approval document <span class="name">e1</span>.</p>
<pre class="codeexample"><span class="delete">entity(e1,[prov:type="approval document"])
@@ -2755,7 +2759,7 @@
-<div class="anexample" id="anexample-invalidation1" count="26">
+<div class="anexample" id="anexample-invalidation1" data-count="26"><div class="anexampleTitle"><span class="insert">Example 26</span></div>
<p>
<em>The <span class="delete">Painter,</span><span class="insert">Painter</span></em><span class="insert">,</span> a Picasso painting, is known to have been destroyed in a <a href="http://en.wikipedia.org/wiki/Lost_artworks#20th_century">plane accident</a>.
@@ -2767,7 +2771,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-invalidation2" count="27">
+<div class="anexample" id="anexample-invalidation2" data-count="27"><div class="anexampleTitle"><span class="insert">Example 27</span></div>
<p>
The BBC news home page on 2012-04-03 <span class="name">ex:bbcNews2012-04-03</span>
contained a reference to a given news item
@@ -2787,7 +2791,7 @@
</div>
-<div class="anexample" id="anexample-invalidation3" count="28">
+<div class="anexample" id="anexample-invalidation3" data-count="28"><div class="anexampleTitle"><span class="insert">Example 28</span></div>
<p>
In this example, the "buy one beer, get one free" offer expired at the end of the happy hour.</p>
<pre class="codeexample">entity(buy_one_beer_get_one_free_offer_during_happy_hour)
@@ -2817,26 +2821,117 @@
-<span class="delete">4.1.8 </span><span class="delete">Communication</span>
-
- <span class="delete">Communication</span><span class="delete"> is the exchange of an entity by two activities, one activity using the entity generated by the other. </span>
-
-
-<span class="delete">A communication implies that activity </span><span class="delete">a2</span><span class="delete"> is dependent on another </span><span class="delete">a1</span><span class="delete">, by way of some unspecified entity that is generated by </span><span class="delete">a1</span><span class="delete"> and used by </span><span class="delete">a2</span><span class="delete">.</span>
-
-
-
-
-<span class="delete">
-A </span><span class="delete">communication</span><span class="delete">, written as
+
+
+</div>
+
+
+<div id="component2" class="section">
+<h3><span class="secno"><span class="insert">5.2 </span></span><span class="insert">Component 2: Derivations</span></h3>
+
+
+
+<p><span class="insert">The third component of PROV-DM is concerned with: </span><a title="derivation" href="#concept-derivation" class="internalDFN"><span class="insert">derivations</span></a><span class="insert"> of </span><a title="entity" href="#concept-entity" class="internalDFN"><span class="insert">entities</span></a><span class="insert"> from others; derivation subtypes </span><a href="#concept-revision" class="internalDFN"><span class="insert">Revision</span></a><span class="insert">, </span><a href="#concept-quotation" class="internalDFN"><span class="insert">Quotation</span></a><span class="insert">, and </span><a href="#concept-original-source" class="internalDFN"><span class="insert">Original Source</span></a><span class="insert">; derivation-related </span><a href="#concept-trace" class="internalDFN"><span class="insert">Trace</span></a><span class="insert">.
+ </span><a href="#figure-component2"><span class="insert">Figure 6</span></a><span class="insert"> depicts the third component
+with PROV core structures in the yellow area, including two classes
+(</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">) and binary association
+(</span><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a><span class="insert">). PROV extended structures are found outside this
+area. UML association classes express expanded n-ary relations.
+</span></p>
+
+
+<div style="text-align: center;">
+<figure>
+
+<img src="uml/component2.png" alt="derivation">
+<div class="figcaption" id="figure-component2"><span class="insert">Figure 6: Derivation Component Overview</span></div>
+</figure>
+</div>
+
+<div id="term-derivation" class="section">
+<h4><span class="secno"><span class="delete">4.1.8 </span><span class="delete">Communication</span><span class="insert">5.2.1 </span></span><span class="insert">Derivation</span></h4>
+
+
+
+
+
+
+
+<div class="glossary-ref"> <span class="delete">Communication</span><span class="insert">A </span><dfn id="concept-derivation"><span class="insert">derivation</span></dfn> is <span class="delete">the exchange</span><span class="insert">a transformation</span> of an entity <span class="delete">by</span><span class="insert">into another, an update of an entity, resulting in a new one, or based on an entity, the construction of another.</span></div>
+
+
+
+
+<p><span class="insert">According to </span><a href="#section-prov-overview"><span class="insert">Section 2</span></a><span class="insert">, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
+underpinning activities performing the necessary actions resulting in such a derivation.
+A derivation can be described at various levels of precision. In its simplest form, derivation relates</span> two <span class="delete">activities, one</span><span class="insert">entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this</span> activity <span class="delete">using the entity</span><span class="insert">can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the</span> generated <span class="delete">by the other. </span><span class="insert">and used entities, respectively, can be provided, so as to make the derivation path, through usage, activity, and generation, explicit. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </span></p>
+
+
+<p></p><div class="attributes" id="attributes-derivation">A <span class="delete">communication implies</span><dfn title="wasDerivedFrom" id="dfn-wasderivedfrom"><span class="insert">derivation</span></dfn><span class="withPn"><span class="insert">, written </span><span class="pnExpression" id="pn-wasDerivedFrom"><span class="insert">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span></span><span class="insert"> in PROV-N,</span></span><span class="insert"> has:
+</span><ul>
+<li><span class="attribute" id="derivation.id"><span class="insert">id</span></span><span class="insert">: an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert"> identifier for a derivation;</span></li>
+<li><span class="attribute" id="derivation.generatedEntity"><span class="insert">generatedEntity</span></span><span class="insert">: the identifier (</span><span class="name"><span class="insert">e2</span></span><span class="insert">) of the entity generated by the derivation;</span></li>
+<li><span class="attribute" id="derivation.usedEntity"><span class="insert">usedEntity</span></span><span class="insert">: the identifier (</span><span class="name"><span class="insert">e1</span></span><span class="insert">) of the entity used by the derivation;</span></li>
+<li><span class="attribute" id="derivation.activity"><span class="insert">activity</span></span><span class="insert">: an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert"> identifier (</span><span class="name"><span class="insert">a</span></span><span class="insert">) for the activity using and generating the above entities;</span></li>
+<li><span class="attribute" id="derivation.generation"><span class="insert">generation</span></span><span class="insert">: an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert"> identifier (</span><span class="name"><span class="insert">g2</span></span><span class="insert">) for the generation involving the generated entity (</span><span class="name"><span class="insert">e2</span></span><span class="insert">) and activity;</span></li>
+<li><span class="attribute" id="derivation.usage"><span class="insert">usage</span></span><span class="insert">: an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert"> identifier (</span><span class="name"><span class="insert">u1</span></span><span class="insert">) for the usage involving the used entity (</span><span class="name"><span class="insert">e1</span></span><span class="insert">) and activity;</span></li>
+<li><span class="attribute" id="derivation.attributes"><span class="insert">attributes</span></span><span class="insert">: an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert"> set (</span><span class="name"><span class="insert">attrs</span></span><span class="insert">) of attribute-value pairs representing additional information about this derivation.</span></li>
+</ul>
+</div>
+
+
+
+<div class="anexample" data-count="29"><div class="anexampleTitle"><span class="insert">Example 29</span></div>
+<p><span class="insert">The following descriptions are about derivations between </span><span class="name"><span class="insert">e2</span></span><span class="insert"> and </span><span class="name"><span class="insert">e1</span></span><span class="insert">, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</span></p>
+<pre class="codeexample"><span class="insert">wasDerivedFrom(e2, e1)
+wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
+</span></pre>
+<p><span class="insert">The following description expresses</span> that activity <span class="name"><span class="delete">a2</span><span class="insert">a</span></span><span class="insert">,
+using the entity </span><span class="name"><span class="insert">e1</span></span><span class="insert"> according to usage </span><span class="name"><span class="insert">u1</span></span><span class="insert">,
+ derived the
+entity </span><span class="name"><span class="insert">e2</span></span><span class="insert"> and generated it according to generation
+ </span><span class="name"><span class="insert">g2</span></span><span class="insert">. It</span> is <span class="delete">dependent on another</span><span class="insert">followed by descriptions for generation</span> <span class="name"><span class="delete">a1</span><span class="delete">, by way of some unspecified entity that is generated by</span><span class="insert">g2</span></span><span class="insert"> and usage</span> <span class="name"><span class="delete">a1</span><span class="delete"> and used by </span><span class="delete">a2</span><span class="insert">u1</span></span>.</p>
+<pre class="codeexample"><span class="insert">wasDerivedFrom(e2, e1, a, g2, u1)
+wasGeneratedBy(g2; e2, a, -)
+used(u1; a, e1, -)
+</span></pre>
+<p><span class="insert">With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity </span><span class="name"><span class="insert">e1</span></span><span class="insert"> was used by the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity </span><span class="name"><span class="insert">e2</span></span><span class="insert"> was obtained from (say, for a function returning multiple results).</span></p>
+</div>
+
+
+
+
+</div>
+
+<div id="term-revision" class="section">
+<h4><span class="secno"><span class="insert">5.2.2 </span></span><span class="insert">Revision</span></h4>
+
+<p><span class="glossary-ref"><span class="insert"> A </span><dfn id="concept-revision"><span class="insert">revision</span></dfn><span class="insert"> is a derivation that revises an entity into a revised version. </span></span></p><span class="delete">
+A </span><span class="delete">communication</span>
+
+<p><span class="insert">Revision is a particular case of </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert"> of an entity into its revised version.</span></p>
+
+
+
+
+<div class="anexample" id="anexample-revision" data-count="30"><div class="anexampleTitle"><span class="insert">Example 30</span></div>
+<p><span class="insert">
+Revisiting the example of </span><a href="#section-example-two"><span class="insert">Section 4.2</span></a>,<span class="delete"> written as
</span><span class="delete">wasInformedBy(id,a2,a1,attrs)</span><span class="delete"> in PROV-N,</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">id</span><span class="delete">:</span><span class="insert">
+we can now state that the report
+ </span><span class="name"><span class="insert">tr:WD-prov-dm-20111215</span></span><span class="insert"> was a revision of
+ the report </span><span class="name"><span class="insert">tr:WD-prov-dm-20111018</span></span><span class="insert">.
+</span></p><pre class="codeexample"><span class="insert">entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD'</span> <span class="delete">an </span><span class="delete">optional</span><span class="delete"> identifier</span><span class="insert">])
+entity(tr:WD-prov-dm-20111018, [ prov:type='rec54:WD'</span> <span class="delete">identifying the relation;</span>
<span class="delete">informed</span><span class="delete">: the identifier (</span><span class="delete">a2</span><span class="delete">) of the informed activity;
</span><span class="delete">informant</span><span class="delete">: the identifier (</span><span class="delete">a1</span><span class="delete">) of the informant activity;
</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 communication.</span>
-
-
+<span class="insert">])
+wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018, [ prov:type='prov:WasRevisionOf' ])
+</span></pre>
+</div>
@@ -2848,24 +2943,43 @@
wasInformedBy(a2,a1)
</span><span class="delete">
The last line indicates that some implicit entity was generated by </span><span class="delete">a1</span><span class="delete"> and used by </span><span class="delete">a2</span><span class="delete">; this entity may be a traffic ticket that had a notice of fine, amount, and payment mailing details.
-</span>
-
-
-
-<span class="delete">4.1.9 </span><span class="delete">Start by Activity</span>
-
- <span class="delete">Start by Activity</span><span class="delete"> is the start of an activity with an implicit trigger generated by another activity. </span>
-
-
-
-<span class="delete">
-A </span><span class="delete">start by activity</span><span class="delete">, written as
+</span></div>
+
+
+
+
+<div id="term-quotation" class="section">
+<h4><span class="secno"><span class="delete">4.1.9 </span><span class="delete">Start by Activity</span><span class="insert">5.2.3 </span></span><span class="insert">Quotation</span></h4>
+
+<p>
+<span class="glossary-ref"> <span class="delete">Start</span><span class="insert">A </span><dfn id="concept-quotation"><span class="insert">quotation</span></dfn><span class="insert"> is the repeat of (some or all of) an entity, such as text or image,</span> by <span class="delete">Activity</span> <span class="insert">someone who may or may not be its original author. </span></span>
+</p>
+
+<p><span class="insert">Quotation
+ </span>is <span class="delete">the start of</span><span class="insert">a particular case of </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert"> in which</span> an <span class="delete">activity with</span><span class="insert">entity is derived from</span> an <span class="delete">implicit trigger generated</span><span class="insert">original entity</span> by <span class="delete">another activity. </span><span class="insert">copying, or "quoting", some or all of it.</span></p>
+
+
+
+
+<div class="anexample" id="anexample-quotation" data-count="31"><div class="anexampleTitle"><span class="insert">Example 31</span></div>
+
+
+
+
+<p><span class="insert">
+The following paragraph is a quote from one of </span><a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="insert">the author's blogs</span></a><span class="insert">.
+</span></p><span class="delete">
+A </span><span class="delete">start</span><blockquote id="bl-dagstuhl"><em><span class="insert">
+"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."</span></em>
+</blockquote>
+<p><span class="insert">If </span><a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="name"><span class="insert">wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/</span></span></a><span class="insert"> denotes the original blog</span> by <span class="delete">activity</span><span class="insert">agent </span><span class="name"><span class="insert">ex:Paul</span></span>, <span class="delete">written as
</span><span class="delete">wasStartedByActivity(id, a2, a1, attrs)</span><span class="delete"> in PROV-N,</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 of the relation;</span>
-<span class="delete">started</span><span class="delete">: the identifier (</span><span class="delete">a2</span><span class="delete">) of the started activity;
-</span><span class="delete">starter</span><span class="delete">: the identifier (</span><span class="delete">a1</span><span class="delete">) of the activity that started the other;</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 start by activity.</span>
+<span class="delete">started</span><span class="delete">: the identifier (</span><span class="insert">and
+ </span><a href="#bl-dagstuhl"><span class="name"><span class="delete">a2</span><span class="delete">) of the started activity;
+</span><span class="delete">starter</span><span class="delete">: the identifier (</span><span class="insert">dm:bl-dagstuhl</span></span></a><span class="insert"> denotes the above paragraph, then the following descriptions express that the above paragraph was copied by agent </span><span class="name"><span class="delete">a1</span><span class="delete">) of the activity that started the other;</span>
+<span class="delete">attributes</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> set (</span><span class="insert">ex:Luc</span></span><span class="insert"> from a part of the blog, attributed to the agent </span><span class="name"><span class="delete">attrs</span><span class="delete">) of attribute-value pairs representing additional information about this start by activity.</span>
@@ -2873,29 +2987,64 @@
<span class="delete">
-Suppose activities </span><span class="delete">a1</span><span class="delete"> and </span><span class="delete">a2</span><span class="delete"> are computer processes that are executed on different hosts, and that </span><span class="delete">a1</span><span class="delete"> started </span><span class="delete">a2</span><span class="delete">. This can be expressed as in the following fragment:</span>
-<span class="delete">activity(a1,t1,t2,[ex:host="server1.example.org",prov:type="workflow"])
+Suppose activities </span><span class="delete">a1</span><span class="delete"> and </span><span class="delete">a2</span><span class="delete"> are computer processes that are executed on different hosts, and that </span><span class="delete">a1</span><span class="delete"> started </span><span class="delete">a2</span><span class="insert">ex:Paul</span></span>.<span class="delete"> This can be expressed as in the following fragment:</span></p>
+<pre class="codeexample"><span class="delete">activity(a1,t1,t2,[ex:host="server1.example.org",prov:type="workflow"])
activity(a2,t3,t4,[ex:host="server2.example.org",prov:type="subworkflow"])
-wasStartedByActivity(a2,a1)
-</span><span class="delete">
+wasStartedByActivity(a2,a1)</span><span class="insert">entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/)
+entity(dm:bl-dagstuhl)
+agent(ex:Luc)
+agent(ex:Paul)
+wasDerivedFrom(dm:bl-dagstuhl,
+ wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/,
+ [ prov:type='prov:WasQuotedFrom' ])
+wasAttributedTo(dm:bl-dagstuhl, ex:Luc)
+wasAttributedTo(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/, ex:Paul)</span>
+</pre><span class="delete">
It is assumed that the activities </span><span class="delete">a1</span><span class="delete"> and </span><span class="delete">a2</span><span class="delete"> are of type "workflow" and "subworkflow", respectively; the latter was started by the former.
</span>
-
-
-
-
-
-
-
+</div>
+
+
+</div>
+
+
+<div id="term-original-source" class="section">
+<h4><span class="secno"><span class="insert">5.2.4 </span></span><span class="insert">Original Source</span></h4>
+
+<p>
+<span class="glossary-ref"><span class="insert"> An </span><dfn id="concept-original-source"><span class="insert">original source</span></dfn><span class="insert"> refers to the source material that is closest to the person, information, period, or idea being studied. </span></span>
+</p>
+
+<p><span class="insert">An </span><dfn id="dfn-original-source"><span class="insert">original source</span></dfn><span class="insert"> relation is a particular case of </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert">
+that aims to give
+credit to the source that originated some information. It is recognized that it may be
+hard to determine which entity constitutes an original source. This definition is inspired by
+</span><span class="name"><span class="insert">original-source</span></span><span class="insert"> as defined in
+</span><a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html"><span class="insert">http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html</span></a><span class="insert">.</span></p>
+
+
+<div class="anexample" data-count="32"><div class="anexampleTitle"><span class="insert">Example 32</span></div>
+<p><span class="insert">
+Let us consider the concept introduced in the current section, identified as </span><a title="original source" href="#concept-original-source" class="internalDFN"><span class="name"><span class="insert">dm:concept-original-source</span></span></a><span class="insert">, and
+the Google page </span><a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html"><span class="name"><span class="insert">go:credit-where-credit-is-due.html</span></span></a><span class="insert">, where the notion original-source was originally described (to the knowledge of the authors).
+</span></p><pre class="codeexample"><span class="insert">entity(dm:concept-original-source)
+entity(go:credit-where-credit-is-due.html)
+wasDerivedFrom(dm:concept-original-source, go:credit-where-credit-is-due.html,
+ [ prov:type='prov:HadOriginalSource' ])
+</span></pre>
+</div>
+
+
+</div>
</div>
-<div id="component2" class="section">
-<h3><span class="secno"><span class="delete">4.2</span><span class="insert">5.2</span> </span>Component 2: Agents and Responsibility</h3>
-
-<p>The second component of <span class="delete">PROV-DM</span><span class="insert">PROV-DM, depicted in </span><a href="#figure-component2"><span class="insert">Figure 6</span></a><span class="insert">,</span> is concerned with <a title="agent" href="#concept-agent" class="internalDFN">agents</a> and the notions of
+<div id="component3" class="section">
+<h3><span class="secno"><span class="delete">4.2</span><span class="insert">5.3</span> </span>Component <span class="delete">2:</span><span class="insert">3:</span> Agents and Responsibility</h3>
+
+<p>The second component of <span class="delete">PROV-DM</span><span class="insert">PROV-DM, depicted in </span><a href="#figure-component3"><span class="insert">Figure 7</span></a><span class="insert">,</span> 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>, <span class="delete">Responsibility</span><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a>, relating agents to entities, activities, and agents, respectively.<span class="delete">
Figure </span><span class="delete">figure-component2</span><span class="delete"> depicts the second component with four</span><span class="insert">
Core structures are displayed in the yellow area and include three</span> classes <span class="delete">(Entity, Activity, Agent, </span>and <span class="delete">Plan)</span><span class="insert">three binary associations. Outside the yellow area, extended structures comprise</span> and <span class="delete">associations between them. </span>UML association classes <span class="insert">to express expanded n-ary relations, and subclasses </span><a href="#concept-plan" class="internalDFN"><span class="insert">Plan</span></a><span class="insert">, </span><a href="#concept-person" class="internalDFN"><span class="insert">Person</span></a><span class="insert">, </span><a title="software-agent" href="#concept-software-agent" class="internalDFN"><span class="insert">SofwareAgent</span></a><span class="insert">, and </span><a href="#concept-organization" class="internalDFN"><span class="insert">Organization</span></a><span class="insert">. The subclasses </span>are <span class="delete">used</span><span class="insert">marked by the UML stereotype "prov:type"</span> to <span class="delete">express n-ary relations.</span><span class="insert">indicate that that these are valid values for the attribute </span><a href="#term-attribute-type"><span class="insert">prov:type</span></a>
@@ -2904,15 +3053,16 @@
<div style="text-align: center;">
+
<figure>
-<img src="uml/component2.png" alt="agents and responsibilities">
-<div class="figcaption" id="figure-component2">Figure 6: Agents and <span class="delete">Responsibilities</span><span class="insert">Responsibility</span> Component Overview</div>
+<img src="uml/component3.png" alt="agents and responsibilities">
+<div class="figcaption" id="figure-component3">Figure <span class="delete">6:</span><span class="insert">7:</span> Agents and <span class="delete">Responsibilities</span><span class="insert">Responsibility</span> Component Overview</div>
</figure>
</div>
<div id="term-agent" class="section">
-<h4><span class="secno"><span class="delete">4.2.1</span><span class="insert">5.2.1</span> </span>Agent</h4>
+<h4><span class="secno"><span class="delete">4.2.1</span><span class="insert">5.3.1</span> </span>Agent</h4>
<div class="glossary-ref"> An <dfn id="concept-agent">agent</dfn> is something that bears some form of responsibility for an activity taking place or for the existence of an entity. </div>
@@ -2950,7 +3100,7 @@
-<div class="anexample" count="29">
+<div class="anexample" data-count="33"><div class="anexampleTitle"><span class="insert">Example 33</span></div>
<p>The following expression is about an agent identified by <span class="name">e1</span>, which is a person, named Alice, with employee number 1234.</p>
<pre class="codeexample">agent(e1, [ex:employee="1234", ex:name="Alice", <span class="delete">prov:type="prov:Person" %% xsd:QName])</span><span class="insert">prov:type='prov:Person' ])</span>
</pre>
@@ -2960,7 +3110,7 @@
</div>
<div id="term-attribution" class="section">
-<h4><span class="secno"><span class="delete">4.2.2</span><span class="insert">5.2.2</span> </span>Attribution</h4>
+<h4><span class="secno"><span class="delete">4.2.2</span><span class="insert">5.3.2</span> </span>Attribution</h4>
<div class="glossary-ref"> <dfn id="concept-attribution">Attribution</dfn> is the ascribing of an entity to an agent. </div>
@@ -2975,7 +3125,7 @@
</ul>
</div>
-<div class="anexample" id="anexample-attribution" count="30">
+<div class="anexample" id="anexample-attribution" data-count="34"><div class="anexampleTitle"><span class="insert">Example 34</span></div>
<p>
Revisiting the example of <a href="#section-example-one">Section <span class="delete">3.1</span><span class="insert">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 href="#term-attribute-role">Section <span class="delete">4.7.4.3</span><span class="insert">5.7.4.3</span></a>) allows for role of the agent in the attribution to be specified.
@@ -2991,7 +3141,7 @@
<div id="term-ActivityAssociation" class="section">
-<h4><span class="secno"><span class="delete">4.2.3</span><span class="insert">5.2.3</span> </span>Association</h4>
+<h4><span class="secno"><span class="delete">4.2.3</span><span class="insert">5.3.3</span> </span>Association</h4>
<div class="glossary-ref"> An activity <dfn id="concept-activityAssociation">association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
@@ -3013,7 +3163,7 @@
<p><span class="insert">While each of </span><a href="#association.id"><span class="attribute"><span class="insert">id</span></span></a><span class="insert">, </span><a href="#association.agent"><span class="attribute"><span class="insert">agent</span></span></a><span class="insert">, </span><a href="#association.plan"><span class="attribute"><span class="insert">plan</span></span></a><span class="insert">, and </span><a href="#association.attributes"><span class="attribute"><span class="insert">attributes</span></span></a><span class="insert"> is </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert">, at least one of them </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be present.</span></p>
-<div class="anexample" id="anexample-wasAssociatedWith" count="31">
+<div class="anexample" id="anexample-wasAssociatedWith" data-count="35"><div class="anexampleTitle"><span class="insert">Example 35</span></div>
<p>In the following example, a designer <span class="insert">agent </span>and an operator <span class="delete">agents</span><span class="insert">agent</span> are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an an entity of type <span class="name"><a href="#concept-plan" class="internalDFN">plan</a></span>. </p>
<pre class="codeexample">activity(ex:a, <span class="delete">[prov:type="workflow execution"])</span><span class="insert">[ prov:type="workflow execution" ])</span>
agent(ex:ag1,<span class="delete"> [prov:type="operator"])</span><span class="insert"> [ prov:type="operator" ])</span>
@@ -3029,7 +3179,7 @@
for instance.
</div>
-<div class="anexample" id="anexample-wasAssociatedWith-2" count="32">
+<div class="anexample" id="anexample-wasAssociatedWith-2" data-count="36"><div class="anexampleTitle"><span class="insert">Example 36</span></div>
<p>In some cases, one wants to indicate a plan was followed, without having to specify which agent was involved.</p>
<pre class="codeexample"><span class="delete">activity(ex:a,[prov:type="workflow execution"])
wasAssociatedWith(ex:a,-,ex:wf)
@@ -3050,7 +3200,7 @@
<div id="term-delegation" class="section">
-<h4><span class="secno"><span class="delete">4.2.4 </span><span class="delete">Responsibility</span><span class="insert">5.2.4 </span></span><span class="insert">Delegation</span></h4>
+<h4><span class="secno"><span class="delete">4.2.4 </span><span class="delete">Responsibility</span><span class="insert">5.3.4 </span></span><span class="insert">Delegation</span></h4>
<div class="glossary-ref"> <span class="delete">Responsibility</span> <dfn id="concept-delegation"><span class="insert">Delegation</span></dfn> is the <span class="delete">fact</span><span class="insert">assignment of authority to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent</span> that <span class="delete">an agent is accountable</span><span class="insert">it represents remains responsible</span> for the <span class="delete">actions of a "subordinate" agent, in the context of an activity. </span><span class="insert">outcome of the delegated work. </span></div>
@@ -3080,7 +3230,7 @@
</ul></div>
-<div class="anexample" count="33">
+<div class="anexample" data-count="37"><div class="anexampleTitle"><span class="insert">Example 37</span></div>
<p>The following fragment describes three agents: a programmer, a researcher, and a funder. The programmer and researcher are associated with a workflow activity. The programmer acts on behalf
of the researcher <span class="delete">(delegation)</span><span class="insert">(line-management)</span> encoding the commands specified by the researcher; the researcher acts on behalf of the funder, who has a contractual agreement with the researcher. The terms
<span class="delete">'delegation'</span><span class="insert">'line-management'</span> and <span class="delete">'contact'</span><span class="insert">'contract'</span> used in this example are domain specific.</p>
@@ -3102,7 +3252,7 @@
actedOnBehalfOf(ag1, ag2, a, [ prov:type="line-management" ])
actedOnBehalfOf(ag2, ag3, a, [ prov:type="contract" ])</span>
</pre>
-</div>
+
@@ -3112,91 +3262,84 @@
</div>
-<div id="component3" class="section">
-<h3><span class="secno"><span class="delete">4.3</span><span class="insert">5.3</span> </span>Component 3: Derivations</h3>
-
-
-
-<p>The third component of PROV-DM is concerned <span class="delete">with</span><span class="insert">with:</span> <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, and</span><span class="insert">others;</span> derivation subtypes <a href="#concept-revision" class="internalDFN">Revision</a>, <a href="#concept-quotation" class="internalDFN">Quotation</a>, <span class="insert">and </span><a href="#concept-original-source" class="internalDFN">Original Source</a><span class="delete">, and</span><span class="insert">; derivation-related</span> <a href="#concept-trace" class="internalDFN">Trace</a>.
- <a href="#figure-component3">Figure <span class="delete">figure-component3</span><span class="insert">7</span></a> depicts the third component
-with <span class="delete">three </span><span class="insert">PROV core structures in the yellow area, including two </span>classes<span class="delete"> (Entity, Activity,</span><span class="insert">
-(</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> and <span class="delete">Agent) and associations between them.</span><span class="insert">binary association
-(</span><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a><span class="insert">). PROV extended structures are found outside this
-area.</span> UML association classes express<span class="insert"> expanded</span> n-ary relations.
-</p>
-
-
-<div style="text-align: center;">
-
-<figure>
-
-<img src="uml/component3.png" alt="derivation">
-<div class="figcaption" id="figure-component3">Figure 7: Derivation Component Overview</div>
-</figure>
-</div>
-
-<div id="term-derivation" class="section">
-<h4><span class="secno"><span class="delete">4.3.1</span><span class="insert">5.3.1</span> </span>Derivation</h4>
-
-
-
-
-
-<div class="glossary-ref"> A <dfn id="concept-derivation">derivation</dfn> is a transformation of an entity into another, <span class="delete">a</span><span class="insert">an update of an entity, resulting in a new one, or based on an entity, the</span> construction of <span class="delete">an entity into another, or an update of an entity, resulting in a new one.</span><span class="insert">another.</span></div>
-
-
-
-
-<p>According to <a href="#section-prov-overview">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
+<span class="delete">4.3 </span><span class="delete">Component 3: Derivations</span>
+
+
+
+<span class="delete">The third component of PROV-DM is concerned with </span><span class="delete">derivations</span><span class="delete"> of </span><span class="delete">entities</span><span class="delete"> from others, and derivation subtypes </span><span class="delete">Revision</span><span class="delete">, </span><span class="delete">Quotation</span><span class="delete">, </span><span class="delete">Original Source</span><span class="delete">, and </span><span class="delete">Trace</span><span class="delete">.
+Figure </span><span class="delete">figure-component3</span><span class="delete"> depicts the third component with three classes (Entity, Activity, and Agent) and associations between them. UML association classes express n-ary relations.
+</span>
+
+
+
+
+
+<span class="delete">Figure 7: Derivation Component Overview</span>
+
+
+
+<div id="term-trace" class="section">
+<h4><span class="secno"><span class="delete">4.3.1 </span><span class="delete">Derivation</span>
+
+
+
+
+
+<span class="delete"> A </span><span class="delete">derivation</span><span class="delete"> is a transformation of an entity into another, a construction of an entity into another, or an update of an entity, resulting in a new one.</span>
+
+
+
+
+<span class="delete">According to </span><span class="delete">Section 2</span><span class="delete">, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
underpinning activities performing the necessary actions resulting in such a derivation.
-A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be <span class="delete">provided.</span><span class="insert">provided, so as to make the derivation path, through usage, activity, and generation, explicit.</span> Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
-
-
-<p></p><div class="attributes" id="attributes-derivation">A <dfn title="wasDerivedFrom" id="dfn-wasderivedfrom">derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom"><span class="delete">wasDerivedFrom(id,</span><span class="insert">wasDerivedFrom(id;</span> e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:
-<ul>
-<li><span class="attribute" id="derivation.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for a derivation;</li>
-<li><span class="attribute" id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name"><span class="delete">ee</span><span class="insert">e2</span></span>) of the entity generated by the derivation;</li>
-<li><span class="attribute" id="derivation.usedEntity">usedEntity</span>: the identifier (<span class="name">e1</span>) of the entity used by the derivation;</li>
-<li><span class="attribute" id="derivation.activity">activity</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">a</span>) for the activity using and generating the above entities;</li>
-<li><span class="attribute" id="derivation.generation">generation</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">g2</span>) for the generation involving the generated entity<span class="insert"> (</span><span class="name"><span class="insert">e2</span></span><span class="insert">)</span> and activity;</li>
-<li><span class="attribute" id="derivation.usage">usage</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">u1</span>) for the usage involving the used entity <span class="insert">(</span><span class="name"><span class="insert">e1</span></span><span class="insert">) </span>and activity;</li>
-<li><span class="attribute" id="derivation.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 derivation.</li>
-</ul>
-</div>
-
-
-
-<div class="anexample" count="34">
-<p>The following descriptions are about derivations between <span class="name">e2</span> and <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
-<pre class="codeexample">wasDerivedFrom(e2, e1)
+A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </span>
+
+
+<span class="delete">A </span><span class="delete">derivation</span><span class="delete">, written </span><span class="delete">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span><span class="delete"> in PROV-N,</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 for a derivation;</span>
+<span class="delete">generatedEntity</span><span class="delete">: the identifier (</span><span class="delete">ee</span><span class="delete">) of the entity generated by the derivation;</span>
+<span class="delete">usedEntity</span><span class="delete">: the identifier (</span><span class="delete">e1</span><span class="delete">) of the entity used by the derivation;</span>
+<span class="delete">activity</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> identifier (</span><span class="delete">a</span><span class="delete">) for the activity using and generating the above entities;</span>
+<span class="delete">generation</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> identifier (</span><span class="delete">g2</span><span class="delete">) for the generation involving the generated entity and activity;</span>
+<span class="delete">usage</span><span class="delete">: an </span><span class="delete">optional</span><span class="delete"> identifier (</span><span class="delete">u1</span><span class="delete">) for the usage involving the used entity and activity;</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 derivation.</span>
+
+
+
+
+
+
+<span class="delete">The following descriptions are about derivations between </span><span class="delete">e2</span><span class="delete"> and </span><span class="delete">e1</span><span class="delete">, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</span>
+<span class="delete">wasDerivedFrom(e2, e1)
wasDerivedFrom(e2, e1, [prov:type="physical transform"])
-</pre>
-<p>The following description expresses that activity <span class="name">a</span>,
-using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,
+</span>
+<span class="delete">The following description expresses that activity </span><span class="delete">a</span><span class="delete">,
+using the entity </span><span class="delete">e1</span><span class="delete"> according to usage </span><span class="delete">u1</span><span class="delete">,
derived the
-entity <span class="name">e2</span> and generated it according to generation
- <span class="name">g2</span>. It is followed by descriptions for generation <span class="name">g2</span> and usage <span class="name">u1</span>.</p>
-<pre class="codeexample">wasDerivedFrom(e2, e1, a, g2, u1)
-<span class="delete">wasGeneratedBy(g2,</span><span class="insert">wasGeneratedBy(g2;</span> e2, a, -)
-<span class="delete">used(u1,</span><span class="insert">used(u1;</span> a, e1, -)
-</pre>
-<p>With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity <span class="name">e1</span> was used by the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity <span class="name">e2</span> was obtained from (say, for a function returning multiple results).</p>
-</div>
-
-
-
-
-</div>
-
-<div id="term-revision" class="section">
-<h4><span class="secno"><span class="delete">4.3.2</span><span class="insert">5.3.2</span> </span>Revision</h4>
-
-<p><span class="glossary-ref"> A <dfn id="concept-revision">revision</dfn> is a derivation that revises an entity into a revised version. </span></p>
-
-<p><span class="delete"> Deciding whether something is made available as a revision of something else usually involves an agent who takes responsibility for approving that the former is a due variant of the latter.
+entity </span><span class="delete">e2</span><span class="delete"> and generated it according to generation
+ </span><span class="delete">g2</span><span class="delete">. It is followed by descriptions for generation </span><span class="delete">g2</span><span class="delete"> and usage </span><span class="delete">u1</span><span class="delete">.</span>
+<span class="delete">wasDerivedFrom(e2, e1, a, g2, u1)
+wasGeneratedBy(g2, e2, a, -)
+used(u1, a, e1, -)
+</span>
+<span class="delete">With such a comprehensive description of derivation, a program that analyzes provenance can identify the activity underpinning the derivation, it can identify how the original entity </span><span class="delete">e1</span><span class="delete"> was used by the activity (e.g. for instance, which argument it was passed as, if the activity is the result of a function invocation), and which output the derived entity </span><span class="delete">e2</span><span class="delete"> was obtained from (say, for a function returning multiple results).</span>
+
+
+
+
+
+
+
+
+<span class="delete">4.3.2 </span><span class="delete">Revision</span>
+
+<span class="delete"> A </span><span class="delete">revision</span><span class="delete"> is a derivation that revises an entity into a revised version. </span>
+
+<span class="delete"> Deciding whether something is made available as a revision of something else usually involves an agent who takes responsibility for approving that the former is a due variant of the latter.
The agent who is responsible for the revision may optionally be specified.
- </span>Revision is a particular case of <a href="#concept-derivation" class="internalDFN">derivation</a> of an entity into its revised version.</p>
+ Revision is a particular case of </span><span class="delete">derivation</span><span class="delete"> of an entity into its revised version.</span>
<span class="delete"> A </span><span class="delete">revision</span><span class="delete"> relation</span><span class="delete">, written </span><span class="delete">wasRevisionOf(id,e2,e1,ag,attrs)</span><span class="delete"> in PROV-N,</span><span class="delete"> has:</span>
@@ -3210,37 +3353,32 @@
-
-
-
-
-<div class="anexample" id="anexample-revision" count="35">
-<p>
-Revisiting the example of <a href="#section-example-two">Section <span class="delete">3.2</span><span class="insert">4.2</span></a>,
+<span class="delete">
+Revisiting the example of </span><span class="delete">Section 3.2</span><span class="delete">,
we can now state that the report
- <span class="name">tr:WD-prov-dm-20111215</span> <span class="delete">is</span><span class="insert">was</span> a revision of
- the report <span class="name">tr:WD-prov-dm-20111018<span class="delete">, approved by
-agent </span><span class="delete">w3:Consortium</span></span>.
-</p><pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ <span class="delete">prov:type="process:RecsWD" %% xsd:QName </span><span class="insert">prov:type='rec54:WD' </span>])
-entity(tr:WD-prov-dm-20111018, [ <span class="delete">prov:type="process:RecsWD" %% xsd:QName </span><span class="insert">prov:type='rec54:WD' </span>])
-<span class="delete">wasRevisionOf(tr:WD-prov-dm-20111215,</span><span class="insert">wasDerivedFrom(tr:WD-prov-dm-20111215,</span> tr:WD-prov-dm-20111018, <span class="delete">w3:Consortium)</span><span class="insert">[ prov:type='prov:WasRevisionOf' ])</span>
-</pre>
-</div>
-
-
-
-</div>
-
-<div id="term-quotation" class="section">
-<h4><span class="secno"><span class="delete">4.3.3</span><span class="insert">5.3.3</span> </span>Quotation</h4>
-
-<p>
-<span class="glossary-ref"> A <dfn id="concept-quotation">quotation</dfn> is the repeat of (some or all of) an entity, such as text or image, by someone <span class="delete">other than</span><span class="insert">who may or may not be</span> its original author. </span>
-</p>
-
-<p>Quotation
- is a particular case of <a href="#concept-derivation" class="internalDFN">derivation</a> in which <span class="insert">an </span>entity <span class="delete">e2</span> is derived from an original entity <span class="delete">e1</span> by copying, or "quoting", some or all of it.<span class="delete">
- A </span><span class="delete">quotation</span><span class="delete"> relation</span><span class="delete">, written </span><span class="delete">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span><span class="delete"> in PROV-N,</span><span class="delete"> has:</span></p>
+ </span><span class="delete">tr:WD-prov-dm-20111215</span><span class="delete"> is a revision of
+ the report </span><span class="delete">tr:WD-prov-dm-20111018</span><span class="delete">, approved by
+agent </span><span class="delete">w3:Consortium</span><span class="delete">.
+</span><span class="delete">entity(tr:WD-prov-dm-20111215, [ prov:type="process:RecsWD" %% xsd:QName ])
+entity(tr:WD-prov-dm-20111018, [ prov:type="process:RecsWD" %% xsd:QName ])
+wasRevisionOf(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018, w3:Consortium)
+</span>
+
+
+
+
+
+
+
+<span class="delete">4.3.3 </span><span class="delete">Quotation</span>
+
+
+<span class="delete"> A </span><span class="delete">quotation</span><span class="delete"> is the repeat of (some or all of) an entity, such as text or image, by someone other than its original author. </span>
+
+
+<span class="delete">Quotation
+ is a particular case of </span><span class="delete">derivation</span><span class="delete"> in which entity </span><span class="delete">e2</span><span class="delete"> is derived from an original entity </span><span class="delete">e1</span><span class="delete"> by copying, or "quoting", some or all of it.
+ A </span><span class="delete">quotation</span><span class="delete"> relation</span><span class="delete">, written </span><span class="delete">wasQuotedFrom(id,e2,e1,ag2,ag1,attrs)</span><span class="delete"> in PROV-N,</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 for the relation;</span>
<span class="delete">quote</span><span class="delete">: an identifier (</span><span class="delete">e2</span><span class="delete">) for the entity that represents the quote (the partial copy);
@@ -3252,52 +3390,41 @@
-
-
-
-
-<div class="anexample" id="anexample-quotation" count="36">
-<p>
-The following paragraph is a quote from one of <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/">the author's blogs</a>.
-</p><blockquote id="bl-dagstuhl"><em>
-"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."</em>
-</blockquote>
-<p>If <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="name">wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/</span></a> denotes the original blog by agent <span class="name">ex:Paul</span>, and
- <a href="#bl-dagstuhl"><span class="name">dm:bl-dagstuhl</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph <span class="delete">is</span><span class="insert">was</span> copied by agent <span class="name">ex:Luc</span> from a part of the blog, attributed to the agent <span class="name">ex:Paul</span>.</p>
-<pre class="codeexample">entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/)
-<span class="insert">entity(dm:bl-dagstuhl)
-</span>agent(ex:Luc)
+<span class="delete">
+The following paragraph is a quote from one of </span><span class="delete">the author's blogs</span><span class="delete">.
+</span><span class="delete">
+"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax. This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."</span>
+
+<span class="delete">If </span><span class="delete">wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/</span><span class="delete"> denotes the original blog by agent </span><span class="delete">ex:Paul</span><span class="delete">, and
+ </span><span class="delete">dm:bl-dagstuhl</span><span class="delete"> denotes the above paragraph, then the following descriptions express that the above paragraph is copied by agent </span><span class="delete">ex:Luc</span><span class="delete"> from a part of the blog, attributed to the agent </span><span class="delete">ex:Paul</span><span class="delete">.</span>
+<span class="delete">entity(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/)
+agent(ex:Luc)
agent(ex:Paul)
-<span class="delete">wasQuotedFrom(dm:bl-dagstuhl,wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/,ex:Luc,ex:Paul)</span><span class="insert">wasDerivedFrom(dm:bl-dagstuhl,
- wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/,
- [ prov:type='prov:WasQuotedFrom' ])
-wasAttributedTo(dm:bl-dagstuhl, ex:Luc)
-wasAttributedTo(wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/, ex:Paul)</span>
-</pre>
-
-</div>
-
-
-</div>
-
-
-<div id="term-original-source" class="section">
-<h4><span class="secno"><span class="delete">4.3.4</span><span class="insert">5.3.4</span> </span>Original Source</h4>
-
-<p>
-<span class="glossary-ref"> An <dfn id="concept-original-source">original source</dfn> refers to the source material that is closest to the person, information, period, or idea being studied. </span>
-</p>
-
-<p>An <dfn id="dfn-original-source">original source</dfn> relation is a particular case of <a href="#concept-derivation" class="internalDFN">derivation</a>
+wasQuotedFrom(dm:bl-dagstuhl,wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/,ex:Luc,ex:Paul)
+</span>
+
+
+
+
+
+
+
+
+<span class="delete">4.3.4 </span><span class="delete">Original Source</span>
+
+
+<span class="delete"> An </span><span class="delete">original source</span><span class="delete"> refers to the source material that is closest to the person, information, period, or idea being studied. </span>
+
+
+<span class="delete">An </span><span class="delete">original source</span><span class="delete"> relation is a particular case of </span><span class="delete">derivation</span><span class="delete">
that aims to give
credit to the source that originated some information. It is recognized that it may be
hard to determine which entity constitutes an original source. This definition is inspired by
-<span class="name">original-source</span> as defined in
-<a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html">http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html</a>.</p>
-
-
-<div class="anexample" count="37">
-<p><span class="delete"> An </span><span class="delete">original source</span><span class="delete"> relation</span><span class="delete">, written </span><span class="delete">hadOriginalSource(id,e2,e1,attrs)</span><span class="delete">,</span><span class="delete"> has:</span>
+</span><span class="delete">original-source</span><span class="delete"> as defined in
+</span><span class="delete">http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html</span><span class="delete">.</span>
+
+
+<span class="delete"> An </span><span class="delete">original source</span><span class="delete"> relation</span><span class="delete">, written </span><span class="delete">hadOriginalSource(id,e2,e1,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 for the relation;</span>
<span class="delete">derived</span><span class="delete">: an identifier (</span><span class="delete">e2</span><span class="delete">) for the derived entity; </span>
@@ -3306,21 +3433,20 @@
-
-Let us consider the concept introduced in the current section, identified as <a title="original source" href="#concept-original-source" class="internalDFN"><span class="name">dm:concept-original-source</span></a>, and
-the Google page <a href="http://googlenewsblog.blogspot.com/2010/11/credit-where-credit-is-due.html"><span class="name">go:credit-where-credit-is-due.html</span></a>, where the notion original-source was originally described (to the knowledge of the authors).
-</p><pre class="codeexample">entity(dm:concept-original-source)
+<span class="delete">
+Let us consider the concept introduced in the current section, identified as </span><span class="delete">dm:concept-original-source</span><span class="delete">, and
+the Google page </span><span class="delete">go:credit-where-credit-is-due.html</span><span class="delete">, where the notion original-source was originally described (to the knowledge of the authors).
+</span><span class="delete">entity(dm:concept-original-source)
entity(go:credit-where-credit-is-due.html)
-<span class="delete">hadOriginalSource(dm:concept-original-source,go:credit-where-credit-is-due.html)</span><span class="insert">wasDerivedFrom(dm:concept-original-source, go:credit-where-credit-is-due.html,
- [ prov:type='prov:HadOriginalSource' ])</span>
-</pre>
-</div>
-
-
-</div>
-
-<div id="term-trace" class="section">
-<h4><span class="secno"><span class="delete">4.3.5</span><span class="insert">5.3.5</span> </span>Trace</h4>
+hadOriginalSource(dm:concept-original-source,go:credit-where-credit-is-due.html)
+</span>
+
+
+
+
+
+
+<span class="delete">4.3.5</span><span class="insert">5.3.5</span> </span>Trace</h4>
<p>
<span class="glossary-ref"> <dfn id="concept-trace">Trace</dfn> is the ability to link back an entity to another by means of derivation or responsibility relations, possibly repeatedly traversed. </span>
@@ -3345,7 +3471,7 @@
<a href="#concept-derivation" class="internalDFN">Derivation</a> and <a href="#concept-attribution" class="internalDFN">attribution</a> are particular cases of trace.
</p>
-<div class="anexample" count="38">
+<div class="anexample" data-count="38"><div class="anexampleTitle"><span class="insert">Example 38</span></div>
<p>We refer to the example of <a href="#section-example-two">Section <span class="delete">3.1</span><span class="insert">4.2</span></a>, and specifically to <a href="#prov-a-document2-top">Figure 3</a>. We can see that there is a path from
<span class="name">tr:WD-prov-dm-20111215</span> to
<span class="name">w3:Consortium</span> and to
@@ -3360,6 +3486,9 @@
</div>
+
+
+
</div>
<div id="component4" class="section">
@@ -3387,7 +3516,7 @@
<p><span class="delete">Wherever two people describe the</span><span class="insert">Two</span> provenance <span class="delete">of a</span><span class="insert">descriptions about the</span> same <span class="delete">thing,
one cannot expect them to coordinate and agree on the identifiers to use to denote</span><span class="insert">thing may emphasize differents aspects of</span> that thing.</p>
-<div class="anexample" id="entity-example1" count="39">
+<div class="anexample" id="entity-example1" data-count="39"><div class="anexampleTitle"><span class="insert">Example 39</span></div>
<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific <span class="delete">URI,</span><span class="insert">IRI,</span> 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>
@@ -3419,7 +3548,7 @@
</ul>
</div>
-<div class="anexample" id="anexample-specialization" count="40">
+<div class="anexample" id="anexample-specialization" data-count="40"><div class="anexampleTitle"><span class="insert">Example 40</span></div>
<p>
The BBC news home page on 2012-03-23 <span class="name">ex:bbcNews2012-03-23</span>
is a specialization of the BBC news page in general
@@ -3455,7 +3584,7 @@
</ul>
</div>
-<div class="anexample" id="anexample-alternate" count="41">
+<div class="anexample" id="anexample-alternate" data-count="41"><div class="anexampleTitle"><span class="insert">Example 41</span></div>
<p>
A given news item on the BBC News site
<a href="http://www.bbc.co.uk/news/science-environment-17526723">bbc:news/science-environment-17526723</a> for desktop
@@ -3469,7 +3598,7 @@
</div>
-<div class="anexample" id="anexample-alternate2" count="42">
+<div class="anexample" id="anexample-alternate2" data-count="42"><div class="anexampleTitle"><span class="insert">Example 42</span></div>
<p>
Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternate of each other.
</p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
@@ -3558,7 +3687,7 @@
and
</span><a href="#anexample-provenance-aggregation" class="anexample-ref"><span><span class="insert">Example 44</span></span></a><span class="insert">.</span></p>
-<div class="anexample" id="anexample-provenance-of-provenance" count="43">
+<div class="anexample" id="anexample-provenance-of-provenance" data-count="43"><div class="anexampleTitle"><span class="insert">Example 43</span></div>
<p><span class="insert">Let us consider two entities </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert"> and </span><span class="name"><span class="insert">ex:report2</span></span><span class="insert">.</span></p>
<pre class="codeexample"><span class="insert">
entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -3605,7 +3734,7 @@
</span></pre>
</div>
-<div class="anexample" id="anexample-provenance-aggregation" count="44">
+<div class="anexample" id="anexample-provenance-aggregation" data-count="44"><div class="anexampleTitle"><span class="insert">Example 44</span></div>
<p><span class="insert">A provenance aggregator could merge two bundles, resulting in a novel bundle, whose provenance is described as follows.</span></p>
<pre class="codeexample"><span class="insert">
bundle agg:bundle3
@@ -3663,7 +3792,7 @@
<p><span class="insert">When the subject and optional target denote entities,
a provenance locator not only provides a </span><em><span class="insert">located context</span></em><span class="insert">, but it also expresses an </span><a href="#concept-alternate" class="internalDFN"><span class="insert">alternate</span></a><span class="insert"> relation between the entity denoted by </span><span class="name"><span class="insert">subject</span></span><span class="insert"> and the entity described in the located context. This is an alternate since the entity denoted by </span><span class="name"><span class="insert">subject</span></span><span class="insert"> in the current context presents other aspects than the entity in the located one.</span></p>
-<div class="anexample" id="anexample-provenance-locator" count="45">
+<div class="anexample" id="anexample-provenance-locator" data-count="45"><div class="anexampleTitle"><span class="insert">Example 45</span></div>
<p><span class="insert">According to the following provenance locator, provenance descriptions about </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert"> can be found in bundle </span><span class="name"><span class="insert">bob:bundle1</span></span><span class="insert">.</span></p>
<pre class="codeexample"><span class="insert">
hasProvenanceIn(ex:report1, bob:bundle1, -)
@@ -3675,7 +3804,7 @@
</div>
-<div class="anexample" id="anexample-provenance-locator2" count="46">
+<div class="anexample" id="anexample-provenance-locator2" data-count="46"><div class="anexampleTitle"><span class="insert">Example 46</span></div>
<p><span class="insert">Let us again consider the same scenario involving two entities </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert"> and </span><span class="name"><span class="insert">ex:report2</span></span><span class="insert">.</span></p>
<p><span class="insert">The first bundle can be expressed with all Bob's observations about the creation of </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert">.
</span></p>
@@ -3703,7 +3832,7 @@
</div>
-<div class="anexample" id="anexample-provenance-locator3" count="47">
+<div class="anexample" id="anexample-provenance-locator3" data-count="47"><div class="anexampleTitle"><span class="insert">Example 47</span></div>
<p><span class="insert">Alternatively, Alice may have decided to use a different identifier for </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert">.</span></p>
<pre class="codeexample"><span class="insert">
bundle alice:bundle6
@@ -3719,7 +3848,7 @@
</span><span class="name"><span class="insert">bob:bundle4</span></span><span class="insert"> under the name </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert">. In effect, </span><span class="name"><span class="insert">alice:report1</span></span><span class="insert"> and </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert"> are declared to be alternate.</span></p>
</div>
-<div class="anexample" id="aexample-note" count="48">
+<div class="anexample" id="aexample-note" data-count="48"><div class="anexampleTitle"><span class="insert">Example 48</span></div>
<p><span class="insert">Consider the following bundle of descriptions, in which derivation and generations have been identified.
</span></p><pre class="codeexample"><span class="insert">
bundle obs:bundle7
@@ -3837,7 +3966,7 @@
-<div class="anexample" count="49">
+<div class="anexample" data-count="49"><div class="anexampleTitle"><span class="insert">Example 49</span></div>
<pre class="codeexample">entity(d0, <span class="delete">[prov:type="prov:EmptyDictionary" %% xsd:QName])</span><span class="insert">[prov:type='prov:EmptyDictionary' ])</span> // d0 is an empty dictionary
entity(d1, <span class="delete">[prov:type="prov:Dictionary"</span><span class="insert">[prov:type='prov:Dictionary'</span> <span class="delete">%% xsd:QName])</span><span class="insert">])</span> // d1 is a dictionary, with unknown content
</pre>
@@ -3879,7 +4008,7 @@
-<div class="anexample" count="50">
+<div class="anexample" data-count="50"><div class="anexampleTitle"><span class="insert">Example 50</span></div>
<pre class="codeexample">entity(d0, <span class="delete">[prov:type="prov:EmptyDictionary" %% xsd:QName])</span><span class="insert">[prov:type='prov:EmptyDictionary' ])</span> // d0 is an empty dictionary
entity(e1)
entity(e2)
@@ -3901,7 +4030,7 @@
<p>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.</p>
-<div class="anexample" count="51">
+<div class="anexample" data-count="51"><div class="anexampleTitle"><span class="insert">Example 51</span></div>
<pre class="codeexample">entity(d0, <span class="delete">[prov:type="prov:EmptyDictionary" %% xsd:QName])</span><span class="insert">[prov:type='prov:EmptyDictionary' ])</span> // d0 is an empty dictionary
entity(e1)
entity(e2)
@@ -3946,7 +4075,7 @@
<p>A Removal relation <span class="name"><span class="delete">derivedByRemovalFrom(id,</span><span class="insert">derivedByRemovalFrom(id;</span> d2,d1, {key_1, ..., key_n})</span> states that <span class="name">d2</span> is the state of the dictionary following the removal of the set of pairs corresponding to keys <span class="name">key_1...key_n</span> from <span class="name">d1</span>.
-</p><div class="anexample" count="52">
+</p><div class="anexample" data-count="52"><div class="anexampleTitle"><span class="insert">Example 52</span></div>
<pre class="codeexample">entity(d0, [prov:type="prov:EmptyDictionary"]) // d0 is an empty dictionary
entity(e1)
entity(e2)
@@ -3999,7 +4128,7 @@
<p>The description <span class="name">memberOf(c, {(key_1, e_1), ..., (key_n, e_n)})</span> states that <span class="name">c</span> is known to include <span class="name">(key_1, e_1)</span>, ..., <span class="name">(key_n, e_n)}</span>, without having to introduce a previous state. </p>
-<div class="anexample" count="53">
+<div class="anexample" data-count="53"><div class="anexampleTitle"><span class="insert">Example 53</span></div>
<pre class="codeexample">entity(d1, <span class="delete">[prov:type="prov:Dictionary"</span><span class="insert">[prov:type='prov:Dictionary'</span> <span class="delete">%% xsd:QName])</span><span class="insert">])</span> // d1 is a dictionary, with unknown content
entity(d2, <span class="delete">[prov:type="prov:Dictionary"</span><span class="insert">[prov:type='prov:Dictionary'</span> <span class="delete">%% xsd:QName])</span><span class="insert">])</span> // d2 is a dictionary, with unknown content
@@ -4253,7 +4382,7 @@
<span class="glossary-ref"> The attribute <dfn id="concept-label" title="label"><span class="name">prov:label</span></dfn> provides a human-readable representation of <span class="insert">an instance of </span>a PROV-DM <span class="delete">element</span><span class="insert">type</span> 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" count="54">
+<div class="anexample" data-count="54"><div class="anexampleTitle"><span class="insert">Example 54</span></div>
<p>The following entity is provided with a label attribute.</p>
<pre class="codeexample"> entity(ex:e1, <span class="delete">[prov:label="This</span><span class="insert">[ prov:label="This</span> is a <span class="delete">label"])</span><span class="insert">human-readable label" ])</span>
</pre>
@@ -4276,7 +4405,7 @@
The attribute <span class="name">prov:location</span> is an <em class="rfc2119" title="optional">optional</em> attribute of entity, activity, usage, and generation. 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" count="55">
+<div class="anexample" id="example-location" data-count="55"><div class="anexampleTitle"><span class="insert">Example 55</span></div>
<p>The following expression describes entity Mona Lisa, a painting, with a location attribute. </p>
<pre class="codeexample"> entity(ex:MonaLisa, <span class="delete">[prov:location="Le</span><span class="insert">[ prov:location="Le</span> Louvres, Paris", <span class="delete">prov:type="StillImage"])</span><span class="insert">prov:type="StillImage" ])</span>
</pre>
@@ -4301,7 +4430,7 @@
association, start, and end. </span>
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" count="56">
+<div class="anexample" id="anexample-role" data-count="56"><div class="anexampleTitle"><span class="insert">Example 56</span></div>
<p>The following activity is associated with an agent acting as the operator. </p>
<pre class="codeexample"> wasAssociatedWith(a, ag, <span class="delete">[prov:role="operator"])</span><span class="insert">[ prov:role="operator" ])
</span></pre>
@@ -4322,7 +4451,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" count="57">
+<div class="anexample" data-count="57"><div class="anexampleTitle"><span class="insert">Example 57</span></div>
<p>The following describes an agent of type software agent.</p>
<pre class="codeexample"> agent(ag, <span class="delete">[prov:type="prov:SoftwareAgent" %% xsd:QName])</span><span class="insert">[ prov:type='prov:SoftwareAgent' ])</span>
</pre>
@@ -4341,20 +4470,20 @@
<tr><td><a title="collection" href="#concept-collection" class="internalDFN"><span class="name"><span class="insert">prov:Collection</span></span></a></td><td><a href="#term-collection"><span class="insert">Section 5.6.1</span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a></td></tr>
<tr><td><a title="dictionary" href="#concept-dictionary" class="internalDFN"><span class="name"><span class="insert">prov:Dictionary</span></span></a></td><td><a href="#term-dictionary"><span class="insert">Section 5.6.2</span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a></td></tr>
<tr><td><a title="empty dictionary" href="#concept-empty-dictionary" class="internalDFN"><span class="name"><span class="insert">prov:EmptyDictionary</span></span></a></td><td><a href="#term-dictionary"><span class="insert">Section 5.6.2</span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a></td></tr>
-<tr><td><a title="original source" href="#concept-original-source" class="internalDFN"><span class="name"><span class="insert">prov:HadOriginalSource</span></span></a></td><td><a href="#term-original-source"><span class="insert">Section 5.3.4</span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</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 href="#term-agent"><span class="insert">Section 5.2.1</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 href="#term-agent"><span class="insert">Section 5.2.1</span></a></td><td><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a></td></tr>
+<tr><td><a title="original source" href="#concept-original-source" class="internalDFN"><span class="name"><span class="insert">prov:HadOriginalSource</span></span></a></td><td><a href="#term-original-source"><span class="insert">Section 5.2.4</span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</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 href="#term-agent"><span class="insert">Section 5.3.1</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 href="#term-agent"><span class="insert">Section 5.3.1</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">prov:Plan</span>
<span class="delete">prov:Account</span>
-</a></td> <td><a href="#term-entity"><span class="insert">Section 5.2.3</span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a></td></tr>
+</a></td> <td><a href="#term-entity"><span class="insert">Section 5.3.3</span></a></td><td><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></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 href="#term-agent"><span class="insert">Section 5.2.1</span></a></td><td><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a></td></tr>
+</a></td><td><a href="#term-agent"><span class="insert">Section 5.3.1</span></a></td><td><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></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:WasQuotedFrom</span></span></a></td><td><a href="#term-quotation"><span class="insert">Section 5.3.3</span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td></tr>
+<span class="insert">prov:WasQuotedFrom</span></span></a></td><td><a href="#term-quotation"><span class="insert">Section 5.2.3</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="delete">prov:Person</span>
<span class="delete">prov:Collection</span>
@@ -4363,7 +4492,7 @@
<span class="delete">prov:EmptyDictionary</span>
-<span class="insert">prov:WasRevisionOf</span></span></a></td><td><a href="#term-revision"><span class="insert">Section 5.3.2</span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td></tr>
+<span class="insert">prov:WasRevisionOf</span></span></a></td><td><a href="#term-revision"><span class="insert">Section 5.2.2</span></a></td><td><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a></td></tr>
</tbody></table>
</div>
@@ -4378,7 +4507,7 @@
<p><span class="insert">The attribute </span><span class="name"><span class="insert">prov:value</span></span><span class="insert"> is an </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert"> attribute of entity. The value </span>associated with <span class="insert">the attribute </span><span class="name"><span class="insert">prov:value</span></span> <em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be a PROV-DM </span><a title="value" href="#concept-value" class="internalDFN"><span class="insert">Value</span></a><span class="insert">. The attribute </span><span class="name"><span class="insert">prov:value</span></span> <em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> occur at most once in a set of attribute-value pairs.</span></p>
-<div class="anexample" count="58">
+<div class="anexample" data-count="58"><div class="anexampleTitle"><span class="insert">Example 58</span></div>
<p><span class="insert">The following example illustrates the provenance of the number </span><span class="name"><span class="insert">4</span></span><span class="insert"> obtained by </span>an <span class="delete">entity.</span><span class="insert">activity that computed the length of an input string </span><span class="name"><span class="insert">"abcd"</span></span><span class="insert">.
The input and the output are expressed as entities </span><span class="name"><span class="insert">ex:in</span></span><span class="insert"> and </span><span class="name"><span class="insert">ex:out</span></span><span class="insert">, respectively. They each have a </span><span class="name"><span class="insert">prov:value</span></span><span class="insert"> attribute associated with the corresponding value.
</span></p>
@@ -4409,7 +4538,7 @@
</span><a href="#term-attribute-provenance-uri"><span class="name"><span class="insert">prov:provenance-uri</span></span></a><span class="insert"> are mutually exclusive.</span></p>
-<div class="anexample" id="anexample-provenance-uri" count="59">
+<div class="anexample" id="anexample-provenance-uri" data-count="59"><div class="anexampleTitle"><span class="insert">Example 59</span></div>
<p><span class="insert">According to the following provenance locator, provenance descriptions about </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert"> can be found in bundle </span><span class="name"><span class="insert">bob:bundle1</span></span><span class="insert">, which is available from the provenance service identified by the provided URI.</span></p>
<pre class="codeexample"><span class="insert">
hasProvenanceIn(ex:report1, bob:bundle1, -, [ prov:provenance-uri="http://example.com/service" %% xsd:anyURI ])
@@ -4441,7 +4570,7 @@
</span><a href="#term-attribute-provenance-uri"><span class="name"><span class="insert">prov:provenance-uri</span></span></a><span class="insert"> are mutually exclusive.</span></p>
-<div class="anexample" id="anexample-service-uri" count="60">
+<div class="anexample" id="anexample-service-uri" data-count="60"><div class="anexampleTitle"><span class="insert">Example 60</span></div>
<p><span class="insert">According to the </span>following <span class="delete">example illustrates the </span>provenance <span class="delete">of the number</span><span class="insert">locator, provenance descriptions about</span> <span class="name"><span class="delete">4</span><span class="delete"> obtained</span><span class="insert">ex:report1</span></span><span class="insert"> can be found in the resource identified</span> by <span class="delete">an activity that computed the length of an input string </span><span class="delete">"abcd"</span><span class="delete">.
The input and the output are expressed as entities </span><span class="delete">ex:in</span><span class="delete"> and </span><span class="delete">ex:out</span><span class="delete">, respectively. They each have a </span><span class="delete">prov:value</span><span class="delete"> attribute associated with the corresponding value.
</span><span class="insert">the provided URI.</span></p>
@@ -4514,7 +4643,7 @@
-<div class="anexample" id="anexample-value" count="61">
+<div class="anexample" id="anexample-value" data-count="61"><div class="anexampleTitle"><span class="insert">Example 61</span></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"
@@ -4531,7 +4660,7 @@
-<div class="anexample" id="anexample-time" count="62">
+<div class="anexample" id="anexample-time" data-count="62"><div class="anexampleTitle"><span class="insert">Example 62</span></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/xmlschema-2/#dateTime">xsd:dateTime</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a></cite>].</p>
@@ -4568,7 +4697,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" count="63">
+<div class="anexample" id="anexample-sub-relation" data-count="63"><div class="anexampleTitle"><span class="insert">Example 63</span></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.
@@ -4577,7 +4706,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-sub-type" count="64">
+<div class="anexample" id="anexample-sub-type" data-count="64"><div class="anexampleTitle"><span class="insert">Example 64</span></div>
<p>
In the following example, <span class="name">e</span> is described as a Car, a type of entity.
</p><pre class="codeexample">