--- a/model/comments/wd6-Graham.txt	Wed May 30 16:13:57 2012 -0400
+++ b/model/comments/wd6-Graham.txt	Wed May 30 16:17:09 2012 -0400
@@ -20,9 +20,9 @@
   > 2.  So my proposals focus more on explaining how the concepts work
   > together and not repeating the actual definitions.
 
-I am in favour of keeping definitions in section 2, to make it self-contained.
-Paul, Paolo, what do you think?
-Do we seek a WG resolution?
+I am in favour of keeping definitions in section 2 to make it self-contained.
+Also, as I mention below, there is a danger of paraphrasing definitions and
+conveying a different meaning.
 
   > 
   > As I reflect on what I've read, I think it might be worth linking each
@@ -32,6 +32,7 @@
 
 This can be done. 
 Suggestion: at the end of each definition, add a link to the corresponding subsection in section 5.
+I did it for activty/entiy in 2.1.1. Thoughts?
 
   > 
   > Detailed comments follow.
@@ -77,6 +78,9 @@
   >   "core structures form the essence of provenance descriptions, and
   >   are commonly found in various domain-specific vocabularies that deal
   >   with provenance or similar kinds of information".
+
+Done.
+
   > 
   > (Examples, or informational references, could be added to back up this
   > statement - precursor provenance models and CIDOC-CRM are examples I
@@ -91,9 +95,8 @@
   > follow on from entities and activities (or folded in with those).
   > More detail later in discussion of core structures.
 
-We have reorganized components as follows,
-addressing your concern that derivation follows entities and activities, 
-generation and usage.
+We have reorganized components as follows, addressing your concern
+that derivation follows entities and activities, generation and usage.
 
   component 2: derivation
   component 3: agent/responsibility.
@@ -172,21 +175,8 @@
   > column of the table, but types use values from the "Concepts" column.
   > 
 
-I am aware of this. It shows at a couple of other places.
-
-How do we write 
-  wasDerivedFrom(e2,e1,[prov:type='prov:WasRevisionOf'])
-
-Is it prov:WasRevisionOf or prov:wasRevisionOf?
-
-Should relation names be capitalized, e.g. WasDerivedFrom
-while their writing in prov-n is not, e.g. wasDerivedFrom(e2,e1)?
-
-Proposal: In all diagrams, capitalize relations.
-          In table 2, capitalize all entries in column 'Name'
-
-
-Paolo?
+The inconsistency was addressed.
+Relations are now capitalized.  Instances, in prov-n, are lower case.
 
   > I think it's a little confusing that there are named "concepts" and
   > (sometimes) different names for the types and relations.  This is
@@ -203,7 +193,7 @@
 The latter is the concept, the former the relation.
 
 I would be reluctant to replace 'wasGeneratedBy' by 'Generation' in
-Figure.  Likewise, I would be reluctant to say "WasGeneratedBy is the
+figures.  Likewise, I would be reluctant to say "WasGeneratedBy is the
 completion of production of a new entity ..."
 
 So, the solution above, with capitalization of relations would address
@@ -242,6 +232,7 @@
   > entities; they are the mechanisms by which entities are created and
 
 I don't feel like we should paraphrase definitions of terms.
+Choice of term 'consume' is too restrictive, that's why I also use alternatives.
 
 
   > used in the creation of further entities.  Just as entities cover a
@@ -278,7 +269,7 @@
   > <example 4 here>
 
 The above suggested text says 'Usage is relationship' .... 'Usage is considered to occur'
-So, it mixes 'data model construct' and 'concept' 
+So, it mixes 'data model construct' and 'concept'. 
 I tried to stay with definitions of concepts here.
 
   > 
@@ -302,14 +293,14 @@
 
 Good!
 
-Can I check that you meant "in this case a car in Boston may be a
- different ENTITY from a car in Cambridge"  ... and not ARTIFACT?
+I summed that you meant "in this case a car in Boston may be a
+different ENTITY from a car in Cambridge"  ... and not ARTIFACT?
 
   > 
   > <I added a fair amount of explanatory text here, because I think that
   > the whole issue of breadth of interpretation begs some explanation.>
 
-Yes, good idea.
+Yes, it is good idea. I included it.
 
   > 
   > Communication is the generation of an entity by an activity and its
@@ -337,10 +328,6 @@
 
 
 
-<!-- The activity of purchasing a
- car in Boston can be informed by the the activity of its being
- designed in Japan.-->
-
 
   > 
   > == After section 2.1.1 ==
@@ -354,7 +341,7 @@
   > Y and Z; my Ford car was derived from a VW design).
   > 
 
-I would propose to swap 2.1.2 and 2.1.3
+I have swapped 2.1.2 and 2.1.3.
 
   > Thus, following on from the proposed revised 2.1.1:
   > 
@@ -395,8 +382,6 @@
 
 I like it, I have added it after a few tweaks.
 
-
-
   > 
   > == Section 2.1.2 ==
   > 
@@ -435,6 +420,7 @@
   > initiate, control or otherwise bear responsibility for an activity.
 
 Again, I want to avoid paraphrasing the definition.
+We moved away from "control" a long time ago. 
 
   > 
   > <example 6 here>
@@ -443,10 +429,6 @@
   > had some role in the activity.
   > 
 
-An entity used by an activity also has some roles. 
-The WG agreed that agent association means implies responsibility.
-
-
   > <example 8 here>
   > 
   > An /attribution/ of an entity to an agent means that the entity was
@@ -462,7 +444,8 @@
   > any such decisions should be made.  ]]
   > 
 
-There is too much instance on this in your suggestions. I am dropping this.
+There is too much instance on this in your suggestions. 
+I am not including this.
 
 
   > .........
@@ -474,6 +457,8 @@
   > Section 2.2 structure feels a bit contrived to me ... it deals with
   > extension mechanisms (2.2.1) and some new concepts (2.2.2 and 2.2.3)
   > 
+
+... but the new concepts belong to the extended structures. 
   > My inclination would be to present:
   >   2.2 Additional structures
   >   2.2.1 Bundle
@@ -482,6 +467,9 @@
   >   2.3.1 Subtyping
   >   2.3.2 Multi-way relations
   >   2.3.3 Optional identification and new relations
+
+What is 'additional structures' here? are they extended structures?
+
   > 
   > My further comments use the current section numbering...
   > 
@@ -533,6 +521,10 @@
   > 
   > The section title doesn't make any sense to me.  The "New relations"
   > bit is particularly confusing.
+
+I made it a separate header.  This now identifies four ways by which we
+have created extended structures.
+
   > 
   > From the description, it looks to me like reification of a relation so
   > that arbitrary further information can be added to an instance.
@@ -565,7 +557,7 @@
   > A /provenance description/ is a set of assertions based on the core and extended provenance structures described below.
   > ]]
 
-I added "provenance description is an instance of a core and extended 
+I added "a provenance description is an instance of a core and extended 
 provenance structure described below."
 
   > 
@@ -624,6 +616,8 @@
   > 
   > Figure 5: uses UML, but at one point I was looking for cardinality indicators (1:1, 1:N, N:M, etc.)
 
+
+TO DO.
 Paolo, can you tell me what to add? where? What's the UML default?
 
 
@@ -649,7 +643,7 @@
   > "An activity is not an entity" - I think you said otherwise further up (see previous email).
   > 
 
-Not to my knowledge. It was about agent.
+Not to my knowledge. 
 
   > == Section 5.1.3 ==
   > 
@@ -684,12 +678,18 @@
   > (what bureaucratic process could be so simple?).
 
 
+Yes, it was the intent. 
+
+
   > 
   > == Section 5.1.6 ==
   > 
   > The phrase "that initiated the activity" suggests to me that the
   > trigger is an agent (i.e. capable of action).  Maybe "that set of..."
   > ?
+
+Good suggestion.
+
   > 
   > 
   > == Section 5.2.1 ==
@@ -700,6 +700,12 @@
   > unsupervised action; that they can directly initiate an activity
   > without the direct involvement of any other agent at the time.
   > 
+
+That's exactly the path we didn't want to follow: some communities
+don't see autonomy as a key feature of an agent (e.g. mail agent).
+
+
+
   > == Section 5.2.3 ==
   > 
   > As above.
@@ -708,6 +714,13 @@
   > agent can be associated with an activity.  The example makes it clear
   > that this is allowed, but the phrasing "assignment of responsibility"
   > suggests otherwise to me.
+
+Sorry, I don't understand the issue about the phrasing.
+
+Yes, we can have multiple agents associated with an activity, each with
+a different association.
+
+
   > 
   > == Section 5.2.4 ==
   > 
@@ -715,6 +728,10 @@
   > The use of responsibility here is rather more in line with my
   >     expectation, and not, I think, fully consistent with the preceding
   >     uses.
+
+
+In what way is this inconsistent?
+
   > 
   > == Section 5.3.1 ==
   > 
@@ -737,6 +754,15 @@
   > information obtained directly or indirectly from another pre-existing
   > entity.  ]]
   > 
+
+It seems to restrictive: why information?
+
+New definition:
+
+
+A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-exisiting entity.
+
+
   > 
   > == Section 5.3.2 ==
   > 
@@ -747,6 +773,9 @@
   >     revised version of some original.  The implication here is that
   >     the resulting entity contains substantial content from the
   >     original."
+
+Good.
+
   > 
   > 
   > == Section 5.3.3 ==
@@ -757,6 +786,11 @@
   > 
   > "A quotation is a form of derivation in which the new entity contains
   > a verbatim copy of some or all of the original entity's content."
+
+
+This was agreed a while back.  If you feel like changing it, I suggest
+you raise an issue about it.
+
   > 
   > 
   > == Section 5.3.4 ==
@@ -765,9 +799,14 @@
   > == Section 5.3.5 ==
   > 
   > What's a "responsibility" relation - I don't see that defined anywhere.
+
+It was Delegation.
+
   > 
   > I'm completely unclear what is meant by this relation that isn't already covered by derivation.
   > 
+
+Delegation.  + the fact that it is transitive.
   > 
   > I might /guess/ that it's meant to allow the "entity" concerned to be
   > an agent in the overall process, but I find that confusing given that
@@ -775,6 +814,8 @@
   > 
   > What's the requirement for this relation?  Do we really need it?
   > 
+http://www.w3.org/2011/prov/track/issues/370
+
   > 
   > == Section 5.4.1 ==
   > 
@@ -785,6 +826,9 @@
   > the lifetime of the more general entity contains that of any
   > specialization."
   > 
+
+This was voted recently. You need to raise a new ISSUE for this.
+
   > 
   > I know this is formally a topic for CONSTRAINTS, but I think it would
   > help to give an indication of whether a thing can be considered a
@@ -797,6 +841,9 @@
   > In example 41, you claim "They are both specialization of an
   > (unspecified) entity."  If this is true, shouldn't it be part of the
   > definition of alternate?
+
+I dropped it.
+
   > 
   > 
   > == section 5.5 ==
@@ -810,6 +857,8 @@
   > element in a definition.  (See previous comment - maybe in other
   > email)
   > 
+
+was added as suggested.
   > 
   > == Section 5.5.2 ==
   > 
@@ -830,6 +879,19 @@
   > provides no new information.  If the bundle constructor is not
   > present, WHY does it matter that the entity described is provenance?
   > 
+
+Note that the Bundle constructor may not be present (when considering
+incremental navigation, because it has not been retrieved yet).
+
+In fact there is a good reason why you may want to analyse provenance-of-provenance
+before you retrieve the provenance of something. I will retrieve an account that
+is generated by xyz, or an account that provides details.
+
+
+prov:Collection, prov:Plan, prov:Bundle, prov:Dictionary all fall in the same category.
+This type information can be inferred. (We discussed this by email on a separate thread.)
+
+
   > 
   > == Section  5.5.3 ==
   > 
@@ -851,6 +913,9 @@
   > 
   > I've raised this as a separate issue, as I think it needs discussion.
   > 
+
+Discussion in progress.
+
   > 
   > == Section 5.6 ==
   > 
@@ -867,6 +932,11 @@
   > provenance data model, rather than part of the PROV-N specification?
   > It seems to me that most of this is syntactic artifact.
   > 
+
+prov-n is just a serialization for what prov-dm defines.
+If identifiers have not been specified as qualified names in prov-dm,
+how can we create a serialization prov-n?
+
   > 
   > == Section 5.7.4 ==
   > 
@@ -875,9 +945,16 @@
   > would be more appropriately presented as an immediate subsection of
   > section 5 (e.g. 5.7, with the rest of section 5.7 becoming 5.8)
   > 
+
+
   > == Section 5.7.5 ==
   > 
   > Similar comments to above.
+
+
+I moved namespace declaration and qualified name after identifier/attribute/value.
+
+
   > 
   > 
   > == Section 6 ==
@@ -892,6 +969,9 @@
 
   > The second bullet point already does this for prov:type. I think
   >     this should come first, followed by a similar entry for prov:role.
+
+OK, I will have a go at this.
+
   > 
   > 
   > == Section 7 ==
@@ -902,4 +982,11 @@
   > the PROV-CONSTRAINTS document settles (especially its introduction and
   > abstract).  I think they should be conveying the same message.
   > 
-  > 
+
+
+I think it's useful to have a 'taster' for prov-constraints.
+Otherwise, readers won't remember we mentioned it in introduction.
+
+Agreed it should be aligned with prov-constraints.
+
+Luc

--- a/model/diff.html	Wed May 30 16:13:57 2012 -0400
+++ b/model/diff.html	Wed May 30 16:17:09 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-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>
+  <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-30-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">30</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>
@@ -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-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> 
+</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" class="tocxref"><span class="secno"><span class="insert">2.2.1.3 </span></span><span class="insert">Optional Identification</span></a></li><li class="tocline"><a href="#section-prov-extended-approach-further-relations" class="tocxref"><span class="secno"><span class="insert">2.2.1.4 </span></span><span class="insert">Further 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 Type</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"><span class="delete">4.7.1 </span><span class="delete">Namespace Declaration</span><span class="delete">4.7.2 </span><span class="delete">Qualified Name</span><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno"><span class="delete">4.7.3</span><span class="insert">5.7.1</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.2</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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.3</span> </span>Value</a></li><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno"><span class="insert">5.7.4 </span></span><span class="insert">Namespace Declaration</span></a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno"><span class="insert">5.7.5 </span></span><span class="insert">Qualified Name</span></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> 
 
 
 
@@ -1525,19 +1525,19 @@
 </span></p>
 
 <p>
-</p><div class="glossary-ref"><span class="insert">
-   An </span><span class="dfn"><span class="insert">entity</span></span><span class="insert"> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span></div>
-
-
-
-<div class="anexample conceptexample" id="entity-example" data-count="1"><div class="anexampleTitle"><span class="insert">Example 1</span></div>
+<span class="glossary-ref"><span class="insert">
+   An </span><span class="dfn"><span class="insert">entity</span></span><span class="insert"> is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. </span></span><span class="insert"> [</span><a href="#term-entity"><span class="insert">Detailed specification</span></a><span class="insert">]</span></p>
+
+
+
+<div class="anexample conceptexample" id="entity-example" data-count="1"><div class="anexampleTitle"><a href="#entity-example"><span class="insert">Example 1</span></a></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, or generating 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"> [</span><a href="#term-activity"><span class="insert">Detailed specification</span></a><span class="insert">]
 Just as entities cover a broad range of notions, 
 activities can cover a broad range of
 notions:
@@ -1549,7 +1549,7 @@
 
 
 
-<div class="anexample conceptexample" id="activity-example" data-count="2"><div class="anexampleTitle"><span class="insert">Example 2</span></div>
+<div class="anexample conceptexample" id="activity-example" data-count="2"><div class="anexampleTitle"><a href="#activity-example"><span class="insert">Example 2</span></a></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>
 
@@ -1568,7 +1568,7 @@
 
 
 
-<div class="anexample conceptexample" id="generation-example" data-count="3"><div class="anexampleTitle"><span class="insert">Example 3</span></div>
+<div class="anexample conceptexample" id="generation-example" data-count="3"><div class="anexampleTitle"><a href="#generation-example"><span class="insert">Example 3</span></a></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.
@@ -1605,7 +1605,7 @@
 
 
 
-<div class="anexample conceptexample" id="usage-example" data-count="4"><div class="anexampleTitle"><span class="insert">Example 4</span></div>
+<div class="anexample conceptexample" id="usage-example" data-count="4"><div class="anexampleTitle"><a href="#usage-example"><span class="insert">Example 4</span></a></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).
@@ -1622,7 +1622,7 @@
 
 
 
-<div class="anexample conceptexample" id="communication-example" data-count="5"><div class="anexampleTitle"><span class="insert">Example 5</span></div>
+<div class="anexample conceptexample" id="communication-example" data-count="5"><div class="anexampleTitle"><a href="#communication-example"><span class="insert">Example 5</span></a></div>
 <p><span class="insert">
 The activity of writing a celebrity article was informed by (a
 communication instance) the activity of intercepting voicemails.
@@ -1641,13 +1641,13 @@
 </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>
+<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 the construction of a new entity based on a pre-exisiting entity.</span></span>
+
+
+
+
+
+</p><div class="anexample conceptexample" id="derivation-example" data-count="6"><div class="anexampleTitle"><a href="#derivation-example"><span class="insert">Example 6</span></a></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>
@@ -1699,7 +1699,7 @@
 
 
 
-<div class="anexample conceptexample" id="agent-example" data-count="7"><div class="anexampleTitle"><span class="insert">Example 7</span></div>
+<div class="anexample conceptexample" id="agent-example" data-count="7"><div class="anexampleTitle"><a href="#agent-example"><span class="insert">Example 7</span></a></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.
@@ -1713,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" data-count="8"><div class="anexampleTitle"><span class="insert">Example 8</span></div>
+<div class="anexample conceptexample" id="attribution-example" data-count="8"><div class="anexampleTitle"><a href="#attribution-example"><span class="insert">Example 8</span></a></div>
 <p><span class="insert">A blog post can be attributed to an author, a mobile phone to its manufacturer.</span></p>
 </div>
 
@@ -1727,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" data-count="9"><div class="anexampleTitle"><span class="insert">Example 9</span></div>
+<div class="anexample conceptexample" id="association-example" data-count="9"><div class="anexampleTitle"><a href="#association-example"><span class="insert">Example 9</span></a></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>
@@ -1745,15 +1745,12 @@
 
 
 
-<div class="anexample conceptexample" id="responsibility-example" data-count="10"><div class="anexampleTitle"><span class="insert">Example 10</span></div>
+<div class="anexample conceptexample" id="responsibility-example" data-count="10"><div class="anexampleTitle"><a href="#responsibility-example"><span class="insert">Example 10</span></a></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  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.  
+student published a web page, but</span> it <span class="delete">only illustrates  types and relations introduced</span><span class="insert">may matter significantly that the department
+told the student to put up the web page.  
 </span></p>
 </div>
 </div>
@@ -1761,13 +1758,13 @@
 
 </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>
-
-<p><span class="insert">While the core of PROV focuses on essential provenance structures commonly found in provenance descriptions, extended structures 
-are designed to support more advanced uses of provenance. 
-</span>The <span class="delete">Provenance Notation</span><span class="insert">purpose of this section is twofold. First, mechanisms to specify these extended structures are introduced.  Second,  two further kinds of provenance structures are overviewed: they cater for provenance of provenance and collections,  respectively.</span></p>
+<h3><span class="secno"><span class="insert">2.2 </span></span><span class="insert">PROV Extended Structures</span></h3>
+
+<p><span class="insert">While the core of PROV focuses on essential provenance structures commonly found</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">, 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="insert">provenance descriptions, extended structures</span> 
+are <span class="delete">listed</span><span class="insert">designed to support more advanced uses of provenance. 
+The purpose of this section is twofold. First, mechanisms to specify these extended structures are introduced.  Second,  two further kinds of provenance structures are overviewed: they cater for provenance of provenance and collections,  respectively.</span></p>
 
 
 
@@ -1776,7 +1773,8 @@
 <h4><span class="secno"><span class="insert">2.2.1 </span></span><span class="insert">Mechanisms to Define Extended Structures</span></h4>
 
 <p><span class="insert">Extended structures are defined by a variety of mechanisms 
-outlined in this section: subtyping, expanded relations, optional
+outlined</span> in<span class="delete">
+the third column of </span><span class="delete">Table 2</span><span class="insert"> this section: subtyping, expanded relations, optional
 identification, and new relations.</span></p>
 
 
@@ -1792,7 +1790,7 @@
 <p><span class="insert">Subtyping can also be applied to  core relations. For example, a revision is a special kind of derivation, defined as follows.</span></p>
 
 
-<p><span class="glossary-ref"><span class="insert">   A </span><span class="dfn"><span class="insert">revision</span></span><span class="insert"> is a derivation that revises an entity into a revised version. </span></span></p>
+<p><span class="glossary-ref"><span class="insert">   A </span><span class="dfn"><span class="insert">revision</span></span><span class="insert">   is a derivation for which the resulting entity is a revised version of some original. </span></span></p>
 
 </div>
 
@@ -1802,51 +1800,35 @@
 <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 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
+<p><span class="insert">To illustrate expanded relations, we consider the concept of
 association, described
 in </span><a href="#section-agents-attribution-association-delegation"><span class="insert">section
-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
+2.1.3</span></a>.<span class="delete"> These names</span><span class="insert">  Agents may adopt </span><em><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"> 
+association relation allows for a plan to be specified. Plan is defined by subtyping and 
 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</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>
+   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>
 </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>
+<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>
 
 <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
+it may become necessary to track their provenance, so plans themselves</span> are<span class="insert">
 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>
 
 
-<div class="anexample conceptexample" id="association-example2" data-count="11"><div class="anexampleTitle"><span class="insert">Example 11</span></div>
+<div class="anexample conceptexample" id="association-example2" data-count="11"><div class="anexampleTitle"><a href="#association-example2"><span class="insert">Example 11</span></a></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).
 
@@ -1854,8 +1836,8 @@
 </div>
 
 
-<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>
+<div id="section-prov-extended-approach-optional-identification" class="section"> 
+<h5><span class="secno"><span class="insert">2.2.1.3 </span></span><span class="insert">Optional Identification</span></h5>
 
 <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
@@ -1865,21 +1847,24 @@
 an optional identifier to be
 expressed to identify an instance of an association between two or
 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" 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. 
+an instance as</span> part of <span class="delete">a textual notation</span><span class="insert">other concepts.</span></p>
+
+<div class="anexample conceptexample" id="identifier-example" data-count="12"><div class="anexampleTitle"><a href="#identifier-example"><span class="insert">Example 12</span></a></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</span> to <span class="delete">write instances of the PROV data model, which we introduce in the next section. </span><span class="insert">be distinguished. 
 </span></p></div>
 
-<p><span class="insert">Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations.</span></p>
-
-
-
 
 </div>
 
 
 
+<div id="section-prov-extended-approach-further-relations" class="section"> 
+<h5><span class="secno"><span class="insert">2.2.1.4 </span></span><span class="insert">Further Relations</span></h5>
+
+<p><span class="insert">Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations.</span></p>
+
+
+</div>
 </div>
 
 
@@ -1894,7 +1879,7 @@
 <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, 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><div class="anexample conceptexample" id="bundle-example" data-count="13"><div class="anexampleTitle"><a href="#bundle-example"><span class="insert">Example 13</span></a></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
@@ -1911,10 +1896,9 @@
 <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 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>
+<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="insert">sets</span></em><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"><a href="#collection-example"><span class="insert">Example 14</span></a></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 in time, how it was assembled, etc. 
 </span></p></div>
@@ -1929,44 +1913,65 @@
 </div>
 
 <div id="section-overview-components" class="section"> 
-<h3><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Modular Organization</span></h3>
-
-<p><span class="insert">Besides the separation between core and extended structures, PROV-DM
-is further organized according to components, grouping concepts in a
+<h3><span class="secno"><span class="delete">2.6 </span><span class="delete">PROV-N: The Provenance Notation</span><span class="insert">2.3 </span></span><span class="insert">Modular Organization</span></h3>
+
+
+
+
+<p><span class="delete">To illustrate the application of PROV</span><span class="insert">Besides the separation between core and extended structures, PROV-DM
+is further organized according to components, grouping</span> concepts <span class="insert">in a
 thematic manner. </span></p>
 
-<p> <a href="#components-overview"><span class="insert">Table 3</span></a><span class="insert"> enumerates the six components, five of which have already been implicitly overviewed in this section. All components specify extended structures, whereas only the first three</span>  <span class="delete">-</span><span class="delete"> can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising.
-</span>
-<span class="insert">define core structures.</span>
-
-
-<span class="delete">
-An activity with identifier </span><span class="delete">a1</span></p><div id="components-overview-div" style="text-align: center;">
+<p> <a href="#components-overview"><span class="insert">Table 3</span></a><span class="insert"> enumerates the six components, five of which have already been implicitly overviewed in this section. All components specify extended structures, whereas only the first three  define core structures.
+
+</span></p><div id="components-overview-div" style="text-align: center;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <caption id="components-overview"><span class="insert">Table 3: Components Overview</span></caption>
 <tbody><tr><td style="border-width: 0px; "></td><td><span class="insert">Component</span></td><td><span class="insert">Core </span><br><span class="insert">Structures</span></td><td><span class="insert">Overview</span></td><td><span class="insert">Specification</span></td><td><span class="insert">Description</span></td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr><td style="	padding: 8px;"><span class="insert">1</span></td><td style="text-align: left;"><span class="insert">Entities</span> and <span class="delete">an attribute </span><span class="delete">type</span><span class="delete"> with value </span><span class="delete">createFile</span><span class="delete">.
+<tr><td style="	padding: 8px;"><span class="insert">1</span></td><td style="text-align: left;"><span class="insert">Entities and Activities</span></td><td><span class="insert">✔</span></td><td><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td><td><a href="#component1"><span class="insert">5.1</span></a></td><td style="text-align: left;"><span class="insert">about entities and activities, and their interrelations</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 </span>to <span class="delete">a concrete example (see </span><span class="delete">Section 3</span><span class="delete">)</span><span class="insert">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 same 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">to provide examples of </span>concepts <span class="delete">(see </span><span class="delete">Section 4</span><span class="delete">),
+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 [</span><span class="delete">PROV-N</span><span class="delete">].
+PROV-N is a notation  aimed at human consumption, with the following characteristics:</span>
+
+<span class="delete">PROV-N expressions adopt a </span><span class="delete">functional notation</span><span class="delete"> consisting
+of a name</span><span class="insert">capturing their transformation, such as insertion</span> and <span class="delete">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</span><span class="insert">removal</span></td></tr> 
+<span class="delete">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="delete">, and the the set of attribute-value pairs in the </span><span class="delete">last position</span><span class="delete">.
+Consistent with the convention on arguments, the marker  </span><span class="delete">-</span><span class="delete"> can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising.
+</span>
+
+
+
+<span class="delete">
+An activity with identifier </span><span class="delete">a1</span><span class="delete"> and an attribute </span><span class="delete">type</span><span class="delete"> with value </span><span class="delete">createFile</span><span class="delete">.
 </span><span class="delete">activity(a1, [prov:type="createFile"])
 </span><span class="delete">
-Two</span><span class="insert">Activities</span></td><td><span class="insert">✔</span></td><td><a href="#section-entity-activity"><span class="insert">2.1.1</span></a></td><td><a href="#component1"><span class="insert">5.1</span></a></td><td style="text-align: left;"><span class="insert">about</span> entities <span class="delete">with identifiers </span><span class="delete">e1</span> and <span class="delete">e2</span><span class="delete">.
+Two entities with identifiers </span><span class="delete">e1</span><span class="delete"> and </span><span class="delete">e2</span><span class="delete">.
 </span><span class="delete">entity(e1)
 entity(e2)
 </span><span class="delete">
-The activity  </span><span class="delete">a1</span><span class="delete"> used  </span><span class="delete">e1</span><span class="delete">,</span><span class="insert">activities,</span> and <span class="delete">e2</span><span class="delete"> was generated by </span><span class="delete">a1</span><span class="delete">.
+The activity  </span><span class="delete">a1</span><span class="delete"> used  </span><span class="delete">e1</span><span class="delete">, and </span><span class="delete">e2</span><span class="delete"> was generated by </span><span class="delete">a1</span><span class="delete">.
 </span><span class="delete">used(a1,e1)
 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">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.
+The same description, but with an explicit identifier </span><span class="delete">u1</span><span class="delete"> for the usage, and the syntactic marker </span><span class="delete">-</span><span class="delete"> to mark the absence of identifier in the generation.
 </span><span class="delete">used(u1,a1,e1)
 wasGeneratedBy(-,e2,a1)
-</span><span class="insert">concepts capturing their transformation, such as insertion and removal</span></td></tr> 
-</tbody></table>
+</span></tbody></table>
 </div>
 
 </div>
@@ -1999,7 +2004,7 @@
 </span></li>
 </ul>
 
-<div class="anexample" data-count="15"><div class="anexampleTitle"><span class="insert">Example 15</span></div>
+<div class="anexample" id="anexample-prov-n" data-count="15"><div class="anexampleTitle"><a href="#anexample-prov-n"><span class="insert">Example 15</span></a></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"])
@@ -2326,10 +2331,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"><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>
+<tr><td rowspan="3"><span class="insert">Subject</span></td><td>Entity</td><td><span class="delete">wasDerivedFrom</span><div class="component2-color"><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><span class="delete">wasAttributedTo</span><span class="delete">hasAnnotation</span><td class="component3-color"><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><span class="delete">wasAssociatedWith</span><span class="delete">hasAnnotation</span><td class="component3-color"><a class="essential internalDFN" href="#dfn-wasassociatedwith"><span class="insert">WasAssociatedWith</span></a></td></tr>
+<tr><td>Agent</td><td>—</td><td>—</td><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><td class="component3-color"><a class="essential internalDFN" href="#dfn-actedonbehalfof"><span class="insert">ActedOnBehalfOf</span></a></td></tr>
 </tbody></table>
 </div>
 
@@ -2342,7 +2347,7 @@
 <tbody><tr><td><a><b>Type or Relation Name</b></a></td><td><b>Representation in the PROV-N notation</b></td><td><b><span class="insert">Component</span></b></td></tr>
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 
-<tr class="component1-color"><td class="essential"><a href="#concept-entity" class="internalDFN">Entity</a></td><td><a title="dfn-Entity" class="essential internalDFN" href="#dfn-entity">entity(id, [ attr1=val1, ...])</a></td><td rowspan="8"><a href="#component1"><span class="insert">Component 1: entities/activities</span></a></td></tr>
+<tr class="component1-color"><td class="essential"><a href="#concept-entity" class="internalDFN">Entity</a></td><td><a title="dfn-Entity" class="essential internalDFN" href="#dfn-entity">entity(id, [ attr1=val1, ...])</a></td><td rowspan="8"><a href="#component1"><span class="insert">Component 1: Entities/Activities</span></a></td></tr>
 <tr class="component1-color"><td class="essential"><a href="#concept-activity" class="internalDFN">Activity</a></td><td><a title="dfn-Activity" class="essential internalDFN" href="#dfn-activity">activity(id, st, et, [ attr1=val1, ...])</a></td></tr>
 <tr class="component1-color"><td class="essential"><a href="#concept-generation" class="internalDFN">Generation</a></td><td><a title="wasGeneratedBy" href="#dfn-wasgeneratedby" class="internalDFN"><span class="delete">wasGeneratedBy(id,e,a,t,attrs)</span><span class="essential"><span class="insert">wasGeneratedBy(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">e,a</span></span><span class="insert">,t,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
 <tr class="component1-color"><td class="essential"><a href="#concept-usage" class="internalDFN">Usage</a></td><td><a title="used" href="#dfn-used" class="internalDFN"><span class="delete">used(id,a,e,t,attrs)</span><span class="essential"><span class="insert">used(</span></span><span class="insert">id;</span><span class="essential"><span class="insert">a,e</span></span><span class="insert">,t,attrs</span><span class="essential"><span class="insert">)</span></span></a></td></tr>
@@ -2353,14 +2358,14 @@
 <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"><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>
+<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: Derivations</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" 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>
@@ -2376,12 +2381,12 @@
 
 
 
-<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-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>
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 
-<tr class="component5-color"><td><a title="bundle" href="#concept-bundle" class="internalDFN"><span class="insert">Bundle constructor</span></a></td><td><a title="dfn-bundle" href="#dfn-bundle-declaration" class="internalDFN"><span class="insert">bundle id description_1 ... description_n endBundle</span></a></td><td rowspan="3"><a href="#component5"><span class="insert">Component 5: bundles</span></a></td></tr>
-<tr class="component5-color"><td class="provType"><a title="bundle" href="#concept-bundle" class="internalDFN"><span class="insert">Bundle description</span></a></td><td><a><span class="insert">... prov:type='prov:Bundle' ...</span></a></td></tr>
+<tr class="component5-color"><td><a title="bundle" href="#concept-bundle" class="internalDFN"><span class="insert">Bundle constructor</span></a></td><td><a title="dfn-bundle" href="#dfn-bundle-declaration" class="internalDFN"><span class="insert">bundle id description_1 ... description_n endBundle</span></a></td><td rowspan="3"><a href="#component5"><span class="insert">Component 5: Bundles</span></a></td></tr>
+<tr class="component5-color"><td class="provType"><a title="bundle" href="#concept-bundle" class="internalDFN"><span class="insert">Bundle type</span></a></td><td><a><span class="insert">... prov:type='prov:Bundle' ...</span></a></td></tr>
 <tr class="component5-color"><td><a href="#concept-provenance-locator" class="internalDFN"><span class="insert">Provenance Locator</span></a></td><td><a title="hasProvenanceIn" href="#dfn-hasprovenancein" class="internalDFN"><span class="insert">hasProvenanceIn(id, subject, bundle, target, service, prov, 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>
 
@@ -2436,7 +2441,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" data-count="16"><div class="anexampleTitle"><span class="insert">Example 16</span></div>
+<div class="anexample" id="anexample-entity" data-count="16"><div class="anexampleTitle"><a href="#anexample-entity"><span class="insert">Example 16</span></a></div>
 <p>
 The following expression</p>
 <pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
@@ -2464,7 +2469,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" data-count="17"><div class="anexampleTitle"><span class="insert">Example 17</span></div>
+<div class="anexample" id="anexample-activity" data-count="17"><div class="anexampleTitle"><a href="#anexample-activity"><span class="insert">Example 17</span></a></div>
 <p>
 The following expression</p>
 <pre class="codeexample">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
@@ -2507,7 +2512,7 @@
 
 
 
-<div class="anexample" data-count="18"><div class="anexampleTitle"><span class="insert">Example 18</span></div>
+<div class="anexample" id="anexample-generation1" data-count="18"><div class="anexampleTitle"><a href="#anexample-generation1"><span class="insert">Example 18</span></a></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>
@@ -2520,7 +2525,7 @@
 </div>
 
 
-<div class="anexample" data-count="19"><div class="anexampleTitle"><span class="insert">Example 19</span></div>
+<div class="anexample" id="anexample-generation2" data-count="19"><div class="anexampleTitle"><a href="#anexample-generation2"><span class="insert">Example 19</span></a></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>
@@ -2554,7 +2559,7 @@
 </p>
 
 
-<div class="anexample" data-count="20"><div class="anexampleTitle"><span class="insert">Example 20</span></div>
+<div class="anexample" id="anexample-usage" data-count="20"><div class="anexampleTitle"><a href="#anexample-usage"><span class="insert">Example 20</span></a></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>
@@ -2588,16 +2593,16 @@
 A </span><dfn title="wasInformedBy" id="dfn-wasinformedby"><span class="insert">communication</span></dfn><span class="withPn"><span class="insert">, written as 
 </span><span class="pnExpression"><span class="insert">wasInformedBy(id; a2, a1, attrs)</span></span><span class="insert"> in PROV-N,</span></span><span class="insert"> has: 
 </span><ul>
-<li><span class="attribute" id="wasInformedBy.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  identifying the relation;</span></li> 
-<li><span class="attribute" id="wasInformedBy.informed"><span class="insert">informed</span></span><span class="insert">: the identifier (</span><span class="name"><span class="insert">a2</span></span><span class="insert">) of the informed activity;
-</span></li><li><span class="attribute" id="wasInformedBy.informant"><span class="insert">informant</span></span><span class="insert">: the identifier (</span><span class="name"><span class="insert">a1</span></span><span class="insert">) of the informant activity;
-</span></li><li><span class="attribute" id="wasInformedBy.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 communication.</span></li>
+<li><span class="attribute" id="communication.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  identifying the relation;</span></li> 
+<li><span class="attribute" id="communication.informed"><span class="insert">informed</span></span><span class="insert">: the identifier (</span><span class="name"><span class="insert">a2</span></span><span class="insert">) of the informed activity;
+</span></li><li><span class="attribute" id="communication.informant"><span class="insert">informant</span></span><span class="insert">: the identifier (</span><span class="name"><span class="insert">a1</span></span><span class="insert">) of the informant activity;
+</span></li><li><span class="attribute" id="communication.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 communication.</span></li>
 </ul>
 </div>
 
 
 
-<div class="anexample" data-count="21"><div class="anexampleTitle"><span class="insert">Example 21</span></div>
+<div class="anexample" id="anexample-communication" data-count="21"><div class="anexampleTitle"><a href="#anexample-communication"><span class="insert">Example 21</span></a></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" ])
@@ -2611,7 +2616,7 @@
 <div id="term-Start" class="section">
 <h4><span class="secno"><span class="insert">5.1.6</span> </span>Start</h4>
 
-<div class="glossary-ref">   <dfn id="concept-start">Start</dfn> is when an activity is deemed to have started.  The activity did not exist before its start. Any usage or generation involving an activity follows the activity's start. A start may refer to an entity, known as <dfn id="concept-start-trigger">trigger</dfn>, that initiated the <span class="delete">activity.</span><span class="insert">activity, or to an activity, known as </span><dfn id="concept-start-starter"><span class="insert">starter</span></dfn><span class="insert">, that generated the trigger.</span> </div>
+<div class="glossary-ref">   <dfn id="concept-start">Start</dfn> is when an activity is deemed to have started.  The activity did not exist before its start. Any usage or generation involving an activity follows the activity's start. A start may refer to an entity, known as <dfn id="concept-start-trigger">trigger</dfn>, that <span class="delete">initiated the activity.</span><span class="insert">set off the activity, or to an activity, known as </span><dfn id="concept-start-starter"><span class="insert">starter</span></dfn><span class="insert">, that generated the trigger.</span> </div>
 
 
 <p></p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy" id="dfn-wasstartedby">start</dfn><span class="withPn">, written <span class="pnExpression"><span class="delete">wasStartedBy(id,a,e,t,attrs)</span><span class="insert">wasStartedBy(id; a2, e, a1, t, attrs)</span></span> in PROV-N,</span> has:
@@ -2628,7 +2633,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" data-count="22"><div class="anexampleTitle"><span class="insert">Example 22</span></div>
+<div class="anexample" id="anexample-start1" data-count="22"><div class="anexampleTitle"><a href="#anexample-start1"><span class="insert">Example 22</span></a></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"])
@@ -2650,7 +2655,7 @@
 </pre>
 </div>
 
-<div class="anexample" data-count="23"><div class="anexampleTitle"><span class="insert">Example 23</span></div>
+<div class="anexample" id="anexample-start2" data-count="23"><div class="anexampleTitle"><a href="#anexample-start2"><span class="insert">Example 23</span></a></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>.
@@ -2663,7 +2668,7 @@
 </pre>
 </div>
 
-<div class="anexample" data-count="24"><div class="anexampleTitle"><span class="insert">Example 24</span></div>
+<div class="anexample" id="anexample-start3" data-count="24"><div class="anexampleTitle"><a href="#anexample-start3"><span class="insert">Example 24</span></a></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
@@ -2671,7 +2676,7 @@
 indicator needle position, or the engine not running properly.</span>
 
 
-</p><pre class="codeexample"><span class="insert">activity(ex:filling-fuel)
+</p><pre class="codeexample" id="anexample-start4"><span class="insert">activity(ex:filling-fuel)
 activity(ex:observing-low-fuel)
 
 agent(ex:driver, [ prov:type='prov:Person'  )
@@ -2706,7 +2711,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" data-count="25"><div class="anexampleTitle"><span class="insert">Example 25</span></div>
+<div class="anexample" id="anexample-end" data-count="25"><div class="anexampleTitle"><a href="#anexample-end"><span class="insert">Example 25</span></a></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"])
@@ -2759,7 +2764,7 @@
 
 
 
-<div class="anexample" id="anexample-invalidation1" data-count="26"><div class="anexampleTitle"><span class="insert">Example 26</span></div>
+<div class="anexample" id="anexample-invalidation1" data-count="26"><div class="anexampleTitle"><a href="#anexample-invalidation1"><span class="insert">Example 26</span></a></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>.
 
@@ -2771,7 +2776,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-invalidation2" data-count="27"><div class="anexampleTitle"><span class="insert">Example 27</span></div>
+<div class="anexample" id="anexample-invalidation2" data-count="27"><div class="anexampleTitle"><a href="#anexample-invalidation2"><span class="insert">Example 27</span></a></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
@@ -2791,7 +2796,7 @@
 </div>
 
 
-<div class="anexample" id="anexample-invalidation3" data-count="28"><div class="anexampleTitle"><span class="insert">Example 28</span></div>
+<div class="anexample" id="anexample-invalidation3" data-count="28"><div class="anexampleTitle"><a href="#anexample-invalidation3"><span class="insert">Example 28</span></a></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)
@@ -2857,7 +2862,7 @@
 
 
 
-<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>
+<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 the construction of a new entity based on a pre-exisiting entity.</span></div>
 
 
 
@@ -2881,7 +2886,7 @@
 
 
 
-<div class="anexample" data-count="29"><div class="anexampleTitle"><span class="insert">Example 29</span></div>
+<div class="anexample" id="anexample-derivation" data-count="29"><div class="anexampleTitle"><a href="#anexample-derivation"><span class="insert">Example 29</span></a></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" ])
@@ -2906,15 +2911,19 @@
 <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">
+<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 for which the resulting entity is a revised version of some original. </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">
+  The implication here is that
+     the resulting entity contains substantial content from the
+     original.
+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"><a href="#anexample-revision"><span class="insert">Example 30</span></a></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: 
@@ -2961,7 +2970,7 @@
 
 
 
-<div class="anexample" id="anexample-quotation" data-count="31"><div class="anexampleTitle"><span class="insert">Example 31</span></div>
+<div class="anexample" id="anexample-quotation" data-count="31"><div class="anexampleTitle"><a href="#anexample-quotation"><span class="insert">Example 31</span></a></div>
 
 
 
@@ -3024,7 +3033,7 @@
 </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>
+<div class="anexample" data-count="32"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 32</span></a></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).
@@ -3100,7 +3109,7 @@
 
 
 
-<div class="anexample" data-count="33"><div class="anexampleTitle"><span class="insert">Example 33</span></div>
+<div class="anexample" data-count="33"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 33</span></a></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>
@@ -3125,7 +3134,7 @@
 </ul>
 </div>
 
-<div class="anexample" id="anexample-attribution" data-count="34"><div class="anexampleTitle"><span class="insert">Example 34</span></div>
+<div class="anexample" id="anexample-attribution" data-count="34"><div class="anexampleTitle"><a href="#anexample-attribution"><span class="insert">Example 34</span></a></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.
@@ -3163,7 +3172,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" data-count="35"><div class="anexampleTitle"><span class="insert">Example 35</span></div>
+<div class="anexample" id="anexample-wasAssociatedWith" data-count="35"><div class="anexampleTitle"><a href="#anexample-wasAssociatedWith"><span class="insert">Example 35</span></a></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>
@@ -3179,7 +3188,7 @@
 for instance.
 </div>
 
-<div class="anexample" id="anexample-wasAssociatedWith-2" data-count="36"><div class="anexampleTitle"><span class="insert">Example 36</span></div>
+<div class="anexample" id="anexample-wasAssociatedWith-2" data-count="36"><div class="anexampleTitle"><a href="#anexample-wasAssociatedWith-2"><span class="insert">Example 36</span></a></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)
@@ -3230,7 +3239,7 @@
 </ul></div>
 
 
-<div class="anexample" data-count="37"><div class="anexampleTitle"><span class="insert">Example 37</span></div>
+<div class="anexample" data-count="37"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 37</span></a></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>
@@ -3471,7 +3480,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" data-count="38"><div class="anexampleTitle"><span class="insert">Example 38</span></div>
+<div class="anexample" data-count="38"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 38</span></a></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
@@ -3516,7 +3525,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" data-count="39"><div class="anexampleTitle"><span class="insert">Example 39</span></div>
+<div class="anexample" id="entity-example1" data-count="39"><div class="anexampleTitle"><a href="#entity-example1"><span class="insert">Example 39</span></a></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>
@@ -3548,7 +3557,7 @@
 </ul>
 </div>
 
-<div class="anexample" id="anexample-specialization" data-count="40"><div class="anexampleTitle"><span class="insert">Example 40</span></div>
+<div class="anexample" id="anexample-specialization" data-count="40"><div class="anexampleTitle"><a href="#anexample-specialization"><span class="insert">Example 40</span></a></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
@@ -3584,7 +3593,7 @@
 </ul>
 </div>
 
-<div class="anexample" id="anexample-alternate" data-count="41"><div class="anexampleTitle"><span class="insert">Example 41</span></div>
+<div class="anexample" id="anexample-alternate" data-count="41"><div class="anexampleTitle"><a href="#anexample-alternate"><span class="insert">Example 41</span></a></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
@@ -3594,11 +3603,11 @@
 entity(bbc:news/mobile/science-environment-17526723, [ prov:type="a news item for mobile devices"])
 alternateOf(bbc:news/science-environment-17526723, bbc:news/mobile/science-environment-17526723)
 </pre>
-<p>They are both specialization of an (unspecified) entity. </p>
+<span class="delete">They are both specialization of an (unspecified) entity. </span>
 </div>
 
 
-<div class="anexample" id="anexample-alternate2" data-count="42"><div class="anexampleTitle"><span class="insert">Example 42</span></div>
+<div class="anexample" id="anexample-alternate2" data-count="42"><div class="anexampleTitle"><a href="#anexample-alternate2"><span class="insert">Example 42</span></a></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)
@@ -3619,7 +3628,7 @@
 
 
 <p><span class="insert">The fifth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance. 
-</span><a href="#figure-component5"><span class="insert">Figure 9</span></a><span class="insert">  depict a UML class diagram for the fifth component.  It comprises a </span><a href="#concept-bundle" class="internalDFN"><span class="insert">Bundle</span></a><span class="insert"> class, a subclass of </span><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a><span class="insert"> and a novel n-ary relation, </span><a href="#concept-provenance-locator" class="internalDFN"><span class="insert">Provenance Locator</span></a><span class="insert">.
+</span><a href="#figure-component5"><span class="insert">Figure 9</span></a><span class="insert">  depicts a UML class diagram for the fifth component.  It comprises a </span><a href="#concept-bundle" class="internalDFN"><span class="insert">Bundle</span></a><span class="insert"> class, a subclass of </span><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a><span class="insert"> and a novel n-ary relation, </span><a href="#concept-provenance-locator" class="internalDFN"><span class="insert">Provenance Locator</span></a><span class="insert">.
 </span></p>
 
 <div style="text-align: center;">
@@ -3664,7 +3673,7 @@
 
 <div id="term-bundle-entity" class="section"> 
 
-<h4><span class="secno"><span class="insert">5.5.2 </span></span><span class="insert">Bundle Description</span></h4>
+<h4><span class="secno"><span class="insert">5.5.2 </span></span><span class="insert">Bundle Type</span></h4>
 
 <p><span class="insert">A  bundle is a named set of descriptions, but it is also an entity so that its provenance can be described.  </span></p><span class="insert">
 
@@ -3687,7 +3696,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" data-count="43"><div class="anexampleTitle"><span class="insert">Example 43</span></div>
+<div class="anexample" id="anexample-provenance-of-provenance" data-count="43"><div class="anexampleTitle"><a href="#anexample-provenance-of-provenance"><span class="insert">Example 43</span></a></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 ])
@@ -3734,7 +3743,7 @@
 </span></pre>
 </div>
 
-<div class="anexample" id="anexample-provenance-aggregation" data-count="44"><div class="anexampleTitle"><span class="insert">Example 44</span></div>
+<div class="anexample" id="anexample-provenance-aggregation" data-count="44"><div class="anexampleTitle"><a href="#anexample-provenance-aggregation"><span class="insert">Example 44</span></a></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
@@ -3792,7 +3801,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" data-count="45"><div class="anexampleTitle"><span class="insert">Example 45</span></div>
+<div class="anexample" id="anexample-provenance-locator" data-count="45"><div class="anexampleTitle"><a href="#anexample-provenance-locator"><span class="insert">Example 45</span></a></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, -)
@@ -3804,7 +3813,7 @@
 </div>
 
 
-<div class="anexample" id="anexample-provenance-locator2" data-count="46"><div class="anexampleTitle"><span class="insert">Example 46</span></div>
+<div class="anexample" id="anexample-provenance-locator2" data-count="46"><div class="anexampleTitle"><a href="#anexample-provenance-locator2"><span class="insert">Example 46</span></a></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>
@@ -3832,7 +3841,7 @@
 </div>
 
 
-<div class="anexample" id="anexample-provenance-locator3" data-count="47"><div class="anexampleTitle"><span class="insert">Example 47</span></div>
+<div class="anexample" id="anexample-provenance-locator3" data-count="47"><div class="anexampleTitle"><a href="#anexample-provenance-locator3"><span class="insert">Example 47</span></a></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
@@ -3848,7 +3857,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" data-count="48"><div class="anexampleTitle"><span class="insert">Example 48</span></div>
+<div class="anexample" id="aexample-note" data-count="48"><div class="anexampleTitle"><a href="#aexample-note"><span class="insert">Example 48</span></a></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
@@ -3966,7 +3975,7 @@
 
 
 
-<div class="anexample" data-count="49"><div class="anexampleTitle"><span class="insert">Example 49</span></div>
+<div class="anexample" data-count="49"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 49</span></a></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>
@@ -4008,7 +4017,7 @@
 
 
 
-<div class="anexample" data-count="50"><div class="anexampleTitle"><span class="insert">Example 50</span></div>
+<div class="anexample" data-count="50"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 50</span></a></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)
@@ -4030,7 +4039,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" data-count="51"><div class="anexampleTitle"><span class="insert">Example 51</span></div>
+<div class="anexample" data-count="51"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 51</span></a></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)
@@ -4075,7 +4084,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" data-count="52"><div class="anexampleTitle"><span class="insert">Example 52</span></div>
+</p><div class="anexample" data-count="52"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 52</span></a></div>
 <pre class="codeexample">entity(d0, [prov:type="prov:EmptyDictionary"])    // d0 is an empty dictionary
 entity(e1)
 entity(e2)
@@ -4128,7 +4137,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" data-count="53"><div class="anexampleTitle"><span class="insert">Example 53</span></div>
+<div class="anexample" data-count="53"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 53</span></a></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
 
@@ -4295,43 +4304,45 @@
 
 This section introduces further elements of PROV-DM.
 
-<div id="term-NamespaceDeclaration" class="section">
-<h4><span class="secno"><span class="delete">4.7.1</span><span class="insert">5.7.1</span> </span>Namespace Declaration</h4>
-
-<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI [<cite><a class="bibref" rel="biblioentry" href="#bib-IRI">IRI</a></cite>]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name" href="#concept-qualifiedName" class="internalDFN">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
-
-
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
-declaration refers to this namespace. 
- </p>
-
-<p>A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name<span class="delete"> in the scope of this</span><span class="insert">
-refers to</span> default namespace <span class="delete">declaration
-refers to this namespace.</span><span class="insert">declaration.</span></p>
-
-<p>The <dfn title="prov-namespace" id="dfn-prov-namespace">PROV namespace</dfn> is identified by the URI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
-
-</div>
-
-<div id="term-qualified-name" class="section">
-<h4><span class="secno"><span class="delete">4.7.2</span><span class="insert">5.7.2</span> </span>Qualified Name</h4>
-
-
-<span class="glossary-ref">   A <dfn id="concept-qualifiedName">qualified name</dfn> is a name subject to <a href="#dfn-namespace" class="internalDFN">namespace</a> interpretation. It consists of a <a href="#dfn-namespace" class="internalDFN">namespace</a>, denoted by an optional prefix, and a local name.<p></p> </span>
-
-<p>PROV-DM stipulates that a qualified name can be mapped into an IRI
- by concatenating the IRI associated with the prefix and the local part.</p>
-
-<p>A qualified name's prefix is <em class="rfc2119" title="optional">optional</em>. If a prefix occurs in a
- qualified name, it refers to a <a href="#dfn-namespace" class="internalDFN">namespace</a> declared in a namespace declaration.  In the absence of prefix, the qualified name 
- refers to the <a title="default namespace declaration" href="#dfn-defaultNamespaceDeclaration" class="internalDFN">default namespace</a>.</p>
-
-</div>
+
+
 
 
 
 <div id="term-identifier" class="section">
-<h4><span class="secno"><span class="delete">4.7.3</span><span class="insert">5.7.3</span> </span>Identifier</h4>
+<h4><span class="secno"><span class="delete">4.7.1 </span><span class="delete">Namespace Declaration</span>
+
+<span class="delete">A PROV-DM </span><span class="delete">namespace</span><span class="delete"> is identified by an IRI [</span><span class="delete">IRI</span><span class="delete">]. In PROV-DM, attributes, identifiers, and values with </span><span class="delete">qualified names</span><span class="delete"> as data type can be placed in a namespace using the mechanisms described in this specification. </span>
+
+
+<span class="delete">A </span><span class="delete">namespace declaration</span><span class="delete"> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
+declaration refers to this namespace. 
+A </span><span class="delete">default namespace declaration</span><span class="delete"> consists of a namespace. Every un-prefixed qualified name in the scope of this default namespace declaration
+refers to this namespace.</span>
+
+<span class="delete">The </span><span class="delete">PROV namespace</span><span class="delete"> is identified by the URI </span><span class="delete">http://www.w3.org/ns/prov#</span><span class="delete">.</span>
+
+
+
+
+<span class="delete">4.7.2 </span><span class="delete">Qualified Name</span>
+
+
+<span class="delete">   A </span><span class="delete">qualified name</span><span class="delete"> is a name subject to </span><span class="delete">namespace</span><span class="delete"> interpretation. It consists of a </span><span class="delete">namespace</span><span class="delete">, denoted by an optional prefix, and a local name.</span>
+
+<span class="delete">PROV-DM stipulates that a qualified name can be mapped into an IRI
+ by concatenating the IRI associated with the prefix and the local part.</span>
+
+<span class="delete">A qualified name's prefix is </span><span class="delete">optional</span><span class="delete">. If a prefix occurs in a
+ qualified name, it refers to a </span><span class="delete">namespace</span><span class="delete"> declared in a namespace declaration.  In the absence of prefix, the qualified name 
+ refers to the </span><span class="delete">default namespace</span><span class="delete">.</span>
+
+
+
+
+
+
+<span class="delete">4.7.3</span><span class="insert">5.7.1</span> </span>Identifier</h4>
 
 <p>
 An <dfn id="dfn-identifier">identifier</dfn> is a <a href="#concept-qualifiedName" class="internalDFN">qualified
@@ -4341,7 +4352,7 @@
 </div>
 
 <div id="term-attribute" class="section">
-<h4><span class="secno"><span class="delete">4.7.4</span><span class="insert">5.7.4</span> </span>Attribute</h4>
+<h4><span class="secno"><span class="delete">4.7.4</span><span class="insert">5.7.2</span> </span>Attribute</h4>
 
 <p>An <dfn title="dfn-attribute" id="dfn-attribute">attribute</dfn> is a <a href="#concept-qualifiedName" class="internalDFN">qualified name</a>. 
 
@@ -4373,7 +4384,7 @@
 
 
 <div id="term-attribute-label" class="section">
-<h5><span class="secno"><span class="delete">4.7.4.1</span><span class="insert">5.7.4.1</span> </span>prov:label</h5>
+<h5><span class="secno"><span class="delete">4.7.4.1</span><span class="insert">5.7.2.1</span> </span>prov:label</h5>
 
 
 
@@ -4382,7 +4393,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" data-count="54"><div class="anexampleTitle"><span class="insert">Example 54</span></div>
+<div class="anexample" data-count="54"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 54</span></a></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>
@@ -4394,7 +4405,7 @@
 
 
 <div id="term-attribute-location" class="section">
-<h5><span class="secno"><span class="delete">4.7.4.2</span><span class="insert">5.7.4.2</span> </span>prov:location</h5>
+<h5><span class="secno"><span class="delete">4.7.4.2</span><span class="insert">5.7.2.2</span> </span>prov:location</h5>
 
 <p><span class="glossary-ref">   A <dfn id="concept-location" title="location">location</dfn> can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column.   </span>
 As such, there are numerous ways in which location can be expressed, such as by a coordinate,
@@ -4405,7 +4416,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" data-count="55"><div class="anexampleTitle"><span class="insert">Example 55</span></div>
+<div class="anexample" id="example-location" data-count="55"><div class="anexampleTitle"><a href="#example-location"><span class="insert">Example 55</span></a></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>
@@ -4421,7 +4432,7 @@
 
 
 <div id="term-attribute-role" class="section">
-<h5><span class="secno"><span class="delete">4.7.4.3</span><span class="insert">5.7.4.3</span> </span>prov:role</h5>
+<h5><span class="secno"><span class="delete">4.7.4.3</span><span class="insert">5.7.2.3</span> </span>prov:role</h5>
 
 
 <p><span class="glossary-ref"><span class="insert">   A </span><dfn id="concept-role"><span class="insert">role</span></dfn><span class="insert"> is the function of an entity with respect to an activity, in the context of a </span><a href="#concept-usage" class="internalDFN"><span class="insert">usage</span></a><span class="insert">, </span><a href="#concept-generation" class="internalDFN"><span class="insert">generation</span></a><span class="insert">, </span><a href="#concept-activityAssociation" class="internalDFN"><span class="insert">association</span></a><span class="insert">,  </span><a href="#concept-start" class="internalDFN"><span class="insert">start</span></a><span class="insert">, and  </span><a href="#concept-end" class="internalDFN"><span class="insert">end</span></a><span class="insert">. </span></span></p>
@@ -4430,7 +4441,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" data-count="56"><div class="anexampleTitle"><span class="insert">Example 56</span></div>
+<div class="anexample" id="anexample-role" data-count="56"><div class="anexampleTitle"><a href="#anexample-role"><span class="insert">Example 56</span></a></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>
@@ -4441,7 +4452,7 @@
 </div>
 
 <div id="term-attribute-type" class="section">
-<h5><span class="secno"><span class="delete">4.7.4.4</span><span class="insert">5.7.4.4</span> </span>prov:type</h5>
+<h5><span class="secno"><span class="delete">4.7.4.4</span><span class="insert">5.7.2.4</span> </span>prov:type</h5>
 
 <p><span class="glossary-ref">   The attribute <dfn id="concept-type" title="type"><span class="name">prov:type</span></dfn>  provides further typing information   for <span class="insert">any construct with </span>an <span class="delete">element or relation. </span><span class="insert">optional set of attribute-value pairs. </span></span></p>
 
@@ -4451,7 +4462,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" data-count="57"><div class="anexampleTitle"><span class="insert">Example 57</span></div>
+<div class="anexample" data-count="57"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 57</span></a></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>
@@ -4499,7 +4510,7 @@
 
 
 <div id="term-attribute-value" class="section">
-<h5><span class="secno"><span class="delete">4.7.4.5</span><span class="insert">5.7.4.5</span> </span>prov:value</h5>
+<h5><span class="secno"><span class="delete">4.7.4.5</span><span class="insert">5.7.2.5</span> </span>prov:value</h5>
 
 <p><span class="glossary-ref">   The attribute <dfn id="concept-value-attribute" title="value-attribute"><span class="name">prov:value</span></dfn>  provides a <a href="#concept-value" class="internalDFN">Value</a> <span class="insert">for an entity. </span></span></p>
 
@@ -4507,7 +4518,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" data-count="58"><div class="anexampleTitle"><span class="insert">Example 58</span></div>
+<div class="anexample" data-count="58"><div class="anexampleTitle"><a href="#undefined"><span class="insert">Example 58</span></a></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>
@@ -4525,7 +4536,7 @@
 </div>
 
 <div id="term-attribute-provenance-uri" class="section">
-<h5><span class="secno"><span class="insert">5.7.4.6 </span></span><span class="insert">prov:provenance-uri</span></h5>
+<h5><span class="secno"><span class="insert">5.7.2.6 </span></span><span class="insert">prov:provenance-uri</span></h5>
 
 <p><span class="glossary-ref"><span class="insert">   A </span><dfn id="concept-provenance-uri"><span class="insert">provenance-URI</span></dfn><span class="insert"> is the IRI denoting some provenance information. </span></span><span class="insert"> (See  </span><a href="http://www.w3.org/TR/prov-aq/#dfn-provenance-uri"><span class="insert">Provenance-URI</span></a><span class="insert"> in [</span><cite><a class="bibref" rel="biblioentry" href="#bib-PROV-AQ"><span class="insert">PROV-AQ</span></a></cite><span class="insert">].) </span></p>
 
@@ -4538,7 +4549,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" data-count="59"><div class="anexampleTitle"><span class="insert">Example 59</span></div>
+<div class="anexample" id="anexample-provenance-uri" data-count="59"><div class="anexampleTitle"><a href="#anexample-provenance-uri"><span class="insert">Example 59</span></a></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 ])
@@ -4551,7 +4562,7 @@
 
 
 <div id="term-attribute-service-uri" class="section">
-<h5><span class="secno"><span class="insert">5.7.4.7 </span></span><span class="insert">prov:service-uri</span></h5>
+<h5><span class="secno"><span class="insert">5.7.2.7 </span></span><span class="insert">prov:service-uri</span></h5>
 
 <p><span class="glossary-ref"><span class="insert">   A </span><dfn id="concept-provenance-service"><span class="insert">provenance service</span></dfn><span class="insert">   is a service that provides provenance information or a </span><a href="#concept-provenance-uri" class="internalDFN"><span class="insert">provenance-URI</span></a><span class="insert"> given an </span><a href="#dfn-identifier" class="internalDFN"><span class="insert">identifier</span></a><span class="insert">. </span></span><span class="insert"> (See </span><a href="http://www.w3.org/TR/prov-aq/#dfn-provenance-service"><span class="insert">provenance service</span></a><span class="insert"> in [</span><cite><a class="bibref" rel="biblioentry" href="#bib-PROV-AQ"><span class="insert">PROV-AQ</span></a></cite><span class="insert">].)</span></p>
 
@@ -4570,7 +4581,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" data-count="60"><div class="anexampleTitle"><span class="insert">Example 60</span></div>
+<div class="anexample" id="anexample-service-uri" data-count="60"><div class="anexampleTitle"><a href="#anexample-service-uri"><span class="insert">Example 60</span></a></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>
@@ -4602,7 +4613,7 @@
 </div>
 
 <div id="term-value" class="section">
-<h4><span class="secno"><span class="delete">4.7.5</span><span class="insert">5.7.5</span> </span>Value</h4>
+<h4><span class="secno"><span class="delete">4.7.5</span><span class="insert">5.7.3</span> </span>Value</h4>
 
 <p><span class="glossary-ref"><span class="insert">   A </span><dfn id="concept-value" title="value"><span class="insert">value</span></dfn><span class="insert">  is a constant such as a string, number, time, qualified name, and IRI, whose interpretation  is outside the scope of PROV-DM. </span></span></p>
 
@@ -4643,7 +4654,7 @@
 
 
 
-<div class="anexample" id="anexample-value" data-count="61"><div class="anexampleTitle"><span class="insert">Example 61</span></div>
+<div class="anexample" id="anexample-value" data-count="61"><div class="anexampleTitle"><a href="#anexample-value"><span class="insert">Example 61</span></a></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"
@@ -4660,7 +4671,7 @@
 
 
 
-<div class="anexample" id="anexample-time" data-count="62"><div class="anexampleTitle"><span class="insert">Example 62</span></div>
+<div class="anexample" id="anexample-time" data-count="62"><div class="anexampleTitle"><a href="#anexample-time"><span class="insert">Example 62</span></a></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>
@@ -4673,6 +4684,39 @@
 We need to check that we are including all xsd types that are the latest versions of XML Schema/RDF.
 </div>
 </div>
+
+
+<div id="term-NamespaceDeclaration" class="section">
+<h4><span class="secno"><span class="insert">5.7.4 </span></span><span class="insert">Namespace Declaration</span></h4>
+
+<p><span class="insert">A PROV-DM </span><dfn id="dfn-namespace"><span class="insert">namespace</span></dfn><span class="insert"> is identified by an IRI [</span><cite><a class="bibref" rel="biblioentry" href="#bib-IRI"><span class="insert">IRI</span></a></cite><span class="insert">]. In PROV-DM, attributes, identifiers, and values with </span><a title="qualified name" href="#concept-qualifiedName" class="internalDFN"><span class="insert">qualified names</span></a><span class="insert"> as data type can be placed in a namespace using the mechanisms described in this specification. </span></p>
+
+
+<p><span class="insert">A </span><dfn id="dfn-namespaceDeclaration"><span class="insert">namespace declaration</span></dfn><span class="insert"> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
+declaration refers to this namespace. </span></p>
+
+<p><span class="insert">A </span><dfn id="dfn-defaultNamespaceDeclaration"><span class="insert">default namespace declaration</span></dfn><span class="insert"> consists of a namespace. Every un-prefixed qualified name
+refers to default namespace declaration.</span></p>
+
+<p><span class="insert">The </span><dfn title="prov-namespace" id="dfn-prov-namespace"><span class="insert">PROV namespace</span></dfn><span class="insert"> is identified by the URI </span><a href="http://www.w3.org/ns/prov#"><span class="insert">http://www.w3.org/ns/prov#</span></a><span class="insert">.</span></p>
+
+</div>
+
+<div id="term-qualified-name" class="section">
+<h4><span class="secno"><span class="insert">5.7.5 </span></span><span class="insert">Qualified Name</span></h4>
+
+
+<span class="glossary-ref"><span class="insert">   A </span><dfn id="concept-qualifiedName"><span class="insert">qualified name</span></dfn><span class="insert"> is a name subject to </span><a href="#dfn-namespace" class="internalDFN"><span class="insert">namespace</span></a><span class="insert"> interpretation. It consists of a </span><a href="#dfn-namespace" class="internalDFN"><span class="insert">namespace</span></a><span class="insert">, denoted by an optional prefix, and a local name.</span><p></p> </span>
+
+<p><span class="insert">PROV-DM stipulates that a qualified name can be mapped into an IRI
+ by concatenating the IRI associated with the prefix and the local part.</span></p>
+
+<p><span class="insert">A qualified name's prefix is </span><em class="rfc2119" title="optional"><span class="insert">optional</span></em><span class="insert">. If a prefix occurs in a
+ qualified name, it refers to a </span><a href="#dfn-namespace" class="internalDFN"><span class="insert">namespace</span></a><span class="insert"> declared in a namespace declaration.  In the absence of prefix, the qualified name 
+ refers to the </span><a title="default namespace declaration" href="#dfn-defaultNamespaceDeclaration" class="internalDFN"><span class="insert">default namespace</span></a><span class="insert">.</span></p>
+
+</div>
+
 </div>
  
 
@@ -4697,7 +4741,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" data-count="63"><div class="anexampleTitle"><span class="insert">Example 63</span></div>
+<div class="anexample" id="anexample-sub-relation" data-count="63"><div class="anexampleTitle"><a href="#anexample-sub-relation"><span class="insert">Example 63</span></a></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.
@@ -4706,7 +4750,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-sub-type" data-count="64"><div class="anexampleTitle"><span class="insert">Example 64</span></div>
+<div class="anexample" id="anexample-sub-type" data-count="64"><div class="anexampleTitle"><a href="#anexample-sub-type"><span class="insert">Example 64</span></a></div>
 <p>
 In the following example,  <span class="name">e</span> is described as a Car, a type of entity.
 </p><pre class="codeexample"> 

--- a/model/glossary.html	Wed May 30 16:13:57 2012 -0400
+++ b/model/glossary.html	Wed May 30 16:17:09 2012 -0400
@@ -26,7 +26,7 @@
 </span>
 
 <span class="glossary" id="glossary-derivation">  
-A <dfn id="concept-derivation">derivation</dfn>  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>
+A <dfn id="concept-derivation">derivation</dfn>  is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-exisiting entity.</span>
 
 
 
@@ -67,9 +67,9 @@
 </span>
 
 <span class="glossary" id="glossary-delegation">  
-<dfn id="concept-delegation">Delegation</dfn> is the assignment of authority to an agent
+<dfn id="concept-delegation">Delegation</dfn> is the assignment of authority and responsibility to an agent
 (by itself or by another agent)
- to carry out a specific activity as a delegate or representative, while the agent that it represents remains responsible for the outcome of the delegated work.
+ to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work.
 </span>
 
 <!--A <dfn title="concept-responsibility">responsibility chain</dfn> is a relation between two agents,
@@ -133,13 +133,15 @@
 </span>
 
 <span class="glossary" id="glossary-revision">  
-A <dfn id="concept-revision">revision</dfn> is a derivation that revises an entity into a revised version.
+A <dfn id="concept-revision">revision</dfn> 
+ is a derivation for which the resulting entity is a
+revised version of some original.
 </span>
 
 <span class="glossary" id="glossary-start">  
 <dfn id="concept-start">Start</dfn> is when an activity is deemed to have started.
  The activity did not exist before its start. Any usage or generation involving an activity follows the activity's start.
-A start may refer to an entity, known as <dfn id="concept-start-trigger">trigger</dfn>, that initiated the activity, or to an activity, known as <dfn id="concept-start-starter">starter</dfn>, that generated the trigger.
+A start may refer to an entity, known as <dfn id="concept-start-trigger">trigger</dfn>, that set off the activity, or to an activity, known as <dfn id="concept-start-starter">starter</dfn>, that generated the trigger.
 </span>
 
 

--- a/model/glossary.js	Wed May 30 16:13:57 2012 -0400
+++ b/model/glossary.js	Wed May 30 16:17:09 2012 -0400
@@ -3,7 +3,7 @@
 //  with <script src="glossary.js" class="remove"></script>
 //Insert glossary definitions with the following 
 // <div class="glossary-ref" ref="glossary-generation"></div>
-glossary_hg='http://dvcs.w3.org/hg/prov/file/51c1fe338db9/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/51c9b9141a25/model/glossary.html';
 glossary_string= 
 ' ' + 
 '<html> ' + 
@@ -33,7 +33,7 @@
 '</span> ' + 
 ' ' + 
 '<span class="glossary" id="glossary-derivation">   ' + 
-'A <dfn id="concept-derivation">derivation</dfn>  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> ' + 
+'A <dfn id="concept-derivation">derivation</dfn>  is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-exisiting entity.</span> ' + 
 ' ' + 
 ' ' + 
 ' ' + 
@@ -74,9 +74,9 @@
 '</span> ' + 
 ' ' + 
 '<span class="glossary" id="glossary-delegation">   ' + 
-'<dfn id="concept-delegation">Delegation</dfn> is the assignment of authority to an agent ' + 
+'<dfn id="concept-delegation">Delegation</dfn> is the assignment of authority and responsibility to an agent ' + 
 '(by itself or by another agent) ' + 
-' to carry out a specific activity as a delegate or representative, while the agent that it represents remains responsible for the outcome of the delegated work. ' + 
+' to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. ' + 
 '</span> ' + 
 ' ' + 
 '<!--A <dfn title="concept-responsibility">responsibility chain</dfn> is a relation between two agents, ' + 
@@ -140,13 +140,15 @@
 '</span> ' + 
 ' ' + 
 '<span class="glossary" id="glossary-revision">   ' + 
-'A <dfn id="concept-revision">revision</dfn> is a derivation that revises an entity into a revised version. ' + 
+'A <dfn id="concept-revision">revision</dfn>  ' + 
+' is a derivation for which the resulting entity is a ' + 
+'revised version of some original. ' + 
 '</span> ' + 
 ' ' + 
 '<span class="glossary" id="glossary-start">   ' + 
 '<dfn id="concept-start">Start</dfn> is when an activity is deemed to have started. ' + 
 ' The activity did not exist before its start. Any usage or generation involving an activity follows the activity\'s start. ' + 
-'A start may refer to an entity, known as <dfn id="concept-start-trigger">trigger</dfn>, that initiated the activity, or to an activity, known as <dfn id="concept-start-starter">starter</dfn>, that generated the trigger. ' + 
+'A start may refer to an entity, known as <dfn id="concept-start-trigger">trigger</dfn>, that set off the activity, or to an activity, known as <dfn id="concept-start-starter">starter</dfn>, that generated the trigger. ' + 
 '</span> ' + 
 ' ' + 
 ' ' + 

--- a/model/prov-dm.html	Wed May 30 16:13:57 2012 -0400
+++ b/model/prov-dm.html	Wed May 30 16:17:09 2012 -0400
@@ -604,8 +604,8 @@
 </p>
 
 <p>
-<div class="glossary-ref" data-ref="glossary-entity"  data-withspan="true">
-</div>
+<span class="glossary-ref" data-ref="glossary-entity"  data-withspan="true">
+</span> [<a href="#term-entity">Detailed specification</a>]</p>
 
 
 
@@ -616,7 +616,7 @@
 
 
 <p>
-<span class="glossary-ref" data-ref="glossary-activity"  data-withspan="true"></span> 
+<span class="glossary-ref" data-ref="glossary-activity"  data-withspan="true"></span> [<a href="#term-activity">Detailed specification</a>]
 Just as entities cover a broad range of notions, 
 activities can cover a broad range of
 notions:
@@ -912,8 +912,8 @@
 </section>
 
 
-<section id="section-prov-extended-approach-optional-identification-new-relation"> 
-<h2>Optional Identification and New Relations</h2>
+<section id="section-prov-extended-approach-optional-identification"> 
+<h2>Optional Identification</h2>
 
 <p>Some concepts exhibit both a core use, expressed as
 binary relation, and an extended use, expressed as n-ary relation.  In
@@ -929,15 +929,18 @@
 <p>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. 
 </div>
 
+
+</section>
+
+
+
+<section id="section-prov-extended-approach-further-relations"> 
+<h2>Further Relations</h2>
+
 <p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations.</p>
 
 
-
-
 </section>
-
-
-
 </section>
 
 
@@ -1394,7 +1397,7 @@
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 
 <tr class="component5-color"><td><a title="bundle">Bundle constructor</a></td><td><a title="dfn-bundle">bundle id description_1 ... description_n endBundle</a></td><td  rowspan="3"><a href="#component5">Component 5: Bundles</a></td></tr>
-<tr class="component5-color"><td class="provType"><a title="bundle">Bundle description</a></td><td><a>... prov:type='prov:Bundle' ...</a></td></tr>
+<tr class="component5-color"><td class="provType"><a title="bundle">Bundle type</a></td><td><a>... prov:type='prov:Bundle' ...</a></td></tr>
 <tr class="component5-color"><td><a>Provenance Locator</a></td><td><a title="hasProvenanceIn">hasProvenanceIn(id, subject, bundle, target, service, prov, attrs)</a></td></tr>
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 
@@ -1935,7 +1938,11 @@
 
 <p><span class="glossary-ref" data-ref="glossary-revision"></span></p>
 
-<p>Revision is a particular case of <a>derivation</a> of an entity into its revised version.</p>
+<p>
+  The implication here is that
+     the resulting entity contains substantial content from the
+     original.
+Revision is a particular case of <a>derivation</a> of an entity into its revised version.</p>
 
 <!-- <p> A <dfn title="wasRevisionOf">revision</dfn> relation<span class="withPn">, written <span class="pnExpression">wasRevisionOf(id; e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:</p>
 <ul>
@@ -2419,7 +2426,6 @@
 entity(bbc:news/mobile/science-environment-17526723, [ prov:type="a news item for mobile devices"])
 alternateOf(bbc:news/science-environment-17526723, bbc:news/mobile/science-environment-17526723)
 </pre>
-<p>They are both specialization of an (unspecified) entity. </p>
 </div>
 
 
@@ -2443,7 +2449,7 @@
 
 
 <p>The fifth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance. 
-<a href="#figure-component5">Figure 9</a>  depict a UML class diagram for the fifth component.  It comprises a <a>Bundle</a> class, a subclass of <a>Entity</a> and a novel n-ary relation, <a>Provenance Locator</a>.
+<a href="#figure-component5">Figure 9</a>  depicts a UML class diagram for the fifth component.  It comprises a <a>Bundle</a> class, a subclass of <a>Entity</a> and a novel n-ary relation, <a>Provenance Locator</a>.
 </p>
 
 <div style="text-align: center;">
@@ -2488,7 +2494,7 @@
 
 <section id="term-bundle-entity"> 
 
-<h3>Bundle Description</h3>
+<h3>Bundle Type</h3>
 
 <p>A  bundle is a named set of descriptions, but it is also an entity so that its provenance can be described.  </p>
 
@@ -3020,36 +3026,6 @@
 
 This section introduces further elements of PROV-DM.
 
-<section id="term-NamespaceDeclaration">
-<h3>Namespace Declaration</h3>
-
-<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI [[!IRI]]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
-
-
-<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
-declaration refers to this namespace. </p>
-
-<p>A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name
-refers to default namespace declaration.</p>
-
-<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the URI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
-
-</section>
-
-<section id="term-qualified-name">
-<h4>Qualified Name</h4>
-
-
-<span class="glossary-ref" data-ref="glossary-qualifiedName"></span>
-
-<p>PROV-DM stipulates that a qualified name can be mapped into an IRI
- by concatenating the IRI associated with the prefix and the local part.</p>
-
-<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
- qualified name, it refers to a <a>namespace</a> declared in a namespace declaration.  In the absence of prefix, the qualified name 
- refers to the <a title="default namespace declaration">default namespace</a>.</p>
-
-</section>
 
 
 
@@ -3353,6 +3329,38 @@
 We need to check that we are including all xsd types that are the latest versions of XML Schema/RDF.
 </div>
 </section>
+
+<section id="term-NamespaceDeclaration">
+<h3>Namespace Declaration</h3>
+
+<p>A PROV-DM <dfn id="dfn-namespace">namespace</dfn> is identified by an IRI [[!IRI]]. In PROV-DM, attributes, identifiers, and values with <a title="qualified name">qualified names</a> as data type can be placed in a namespace using the mechanisms described in this specification. </p>
+
+
+<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
+declaration refers to this namespace. </p>
+
+<p>A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name
+refers to default namespace declaration.</p>
+
+<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the URI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
+
+</section>
+
+<section id="term-qualified-name">
+<h4>Qualified Name</h4>
+
+
+<span class="glossary-ref" data-ref="glossary-qualifiedName"></span>
+
+<p>PROV-DM stipulates that a qualified name can be mapped into an IRI
+ by concatenating the IRI associated with the prefix and the local part.</p>
+
+<p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
+ qualified name, it refers to a <a>namespace</a> declared in a namespace declaration.  In the absence of prefix, the qualified name 
+ refers to the <a title="default namespace declaration">default namespace</a>.</p>
+
+</section>
+
 </section>
  
 

Binary file model/uml/component6.png has changed

--- a/model/uml/component6.svg	Wed May 30 16:13:57 2012 -0400
+++ b/model/uml/component6.svg	Wed May 30 16:17:09 2012 -0400
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE svg PUBLIC '-//W3C//DTD SVG 1.0//EN'
           'http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd'>
-<svg fill-opacity="0" xmlns:xlink="http://www.w3.org/1999/xlink" color-rendering="auto" color-interpolation="auto" stroke="rgb(0,0,0)" text-rendering="auto" stroke-linecap="square" width="792" stroke-miterlimit="10" stroke-opacity="0" shape-rendering="auto" fill="rgb(0,0,0)" stroke-dasharray="none" font-weight="normal" stroke-width="1" height="356" xmlns="http://www.w3.org/2000/svg" font-family="&apos;Dialog&apos;" font-style="normal" stroke-linejoin="miter" font-size="12" stroke-dashoffset="0" image-rendering="auto"
+<svg fill-opacity="0" xmlns:xlink="http://www.w3.org/1999/xlink" color-rendering="auto" color-interpolation="auto" stroke="rgb(0,0,0)" text-rendering="auto" stroke-linecap="square" width="896" stroke-miterlimit="10" stroke-opacity="0" shape-rendering="auto" fill="rgb(0,0,0)" stroke-dasharray="none" font-weight="normal" stroke-width="1" height="356" xmlns="http://www.w3.org/2000/svg" font-family="&apos;Dialog&apos;" font-style="normal" stroke-linejoin="miter" font-size="12" stroke-dashoffset="0" image-rendering="auto"
 ><!--Generated by the Batik Graphics2D SVG Generator--><defs id="genericDefs"
   /><g
   ><defs id="defs1"
@@ -30,53 +30,65 @@
       ><path d="M0 0 L0 37 L80 37 L80 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath9"
-      ><path d="M0 0 L203 0 L203 104 L0 104 L0 0 Z"
+      ><path d="M-7 -7 L131 -7 L131 51 L-7 51 L-7 -7 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath10"
-      ><path d="M0 0 L193 0 L193 104 L0 104 L0 0 Z"
+      ><path d="M0 0 L0 23 L120 23 L120 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath11"
-      ><path d="M0 0 L144 0 L144 203 L0 203 L0 0 Z"
+      ><path d="M0 0 L120 0 L120 28 L0 28 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath12"
-      ><path d="M0 0 L143 0 L143 203 L0 203 L0 0 Z"
+      ><path d="M0 0 L203 0 L203 104 L0 104 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath13"
-      ><path d="M0 0 L174 0 L174 194 L0 194 L0 0 Z"
+      ><path d="M0 0 L193 0 L193 104 L0 104 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath14"
-      ><path d="M0 0 L244 0 L244 134 L0 134 L0 0 Z"
+      ><path d="M0 0 L144 0 L144 203 L0 203 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath15"
-      ><path d="M0 0 L273 0 L273 104 L0 104 L0 0 Z"
+      ><path d="M0 0 L143 0 L143 203 L0 203 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath16"
-      ><path d="M0 0 L164 0 L164 204 L0 204 L0 0 Z"
+      ><path d="M0 0 L174 0 L174 194 L0 194 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath17"
-      ><path d="M0 0 L364 0 L364 304 L0 304 L0 0 Z"
+      ><path d="M0 0 L244 0 L244 134 L0 134 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath18"
-      ><path d="M0 0 L433 0 L433 384 L0 384 L0 0 Z"
+      ><path d="M0 0 L273 0 L273 104 L0 104 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath19"
-      ><path d="M0 0 L594 0 L594 254 L0 254 L0 0 Z"
+      ><path d="M0 0 L164 0 L164 204 L0 204 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath20"
-      ><path d="M0 0 L104 0 L104 133 L0 133 L0 0 Z"
+      ><path d="M0 0 L364 0 L364 304 L0 304 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath21"
-      ><path d="M-77 -14 L154 -14 L154 28 L-77 28 L-77 -14 Z"
+      ><path d="M0 0 L433 0 L433 384 L0 384 L0 0 Z"
       /></clipPath
       ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath22"
+      ><path d="M0 0 L594 0 L594 254 L0 254 L0 0 Z"
+      /></clipPath
+      ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath23"
+      ><path d="M0 0 L104 0 L104 133 L0 133 L0 0 Z"
+      /></clipPath
+      ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath24"
+      ><path d="M0 0 L153 0 L153 104 L0 104 L0 0 Z"
+      /></clipPath
+      ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath25"
+      ><path d="M-77 -14 L154 -14 L154 28 L-77 28 L-77 -14 Z"
+      /></clipPath
+      ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath26"
       ><path d="M-66 -14 L132 -14 L132 28 L-66 28 L-66 -14 Z"
       /></clipPath
-      ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath23"
+      ><clipPath clipPathUnits="userSpaceOnUse" id="clipPath27"
       ><path d="M-67 -14 L134 -14 L134 28 L-67 28 L-67 -14 Z"
       /></clipPath
     ></defs
     ><g fill="white" text-rendering="geometricPrecision" fill-opacity="1" stroke-opacity="1" stroke="white"
-    ><rect x="0" width="792" height="356" y="0" stroke="none"
+    ><rect x="0" width="896" height="356" y="0" stroke="none"
     /></g
     ><g font-size="11" transform="translate(232,2)" fill-opacity="1" fill="rgb(122,207,245)" text-rendering="geometricPrecision" font-family="sans-serif" stroke="rgb(122,207,245)" font-weight="bold" stroke-opacity="1"
     ><rect x="0" width="80" height="50" y="0" clip-path="url(#clipPath1)" stroke="none"
@@ -196,75 +208,93 @@
     ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath3)" stroke="none"
       >MemberOf</text
     ></g
+    ><g font-size="11" transform="translate(772,2)" fill-opacity="1" fill="rgb(179,214,249)" text-rendering="geometricPrecision" font-family="sans-serif" stroke="rgb(179,214,249)" font-weight="bold" stroke-opacity="1"
+    ><rect x="0" width="120" height="40" y="0" clip-path="url(#clipPath9)" stroke="none"
+    /></g
+    ><g font-size="11" stroke-linecap="butt" transform="translate(772,2)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" font-weight="bold" stroke-opacity="1" stroke-miterlimit="0"
+    ><rect fill="none" x="0" width="120" height="40" y="0" clip-path="url(#clipPath9)"
+      /><line y2="28" fill="none" x1="0" clip-path="url(#clipPath9)" x2="120" y1="28"
+    /></g
+    ><g font-size="11" transform="translate(772,2)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke="black" stroke-opacity="1"
+    ><text x="16" xml:space="preserve" y="11" clip-path="url(#clipPath11)" stroke="none"
+      >&lt;&lt;prov:type&gt;&gt;</text
+      ><text x="13" xml:space="preserve" y="25" font-weight="bold" clip-path="url(#clipPath11)" stroke="none"
+      >EmptyDictionary</text
+    ></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(262,-28)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath9)" x2="149" y1="50"
-      /><polygon fill="white" clip-path="url(#clipPath9)" points=" 50 50 62 56 62 44" stroke="none"
-      /><polygon fill="none" points=" 50 50 62 56 62 44" clip-path="url(#clipPath9)"
+    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath12)" x2="149" y1="50"
+      /><polygon fill="white" clip-path="url(#clipPath12)" points=" 50 50 62 56 62 44" stroke="none"
+      /><polygon fill="none" points=" 50 50 62 56 62 44" clip-path="url(#clipPath12)"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(472,-28)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath10)" x2="139" y1="50"
-      /><polygon fill="white" clip-path="url(#clipPath10)" points=" 50 50 62 56 62 44" stroke="none"
-      /><polygon fill="none" points=" 50 50 62 56 62 44" clip-path="url(#clipPath10)"
+    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath13)" x2="139" y1="50"
+      /><polygon fill="white" clip-path="url(#clipPath13)" points=" 50 50 62 56 62 44" stroke="none"
+      /><polygon fill="none" points=" 50 50 62 56 62 44" clip-path="url(#clipPath13)"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(62,-28)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="50" fill="none" x1="90" clip-path="url(#clipPath11)" x2="90" y1="149"
-      /><line y2="50" fill="none" x1="90" clip-path="url(#clipPath11)" x2="50" y1="50"
+    ><line y2="50" fill="none" x1="90" clip-path="url(#clipPath14)" x2="90" y1="149"
+      /><line y2="50" fill="none" x1="90" clip-path="url(#clipPath14)" x2="50" y1="50"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(142,-28)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath12)" x2="50" y1="149"
-      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath12)" x2="89" y1="50"
+    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath15)" x2="50" y1="149"
+      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath15)" x2="89" y1="50"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(532,-18)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="140" fill="none" x1="120" clip-path="url(#clipPath13)" x2="120" y1="60"
-      /><line y2="140" fill="none" x1="120" clip-path="url(#clipPath13)" x2="50" y1="140"
-      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath13)" x2="50" y1="140"
-      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath13)" x2="79" y1="50"
-      /><line y2="44" fill="none" x1="79" clip-path="url(#clipPath13)" x2="67" y1="50"
-      /><line y2="56" fill="none" x1="79" clip-path="url(#clipPath13)" x2="67" y1="50"
+    ><line y2="140" fill="none" x1="120" clip-path="url(#clipPath16)" x2="120" y1="60"
+      /><line y2="140" fill="none" x1="120" clip-path="url(#clipPath16)" x2="50" y1="140"
+      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath16)" x2="50" y1="140"
+      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath16)" x2="79" y1="50"
+      /><line y2="44" fill="none" x1="79" clip-path="url(#clipPath16)" x2="67" y1="50"
+      /><line y2="56" fill="none" x1="79" clip-path="url(#clipPath16)" x2="67" y1="50"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(412,72)" stroke-dashoffset="1" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke-dasharray="5" stroke="black" stroke-opacity="1"
-    ><line y2="80" fill="none" x1="190" clip-path="url(#clipPath14)" x2="190" y1="50"
-      /><line y2="80" fill="none" x1="190" clip-path="url(#clipPath14)" x2="50" y1="80"
+    ><line y2="80" fill="none" x1="190" clip-path="url(#clipPath17)" x2="190" y1="50"
+      /><line y2="80" fill="none" x1="190" clip-path="url(#clipPath17)" x2="50" y1="80"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(162,92)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="50" fill="none" x1="219" clip-path="url(#clipPath15)" x2="50" y1="50"
+    ><line y2="50" fill="none" x1="219" clip-path="url(#clipPath18)" x2="50" y1="50"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(632,-28)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="150" fill="none" x1="50" clip-path="url(#clipPath16)" x2="50" y1="70"
-      /><line y2="150" fill="none" x1="50" clip-path="url(#clipPath16)" x2="110" y1="150"
-      /><line y2="50" fill="none" x1="110" clip-path="url(#clipPath16)" x2="110" y1="150"
-      /><line y2="50" fill="none" x1="110" clip-path="url(#clipPath16)" x2="90" y1="50"
-      /><line y2="82" fill="none" x1="50" clip-path="url(#clipPath16)" x2="44" y1="70"
-      /><line y2="82" fill="none" x1="50" clip-path="url(#clipPath16)" x2="56" y1="70"
+    ><line y2="150" fill="none" x1="50" clip-path="url(#clipPath19)" x2="50" y1="70"
+      /><line y2="150" fill="none" x1="50" clip-path="url(#clipPath19)" x2="110" y1="150"
+      /><line y2="50" fill="none" x1="110" clip-path="url(#clipPath19)" x2="110" y1="150"
+      /><line y2="50" fill="none" x1="110" clip-path="url(#clipPath19)" x2="90" y1="50"
+      /><line y2="82" fill="none" x1="50" clip-path="url(#clipPath19)" x2="44" y1="70"
+      /><line y2="82" fill="none" x1="50" clip-path="url(#clipPath19)" x2="56" y1="70"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(412,72)" stroke-dashoffset="1" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke-dasharray="5" stroke="black" stroke-opacity="1"
-    ><line y2="250" fill="none" x1="310" clip-path="url(#clipPath17)" x2="310" y1="50"
-      /><line y2="250" fill="none" x1="310" clip-path="url(#clipPath17)" x2="50" y1="250"
+    ><line y2="250" fill="none" x1="310" clip-path="url(#clipPath20)" x2="310" y1="50"
+      /><line y2="250" fill="none" x1="310" clip-path="url(#clipPath20)" x2="50" y1="250"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(2,-8)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="330" fill="none" x1="379" clip-path="url(#clipPath18)" x2="50" y1="330"
-      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath18)" x2="50" y1="330"
+    ><line y2="330" fill="none" x1="379" clip-path="url(#clipPath21)" x2="50" y1="330"
+      /><line y2="50" fill="none" x1="50" clip-path="url(#clipPath21)" x2="50" y1="330"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(122,-8)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
-    ><line y2="200" fill="none" x1="50" clip-path="url(#clipPath19)" x2="50" y1="170"
-      /><line y2="200" fill="none" x1="50" clip-path="url(#clipPath19)" x2="540" y1="200"
-      /><line y2="50" fill="none" x1="540" clip-path="url(#clipPath19)" x2="540" y1="200"
-      /><line y2="62" fill="none" x1="540" clip-path="url(#clipPath19)" x2="534" y1="50"
-      /><line y2="62" fill="none" x1="540" clip-path="url(#clipPath19)" x2="546" y1="50"
+    ><line y2="200" fill="none" x1="50" clip-path="url(#clipPath22)" x2="50" y1="170"
+      /><line y2="200" fill="none" x1="50" clip-path="url(#clipPath22)" x2="540" y1="200"
+      /><line y2="50" fill="none" x1="540" clip-path="url(#clipPath22)" x2="540" y1="200"
+      /><line y2="62" fill="none" x1="540" clip-path="url(#clipPath22)" x2="534" y1="50"
+      /><line y2="62" fill="none" x1="540" clip-path="url(#clipPath22)" x2="546" y1="50"
     /></g
     ><g font-size="11" stroke-linecap="butt" transform="translate(372,142)" stroke-dashoffset="1" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke-dasharray="5" stroke="black" stroke-opacity="1"
-    ><line y2="79" fill="none" x1="50" clip-path="url(#clipPath20)" x2="50" y1="50"
+    ><line y2="79" fill="none" x1="50" clip-path="url(#clipPath23)" x2="50" y1="50"
+    /></g
+    ><g font-size="11" stroke-linecap="butt" transform="translate(672,-38)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke-linejoin="round" stroke="black" stroke-opacity="1"
+    ><line y2="50" fill="none" x1="50" clip-path="url(#clipPath24)" x2="99" y1="50"
+      /><polygon fill="white" clip-path="url(#clipPath24)" points=" 50 50 62 56 62 44" stroke="none"
+      /><polygon fill="none" points=" 50 50 62 56 62 44" clip-path="url(#clipPath24)"
     /></g
     ><g font-size="11" transform="translate(202,192)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke="black" stroke-opacity="1"
-    ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath21)" stroke="none"
+    ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath25)" stroke="none"
       >MemberOf</text
     ></g
     ><g font-size="11" transform="translate(722,132)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke="black" stroke-opacity="1"
-    ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath22)" stroke="none"
+    ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath26)" stroke="none"
       >Removal</text
     ></g
     ><g font-size="11" transform="translate(532,132)" fill-opacity="1" fill="black" text-rendering="geometricPrecision" font-family="sans-serif" stroke="black" stroke-opacity="1"
-    ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath23)" stroke="none"
+    ><text x="9" xml:space="preserve" y="11" clip-path="url(#clipPath27)" stroke="none"
       >Insertion</text
     ></g
     ><g fill="rgb(120,120,120)" text-rendering="geometricPrecision" fill-opacity="1" font-size="8" stroke-opacity="1" stroke="rgb(120,120,120)"