--- a/model/comments/issue-331-Tim.txt Thu Apr 12 18:39:55 2012 +0100
+++ b/model/comments/issue-331-Tim.txt Thu Apr 12 22:32:44 2012 +0100
@@ -106,9 +106,16 @@
> ->
> "This entity did not exist before generation and becomes available for usage after this generation."
>
+
+Done
+
> 6)
> The following could benefit from a rephrasing:
> "A Web site and service selling books on the Web and the company hosting them are software agents and organizations, respectively."
+
+Updated: A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
+
+
>
> 7)
> Section 2.4 seems to be asymmetric.
@@ -116,11 +123,18 @@
> Association has two leading paragraphs (which at first reading
> seem like they should be supporting "attribution" and not
> introducing the subsequent "attribution")
+
+Section was restructured and text trimmed.
+
>
> 8)
> Should tables and figures be numbered?
> "Table (Mapping of Provenance concepts to types and relations in PROV-DM)"
>
+
+Yes, all cross-reference to section should use their number. Will do
+this at the next round, when hopefully structure is stable.
+
> 9)
> The following seems to be out of place, or does not link to the fulfillment of its promise:
> "When examining PROV-DM in details, some relations, while involving two primary elements, are shown to be nary."
--- a/model/prov-dm.html Thu Apr 12 18:39:55 2012 +0100
+++ b/model/prov-dm.html Thu Apr 12 22:32:44 2012 +0100
@@ -497,15 +497,15 @@
<p>
The definition of agent intentionally stays away from using concepts such as enabling, causing, initiating, triggering, affecting, etc, because many entities also enable, cause, initiate, and affect in some way
-the activities. Concepts such as triggers are themselves defined in relations between entities and activities. So the notion of having some degree of responsibility is really what makes an agent.</p>
+the activities. (Concepts such as triggers are themselves defined later in relations between entities and activities.) So the notion of having some degree of responsibility is really what makes an agent.</p>
<div class="anexample" id="agent-example">
<p>
-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. A Web site and service selling books on the Web and the company hosting
-them are also agents.
+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.
+A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
</p>
</div>
@@ -543,21 +543,10 @@
</div>
<p>
-Agents are defined as having some kind of responsibility for activities. However, one may want to be more specific about the nature of an agent's responsibility.
-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. </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>Furthermore, provenance reflects activities that have occurred. In some
+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.
-A plan may be associated to an activity, which represents what was intended to
-happen. </p>
+designed in advance to guide the execution. Thus,
+a plan may also be linked to an activity. </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> -->