--- a/model/working-copy/wd6-prov-dm-with-core.html Mon May 21 14:54:01 2012 -0400
+++ b/model/working-copy/wd6-prov-dm-with-core.html Mon May 21 21:24:12 2012 +0100
@@ -389,22 +389,23 @@
<h1>PROV Overview</h1>
<p>This section introduces provenance concepts with informal descriptions and illustrative
-examples. PROV distinguishes <em>core structures</em>, forming the essence of provenance descriptions, from <em>extended structures</em> catering for more advanced uses of provenance. Core and extended structures are respectively presented in <a href="#core-structures">Section 2.1.1</a> and <a href="#extended-structures">Section 2.1.2</a>.
+examples. PROV distinguishes <em>core structures</em>, forming the essence of provenance descriptions, from <em>extended structures</em> catering for more advanced uses of provenance. Core and extended structures are respectively presented in <a href="#core-structures">Section 2.1</a> and <a href="#section-extended-structures">Section 2.2</a>. Furthermore, the PROV data model is organized according to components, which are thematic groupings of concepts, overviewed in <a href="#section-overview-components">Section 2.3</a>.
+</p>
<section id='core-structures'>
<h1>PROV Core Structures</h1>
-<p>PROV core consists of essential provenance structures commonly found in provenance descriptions.
+<p>The core of PROV consists of essential provenance structures commonly found in provenance descriptions.
It is summarized graphically by
the UML diagram of <a href="#prov-core-structures">Figure 1</a>,
-illustrating three types (entity, activity, and agent) and how they relate to each other. In PROV Core, all relations are binary. </p>
+illustrating three types (entity, activity, and agent) and how they relate to each other. In the core of PROV, all relations are binary. </p>
<div style="text-align: center; ">
<figure style="max-width: 70%; " >
<!-- <img src="uml/essentials.svg" alt="PROV Core Structures" style="max-width: 70%; " /> -->
- <img src="../images/OverviewDiagram.png" alt="Simplified Overview of PROV-DM" style="max-width: 70%; " />
+ <img src="../images/OverviewDiagram.png" alt="PROV Core Structures" style="max-width: 70%; " />
<figcaption id="prov-core-structures">Figure 1: PROV Core Structures</figcaption>
</figure>
</div>
@@ -433,7 +434,7 @@
</table>
</div>
-<p>The rest of this section presents the various concepts found in PROV core.</p>
+<p>The rest of this section presents the various concepts found in the core of PROV.</p>
<!--
@@ -625,7 +626,7 @@
</section>
-<section id="section-prov-extended">
+<section id="section-extended-structures">
<h2>PROV Extended Structures</h2>
<p>While the core of PROV focuses on essential provenance structures commonly found in provenance descriptions, extended structures
@@ -638,8 +639,8 @@
<section id="section-prov-extended-mechanisms">
<h2>Mechanisms to Define Extended Structures</h2>
-<p>Extended structures are defined by a variety of mechanisms that we
-outline in this section: subtyping, expanded relations, optional
+<p>Extended structures are defined by a variety of mechanisms
+outlined in this section: subtyping, expanded relations, optional
identification, and new relations.</p>
@@ -670,9 +671,9 @@
in <a href="#section-agents-attribution-association-responsibility">section
2.1.2</a>. Agents may adopt sets of actions or steps to achieve their
goals in the context of an activity: this is captured by the notion of
-plan. Hence, an activity may reflect the execution of a plan that was
+plan. Thus, an activity may reflect the execution of a plan that was
designed in advance to guide the execution. Hence, an expanded
-association relation allows a plan a plan be linked to an
+association relation allows a plan be linked to an
activity. Plan is defined by subtyping and full association by an expanded relation, as follows. </p>
<p>
@@ -710,19 +711,19 @@
<section id="section-prov-extended-approach-optional-identification-new-relation">
<h2>Optional Identification and New Relations</h2>
-<p>We have seen that some concepts exhibit a core use, expressed as
+<p>Some concepts exhibit both a core use, expressed as
binary relation, and an extended use, expressed as n-ary relation. In
some cases, mapping the concept to a relation, whether binary or
n-ary, is not sufficient: instead, it may be required to able to
-identify an instance.</p>
+identify an instance of such concept.</p>
<p>In such circumstances, PROV-DM allows an optional identifier to be
expressed to identify an instance of an association between two or
-more elements. These identifier can then be referred to as part of
-other concepts.</p>
+more elements. This optional identifier can then be used to refer to
+an instance as part of other concepts.</p>
<div class="conceptexample" id="identifier-example">
-<p>A service may read a same configuration file on two different occasion: each usage can be identifed by its own identifier, allowing them to be distinguished.
+<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>
<p>Finally, PROV-DM supports further relations that are not subtypes or expanded versions of existing relations.</p>
@@ -780,6 +781,31 @@
</section>
+
+<section id="section-overview-components">
+<h2>Modular Organization</h2>
+
+<p>Besides the separation between core and extended structures, PROV-DM
+is further organized according to components, grouping concepts in a
+thematic manner. </p>
+
+<p> <a href="#components-overview">Table 3</a> enumerates the six components, five of which have already been implicitly overviewed in this section. All components offer extended structures, whereas the first three only offer core structures.
+
+<div id="components-overview-div" style="text-align: center;">
+<table border="1" style="margin-left: auto; margin-right: auto;">
+<caption id="components-overview">Table 3: Components Overview</caption>
+<tr><td></td><td>Component</td><td>Core <br>Structures</td><td>Extended</br> Structures</td><td>Overview</td><td>Descriptions</td></tr>
+<tr><td>1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr>
+<tr><td>2</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td>✔</td><td><a href="#section-entity-activity">2.1.2</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr>
+<tr><td>3</td><td style="text-align: left;">Derivation</td><td>✔</td><td>✔</td><td><a href="#section-entity-activity">2.1.3</a></td><td style="text-align: left;">about derivations and its subtypes</td></tr>
+<tr><td>4</td><td style="text-align: left;">Alternate</td><td></td><td>✔</td><td>—<td style="text-align: left;">about relations linking entities referring the same thing</td></tr>
+<tr><td>5</td><td style="text-align: left;">Bundles</td><td></td><td>✔</td><td><a href="#section-entity-activity">2.2.2</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr>
+<tr><td>6</td><td style="text-align: left;">Collections</td><td></td><td>✔</td><td><a href="#section-entity-activity">2.2.3</a></td><td style="text-align: left;">about collections and concepts capturing their transformation, such as insertion and removal</td></tr>
+</table>
+</div>
+
+</section>
+
</section>