W3C home > Mailing lists > Public > public-ws-chor-comments@w3.org > October 2004

Added as issue 913 (Clarification on workunit guard projection)

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Tue, 12 Oct 2004 14:12:38 +0100
Message-Id: <63C12B8A-1C50-11D9-8308-000393D13C9A@enigmatec.net>
To: WS-Choreography List <public-ws-chor@w3.org>, public-ws-chor-comments@w3.org


Begin forwarded message:

> Resent-From: public-ws-chor@w3.org
> From: "Gary Brown" <gary@enigmatec.net>
> Date: 7 October 2004 13:43:04 BST
> To: <public-ws-chor@w3.org>
> Subject: Clarification on workunit guard projection
> I understand the role of the globalizedTrigger, to provide a guard 
> condition for each role that is relevant to a work unit.
> However, if a work unit does not use a globalizedTrigger, and the 
> guard condition is related to just one of the roles involved in a 
> workunit, then does this mean that the condition at the other roles is 
> non-observable?
> In which case, does it have to determine what the first observable 
> action of the workunit would be, and monitor for it, to determine 
> dynamically if the workunit should be activated at that role? This 
> would mean that additional validation would be required to ensure that 
> the first observable activity (an interaction) was initiated from the 
> role that was associated with the guard condition.
> If this is true, then I think we need to add an additional rule 
> covering this situation, within the workunit section of the spec.
> Regards
> Gary
Received on Tuesday, 12 October 2004 13:12:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:51 UTC