--- a/model/working-copy/wd6-prov-dm-with-core.html Wed May 23 09:24:47 2012 +0100
+++ b/model/working-copy/wd6-prov-dm-with-core.html Wed May 23 09:52:43 2012 +0100
@@ -340,16 +340,22 @@
<section id="structure-of-this-document">
<h3>Structure of this Document</h3>
-<p><a href="#starting-points">Section 2</a> provides starting points for the PROV Data Model, listing a set of types and relations, which allows users to make initial provenance descriptions.</p>
-
-<p><a href="#prov-dm-example">Section 3</a> illustrates how the PROV data model can be used
+<p><a href="#section-prov-overview">Section 2</a> provides an overview of the PROV Data Model, distinguishing a CORE set of types and relations, commonly found in provenance descriptions, from extended structures catering for advanced uses.</p>
+
+<p><a href="#prov-notation">Section 3</a> overviews the Provenance Notation used to illustrate examples of provenance descriptions.</a>
+
+
+<p><a href="#prov-dm-example">Section 4</a> illustrates how the PROV data model can be used
to express the provenance of a report published on the Web.</p>
-<p><a href="#data-model-components">Section 4</a> provides the definitions of PROV concepts, structured according to six components.</p>
-
-<p><a href="#extensibility-section">Section 5</a> summarizes PROV-DM extensibility points.</p>
-
-<p><a href="#valid-provenance">Section 6</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [[PROV-CONSTRAINTS]].</p>
+
+<p><a href="#data-model-components">Section 5</a> provides the definitions of PROV concepts, structured according to six components.</p>
+
+
+
+<p><a href="#extensibility-section">Section 6</a> summarizes PROV-DM extensibility points.</p>
+
+<p><a href="#valid-provenance">Section 7</a> introduces the idea that constraints can be applied to the PROV data model to refine provenance descriptions; these are covered in the companion specification [[PROV-CONSTRAINTS]].</p>
</section>
@@ -379,13 +385,18 @@
</table>
</div>
+<p>
+ Examples throughout this document use the PROV-N Provenance
+ Notation, briefly introduced in <a href="#prov-notation">Section 3</a> and specified fully in separate document [[PROV-N]].</p>
+
+
</section>
</section>
-<section id='starting-points'>
+<section id='section-prov-overview'>
<h1>PROV Overview</h1>
<p>This section introduces provenance concepts with informal descriptions and illustrative
@@ -410,7 +421,11 @@
</figure>
</div>
-<p>Since PROV-DM is a conceptual data model, <a href="#overview-types-and-relations">Table 2</a> shows the provenance concepts corresponding to types and relations: the first column lists concepts we are introducing in the rest of this section, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen.
+<p>The rest of this section introduces the concepts found in PROV Core structures.
+They are summarized in <a href="#overview-types-and-relations">Table 2</a>, where they are grouped according to
+the types and relations the PROV conceptual data model.
+ The first column lists concepts, the second column indicates whether a concept maps to a type or a relation, whereas the third column contains the corresponding name. Names of relations have a verbal form in the past tense to express what happened in the past, as opposed to what may or will happen.
+</p>
</p>
@@ -418,27 +433,27 @@
<div style="text-align: left;">
<table border="1" style="margin-left: auto; margin-right: auto;">
-<caption id="overview-types-and-relations">Table 2: Mapping of Provenance concepts to types and relations</caption>
-<tr><td><a><b>PROV Concepts</b></a></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td></tr>
+<caption id="overview-types-and-relations">Table 2: Mapping of PROV core concepts to types and relations</caption>
+<tr><td><a><b>PROV Concepts</b></a></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td><td><b>Overview</b></td></tr>
<tr>
-<td><a>Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity">entity</a></td></tr>
-<tr><td><a>Activity</a></td><td><a title="dfn-Activity">activity</a></td></tr>
-<tr><td><a>Agent</a></td><td><a title="dfn-agent">agent</a></td></tr>
+<td><a>Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity">entity</a></td><td style="text-align: center;"><a href="#section-entity-activity">2.1.1</a></td></tr>
+<tr><td><a>Activity</a></td><td><a title="dfn-Activity">activity</a></td><td style="text-align: center;"><a href="#section-entity-activity">2.1.1</a></td></tr>
+<tr><td><a>Agent</a></td><td><a title="dfn-agent">agent</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-responsibility">2.1.2</a></td></tr>
<tr>
-<td><a>Generation</a></td><td rowspan="6" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy">wasGeneratedBy</a></td></tr>
-<tr><td><a>Usage</a></td><td><a title="used">used</a></td></tr>
-<tr><td><a>Attribution</a></td><td><a title="wasAttributedTo">wasAttributedTo</a></td></tr>
-<tr><td><a>Association</a></td><td><a title="wasAssociatedWith">wasAssociatedWith</a></td></tr>
-<tr><td><a>Responsibility</a></td><td><a title="actedOnBehalfOf">actedOnBehalfOf</a></td></tr>
-<tr><td><a>Derivation</a></td><td><a title="wasDerivedFrom">wasDerivedFrom</a></td></tr>
+<td><a>Generation</a></td><td rowspan="6" style="text-align: center;">PROV-DM Relations</td><td><a title="wasGeneratedBy">wasGeneratedBy</a></td><td style="text-align: center;"><a href="#section-entity-activity">2.1.1</a></td></tr>
+<tr><td><a>Usage</a></td><td><a title="used">used</a></td><td style="text-align: center;"><a href="#section-entity-activity">2.1.1</a></td></tr>
+<tr><td><a>Attribution</a></td><td><a title="wasAttributedTo">wasAttributedTo</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-responsibility">2.1.2</a></td></tr>
+<tr><td><a>Association</a></td><td><a title="wasAssociatedWith">wasAssociatedWith</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-responsibility">2.1.2</a></td></tr>
+<tr><td><a>Responsibility</a></td><td><a title="actedOnBehalfOf">actedOnBehalfOf</a></td><td style="text-align: center;"><a href="#section-agents-attribution-association-responsibility">2.1.2</a></td></tr>
+<tr><td><a>Derivation</a></td><td><a title="wasDerivedFrom">wasDerivedFrom</a></td><td style="text-align: center;"><a href="#section-derivation">2.1.3</a></td></tr>
</table>
</div>
-<p>The rest of this section presents the various concepts found in the core of PROV.</p>
+
<!--
-<p><a href="#prov-core-structures">Figure 1</a> is not intended to be complete: it only illustrates types and relations introduced in this section (<a href="#starting-points">Section 2</a>), exploited in the example discussed in <a href="#prov-dm-example">Section 3</a>, and explained in detail in <a href="#data-model-components">Section 4</a>.
+<p><a href="#prov-core-structures">Figure 1</a> is not intended to be complete: it only illustrates types and relations introduced in this section (<a href="#section-prov-overview">Section 2</a>), exploited in the example discussed in <a href="#prov-dm-example">Section 3</a>, and explained in detail in <a href="#data-model-components">Section 4</a>.
Names of relations depicted in <a href="#prov-core-structures">Figure 1</a>
are listed in
the third column of <a href="#overview-types-and-relations">Table 2</a>. These names are part of a textual notation to write instances of the PROV data model, which we introduce in the next section. </p>
@@ -663,7 +678,7 @@
<section id="section-prov-extended-approach-expanded-relation">
<h2>Expanded Relations</h2>
-<p><a href="#core-structures">Section 2.1</a> shows that six concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relations, but require relations to be expanded to n-ary relations.</p>
+<p><a href="#core-structures">Section 2.1</a> shows that six 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.</p>
<p>To illustrate expanded relations, we consider the concept of
@@ -701,7 +716,7 @@
<div class="conceptexample" id="association-example2">
-<p>An examples of association between an activity and an agent involving a plan is:
+<p>An example of association between an activity and an agent involving a plan is:
an XSLT transform launched by a user based on an XSL style sheet (a plan).
</div>
@@ -809,20 +824,11 @@
</section>
-<section id="prov-n">
+<section id="prov-notation">
<h2>The Provenance Notation</h2>
-<div class="note">
-I am unclear where this section should go.
-<ul>
-<li>Completely delete it, since it's the purpose of the prov-n document.
-<li>Move it to a new section "preliminary" (1.3 or 2.): problem, it exposes a serialization too early in this document.
-<li>Move it to appendix: problem, the notation used in section 4/5 is not explained.
-<li>Leave it here ....
-</div>
-
-
-<p>To illustrate the application of PROV concepts to a concrete example (see <a href="#prov-dm-example">Section 3</a>) and to provide examples of concepts (see <a href="#data-model-components">Section 4</a>),
+
+<p>To illustrate the application of PROV concepts to a concrete example (see <a href="#prov-dm-example">Section 4</a>) and to provide examples of concepts (see <a href="#data-model-components">Section 5</a>),
we introduce PROV-N, a notation for writing instances of the PROV data model. For full details, the reader is referred to the companion specification [[PROV-N]].
PROV-N is a notation aimed at human consumption, with the following characteristics:</p>
<ul>
@@ -874,7 +880,7 @@
<section id="prov-dm-example">
<h2>Illustration of PROV-DM by an Example</h2>
-<p><a href="#starting-points">Section 2</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.
+<p><a href="#section-prov-overview">Section 2</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.
With this realistic example, PROV concepts are composed together, and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about the same entity can co-exist, which then justifies the need for provenance of provenance.</p>
@@ -1866,7 +1872,7 @@
-<p>According to <a href="#starting-points">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
+<p>According to <a href="#section-prov-overview">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
underpinning activities performing the necessary actions resulting in such a derivation.
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>