--- a/model/working-copy/towards-wd4.html Wed Feb 15 21:19:13 2012 +0000
+++ b/model/working-copy/towards-wd4.html Wed Feb 15 21:29:39 2012 +0000
@@ -366,13 +366,13 @@
the activities. So the notion of having some degree of responsibility is really what makes an agent.</p>
-<p>An agents is a particular type of Entity. This means that the model can be
+<p>An agent is a particular type of Entity. This means that the model can be
used to express provenance of the agents themselves. </p>
<div class="anexample" id="agent-example">
<p>
For
- example, a software for checking the use of grammar in a document may be defined as an agent of a document preparation activity, and at the same time one can describe its provenance, including for instance the vendor and the version history.</p>
+ example, software for checking the use of grammar in a document may be defined as an agent of a document preparation activity, and at the same time one can describe its provenance, including for instance the vendor and the version history.</p>
</div>
</section>
@@ -385,15 +385,15 @@
<p>
<div class="glossary" id="glossary-generation">
-<dfn title="concept-generation">Generation</dfn> is the completed production of a new entity by activity.
- This entity become available for usage after this generation. This entity did not exist before generation.
+<dfn title="concept-generation">Generation</dfn> is the completed production of a new entity by an activity.
+ This entity becomes available for usage after this generation. This entity did not exist before generation.
</div>
</p>
<p>
<div class="glossary" id="glossary-usage">
-<dfn title="concept-usage">Usage</dfn> is the beginning on an entity being consumed by an activity.
-Before usage, the activity had not begun to consume or use to this entity (and could not have been affected by the entity).
+<dfn title="concept-usage">Usage</dfn> is the beginning of an entity being consumed by an activity.
+Before usage, the activity had not begun to consume or use this entity (and could not have been affected by the entity).
</div>
</p>
@@ -412,7 +412,7 @@
</div>
-<p>Activities are consumers of entities and producers of entities. In some case, the consumption of entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
+<p>Activities are consumers of entities and producers of entities. In some case, the consumption of an entity influences the creation of another in some way. This notion is captured by derivations, defined as follows.</p>
<p>
<div class="glossary" id="glossary-derivation">
@@ -435,13 +435,13 @@
<p>
<div class="glossary" id="glossary-plan">
-A <dfn title="concept-plan">Plan</dfn> is an entity that represent a set of
+A <dfn title="concept-plan">plan</dfn> is an entity that represents a set of
actions or steps intended by one or more agents to achieve some goals.
</div>
PROV-DM is not
prescriptive about the nature of plans, their representation, the
-actions and steps they consist of, and their intended goals. Since plans may evolve over time,
-it may become necessary to track their provenance, and hence, plans are
+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.</p>
<div class="anexample" id="plan-example">
@@ -454,7 +454,7 @@
<div class="anexample" id="collection-example">
<p>
-An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which document it contained at which point in time, how it was assembled, etc.
+An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point in time, how it was assembled, etc.
</div>
@@ -497,9 +497,9 @@
distinguishing among all the agents that have some association with an
activity and determine which ones are really the originators of the
entity. For example, a programmer and a researcher could both be
-associated with running a workflow, but it may not matter what
+associated with running a workflow, but it may not matter which
programmer clicked the button to start the workflow while it would
-matter a lot what researcher told the programmer to do so. So there
+matter a lot which researcher told the programmer to do so. So there
is some notion of responsibility that needs to be captured. </p>
@@ -528,14 +528,14 @@
</div>
<p>A <dfn title="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents,
-indicating that a "subordinate" agent acted on behalf of a "responsible" agent, in the context of an activity. The nature of this relation is intended to be broad, and includes delegation, contractual relation</p>
+indicating that a "subordinate" agent acted on behalf of a "responsible" agent, in the context of an activity. The nature of this relation is intended to be broad, including delegation or a contractual relation.</p>
<div class="anexample" id="responsibilityChain-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 what
+agents associated with the activity, and it may not matter which
student published a web page but it matters a lot that the department
told the student to put up the web page.
</p>
@@ -878,7 +878,7 @@
From an inter-operability perspective, it is useful to define some basic categories of agents since
it will improve the use of provenance by applications.
There should be very few of these basic categories to keep the model simple and accessible.
-There are three types of agents in the model since they are common across most anticipated domain of use:
+There are three types of agents in the model since they are common across most anticipated domains of use:
<ul>
<li><span class="name">Human</span>: agents of type Human are people. (This type is equivalent to a "foaf:person" [[FOAF]])</li>
<li><span class="name">Organization</span>: agents of type Organization are social institutions such as companies, societies etc. (This type is equivalent to a "foaf:organization"
@@ -939,7 +939,7 @@
<p>Alternatively, a reputation service may enrich a provenance record with notes providing reputation ratings about agents. In the following fragment, both agents <span class="name">ex:Simon</span> and <span class="name">ex:Paolo</span> are rated "excellent".</p>
<pre class="codeexample">
-note(ex3:n2,[ex3:reputation:"excellent"])
+note(ex3:n2,[ex3:reputation="excellent"])
hasAnnotation(ex:Simon,ex3:n2)
hasAnnotation(ex:Paolo,ex3:n2)
</pre>
@@ -1087,11 +1087,11 @@
<h4>Activity Association</h4>
-<p>As far as responsibility is concerned, PROV-DM offers two kinds of constructs. The first, introduced in this section, is relation between an agent, a plan, and an activity; the second, introduced in <a
+<p>As far as responsibility is concerned, PROV-DM offers two kinds of constructs. The first, introduced in this section, is a relation between an agent, a plan, and an activity; the second, introduced in <a
href="#term-responsibility">Section Responsibility</a>, is a relation between agents expressing that an agent was acting on behalf of another, in the context of an activity. </p>
-<p>An <dfn title="dfn-activity-association">activity association</dfn><span class="withAsn">, written <span class="name">wasAssociatedWith(id,a,ag2,pl,attrs)</span> in PROV-ASN,</span> has the following
+<p>An <dfn title="dfn-activity-association">activity association</dfn><span class="withAsn">, written <span class="name">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-ASN,</span> has the following
constituents:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier for the association between an activity and an agent;</li>
@@ -1579,9 +1579,9 @@
<h4>prov:steps</h4>
<p> The attribute <dfn title="dfn-steps"><span class="name">prov:steps</span></dfn> defines the level of precision associated with a derivation. The value associated with a <span
-class="name">prov:steps</span> attribute MUST be <span class="name">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:step</span> occurs at most
-once in a derivation. A derivation without attribute <span class="name">prov:step</span> is considered to be equivalent to the same derivation extended with an extra attribute
-<span class="name">prov:step</span> and associated value <span class="name">"any"</span>. </p>
+class="name">prov:steps</span> attribute MUST be <span class="name">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:steps</span> occurs at most
+once in a derivation. A derivation without attribute <span class="name">prov:steps</span> is considered to be equivalent to the same derivation extended with an extra attribute
+<span class="name">prov:steps</span> and associated value <span class="name">"any"</span>. </p>
<div class="anexample">
<p>The following expression declares an imprecise-1 derivation, which is known to involve one activity, though its identity, usage details of <span class="name">ex:e1</span>, and generation