913 2004-10-12 13:11:42 +0000 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... 2004-12-01 16:27:43 +0000 1 1 1 Unclassified WS Choreography Primer unspecified Other other RESOLVED WONTFIX http://lists.w3.org/Archives/Public/public-ws-chor/2004Oct/0008.html P2 normal -- 1 steve martin.chapman martin.chapman oldest_to_newest 2508 0 steve 2004-10-12 13:11:42 +0000 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. 2667 1 martin.chapman 2004-12-01 16:27:43 +0000 at nov 04 f2f we decided no change was necessary 20378 2 steve 2008-06-05 13:24:53 +0000 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.