Issue 14738: Notation for alternaitve data input/output sets (bpmn2-rtf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Critical
Summary: Notation for data input/output sets is missing.  I/O sets have a similar
execution effect as decision and merge gateways, so it seems like they
should be visible.

Comments:
From: wstephe created: Fri, 13 Mar 2009 13:50:54 -0500 (CDT)
The decision on this for BPMN 1.X  was that there would be no notation for this since it would probably be too complicated. There was a non-normative suggestion that inputs that belong in the same inputSet could be connected to the same point on the activity, but we didn't want to have anything like pins. I haven't seen any other suggestions. If we had something to look at, then we could consider.
But, in general, in probably should be deferred for now.



Resolution: 
Revised Text: 
Actions taken:
November 20, 2009: received issue
Discussion: 
The FTF Team is not able to allocate time to reach resolution, so we will defer this issue.
Disposition: Deferred
End of Annotations:=====
s is issue # 14738

[OMG 14738] Notation for alternaitve data input/output sets

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

Notation for data input/output sets is missing.  I/O sets have a similar
execution effect as decision and merge gateways, so it seems like they
should be visible.

Comments:
From: wstephe created: Fri, 13 Mar 2009 13:50:54 -0500 (CDT)
The decision on this for BPMN 1.X  was that there would be no notation for this since it would probably be too complicated. There was a non-normative suggestion that inputs that belong in the same inputSet could be connected to the same point on the activity, but we didn't want to have anything like pins. I haven't seen any other suggestions. If we had something to look at, then we could consider.
But, in general, in probably should be deferred for now.