--- a/model/diff.html Tue Apr 17 15:02:41 2012 +0100
+++ b/model/diff.html Tue Apr 17 16:14:16 2012 +0100
@@ -1,4 +1,3 @@
-
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head><style type="text/css"><!--
@@ -571,7 +570,7 @@
<h4 id="fourth-public-working-draft">Fourth Public Working Draft</h4>
<p>This 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 <span class="delete">model,</span><span class="insert">model</span> from its <span class="delete">contraints,</span><span class="insert">contraints</span> and the notation used to illustrate it. The PROV-DM release is synchronized with the release of the PROV-O, PROV-PRIMER, PROV-N, <span class="insert">and </span>PROV-DM-CONSTRAINTS documents. We are now <span class="delete">making clear what</span><span class="insert">clarifying</span> the entry path to the PROV family of <span class="delete">specifications is.</span><span class="insert">specifications.</span></p>
<p>This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-wg@w3.org">public-prov-wg@w3.org</a> (<a href="mailto:public-prov-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-wg/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction<br>
-</a><ul class="toc"><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.1 </span>Structure of this Document</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span><span class="delete">PROV Namespace</span><span class="delete">1.3 </span><span class="insert">Notational </span>Conventions</a></li></ul></li><li class="tocline"><a href="#starting-points" class="tocxref"><span class="secno">2. </span><span class="delete">PROV-DM</span><span class="insert">PROV</span> Starting Points</a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno">2.1 </span>Entity and Activity</a></li><li class="tocline"><a href="#section-generation-usage-derivation" class="tocxref"><span class="secno">2.2 </span>Generation, Usage, Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-responsibility" class="tocxref"><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Agents, Attribution, Association, and Responsibility</span></a></li><li class="tocline"><a href="#section-types-entities-agents" class="tocxref"><span class="secno"><span class="delete">2.3 </span><span class="delete">Agents</span><span class="insert">2.4 </span></span><span class="insert">Further Entities: Collections</span> and <span class="delete">Other Types of Entities</span><span class="delete">2.4 </span><span class="delete">Attribution, Association, and Responsibility</span><span class="insert">Accounts</span></a></li><li class="tocline"><a href="#section-UML" class="tocxref"><span class="secno">2.5 </span>Simplified Overview Diagram</a></li><li class="tocline"><a href="#prov-n" class="tocxref"><span class="secno">2.6 </span>PROV-N: The Provenance Notation</a></li></ul></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno">3. </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">3.1 </span>The <span class="delete">Process</span><span class="insert">Authors</span> View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno">3.2 </span>The <span class="delete">Authors</span><span class="insert">Process</span> View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno">3.3 </span>Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno">4. </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">4.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">4.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">4.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">4.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">4.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">4.1.5 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">4.1.6 </span>End</a></li><li class="tocline"><a href="#term-wasInformedBy" class="tocxref"><span class="secno">4.1.7 </span>Communication</a></li><li class="tocline"><a href="#term-wasStartedByActivity" class="tocxref"><span class="secno">4.1.8 </span>Start by Activity</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">4.2 </span>Component 2: Agents and Responsibility</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">4.2.1 </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno">4.2.2 </span>Attribution</a></li><li class="tocline"><a href="#term-ActivityAssociation" class="tocxref"><span class="secno">4.2.3 </span>Association</a></li><li class="tocline"><a href="#term-responsibility" class="tocxref"><span class="secno">4.2.4 </span>Responsibility</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">4.3 </span>Component 3: Derivations</a><ul class="toc"><li class="tocline"><a href="#Derivation-Relation" class="tocxref"><span class="secno">4.3.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">4.3.2 </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno">4.3.3 </span>Quotation</a></li><li class="tocline"><a href="#term-original-source" class="tocxref"><span class="secno">4.3.4 </span>Original Source</a></li><li class="tocline"><a href="#term-traceability" class="tocxref"><span class="secno">4.3.5 </span>Traceability</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">4.4 </span>Component 4: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno">4.4.1 </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno">4.4.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">4.5 </span>Component 5: Collections</a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno">4.5.1 </span>Collection</a></li><li class="tocline"><a href="#term-collection-insertion" class="tocxref"><span class="secno">4.5.2 </span>Insertion</a></li><li class="tocline"><a href="#term-collection-removal" class="tocxref"><span class="secno">4.5.3 </span>Removal</a></li><li class="tocline"><a href="#term-collection-membership" class="tocxref"><span class="secno">4.5.4 </span>Membership</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">4.6 </span>Component 6: Annotations</a><ul class="toc"><li class="tocline"><a href="#term-note" class="tocxref"><span class="secno">4.6.1 </span>Note</a></li><li class="tocline"><a href="#term-annotation" class="tocxref"><span class="secno">4.6.2 </span>Annotation</a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno">4.7 </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno">4.7.1 </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno">4.7.2 </span>Qualified Name</a></li><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno">4.7.3 </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno">4.7.4 </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno">4.7.4.1 </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno">4.7.4.2 </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno">4.7.4.3 </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno">4.7.4.4 </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno"><span class="insert">4.7.4.5 </span></span><span class="insert">prov:value</span></a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno">4.7.5 </span>Value</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno">5. </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#FurtherConsiderations" class="tocxref"><span class="secno">6. </span>Towards a Refinement of the PROV Data Model</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><span class="delete">PROV Namespace</span><span class="delete">1.3 </span><span class="insert">Notational </span>Conventions</a></li></ul></li><li class="tocline"><a href="#starting-points" class="tocxref"><span class="secno">2. </span><span class="delete">PROV-DM</span><span class="insert">PROV</span> Starting Points</a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno">2.1 </span>Entity and Activity</a></li><li class="tocline"><a href="#section-generation-usage-derivation" class="tocxref"><span class="secno">2.2 </span>Generation, Usage, Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-responsibility" class="tocxref"><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Agents, Attribution, Association, and Responsibility</span></a></li><li class="tocline"><a href="#section-types-entities-agents" class="tocxref"><span class="secno"><span class="delete">2.3 </span><span class="delete">Agents</span><span class="insert">2.4 </span></span><span class="insert">Further Entities: Collections</span> and <span class="delete">Other Types of Entities</span><span class="delete">2.4 </span><span class="delete">Attribution, Association, and Responsibility</span><span class="insert">Accounts</span></a></li><li class="tocline"><a href="#section-UML" class="tocxref"><span class="secno">2.5 </span>Simplified Overview Diagram</a></li><li class="tocline"><a href="#prov-n" class="tocxref"><span class="secno">2.6 </span>PROV-N: The Provenance Notation</a></li></ul></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno">3. </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">3.1 </span>The <span class="delete">Process</span><span class="insert">Authors</span> View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno">3.2 </span>The <span class="delete">Authors</span><span class="insert">Process</span> View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno">3.3 </span>Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno">4. </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">4.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-Entity" class="tocxref"><span class="secno">4.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">4.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">4.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">4.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">4.1.5 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">4.1.6 </span>End</a></li><li class="tocline"><a href="#term-wasInformedBy" class="tocxref"><span class="secno">4.1.7 </span>Communication</a></li><li class="tocline"><a href="#term-wasStartedByActivity" class="tocxref"><span class="secno">4.1.8 </span>Start by Activity</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">4.2 </span>Component 2: Agents and Responsibility</a><ul class="toc"><li class="tocline"><a href="#term-Agent" class="tocxref"><span class="secno">4.2.1 </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno">4.2.2 </span>Attribution</a></li><li class="tocline"><a href="#term-ActivityAssociation" class="tocxref"><span class="secno">4.2.3 </span>Association</a></li><li class="tocline"><a href="#term-responsibility" class="tocxref"><span class="secno">4.2.4 </span>Responsibility</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">4.3 </span>Component 3: Derivations</a><ul class="toc"><li class="tocline"><a href="#Derivation-Relation" class="tocxref"><span class="secno">4.3.1 </span>Derivation</a></li><li class="tocline"><a href="#term-Revision" class="tocxref"><span class="secno">4.3.2 </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno">4.3.3 </span>Quotation</a></li><li class="tocline"><a href="#term-original-source" class="tocxref"><span class="secno">4.3.4 </span>Original Source</a></li><li class="tocline"><a href="#term-traceability" class="tocxref"><span class="secno">4.3.5 </span>Traceability</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">4.4 </span>Component 4: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno">4.4.1 </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno">4.4.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">4.5 </span>Component 5: Collections</a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno">4.5.1 </span>Collection</a></li><li class="tocline"><a href="#term-collection-insertion" class="tocxref"><span class="secno">4.5.2 </span>Insertion</a></li><li class="tocline"><a href="#term-collection-removal" class="tocxref"><span class="secno">4.5.3 </span>Removal</a></li><li class="tocline"><a href="#term-collection-membership" class="tocxref"><span class="secno">4.5.4 </span>Membership</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">4.6 </span>Component 6: Annotations</a><ul class="toc"><li class="tocline"><a href="#term-note" class="tocxref"><span class="secno">4.6.1 </span>Note</a></li><li class="tocline"><a href="#term-annotation" class="tocxref"><span class="secno">4.6.2 </span>Annotation</a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno">4.7 </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno">4.7.1 </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno">4.7.2 </span>Qualified Name</a></li><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno">4.7.3 </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno">4.7.4 </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno">4.7.4.1 </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno">4.7.4.2 </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno">4.7.4.3 </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno">4.7.4.4 </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno"><span class="insert">4.7.4.5 </span></span><span class="insert">prov:value</span></a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno">4.7.5 </span>Value</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno">5. </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno">6. </span><span class="delete">Towards a Refinement of the PROV Data Model</span><span class="insert">Creating Valid Provenance</span></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>
@@ -668,7 +667,7 @@
<p><a href="#extensibility-section">Section 5</a> summarizes PROV-DM extensibility points.</p>
-<p><a href="#FurtherConsiderations">Section 6</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM-CONSTRAINTS">PROV-DM-CONSTRAINTS</a></cite>].</p>
+<p><a href="#valid-provenance">Section 6</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM-CONSTRAINTS">PROV-DM-CONSTRAINTS</a></cite>].</p>
@@ -811,7 +810,7 @@
<div class="conceptexample" id="usage-example">
<p>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); alternatively, <span class="delete">a</span><span class="insert">the</span> same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
+the mix); <span class="delete">alternatively, a</span><span class="insert">in contrast, the</span> same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
</p></div>
@@ -841,9 +840,6 @@
</span></p>
-<p><span class="insert">
-The definition of agent intentionally stays away from using concepts such as enabling, causing, initiating, triggering, affecting, etc, because many entities also enable, cause, initiate, and affect in some way
-the activities. (Concepts such as triggers are themselves defined later in relations between entities and activities.) So the notion of having some degree of responsibility is really what makes an agent.</span></p>
@@ -884,7 +880,7 @@
<div class="glossary-ref" prov:hadoriginalsource="http://dvcs.w3.org/hg/prov/file/31816209cab0/model/glossary.html"> <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="conceptexample" id="association-example">
+<div class="conceptexample" id="attribution-example">
<p><span class="insert">A blog post can be attributed to an author, a mobile phone to its manufacturer.</span></p>
</div>
@@ -901,7 +897,7 @@
<span class="glossary-ref" prov:hadoriginalsource="http://dvcs.w3.org/hg/prov/file/31816209cab0/model/glossary.html"><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="conceptexample" id="association-example2">
+<div class="conceptexample" id="association-example">
<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>
@@ -921,7 +917,7 @@
-<div class="conceptexample" id="responsibilityChain-example">
+<div class="conceptexample" id="responsibility-example">
<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, and it may not matter which
@@ -987,7 +983,7 @@
-<span class="glossary-ref" prov:hadoriginalsource="http://dvcs.w3.org/hg/prov/file/31816209cab0/model/glossary.html"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> This concept allows for the provenance of the <span class="delete">collection, but also of its constituents</span><span class="insert">collection itself</span> to be <span class="delete">expressed.</span><span class="insert">expressed in addition to that of the members.</span> Such a notion of collection corresponds to a wide variety of concrete data structures, such as a <em>maps</em>, <em>dictionaries</em>, or <em>associative arrays</em>.</p>
+<span class="glossary-ref" prov:hadoriginalsource="http://dvcs.w3.org/hg/prov/file/31816209cab0/model/glossary.html"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> This concept allows for the provenance of the <span class="delete">collection, but also of its constituents</span><span class="insert">collection itself</span> to be <span class="delete">expressed.</span><span class="insert">expressed in addition to that of the members.</span> Such a notion of collection corresponds to a wide variety of concrete data structures, such as a <em>maps</em>, <em>dictionaries</em>, or <em>associative arrays</em><span class="delete">.</span><span class="insert">, all of which involve a membership relationship between the constituents and the collection. </span></p>
<div class="conceptexample" id="collection-example">
<p>
@@ -1136,11 +1132,17 @@
<div id="prov-n" class="section">
<h3><span class="secno">2.6 </span>PROV-N: The Provenance Notation</h3>
-<p>A key goal of <span class="delete">PROV-DM</span><span class="insert">PROV</span> is the specification of a machine-processable data model for provenance so that applications can retrieve provenance and reason about it. As such, representations of <span class="delete">PROV-DM</span><span class="insert">PROV</span> are available in RDF and XML.
-</p>
-
-<p>However, it is important to provide instances of provenance for human consumption, as in this document or elsewhere.
-To this end, PROV-N is a notation <span class="delete">that is designed to write</span><span class="insert">for writing</span> instances of the <span class="delete">PROV-DM</span><span class="insert">PROV</span> data model in a compact textual form, without the syntactic baggage and constraints coming with a markup language such as XML or a description framework such as RDF. We outline here some of its key design principles. For full details, the reader is referred to the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-N">PROV-N</a></cite>].</p>
+
+
+
+<p><span class="delete">A key goal of PROV-DM is the specification of a machine-processable</span><span class="insert">To illustrate the application of PROV concepts to a concrete example (see </span><a href="#prov-dm-example"><span class="insert">Section 3</span></a><span class="insert">) and to provide examples of concepts (see </span><a href="#data-model-components"><span class="insert">Section 4</span></a><span class="insert">),
+we introduce PROV-N, a notation for writing instances of the PROV</span> data <span class="delete">model for provenance so that applications can retrieve provenance and reason about it. As such, representations of PROV-DM are available in RDF and XML.
+</span>
+
+<span class="delete">However, it is important to provide instances of provenance for human consumption, as in this document or elsewhere.
+To this end, PROV-N is a notation that is designed to write instances of the PROV-DM data model in a compact textual form, without the syntactic baggage and constraints coming with a markup language such as XML or a description framework such as RDF. We outline here some of its key design principles.</span><span class="insert">model.</span> For full details, the reader is referred to the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-N">PROV-N</a></cite>].<span class="insert">
+PROV-N is a notation aimed at human consumption, with the following characteristics:</span></p>
+
<ul>
<li>PROV-N expressions adopt a <em>functional notation</em> consisting
@@ -1466,6 +1468,7 @@
Components and their dependencies are illustrated in <a href="#prov-dm-components">Figure <span class="delete">prov-dm-components</span><span class="insert">4</span></a>. A component that relies on concepts defined in another also sits above it in this figure.
PROV-DM consists of the following components.</p>
+<div id="prov-dm-components-ul">
<ul>
<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and<span class="delete"> all</span> concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
<li><b>Component 2: agents and responsibility.</b> The second component consists of agents and concepts ascribing responsibility to agents.</li>
@@ -1474,6 +1477,7 @@
<li><b>Component 5: collections.</b> The fifth component is <span class="delete">comprised of</span><span class="insert">about</span> collections and <span class="delete">operations related to collections.</span><span class="insert">concepts capturing their transformation, such as insertion and removal.</span> </li>
<li><b>Component 6: annotations.</b> The sixth component is concerned with annotations to PROV-DM<span class="delete"> concepts.</span><span class="insert"> instances.</span></li>
</ul>
+</div>
<div style="text-align: center;">
@@ -1496,7 +1500,7 @@
Note that for simplicity, this table does not include collection-oriented relations.
</p>
-<div style="text-align: center;">
+<div id="relations-at-a-glance-div" style="text-align: center;">
<table border="1" style="margin-left: auto; margin-right: auto;">
<caption id="relations-at-a-glance"><span class="insert">Table 3: </span>PROV-DM Relations At a Glance</caption>
<tbody><tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
@@ -1510,7 +1514,7 @@
<p><a href="#prov-dm-types-and-relations">Table <span class="delete">prov-dm-concepts-and-relations</span><span class="insert">4</span></a> is a complete index of all the <span class="delete">concepts</span><span class="insert">types</span> and relations <span class="delete">in prov-dm,</span><span class="insert">of PROV-DM,</span> color-coded according to the component they belong <span class="delete">too.</span><span class="insert">to.</span> In the first column,<span class="delete"> one finds </span> concept names<span class="delete"> directly linking</span><span class="insert"> link</span> to their <span class="delete">English definition. In</span><span class="insert">informal definition, whereas, in</span> the second column, <span class="delete">we find their representation in the PROV-N notation, directly linking</span><span class="insert">representations link</span> to the <span class="delete">definition of their various constituents.</span><span class="insert">information used to represent the concept.</span></p>
-<div style="text-align: left;">
+<div id="prov-dm-types-and-relations" style="text-align: left;">
<table border="1" style="margin-left: auto; margin-right: auto;">
<caption id="prov-dm-types-and-relations"><span class="insert">Table 4: </span>PROV-DM <span class="delete">Concepts</span><span class="insert">Types</span> and Relations</caption>
<tbody><tr><td><a><b><span class="insert">Type or Relation Name</span></b></a></td><td><b><span class="insert">Representation in the PROV-N notation</span></b></td></tr>
@@ -1553,7 +1557,7 @@
<div id="component1" class="section">
<h3><span class="secno">4.1 </span>Component 1: Entities and Activities</h3>
-<p>The first component of PROV-DM is concerned with <a title="entity" href="#concept-entity" class="internalDFN">entities</a> and <a title="activity" href="#concept-activity" class="internalDFN">activities</a>, and their <span class="delete">inter-relations:</span><span class="insert">interrelations:</span> <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a>, <a href="#concept-communication" class="internalDFN">Communication</a>, and <a href="#concept-startByActivity" class="internalDFN">Start by Activity</a>. Figure <a href="#figure-component1">figure-component1</a> <span class="delete">overviews</span><span class="insert">uses UML to depict</span> the first component, with two <span class="delete">"UML classes"</span><span class="insert">classes</span> and binary associations between them. Associations are not just binary; indeed, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a> <span class="delete">are remarkable because they have </span><span class="insert">also include </span><em>time</em> <span class="delete">attributes, which are placeholders for time information related to provenance.</span><span class="insert">attributes.</span>
+<p>The first component of PROV-DM is concerned with <a title="entity" href="#concept-entity" class="internalDFN">entities</a> and <a title="activity" href="#concept-activity" class="internalDFN">activities</a>, and their <span class="delete">inter-relations:</span><span class="insert">interrelations:</span> <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a>, <a href="#concept-communication" class="internalDFN">Communication</a>, and <a href="#concept-startByActivity" class="internalDFN">Start by Activity</a>. Figure <a href="#figure-component1">figure-component1</a> <span class="delete">overviews</span><span class="insert">uses UML to depict</span> the first component, with two <span class="delete">"UML classes"</span><span class="insert">classes</span> and binary associations between them. Associations are not just <span class="delete">binary;</span><span class="insert">binary:</span> indeed, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a> <span class="delete">are remarkable because they have </span><span class="insert">also include </span><em>time</em> <span class="delete">attributes, which are placeholders for time information related to provenance.</span><span class="insert">attributes.</span>
</p>
<div style="text-align: center;">
@@ -1953,15 +1957,16 @@
<p>When an entity <span class="name">e</span> is attributed to agent <span class="name">ag</span>, entity <span class="name">e</span> was generated by some unspecified activity that in turn was associated to agent <span class="name">ag</span>. Thus, this relation is useful when the activity is not known, or irrelevant.</p>
-<p> An <dfn title="wasAttributedTo" id="dfn-wasattributedto">attribution</dfn> relation<span class="withPn">, written <span class="pnExpression">wasAttributedTo(id,e,ag,attrs)</span> in PROV-N,</span> <span class="delete">contains the following elements:</span><span class="insert">has:</span></p>
+<p> </p><div class="attributes" id="attributes-attribution">An <dfn title="wasAttributedTo" id="dfn-wasattributedto">attribution</dfn> relation<span class="withPn">, written <span class="pnExpression">wasAttributedTo(id,e,ag,attrs)</span> in PROV-N,</span> <span class="delete">contains the following elements:</span><span class="insert">has:</span><p></p>
<ul>
<li><span class="attribute" id="attribution.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the relation;</li>
<li><span class="attribute" id="attribution.entity">entity</span>: an entity identifier (<span class="name">e</span>);</li>
<li><span class="attribute" id="attribution.agent">agent</span>: the identifier (<span class="name">ag</span>) of the agent whom the entity is ascribed to;</li>
<li><span class="attribute" id="attribution.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs <span class="delete">to further describe the properties of the relation.</span><span class="insert">representing additional information about this attribution.</span></li>
</ul>
-
-<div class="anexample">
+</div>
+
+<div class="anexample" id="anexample-attribution">
<p>
Revisiting the example of <a href="#section-example-one">Section <span class="delete">3.2</span><span class="insert">3.1</span></a>,
we can ascribe <span class="name">tr:WD-prov-dm-20111215</span> to some agents without an explicit activity.<span class="insert"> The reserved attribute </span><span class="name"><span class="insert">role</span></span><span class="insert"> (see </span><a href="#term-attribute-role"><span class="insert">Section 4.7.4.3</span></a><span class="insert">) allows for role of the agent in the attribution to be specified.</span>
@@ -2343,7 +2348,7 @@
<p>Wherever two people describe the provenance of a same thing,
one cannot expect them to coordinate and agree on the identifiers to use to denote that thing.</p>
<div class="anexample" id="entity-example1">
-<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific URI, as she might edit the article later. Alternatively, user Bob refers to the article in general, indepedently of its variants over time.</p>
+<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific URI, as she might edit the article later. Alternatively, user Bob refers to the article in general, <span class="delete">indepedently</span><span class="insert">independently</span> of its variants over time.</p>
</div>
<p>
To allow for identifiers to be chosen freely and independently by each user, the PROV data model introduces relations
@@ -2381,8 +2386,9 @@
<a href="http://www.bbc.co.uk/news/">bbc:news/</a>. This can be expressed as follows.
</p><pre class="codeexample">specializationOf(ex:bbcNews2012-03-23, bbc:news/)
</pre>
-Given that the BBC news does not define a URI for this day's news page, we are creating a qualified name in the namespace <span class="name">ex</span>.
-</div>
+<span class="delete">Given that the BBC news does not define a URI for this day's news page, we are creating a</span><span class="insert">We have created a new</span> qualified <span class="delete">name</span><span class="insert">name, </span><span class="name"><span class="insert">ex:bbcNews2012-03-23</span></span><span class="insert">,</span> in the namespace <span class="name">ex</span><span class="delete">.
+</span><span class="insert">, to identify the specific page carrying this day's news, which would otherwise be the generic </span><span class="name"><span class="insert">bbc:news/</span></span><span class="insert"> page.
+</span></div>
@@ -2443,7 +2449,7 @@
<h3><span class="secno">4.5 </span>Component 5: Collections</h3>
<p>The fifth component of PROV-DM is concerned with the notion of collections.
-A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. <span class="delete">In many applications, it is also of interest</span><span class="insert">Many applications need</span> to be able to express the provenance of the collection itself: e.g. who maintains the collection, which <span class="delete">member</span><span class="insert">members</span> it contains <span class="delete">at which point in time,</span><span class="insert">as it evolves,</span> and how it was assembled. The purpose of Component 5 is to define the types and relations that are useful to express the provenance of collections. </p>
+A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. <span class="delete">In many applications, it is also of interest</span><span class="insert">Some applications need</span> to be able to express the provenance of the collection itself: e.g. who maintains the collection, which <span class="delete">member</span><span class="insert">members</span> it contains <span class="delete">at which point in time,</span><span class="insert">as it evolves,</span> and how it was assembled. The purpose of Component 5 is to define the types and relations that are useful to express the provenance of collections. </p>
<p>Figure <a href="#figure-component5">figure-component5</a> <span class="delete">overviews
the component, which consists of</span><span class="insert">depicts
@@ -2699,7 +2705,7 @@
</span></li><li> <span class="name"><span class="insert">c2</span></span><span class="insert"> exactly has the following pairs as members: </span><span class="name"><span class="insert">("k1", e1), ("k2", e2)</span></span><span class="insert">, and does not contain any other.
</span></li><li> <span class="name"><span class="insert">c3</span></span><span class="insert"> has the following pairs as members: </span><span class="name"><span class="insert">("k1", e1), ("k2", e2), ("k3", v3)</span></span><span class="insert">, and may contain others.
</span></li></ul>
-<p><span class="insert"> Note that the states of </span><span class="name"><span class="insert">c1</span></span><span class="insert"> and </span><span class="name"><span class="insert">c3</span></span><span class="insert"> are</span> only partially <span class="delete">known, because the state of </span><span class="delete">c</span><span class="delete"> is unknown.</span><span class="insert">known.</span></p>
+<p><span class="insert"> Thus, the states of </span><span class="name"><span class="insert">c1</span></span><span class="insert"> and </span><span class="name"><span class="insert">c3</span></span><span class="insert"> are</span> only partially <span class="delete">known, because the state of </span><span class="delete">c</span><span class="delete"> is unknown.</span><span class="insert">known.</span></p>
</div>
@@ -2771,7 +2777,7 @@
</div>
<div class="anexample" id="anexample-note2">
-<p>Alternatively, a reputation service may enrich <span class="delete">a</span><span class="insert">an existing</span> provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name"><span class="delete">ex:Simon</span><span class="insert">ex2:Simon</span></span> and <span class="name"><span class="delete">ex:Paolo</span><span class="insert">ex2:Paolo</span></span> are rated "excellent".</p>
+<p><span class="delete">Alternatively,</span><span class="insert">In contrast,</span> a reputation service may enrich <span class="delete">a</span><span class="insert">an existing</span> provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name"><span class="delete">ex:Simon</span><span class="insert">ex2:Simon</span></span> and <span class="name"><span class="delete">ex:Paolo</span><span class="insert">ex2:Paolo</span></span> are rated "excellent".</p>
<pre class="codeexample">note(ex3:n2,[ex3:reputation="excellent"])
<span class="delete">hasAnnotation(ex:Simon,ex3:n2)
hasAnnotation(ex:Paolo,ex3:n2)</span><span class="insert">hasAnnotation(ex2:Simon,ex3:n2)
@@ -2892,6 +2898,19 @@
+<div id="attributes-at-a-glance-div" style="text-align: left;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
+<caption id="attributes-at-a-glance"><span class="insert">Table 5: PROV-DM Attributes At a Glance</span></caption>
+<tbody><tr><td><b><span class="insert">Attribute</span></b></td><td><b><span class="insert">value</span></b></td><td><b><span class="insert">Section</span></b></td></tr>
+<tr><td><span class="insert">prov:label</span></td><td><span class="insert">xsd:string</span></td><td><span class="insert">Section </span><a href="#term-attribute-label"><span class="insert">4.7.4.1</span></a> </td></tr>
+<tr><td><span class="insert">prov:location</span></td><td><a title="value" href="#dfn-value" class="internalDFN"><span class="insert">Value</span></a></td><td><span class="insert">Section </span><a href="#term-attribute-location"><span class="insert">4.7.4.2</span></a> </td></tr>
+<tr><td><span class="insert">prov:role</span></td><td><a title="value" href="#dfn-value" class="internalDFN"><span class="insert">Value</span></a></td><td><span class="insert">Section </span><a href="#term-attribute-role"><span class="insert">4.7.4.3</span></a> </td></tr>
+<tr><td><span class="insert">prov:type</span></td><td><a title="value" href="#dfn-value" class="internalDFN"><span class="insert">Value</span></a></td><td><span class="insert">Section </span><a href="#term-attribute-type"><span class="insert">4.7.4.4</span></a> </td></tr>
+<tr><td><span class="insert">prov:value</span></td><td><a title="value" href="#dfn-value" class="internalDFN"><span class="insert">Value</span></a></td><td><span class="insert">Section </span><a href="#term-attribute-value"><span class="insert">4.7.4.5</span></a> </td></tr>
+</tbody></table>
+</div>
+
+
@@ -3034,7 +3053,7 @@
<table border="1" style="margin-left: auto; margin-right: auto;">
-<caption><span class="insert">Table 5: </span>PROV-DM Data Types</caption>
+<caption id="prov-dm-data-types"><span class="insert">Table 6: </span>PROV-DM Data Types</caption>
<tbody><tr><td><a href="http://www.w3.org/TR/xmlschema-2/#decimal">xsd:decimal</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#double">xsd:double</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#dateTime">xsd:dateTime</a></td> </tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:integer</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#float">xsd:float</a></td> </tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a></td> <td><a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-XMLLiteral">rdf:XMLLiteral</a></td> </tr>
@@ -3159,8 +3178,8 @@
-<div id="FurtherConsiderations" class="section">
-<h2><span class="secno">6. </span>Towards a Refinement of the PROV Data Model</h2>
+<div id="valid-provenance" class="section">
+<h2><span class="secno">6. </span><span class="delete">Towards a Refinement of the PROV Data Model</span><span class="insert">Creating Valid Provenance</span></h2>
<ul>
@@ -3188,13 +3207,14 @@
</li>
-<li>The existence of some mechanism(s) by which a set of provenance descriptions can be bundled up and named is assumed. No such mechanism is considered as mature for standardization, and therefore such mechanisms remain outside the scope of PROV-DM. Various ways of achieving this functionality exist, for instance, by:
-<ul>
-<li> bundling up a set of descriptions in a file and exposing it as a Web resource;</li>
-<li> relying on specific serializations to name bundles of descriptions;</li>
-<li> using the idea of a service that is capable of associating provenance descriptions to whom they are attributed to.</li>
-</ul>
-<p>Even though a mechanism for <span class="delete">blundling</span><span class="insert">bundling</span> up provenance descriptions and naming them is not part of PROV-DM, the idea of a bundle of descriptions is crucial to the PROV approach. Indeed, it allows multiple provenance perspectives to be provided for a given entity. It is also the mechanism by which provenance of provenance can be expressed. Such a named bundle is being referred to as an <dfn id="dfn-account">account</dfn> and is regarded as an <a title="concept-account">Account</a> so that its provenance can be expressed. The notion of account is specified in the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM-CONSTRAINTS">PROV-DM-CONSTRAINTS</a></cite>], as well as <span class="delete">constraint</span><span class="insert">the constraints</span> that <dfn id="dfn-structurally-well-formed">structurally well-formed</dfn> descriptions are expected to satisfy.</p>
+<li>
+<p>The <span class="delete">existence of some mechanism(s) </span><span class="insert">idea of bundling provenance descriptions is crucial to the PROV approach. Indeed, it allows multiple provenance perspectives to be provided for a given entity. It is also the mechanism </span>by which <span class="delete">a set of </span>provenance <span class="delete">descriptions</span><span class="insert">of provenance</span> can be <span class="delete">bundled up and</span><span class="insert">expressed. Such a</span> named <span class="insert">bundle </span>is<span class="delete"> assumed. No such mechanism is considered as mature for standardization, and therefore such mechanisms remain outside the scope of PROV-DM. Various ways of achieving this functionality exist, for instance, by:
+</span>
+<span class="delete"> bundling up a set of descriptions in a file and exposing it as a Web resource;</span>
+<span class="delete"> relying on specific serializations to name bundles of descriptions;</span>
+<span class="delete"> using the idea of a service that is capable of associating provenance descriptions to whom they are attributed to.</span>
+
+<span class="delete">Even though a mechanism for blundling up provenance descriptions and naming them is not part of PROV-DM, the idea of a bundle of descriptions is crucial to the PROV approach. Indeed, it allows multiple provenance perspectives to be provided for a given entity. It is also the mechanism by which provenance of provenance can be expressed. Such a named bundle is being</span> referred to as an <dfn id="dfn-account">account</dfn> and is regarded as an <a title="concept-account">Account</a> so that its provenance can be expressed. The notion of account is specified in the companion specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM-CONSTRAINTS">PROV-DM-CONSTRAINTS</a></cite>], as well as <span class="delete">constraint</span><span class="insert">the constraints</span> that <dfn id="dfn-structurally-well-formed">structurally well-formed</dfn> descriptions <span class="delete">are expected to</span><em class="rfc2119" title="should"><span class="insert">should</span></em> satisfy.</p>
</li>
--- a/model/prov-dm.html Tue Apr 17 15:02:41 2012 +0100
+++ b/model/prov-dm.html Tue Apr 17 16:14:16 2012 +0100
@@ -356,7 +356,7 @@
<p><a href="#extensibility-section">Section 5</a> summarizes PROV-DM extensibility points.</p>
-<p><a href="#FurtherConsiderations">Section 6</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [[PROV-DM-CONSTRAINTS]].</p>
+<p><a href="#valid-provenance">Section 6</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [[PROV-DM-CONSTRAINTS]].</p>
</section>
@@ -477,7 +477,7 @@
<div class="conceptexample" id="usage-example">
<p>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); alternatively, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
+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).
</div>
@@ -507,10 +507,11 @@
</p>
+<!--
<p>
The definition of agent intentionally stays away from using concepts such as enabling, causing, initiating, triggering, affecting, etc, because many entities also enable, cause, initiate, and affect in some way
the activities. (Concepts such as triggers are themselves defined later in relations between entities and activities.) So the notion of having some degree of responsibility is really what makes an agent.</p>
-
+-->
@@ -688,12 +689,10 @@
<section id="prov-n">
<h2>PROV-N: The Provenance Notation</h2>
-<p>A key goal of PROV is the specification of a machine-processable data model for provenance so that applications can retrieve provenance and reason about it. As such, representations of PROV are available in RDF and XML.
-</p>
-
-<p>However, it is important to provide instances of provenance for human consumption, as in this document or elsewhere.
-To this end, PROV-N is a notation for writing instances of the PROV data model in a compact textual form, without the syntactic baggage and constraints coming with a markup language such as XML or a description framework such as RDF. We outline here some of its key design principles. For full details, the reader is referred to the companion specification [[PROV-N]].</p>
-
+
+<p>To illustrate the application of PROV concepts to a concrete example (see <a href="#prov-dm-example">Section 3</a>) and to provide examples of concepts (see <a href="#data-model-components">Section 4</a>),
+we introduce PROV-N, a notation for writing instances of the PROV data model. For full details, the reader is referred to the companion specification [[PROV-N]].
+PROV-N is a notation aimed at human consumption, with the following characteristics:</p>
<ul>
<li>PROV-N expressions adopt a <em>functional notation</em> consisting
of a name and a list of arguments in parentheses.</li>
@@ -1039,7 +1038,7 @@
<section id="component1">
<h3>Component 1: Entities and Activities</h3>
-<p>The first component of PROV-DM is concerned with <a title="entity">entities</a> and <a title="activity">activities</a>, and their interrelations: <a>Usage</a>, <a>Generation</a>, <a>Start</a>, <a>End</a>, <a>Communication</a>, and <a>Start by Activity</a>. Figure <a href="#figure-component1">figure-component1</a> uses UML to depict the first component, with two classes and binary associations between them. Associations are not just binary; indeed, <a>Usage</a>, <a>Generation</a>, <a>Start</a>, <a>End</a> also include <em>time</em> attributes.
+<p>The first component of PROV-DM is concerned with <a title="entity">entities</a> and <a title="activity">activities</a>, and their interrelations: <a>Usage</a>, <a>Generation</a>, <a>Start</a>, <a>End</a>, <a>Communication</a>, and <a>Start by Activity</a>. Figure <a href="#figure-component1">figure-component1</a> uses UML to depict the first component, with two classes and binary associations between them. Associations are not just binary: indeed, <a>Usage</a>, <a>Generation</a>, <a>Start</a>, <a>End</a> also include <em>time</em> attributes.
</p>
<div style="text-align: center;">
@@ -1832,7 +1831,7 @@
<p>Wherever two people describe the provenance of a same thing,
one cannot expect them to coordinate and agree on the identifiers to use to denote that thing.</p>
<div class="anexample" id="entity-example1">
-<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific URI, as she might edit the article later. Alternatively, user Bob refers to the article in general, indepedently of its variants over time.</p>
+<p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific URI, 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>
To allow for identifiers to be chosen freely and independently by each user, the PROV data model introduces relations
@@ -1871,7 +1870,7 @@
<pre class="codeexample">
specializationOf(ex:bbcNews2012-03-23, bbc:news/)
</pre>
-Given that the BBC news does not define a URI for this day's news page, we are creating a qualified name in the namespace <span class="name">ex</span>.
+We have created a new qualified name, <span class="name">ex:bbcNews2012-03-23</span>, in the namespace <span class="name">ex</span>, to identify the specific page carrying this day's news, which would otherwise be the generic <span class="name">bbc:news/</span> page.
</div>
@@ -1937,7 +1936,7 @@
<h3>Component 5: Collections</h3>
<p>The fifth component of PROV-DM is concerned with the notion of collections.
-A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Many applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection, which members it contains as it evolves, and how it was assembled. The purpose of Component 5 is to define the types and relations that are useful to express the provenance of collections. </p>
+A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection, which members it contains as it evolves, and how it was assembled. The purpose of Component 5 is to define the types and relations that are useful to express the provenance of collections. </p>
<p>Figure <a href="#figure-component5">figure-component5</a> depicts
the fifth component with two classes and three associations.
@@ -2253,7 +2252,7 @@
</div>
<div class="anexample" id="anexample-note2">
-<p>Alternatively, a reputation service may enrich an existing provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name">ex2:Simon</span> and <span class="name">ex2:Paolo</span> are rated "excellent".</p>
+<p>In contrast, a reputation service may enrich an existing provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name">ex2:Simon</span> and <span class="name">ex2:Paolo</span> are rated "excellent".</p>
<pre class="codeexample">
note(ex3:n2,[ex3:reputation="excellent"])
hasAnnotation(ex2:Simon,ex3:n2)
@@ -2374,6 +2373,19 @@
<p>The PROV data model introduces a pre-defined set of attributes in the <a title="prov-namespace">PROV namespace</a>, which we define below.
The interpretation of any attribute declared in another namespace is out of scope.</p>
+<div id="attributes-at-a-glance-div" style="text-align: left;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
+<caption id="attributes-at-a-glance">Table 5: PROV-DM Attributes At a Glance</caption>
+<tr><td><b>Attribute</b></td><td><b>value</b></td><td><b>Section</b></td></tr>
+<tr><td>prov:label</td><td>xsd:string</td><td>Section <a href="#term-attribute-label">4.7.4.1</a> </td></tr>
+<tr><td>prov:location</td><td><a title="value">Value</a></td><td>Section <a href="#term-attribute-location">4.7.4.2</a> </td></tr>
+<tr><td>prov:role</td><td><a title="value">Value</a></td><td>Section <a href="#term-attribute-role">4.7.4.3</a> </td></tr>
+<tr><td>prov:type</td><td><a title="value">Value</a></td><td>Section <a href="#term-attribute-type">4.7.4.4</a> </td></tr>
+<tr><td>prov:value</td><td><a title="value">Value</a></td><td>Section <a href="#term-attribute-value">4.7.4.5</a> </td></tr>
+</table>
+</div>
+
+
@@ -2517,7 +2529,7 @@
<table border="1" style="margin-left: auto; margin-right: auto;">
-<caption>Table 5: PROV-DM Data Types</caption>
+<caption id="prov-dm-data-types">Table 6: PROV-DM Data Types</caption>
<tr><td><a href="http://www.w3.org/TR/xmlschema-2/#decimal">xsd:decimal</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#double">xsd:double</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#dateTime">xsd:dateTime</a></td> </tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema-2/#integer">xsd:integer</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#float">xsd:float</a></td> </tr>
<tr><td><a href="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger">xsd:nonNegativeInteger</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#string">xsd:string</a></td> <td><a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-XMLLiteral">rdf:XMLLiteral</a></td> </tr>
@@ -2637,8 +2649,8 @@
-<section id="FurtherConsiderations">
-<h4>Towards a Refinement of the PROV Data Model</h4>
+<section id="valid-provenance">
+<h4>Creating Valid Provenance</h4>
<ul>
@@ -2666,13 +2678,8 @@
</li>
-<li>The existence of some mechanism(s) by which a set of provenance descriptions can be bundled up and named is assumed. No such mechanism is considered as mature for standardization, and therefore such mechanisms remain outside the scope of PROV-DM. Various ways of achieving this functionality exist, for instance, by:
-<ul>
-<li> bundling up a set of descriptions in a file and exposing it as a Web resource;</li>
-<li> relying on specific serializations to name bundles of descriptions;</li>
-<li> using the idea of a service that is capable of associating provenance descriptions to whom they are attributed to.</li>
-</ul>
-<p>Even though a mechanism for bundling up provenance descriptions and naming them is not part of PROV-DM, the idea of a bundle of descriptions is crucial to the PROV approach. Indeed, it allows multiple provenance perspectives to be provided for a given entity. It is also the mechanism by which provenance of provenance can be expressed. Such a named bundle is being referred to as an <dfn>account</dfn> and is regarded as an <a title="concept-account">Account</a> so that its provenance can be expressed. The notion of account is specified in the companion specification [[PROV-DM-CONSTRAINTS]], as well as the constraints that <dfn>structurally well-formed</dfn> descriptions are expected to satisfy.</p>
+<li>
+<p>The idea of bundling provenance descriptions is crucial to the PROV approach. Indeed, it allows multiple provenance perspectives to be provided for a given entity. It is also the mechanism by which provenance of provenance can be expressed. Such a named bundle is referred to as an <dfn>account</dfn> and is regarded as an <a title="concept-account">Account</a> so that its provenance can be expressed. The notion of account is specified in the companion specification [[PROV-DM-CONSTRAINTS]], as well as the constraints that <dfn>structurally well-formed</dfn> descriptions SHOULD satisfy.</p>
</li>