--- a/model/prov-dm.html Mon Apr 16 07:47:36 2012 +0100
+++ b/model/prov-dm.html Mon Apr 16 08:36:27 2012 +0100
@@ -219,7 +219,7 @@
</p>
<p>This document introduces the provenance concepts found in
-PROV-DM, and defines PROV-DM types and
+PROV and defines PROV-DM types and
relations. PROV data model is domain-agnostic, but is equipped with
extensibility points allowing domain-specific information to be included. </p>
@@ -322,7 +322,7 @@
<p>
- PROV-DM is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and
+The PROV data model is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and
application-specific extensions to be defined.
The PROV data model is structured according to six components covering various aspects of provenance:</p>
<ul>
@@ -349,10 +349,10 @@
<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 PROV-DM can be used
+<p><a href="#prov-dm-example">Section 3</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-DM concepts, structured according to six components.</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>
@@ -393,7 +393,7 @@
<section id='starting-points'>
-<h1>PROV-DM Starting Points</h1>
+<h1>PROV Starting Points</h1>
<p>
This section introduces provenance concepts with informal descriptions and illustrative
@@ -647,7 +647,7 @@
<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>Provenance Concepts</b></a></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td></tr>
+<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>
@@ -675,7 +675,7 @@
<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-DM data model, which we introduce in the next section. </p>
+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">
@@ -688,11 +688,11 @@
<section id="prov-n">
<h2>PROV-N: The Provenance Notation</h2>
-<p>A key goal of PROV-DM is the specification of a machine-processable data model for provenance so that applications can retrieve provenance and reason about it. As such, representations of PROV-DM are available in RDF and XML.
+<p>A key goal of PROV is the specification of a machine-processable data model for provenance so that applications can retrieve provenance and reason about it. As such, representations of PROV are available in RDF and XML.
</p>
<p>However, it is important to provide instances of provenance for human consumption, as in this document or elsewhere.
-To this end, PROV-N is a notation for writing instances of the PROV-DM data model in a compact textual form, without the syntactic baggage and constraints coming with a markup language such as XML or a description framework such as RDF. We outline here some of its key design principles. For full details, the reader is referred to the companion specification [[PROV-N]].</p>
+To this end, PROV-N is a notation for writing instances of the PROV data model in a compact textual form, without the syntactic baggage and constraints coming with a markup language such as XML or a description framework such as RDF. We outline here some of its key design principles. For full details, the reader is referred to the companion specification [[PROV-N]].</p>
<ul>
<li>PROV-N expressions adopt a <em>functional notation</em> consisting
@@ -744,7 +744,7 @@
<h2>Illustration of PROV-DM by an Example</h2>
<p>Section <a href="#starting-points">starting-points</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-DM constructs 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>
+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>
<p>The World Wide Web Consortium publishes many technical reports. In this example, we consider a technical report, and describe its provenance.
@@ -857,7 +857,7 @@
</ul>
<p>
-We now paraphrase some PROV-DM descriptions, and illustrate them with the PROV-N notation. We then follow them with a graphical illustration. Full details of the provenance record can be found <a href="examples/w3c-publication1.pn">here</a>.
+We now paraphrase some PROV descriptions, and illustrate them with the PROV-N notation. We then follow them with a graphical illustration. Full details of the provenance record can be found <a href="examples/w3c-publication1.pn">here</a>.
<ul>
<li>There was a technical report, a working draft on the recommendation track (<a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsWD">process:RecsWD</a>), which is an entity so that we can describe its provenance. Similar descriptions exist for all entities.
@@ -920,7 +920,7 @@
</div>
-<p> This simple example has shown a variety of PROV-DM constructs, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. In this example, it happens that all entities were already Web resources, with readily available URIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance <span class="name">ex:act2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the URI scheme developed by W3C is particularly suited for expressing provenance of these reports, since each URI denotes a specific version of a report. It then becomes very easy to relate the various versions, with PROV-DM constructs. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
+<p> This simple example has shown a variety of PROV concepts, such as Entity, Agent, Activity, Usage, Generation, Derivation, and Association. In this example, it happens that all entities were already Web resources, with readily available URIs, which we used. We note that some of the resources are public, whereas others have restricted access: provenance statements only make use of their identifiers. If identifiers do not pre-exist, e.g. for activities, then they can be generated, for instance <span class="name">ex:act2</span>, occurring in the namespace identified by prefix <span class="name">ex</span>. We note that the URI scheme developed by W3C is particularly suited for expressing provenance of these reports, since each URI denotes a specific version of a report. It then becomes easy to relate the various versions with PROV-DM relations. We note that an Association is a ternary relation (represented by a multi-edge labeled wasAssociatedWith) from an activity to an agent and a plan.</p>
</section>
@@ -964,7 +964,7 @@
<li><b>Component 3: derivations.</b> The third component is formed with derivations and derivation subtypes.</li>
<li><b>Component 4: alternate.</b> The fourth component consists of relations linking entities somehow referring to the same thing. </li>
<li><b>Component 5: collections.</b> The fifth component is about collections and concepts capturing their transformation, such as insertion and removal. </li>
-<li><b>Component 6: annotations.</b> The sixth component is concerned with annotations to PROV-DM concepts.</li>
+<li><b>Component 6: annotations.</b> The sixth component is concerned with annotations to PROV-DM instances.</li>
</ul>
@@ -1523,7 +1523,7 @@
<div class="glossary-ref" data-ref="glossary-responsibility"></div>
-<p>PROV-DM offers a mild version of responsibility
+<p>PROV offers a mild version of responsibility
in the form of a relation to represent when an agent acted on another
agent's behalf. So for example someone running a mail program,
the program and the person are both