--- a/model/prov-dm.html Wed Mar 28 13:13:15 2012 +0100
+++ b/model/prov-dm.html Wed Mar 28 13:39:14 2012 +0100
@@ -1929,14 +1929,33 @@
<section id="component5">
<h3>Component 5: Collections</h3>
-
-<p><strong>Collection relations and entity types</strong> address the need to describe the evolution of entities that have a collection structure, that is, which may contain other entities. The intent of these relations and entity types is to capture the <em>history of changes that occurred to a collection</em>. Indirectly, such history provides a way to reconstruct, with some limitations discussed <a href="#term-collection-state">below</a>, the contents of a collection entity. Thus, for the purpose of provenance a collection entity is viewed an immutable representation of the state of a collection data structure, following a sequence of insertion and deletion operations.
+<p>The fifth component of PROV-DM is concerned with the notion of collections.
+A collection is an entity that has some parts. The parts are themselves entities, and therefore their provenance can be expressed. In many applications, it is also of interest to be able to express the provenance of the collection itself: e.g. who maintains the collection, which part it contains at which point in time, how it was assembled. The purpose of Component 5 is to define the types and relations that are useful to express the provenance of collections. </p>
+
+<p>Figure <a href="#figure-component5">figure-component5</a> overviews
+the component, which consists of two "UML Class" and three associations.
+</p>
+
+
+<div style="text-align: center;">
+<figure>
+<img src="images/Collections.png" alt="collections"/>
+<figcaption id="figure-component5">Collections Component Overview (TODO)</figcaption>
+</figure>
+</div>
+
+
+<p>The intent of these relations and types is to express the <em>history of changes that occurred to a collection</em>. Indirectly, such history provides a way to reconstruct, the contents of a collection.</p>
+
+<section id="term-collection">
+<h3>Collection</h3>
+
+<span class="glossary-ref" data-ref="glossary-collection"></span>
+
+<p> Thus, for the purpose of provenance a collection entity is viewed an immutable representation of the state of a collection data structure, following a sequence of insertion and deletion operations.
<br/>A collection entity is an entity that has a logical internal structure consisting of key-value pairs, often referred to as a <strong>map</strong>. This collection type provides a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" in some programming languages), relational tables, ordered lists, and more (the specification of such specialized structures in terms of key-value pairs is out of the scope of this document).
-<section id="term-collection-types">
-<h3>Collection types</h3>
-
The following new entity types are introduced:
<ul>