--- a/model/working-copy/towards-wd4.html Sat Feb 18 21:34:32 2012 +0000
+++ b/model/working-copy/towards-wd4.html Sun Feb 19 22:04:53 2012 +0000
@@ -374,7 +374,8 @@
</p>
-<p>Specifically, an agent can be associated to activities to denote the agent's responsibility for those activities.
+<p>The key purpose of agents is to assign responsibility
+ for activities.
The definition of agent intentionally stays away from using concepts such as enabling, causing, initiating, affecting, etc, because many entities also enable, cause, initiate, and affect in some way
the activities. So the notion of having some degree of responsibility is really what makes an agent.</p>
@@ -429,10 +430,7 @@
<p>
<div class="glossary" id="glossary-derivation">
-<dfn title="concept-derivation">Derivation</dfn> of an entity from an another is a relation that denotes that the dervied entity is transformed from, created from, or affected by the deriving entity.
-</div>
-
-<div class="note">To be further refined in WD5</div>
+<dfn title="concept-derivation">Derivation</dfn> is something by which some entity is transformed from, created from, or affected by another entity in the world. </div>
</p>
@@ -511,14 +509,15 @@
responsibility of agents, and that is a major reason for
distinguishing among all the agents that have some association with an
activity and determine which ones are really the originators of the
-entity.
-<div class="note"> to be revisited for WD5. Paolo's proposed text: "Agents are defined in sec. 2.1 as having some kind of responsibility for activities. However, one may want to be more specific regarding the degrees of an agent's responsibility. For example, ..."</div>
- For example, a programmer and a researcher could both be
+entity. For example, a programmer and a researcher could both be
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 which researcher told the programmer to do so. So there
is some notion of responsibility that needs to be captured. </p>
+<!-- <div class="note"> to be revisited for WD5. Paolo's proposed text: "Agents are defined in sec. 2.1 as having some kind of responsibility for activities. However, one may want to be more specific regarding the degrees of an agent's responsibility. For example, ..."</div>
+-->
+
<p>Provenance reflects activities that have occurred. In some
cases, those activities reflect the execution of a plan that was
@@ -528,7 +527,7 @@
validate the execution as represented in the provenance record, to
manage expectation failures, or to provide explanations.</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>
+<!-- <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>
@@ -554,11 +553,11 @@
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.
</div>
-<div class="note">Propose to rephrase as follows: <br/>
+<!--<div class="note">Propose to rephrase as follows: <br/>
A relation between two agents, denoted <dfn title="concept-responsibilityChain">actedOnBehalfOf</dfn> indicates that
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.
When this relation is used transitively, i.e., one agent acts on behalf of another, who also acts on behalf of another, etc., these relations form a <dfn title="concept-responsibilityChain">responsibility chain</dfn>.
-</div>
+</div>-->
</p>
@@ -1444,7 +1443,7 @@
<ol>
<li>e1 and e2 refer to Bob in two contexts (as Facebook and Twitter users, respectively)
- <li> both of e1 and e2 are more detailed then e3.
+ <li> both of e1 and e2 are more detailed than e3.
</ol>