Issue 9327: Ambiguous notations for OR (bpmn-ftf) Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com) Nature: Uncategorized Issue Severity: Summary: Why 2 notations for Data based XOR Why not data and event options for inclusive OR? Resolution: Revised Text: Section 9.5.2, Sub-Section "Data-Based," page 72, Add a Note paragraph after Figure 9.17: "Note - The “X” internal indicator for the Data-Based Exclusive Gateway was included in BPMN to complete the set of indicators for the different types of Gateways (see Figure 9.15). However, it is also understood that most modelers would be familiar with an empty decision diamond that represents an exclusive branching of the process and that most decisions would probably take this form. Thus, Data-Based Exclusive Gateway internal indicator was made optional so that modelers and modeling tools could create diagrams that would conform with the basic flow expectations of modelers." Actions taken: January 30, 2006: received issue April 19, 2007: closed issue Discussion: Resolution: The specification will be modified in Section 9.5.2 to describe the rationale for having the two versions of the Exclusive Gateway. A separate Issue will be generated to evaluation the addition of an Inclusive Event-Based Gateway. End of Annotations:===== ubject: Further BPMN issues Date: Sun, 29 Jan 2006 21:34:26 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Further BPMN issues Thread-Index: AcYlXtWDZBGQwojvTguClGAOoc5ROQ== From: "Pete Rivett" To: , The remainder of those I raised in the AB review, again adjusted to the DAS numbering scheme. Issue C) Ambiguous notations for OR Why 2 notations for Data based XOR To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 9327 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Tue, 8 Aug 2006 16:31:51 -0700 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 08/08/2006 17:31:51, Serialize complete at 08/08/2006 17:31:51 http://www.bpmn.org/FTF/Issues/Issue%209327.htm Description: Why 2 notations for Data based XOR Why not data and event options for inclusive OR? Suggested Resolution: Resolved: The specification will be modified in Section 9.5.2 to describe the rationale for having the two versions of the Exclusive Gateway. A separate Issue will be generated to evaluation the addition of an Inclusive Event-Based Gateway. Revised Text: Section 9.5.2, Sub-Section "Data-Based," page 72, Add a Note paragraph after Figure 9.17: "Note - The .X. internal indicator for the Data-Based Exclusive Gateway was included in BPMN to complete the set of indicators for the different types of Gateways (see Figure 9.15). However, it is also understood that most modelers would be familiar with an empty decision diamond that represents an exclusive branching of the process and that most decisions would probably take this form. Thus, Data-Based Exclusive Gateway internal indicator was made optional so that modelers and modeling tools could create diagrams that would conform with the basic flow expectations of modelers." Why not data and event options for inclusive OR?