integrated optional agent in association
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Fri, 16 Mar 2012 08:32:54 +0000
changeset 1913 41997a5c3b5c
parent 1912 9f00ccf2eb9a
child 1914 8fce4d94ec82
integrated optional agent in association
model/working-copy/wd5-prov-dm-components.html
--- a/model/working-copy/wd5-prov-dm-components.html	Fri Mar 16 08:28:44 2012 +0000
+++ b/model/working-copy/wd5-prov-dm-components.html	Fri Mar 16 08:32:54 2012 +0000
@@ -1283,21 +1283,18 @@
 
 <div class="glossary-ref" ref="glossary-activityAssociation" withspan="true"></div>
 
-<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><div class="attributes" id="attributes-activity-association">An <dfn title="dfn-activity-association">activity association</dfn><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id,a,ag,pl,attrs)</span> in PROV-N,</span> has the following
 constituents:
 <ul>
 <li><span class='attribute'>id</span>:  an OPTIONAL identifier for the association between an activity and an agent;</li> 
 <li><span class='attribute'>activity</span>: an identifier for the activity;</li>
-<li><span class='attribute'>agent</span>: an identifier for the agent associated with the activity;</li>
+<li><span class='attribute'>agent</span>: an OPTIONAL identifier for the agent associated with the activity;</li>
 <li><span class='attribute'>plan</span>: an OPTIONAL identifier for the plan adopted by the agent in the context of this activity;
 <li><span class='attribute'>attributes</span>: an OPTIONAL set of attribute-value pairs that describe the modalities of association of this activity with this agent.</li>
 </ul></div>
 
-<div class="anexample">
+<div class="anexample id="anexample-wasAssociateWith">
 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>.   
 <pre class="codeexample">
 activity(ex:a,[prov:type="workflow execution"])
@@ -1312,6 +1309,20 @@
 for instance.
 </div>
 
+<div class="anexample id="anexample-wasAssociateWith-2">
+In some cases, one wants to indicate a plan was followed, without having to specify which agent was involved.
+<pre class="codeexample">
+activity(ex:a,[prov:type="workflow execution"])
+wasAssociatedWith(ex:a,-,ex:wf)
+entity(ex:wf,[prov:type="prov:Plan"%% xsd:QName, ex:label="Workflow 1", 
+              ex:url="http://example.org/workflow1.bpel" %% xsd:anyURI])
+</pre>
+In this case, it is assumed that an agent exists, but simply it has not been specified.
+</div>
+
+
+
+
 <div class='issue'> The activity association record does not allow for a plan to be asserted without an agent.
 This seems over-restrictive. Discussed in the context of <a href="http://www.w3.org/2011/prov/track/issues/203">ISSUE-203</a>.</div>
 
@@ -1319,8 +1330,7 @@
 <div class='issue'> Agents should not be inferred. WasAssociatedWith should also work with entities.
 This is <a href="http://www.w3.org/2011/prov/track/issues/206">ISSUE-206</a>.</div>
 
-
-</section>
+</section>  <!-- end wasAssociatedWith -->
 
 <section id="term-responsibility">