--- a/model/working-copy/wd6-prov-dm-with-core.html Wed May 23 11:55:29 2012 +0100
+++ b/model/working-copy/wd6-prov-dm-with-core.html Wed May 23 12:35:33 2012 +0100
@@ -332,7 +332,7 @@
<p>This specification presents the key concepts of the PROV Data Model, and
provenance types and relations, without specific concern for how they are applied.
-With these, it becomes possible to write useful provenance descriptions, and publish or embed them along side the data they relate to. </p>
+With these, it becomes possible to write useful provenance descriptions, and publish or embed them alongside the data they relate to. </p>
<p>However, if something about which provenance is expressed is subject to change, then it is challenging to express its provenance precisely (e.g. the data from which a daily weather report is derived changes from day to day).
To address this challenge, a <em>refinement</em> is proposed to enrich simple provenance, with extra descriptions that help qualify the specific subject of provenance and provenance itself, with attributes and temporal information, intended to satisfy a comprehensive set of constraints. These aspects are covered in the companion specification [[PROV-CONSTRAINTS]].
@@ -615,8 +615,8 @@
<div class="conceptexample" id="responsibility-example">
<p>A student publishing a web page describing an academic
department could result in both the student and the department being
-agents associated with the activity, and it may not matter which
-student published a web page but it matters a lot that the department
+agents associated with the activity. It may not matter which actual
+student published a web page, but it may matter significantly that the department
told the student to put up the web page.
</p>
</div>
@@ -627,7 +627,7 @@
-<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>Activities utilize entities and produce 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>
@@ -688,7 +688,7 @@
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. Thus, an activity may reflect the execution of a plan that was
+a 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 be linked to an
activity. Plan is defined by subtyping and full association by an expanded relation, as follows. </p>
@@ -776,7 +776,7 @@
<h2>Collections</h2>
<p>
-<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> This concept allows for the provenance of the collection itself to be expressed in addition to that of the members. Many different types of collections exist, such as a <em>set</em>, <em>dictionaries</em>, or <em>lists</em>, all of which involve a membership relationship between the constituents and the collection. </p>
+<span class="glossary-ref" data-ref="glossary-collection" data-withspan="true"></span> This concept allows for the provenance of the collection itself to be expressed in addition to that of the members. Many different types of collections exist, such as a <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>, all of which involve a membership relationship between the constituents and the collection. </p>
<div class="conceptexample" id="collection-example">
<p>
@@ -834,12 +834,12 @@
<li>
PROV-N <em>optional arguments</em> need not be specified:
-the general rule for optional arguments is that, if none of them are used in the expression, then they are simply omitted, resulting in a simpler expression. However, it may be the case that only some of the optional arguments need to be specified. Because the position of the arguments in the expression matters, in this case an additional marker must be used to indicate that a particular term is not available. The syntactic marker <span class="name">-</span> is used for this purpose.
+the general rule for optional arguments is that, if none of them are used in the expression, then they are simply omitted, resulting in a simpler expression. However, it may be the case that only some of the optional arguments need to be specified. Because the position of the arguments in the expression matters, in this case an additional marker must be used to indicate that a particular term is not available. The syntactic marker '<span class="name">-</span>' is used for this purpose.
</li>
<li>Most expressions
include an identifier
-and a set of attribute-value pairs; both are optional unless otherwise specified. By convention, the identifier occurs in the <em>first position</em>, and the the set of attribute-value pairs in the <em>last position</em>.
+and a set of attribute-value pairs; both are optional unless otherwise specified. By convention, the identifier occurs in the <em>first position</em>, and the set of attribute-value pairs in the <em>last position</em>.
Consistent with the convention on arguments, the marker <span class="name">-</span> can be used when the identifier is not available, or can be omitted altogether with no ambiguity arising.
</li>
</ul>
@@ -974,7 +974,7 @@
</p>
<p>
-We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well defined URIs (some of which refer archived email messages, available to W3C Members).</p>
+We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined URIs (some of which refer archived email messages, available to W3C Members).</p>
<ul>
<li> Two versions of a document were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
@@ -1107,7 +1107,7 @@
<h2>PROV-DM Types and Relations</h2>
<p>Provenance concepts, expressed as PROV-DM types and relations, are structured according to six components that are introduced in this section.
-Components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another also sits above it in this figure.
+The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another also sits above it in this figure.
PROV-DM consists of the following components.</p>
<div id="prov-dm-components-ul">
@@ -1428,8 +1428,8 @@
<span class="name">ex:Bob</span>.
<pre class="codeexample">
activity(ex:foot_race)
+entity(ex:bang)
wasStartedBy(ex:foot_race, ex:bang, -, 2012-03-09T08:05:08-05:00)
-entity(ex:bang)
agent(ex:Bob)
wasAttributedTo(ex:bang, ex:Bob)
</pre>
@@ -1506,7 +1506,7 @@
<li> an entity is time limited: e.g. the BBC news site on April 3rd, 2012;
<li> an entity attribute is changing: e.g. the traffic light changed from green to red.
</ul>
-<p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting. In the last two cases, there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the traffic light became red and therefore is regarded as a different entity to the green light.
+<p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting. In the last three cases, there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the traffic light became red and therefore is regarded as a different entity to the green light.
</p>
@@ -1629,7 +1629,7 @@
<section id="component2">
<h3>Component 2: Agents and Responsibility</h3>
-<p>The second component of PROV-DM, depicted in Figure <a href="#figure-component2">figure-component2</a>, is concerned with <a title="agent">agents</a> and the notions of
+<p>The second component of PROV-DM, depicted in <a href="#figure-component2">Figure 6</a>, is concerned with <a title="agent">agents</a> and the notions of
<a>Attribution</a>, <a>Association</a>, <a>Responsibility</a>, relating agents to entities, activities, and agents, respectively.
Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise the subclass <a>Plan</a> and UML association classes to express expanded n-ary relations.
</p>
@@ -1660,7 +1660,7 @@
<p>
It is useful to define some basic categories of agents from an interoperability perspective.
-There are three types of agents that are common across most anticipated domains of use; It is acknowledged that these types do not cover all kinds of agent. </p>
+There are three types of agents that are common across most anticipated domains of use; it is acknowledged that these types do not cover all kinds of agent. </p>
<ul>
<li><span class="name">SoftwareAgent</span>
<div class="glossary-ref" data-ref="glossary-software-agent"></div>
@@ -1743,7 +1743,7 @@
</ul></div>
<div class="anexample" id="anexample-wasAssociateWith">
-<p>In the following example, a designer and an operator agents are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an an entity of type <span class="name"><a>plan</a></span>. </p>
+<p>In the following example, a designer agent and an operator agent are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an an entity of type <span class="name"><a>plan</a></span>. </p>
<pre class="codeexample">
activity(ex:a, [prov:type="workflow execution"])
agent(ex:ag1, [prov:type="operator"])
@@ -1875,7 +1875,7 @@
<p><div class="attributes" id="attributes-derivation">A <dfn title="wasDerivedFrom">derivation</dfn><span class="withPn">, written <span class="pnExpression" id="pn-wasDerivedFrom">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="derivation.id">id</span>: an OPTIONAL identifier for a derivation;</li>
-<li><span class='attribute' id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name">ee</span>) of the entity generated by the derivation;</li>
+<li><span class='attribute' id="derivation.generatedEntity">generatedEntity</span>: the identifier (<span class="name">e2</span>) of the entity generated by the derivation;</li>
<li><span class='attribute' id="derivation.usedEntity">usedEntity</span>: the identifier (<span class="name">e1</span>) of the entity used by the derivation;</li>
<li><span class='attribute' id="derivation.activity">activity</span>: an OPTIONAL identifier (<span class="name">a</span>) for the activity using and generating the above entities;</li>
<li><span class='attribute' id="derivation.generation">generation</span>: an OPTIONAL identifier (<span class="name">g2</span>) for the generation involving the generated entity (<span class="name">e2</span>) and activity;</li>
@@ -2044,7 +2044,7 @@
some responsibility for <span class="name">e2</span>'s existence.
-<p>A <dfn title="tracedTo">Trace</dfn> relation <span class="withPn">, written <span class="pnExpression">tracedTo(id;e2,e1,attrs)</span> in PROV-N,</span> has:</p>
+<p>A <dfn title="tracedTo">Trace</dfn> relation<span class="withPn">, written <span class="pnExpression">tracedTo(id;e2,e1,attrs)</span> in PROV-N,</span> has:</p>
<ul>
<li><span class='attribute' id="trace.id">id</span>: an OPTIONAL identifier identifying the relation;</li>
<li><span class='attribute' id="trace.entity">entity</span>: an identifier (<span class="name">e2</span>) for an entity;
@@ -2120,11 +2120,11 @@
<p>
-<div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization</dfn> relation<span class="withPn">, written <span class="pnExpression">specializationOf(sub, super)</span> in PROV-N,</span> has:
+<div class="attributes" id="attributes-specialization">A <dfn title="specializationOf">specialization</dfn> relation<span class="withPn">, written <span class="pnExpression">specializationOf(infra, supra)</span> in PROV-N,</span> has:
<ul>
-<li><span class='attribute' id="specialization.specializedEntity">specializedEntity</span>: an identifier (<span class="name">sub</span>) of the specialized entity;</li>
-<li><span class='attribute' id="specialization.generalEntity">generalEntity</span>: an identifier (<span class="name">super</span>) of the entity that is being specialized.</li>
+<li><span class='attribute' id="specialization.specialization">specialization</span>: an identifier (<span class="name">infra</span>) of the specialized entity;</li>
+<li><span class='attribute' id="specialization.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) of the entity that is being specialized.</li>
</ul>
</div>
@@ -2696,7 +2696,7 @@
<span class="glossary-ref" data-ref="glossary-membership"></span>
<p>
-The insertion and removal relations make insertions and removals explicit as part of the history of a dictionary. This, however, requires explicit mention of the state of the dictionary prior to each operation. The membership relation removes this needs, allowing the state of a dictionary <span class="name">c</span> to be expressed without having to introduce a prior state.</p>
+The insertion and removal relations make insertions and removals explicit as part of the history of a dictionary. This, however, requires explicit mention of the state of the dictionary prior to each operation. The membership relation removes this need, allowing the state of a dictionary <span class="name">c</span> to be expressed without having to introduce a prior state.</p>
<p>
<div class="attributes" id="attributes-memberOf">
@@ -2786,8 +2786,9 @@
<p>A <dfn id="dfn-namespaceDeclaration">namespace declaration</dfn> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this
-declaration refers to this namespace.
-A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name in the scope of this default namespace declaration
+declaration refers to this namespace. </p>
+
+<p>A <dfn id="dfn-defaultNamespaceDeclaration">default namespace declaration</dfn> consists of a namespace. Every un-prefixed qualified name in the scope of this default namespace declaration
refers to this namespace.</p>
<p>The <dfn title="prov-namespace">PROV namespace</dfn> is identified by the URI <a href="http://www.w3.org/ns/prov#">http://www.w3.org/ns/prov#</a>.</p>
@@ -3054,7 +3055,7 @@
<h2>PROV-DM Extensibility Points</h2>
-<p>The PROV data model provides extensibility points that allow designers to specialize it to specific applications or domains. We summarize these extensibility points here:
+<p>The PROV data model provides extensibility points that allow designers to specialize it for specific applications or domains. We summarize these extensibility points here:
<ul>
<li> Attribute-value lists occur in all types and relations of the data model. Applications designers are free to introduce further application-specific attributes. Attributes for a given application can be distinguished by qualifying them with a prefix denoting a namespace