--- a/model/glossary.html Tue Feb 28 14:29:57 2012 +0100
+++ b/model/glossary.html Tue Feb 28 16:58:33 2012 +0100
@@ -29,7 +29,9 @@
</span>
<span class="glossary" id="glossary-derivation">
-<dfn id="concept-derivation">Derivation</dfn> is something by which some entity is transformed from, created from, or affected by another entity in the world.</span>
+A <dfn id="concept-derivation">derivation</dfn> is anything that transforms an entity into another, that creates an entity from another, or modifies an entity to another.</span>
+
+
<span class="glossary" id="glossary-plan">
A <dfn id="concept-plan">plan</dfn> is an entity that represent a set of
@@ -51,10 +53,15 @@
</span>
-<span class="glossary" id="glossary-responsibilityChain">
-A <dfn title="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents,
+<span class="glossary" id="glossary-responsibility">
+For an agent, <dfn title="concept-responsibility">responsibility</dfn> is the fact of being accountable
+for the actions of a "subordinate" agent, in the context of an activity.
+</span>
+
+<!--A <dfn title="concept-responsibility">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.
-</span>
+
+-->
<span class="glossary" id="glossary-activityAssociation">
An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had an active role in the activity. It further allows for a plan to be specified, which is the plan
--- a/model/glossary.js Tue Feb 28 14:29:57 2012 +0100
+++ b/model/glossary.js Tue Feb 28 16:58:33 2012 +0100
@@ -3,7 +3,7 @@
// with <script src="glossary.js" class="remove"></script>
//Insert glossary definitions with the following
// <div class="glossary-ref" ref="glossary-generation"></div>
-glossary_hg='http://dvcs.w3.org/hg/prov/file/0fc6749ae432/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/3f21f68c5afa/model/glossary.html';
glossary_string=
' ' +
'<html> ' +
@@ -36,7 +36,9 @@
'</span> ' +
' ' +
'<span class="glossary" id="glossary-derivation"> ' +
-'<dfn id="concept-derivation">Derivation</dfn> is something by which some entity is transformed from, created from, or affected by another entity in the world.</span> ' +
+'A <dfn id="concept-derivation">derivation</dfn> is anything that transforms an entity into another, that creates an entity from another, or modifies an entity to another.</span> ' +
+' ' +
+' ' +
' ' +
'<span class="glossary" id="glossary-plan"> ' +
'A <dfn id="concept-plan">plan</dfn> is an entity that represent a set of ' +
@@ -58,10 +60,15 @@
'</span> ' +
' ' +
' ' +
-'<span class="glossary" id="glossary-responsibilityChain"> ' +
-'A <dfn title="concept-responsibilityChain">responsibility chain</dfn> is a relation between two agents, ' +
+'<span class="glossary" id="glossary-responsibility"> ' +
+'For an agent, <dfn title="concept-responsibility">responsibility</dfn> is the fact of being accountable ' +
+'for the actions of a "subordinate" agent, in the context of an activity. ' +
+'</span> ' +
+' ' +
+'<!--A <dfn title="concept-responsibility">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. ' +
-'</span> ' +
+' ' +
+'--> ' +
' ' +
'<span class="glossary" id="glossary-activityAssociation"> ' +
'An <dfn title="concept-activityAssociation">activity association</dfn> is an assignment of responsibility to an agent for an activity, indicating that the agent had an active role in the activity. It further allows for a plan to be specified, which is the plan ' +
--- a/model/prov-dm.html Tue Feb 28 14:29:57 2012 +0100
+++ b/model/prov-dm.html Tue Feb 28 16:58:33 2012 +0100
@@ -398,8 +398,7 @@
</p>
-<p>The key purpose of agents is to assign responsibility
- for activities.
+<p>The motivation for introducing agents in the model is to denote the agent's 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>
@@ -473,7 +472,9 @@
prescriptive about the nature of plans, their representation, the
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>
+entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to
+validate the execution as represented in the provenance record, to
+manage expectation failures, or to provide explanations.</p>
<div class="anexample" id="plan-example">
<p>
@@ -518,17 +519,15 @@
</section>
<section id="section-responsibility">
-<h2>Activity Association and Responsibility Chain</h2>
+<h2>Activity Association and Responsibility</h2>
-<p>It is important to reflect that there is a degree in the
-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. For example, a programmer and a researcher could both be
+<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. So there
@@ -540,11 +539,9 @@
<p>Provenance reflects activities that have occurred. In some
cases, those activities reflect the execution of a plan that was
-designed in advance to guide the execution. PROV-DM allows attaching
+designed in advance to guide the execution. PROV-DM allows associating
a plan to an activity, which represents what was intended to
-happen. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to
-validate the execution as represented in the provenance record, to
-manage expectation failures, or to provide explanations.</p>
+happen. </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> -->
@@ -564,7 +561,7 @@
</div>
<p>
-<span class="glossary-ref" ref="glossary-responsibilityChain">
+<span class="glossary-ref" ref="glossary-responsibility">
</span> The nature of this relation is intended to be broad, including delegation or a contractual relation. </p>
<!--<div class="note">Propose to rephrase as follows: <br/>
@@ -1953,25 +1950,11 @@
</div>
-<p>Further considerations:</p>
-<ul>
- <li>Traceability is more general than <a href="#Derivation-Relation">Derivation</a>.
-</ul>
-
-
-<div class='note'>
- I propose to delete the following, given that this document does not mention inferences. [LM]
-<p>Further considerations:</p>
-<ul>
- <li>Traceability is more general than <a href="#Derivation-Relation">Derivation</a>. This means that an assertion of the form: <span class="name">tracedTo(...,e2,e1,...)</span> can be inferred from an assertion of the form:
- <span class="name">wasDerivedFrom(e2,e1,..)</span>. The precise inference rules are specified in [REF].
- <li>Traceability is related to responsibility by way of inference rules that involve <a href="#term-responsibility">responsibility chain</a> and <a href="#term-Generation">generation</a> relations.
- These rules are specified in [REF]
-</ul>
-</div>
-
-<div class="note">looking at the definition, there is something wrong. It's not true that e2 was neceaary for e1 (in the transitive case) and
-that e1 bears responsibility. [LM]</div>
+<p>
+<a href="#Derivation-Relation">Derivation</a> and association are particular cases of traceability.
+</p>
+
+
</section>
--- a/presentations/dagstuhl/prov-dm/overview/index.html Tue Feb 28 14:29:57 2012 +0100
+++ b/presentations/dagstuhl/prov-dm/overview/index.html Tue Feb 28 16:58:33 2012 +0100
@@ -606,7 +606,7 @@
<h2>Responsibility</h2>
<p>
-<div class="glossary-ref" ref="glossary-responsibilityChain">
+<div class="glossary-ref" ref="glossary-responsibility">
</div>
</p>