This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 913 - Clarification on workunit guard projectionI 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 re...
Summary: Clarification on workunit guard projectionI understand the role of the global...
Status: RESOLVED WONTFIX
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Primer (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: Martin Chapman
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-12 13:11 UTC by Steve Ross-Talbot
Modified: 2004-12-01 16:27 UTC (History)
0 users

See Also:

Attachments

Description Steve Ross-Talbot 2004-10-12 13:11:42 UTC 
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.
Comment 1 Martin Chapman 2004-12-01 16:27:43 UTC 
at nov 04 f2f we decided no change was necessary
Comment 2 Steve Ross-Talbot 2008-06-05 13:24:53 UTC 
The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

Clarification on workunit guard projectionI 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.