--- a/model/working-copy/wd6-prov-dm-with-core.html Mon May 21 09:15:35 2012 +0100
+++ b/model/working-copy/wd6-prov-dm-with-core.html Mon May 21 11:21:48 2012 +0100
@@ -386,18 +386,68 @@
<section id='starting-points'>
-<h1>PROV Starting Points</h1>
-
-<p>
-This section introduces provenance concepts with informal descriptions and illustrative
-examples. Since PROV-DM is a conceptual data
-model, Section 2.5 maps the concepts to various types and relations,
-which are illustrated graphically in
-a simplified UML diagram in <a href="#prov-dm-overview">Figure 1</a>. Section 2.6
-then summarizes the PROV notation allowing instances of PROV-DM to be
-written down.
+<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>.
+
+
+<section id='core-structures'>
+<h1>PROV Core Structures</h1>
+
+<p>PROV core 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>
+
+
+<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%; " />
+<figcaption id="prov-core-structures">Figure 1: PROV Core Structures</figcaption>
+ </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>
+
+
+
+<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>
+<tr>
+<td><a>Entity</a></td><td rowspan="3">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>
+<tr>
+<td><a>Generation</a></td><td rowspan="6">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>
+</table>
+</div>
+
+<p>The rest of this section presents the various concepts found in PROV core.</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>.
+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>
+
+-->
+
+
+
+
+
<form action="#"><p>
<input id="hide-examples" onclick="set_display_by_class('div','conceptexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button"
value="Hide Concept Examples" />
@@ -440,11 +490,6 @@
<p>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.</p>
</div>
-</section>
-
- <section id="section-generation-usage-derivation">
-<h2>Generation, Usage, Derivation</h2>
-
<p>Activities and entities are associated with each other in two different ways: activities utilize entities and activities produce entities. The act of utilizing or producing an entity may have a duration.
The term 'generation' refers to the completion of the act of producing; likewise, the term 'usage' refers to the beginning of the act of utilizing entities. Thus, we define the following notions of generation and usage. </p>
@@ -475,20 +520,9 @@
</div>
-<p>Activities utilize entities and producer entities. In some cases, utilizing an entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
-
-<p>
-<span class="glossary-ref" data-ref="glossary-derivation" data-withspan="true"></span>
-
-
-
-<div class="conceptexample" id="derivation-example">
-<p>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.</p>
-</div>
-
</section>
+
<section id="section-agents-attribution-association-responsibility">
<h2>Agents, Attribution, Association, and Responsibility</h2>
@@ -517,28 +551,6 @@
</div>
-<p>Agents may adopt sets of actions or steps to achieve their goals. This is captured by the notion of plan. </p>
-
-<p>
-<span class="glossary-ref" data-ref="glossary-plan" data-withspan="true">
-</span>
-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
-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.</p>
-
-<div class="conceptexample" id="plan-example">
-<p>
-A plan can be a blog post tutorial for how to set up a web server, a list of instructions for a micro-processor execution, a cook's written recipe for a chocolate cake, or a workflow for a scientific experiment.
-</p>
-</div>
-
-
-
-
<p>Agents can be related to entities, activities, and other agents.</p>
@@ -550,16 +562,13 @@
</div>
<p>
-Agents are defined as having some kind of responsibility for activities. In some
-cases, those activities reflect the execution of a plan that was
-designed in advance to guide the execution. Thus,
-a plan may also be linked to an activity. </p>
+Agents are defined as having some kind of responsibility for activities. </p>
<!-- <div class="note">Proposal: remove the above para as it repeats from 2.3. Proposed text: "the <em>activity association</em> relation provides a way to indicate that an agent is responsible for an activity, possibly with an associated plan."[PM]</div> -->
<p>
-<span class="glossary-ref" data-ref="glossary-activityAssociation" data-withspan="true"></span>
+<span class="glossary-ref" data-ref="glossary-core-association" data-withspan="true"></span>
</p>
<div class="conceptexample" id="association-example">
@@ -568,7 +577,6 @@
<li>creation of a web page under the guidance of a designer;</li>
<li>various forms of participation in a panel discussion, including audience member, panelist, or panel chair;</li>
<li>a public event, sponsored by a company, and hosted by a museum;</li>
-<li>an XSLT transform launched by a user based on an XSL style sheet (a plan).</li>
</ul>
</div>
@@ -596,6 +604,74 @@
</div>
</section>
+ <section id="section-derivation">
+<h2>Derivation</h2>
+
+
+
+<p>Activities utilize entities and producer entities. In some cases, utilizing an entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
+
+<p>
+<span class="glossary-ref" data-ref="glossary-derivation" data-withspan="true"></span>
+
+
+
+<div class="conceptexample" id="derivation-example">
+<p>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.</p>
+</div>
+
+</section>
+
+</section>
+
+<section id="section-prov-extended">
+<h2>PROV Extended Structures</h2>
+
+<section id="section--prov-extended-appraoch">
+<h2>Approach</h2>
+
+<p>Subtyping, expanded relations, new relations.</p>
+
+
+<p>Agents may adopt sets of actions or steps to achieve their goals. This is captured by the notion of plan. </p>
+<p>In some
+cases, those activities reflect the execution of a plan that was
+designed in advance to guide the execution. Thus,
+a plan may also be linked to an activity. </p>
+<p>
+<span class="glossary-ref" data-ref="glossary-plan" data-withspan="true">
+</span>
+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
+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.</p>
+
+<div class="conceptexample" id="plan-example">
+<p>
+A plan can be a blog post tutorial for how to set up a web server, a list of instructions for a micro-processor execution, a cook's written recipe for a chocolate cake, or a workflow for a scientific experiment.
+</p>
+</div>
+
+
+<div class="conceptexample" id="association-example2">
+<p>Examples of association between an activity and an agent are:
+<ul>
+<li>an XSLT transform launched by a user based on an XSL style sheet (a plan).</li>
+</ul>
+</div>
+
+
+
+
+
+</section>
+
+
+
<section id="section-provenance-of-provnance">
<h2>Provenance of Provenance</h2>
@@ -638,54 +714,9 @@
- <section id="section-UML">
-<h2>Simplified Overview Diagram</h2>
-
-<p>So far, we have introduced a series of concepts underpinning provenance. PROV-DM is a conceptual data model consisting of types and relations between these. <a href="#overview-types-and-relations">Table 2</a> shows how provenance concepts can be mapped to types and relations in PROV-DM: the first column lists concepts introduced in 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>
-
-
-<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>
-<tr>
-<td><a>Entity</a></td><td rowspan="3">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>
-<tr>
-<td><a>Generation</a></td><td rowspan="6">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>
-</table>
-</div>
-
-<p><a href="#prov-dm-overview">Figure 1</a> illustrates the three types (entity, activity, and agent) and how they relate to each other. At this stage, all relations are shown to be binary. Definitions of <a href="#data-model-components">Section 4</a> reveal that some relations, while involving two primary elements, are n-ary. </p>
-
-
-<div style="text-align: center; ">
- <figure style="max-width: 70%; " >
- <img src="images/OverviewDiagram.png" alt="Simplified Overview of PROV-DM" style="max-width: 70%; " />
-<figcaption id="prov-dm-overview">Figure 1: Simplified Overview of PROV-DM</figcaption>
- </figure>
-</div>
-
-<p><a href="#prov-dm-overview">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>.
-Names of relations depicted in <a href="#prov-dm-overview">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>
-
-<!--
-<div class="note">
- TODO: short text required to explain the overview diagram
-<p>I have the impression that the diagram presented in Section 2.5 would
- > be more useful if placed at the beginning of Section 2 [KB]
-</div>
--->
</section>
+
+
<section id="prov-n">
<h2>PROV-N: The Provenance Notation</h2>