Issue 14666: Rules for exclusive gateway in choreography too strict (bpmn2-rtf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: Exclusive gateways in choreography are required to use decision data
accessible to all participants involved in the gatway.  But if if the
senders after gateway are the same, then receivers can use event
gateways or event subprocess to wait for event that might never come.
It isn't necessary for the receivers to have access to the decision
data.

Resolution: 
Revised Text: 
Actions taken:
November 19, 2009: received issue
Discussion: 
The FTF agreed that there is a problem that needs fixing, but could not agree on a resolution and deferred its resolution to a future RTF
Disposition: Deferred
End of Annotations:=====
s is issue # 14666

[OMG 14666] Rules for exclusive gateway in choreography too strict

##Source: NIST (Conrad Bock, conrad.bock@nist.gov)
##Original Issue: http://www.osoa.org/jira/browse/BPMN-567
##Original Info: (Severity: Significant - Nature: Revision)

Exclusive gateways in choreography are required to use decision data
accessible to all participants involved in the gatway.  But if if the
senders after gateway are the same, then receivers can use event
gateways or event subprocess to wait for event that might never come.
It isn't necessary for the receivers to have access to the decision
data.