Issue 15743: Pages 285-287. Missing Events types (bpmn2-rtf)
Source:  (, )
Nature: Revision
Severity: Significant
Summary: i) Chapter/Section  10.4.2. Page 269. Table  10.93. 
Boundary Interrupting Events are: error, cancel, compensation, message, timer, escalation, conditional, signal, multiple and parallel multiple.


Boundary Non-interrupting Events are: message, timer, escalation, conditional, signal, multiple and parallel multiple.


Event Sub-Process Interrupting Events are: error, compensation,  message, timer, escalation, conditional, signal, multiple and parallel multiple.


Event Sub-Process Non-interrupting Events are:  message, timer, escalation, conditional, signal, multiple and parallel multiple.



ii) Chapter/Section  10.4.6. Page 285. Subsection “Handling Events attached to an Activity (Intermediate boundary Events and Event Sub-Processes)”. It says:


“For boundary Events, handling consists of consuming the Event occurrence and either canceling the Activity the Event is 
attached to, followed by normal Sequence Flows leaving that Activity, or by running an Event Handler without canceling the 
Activity (only for Message, Signal, Timer and Conditional Events, not for Error Events).”


iii) Chapter/Section  10.4.6. Page 287. It says:
“For an interrupting Event (Error, Escalation, Message, Signal, Timer, Conditional, Multiple, and Parallel Multiple), 
only one Event Sub-Process for the same Event Declaration MUST be modeled.”


COMMENTS:


In (ii) Escalation, Multiple and Parallel Multiple are not mentioned as Boundary Non-Interrupting. Furthermore, 
Cancel and Compensations are not mentioned  as Boundary Events that always interrupt.


In (iii) Compensation is not mentioned as an interrupting Event for an Event Sub-Process.



SUGGESTIONS:


In (ii) 
“(only for Message, Signal, Timer and Conditional Events, not for Error Events)”   should be replaced by  “(only for Message, 
Signal, Timer, Conditional, Escalation, Multiple and Parallel Multiple Events, not for Error, Cancel and Compensation 
Events)”


In (iii) 
“(Error, Escalation, Message, Signal, Timer, Conditional, Multiple, and Parallel Multiple)”   should be replaced by  “Error, Escalation, Message, Signal, Timer, Conditional, Compensation, Multiple, and Parallel Multiple)”
Resolution: 
Revised Text: 
Actions taken:
October 15, 2010: received issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
Date: 15 Oct 2010 00:35:39 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Eduardo Jara
Employer:        
mailFrom:        ejara@craftware.net
Terms_Agreement: I agree
Specification:   BPMN 2.0 Beta 2
Section:         10.4.6
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         Day
Page:            285, 287
Title:           Pages 285-287. Missing Events types
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


ANTECEDENTS:


i) Chapter/Section  10.4.2. Page 269. Table  10.93. 
Boundary Interrupting Events are: error, cancel, compensation, message, timer, escalation, conditional, signal, multiple and parallel multiple.


Boundary Non-interrupting Events are: message, timer, escalation, conditional, signal, multiple and parallel multiple.


Event Sub-Process Interrupting Events are: error, compensation,  message, timer, escalation, conditional, signal, multiple and parallel multiple.


Event Sub-Process Non-interrupting Events are:  message, timer, escalation, conditional, signal, multiple and parallel multiple.



ii) Chapter/Section  10.4.6. Page 285. Subsection .Handling Events attached to an Activity (Intermediate boundary Events and Event Sub-Processes).. It says:


.For boundary Events, handling consists of consuming the Event occurrence and either canceling the Activity the Event is 
attached to, followed by normal Sequence Flows leaving that Activity, or by running an Event Handler without canceling the 
Activity (only for Message, Signal, Timer and Conditional Events, not for Error Events)..


iii) Chapter/Section  10.4.6. Page 287. It says:
.For an interrupting Event (Error, Escalation, Message, Signal, Timer, Conditional, Multiple, and Parallel Multiple), 
only one Event Sub-Process for the same Event Declaration MUST be modeled..


COMMENTS:


In (ii) Escalation, Multiple and Parallel Multiple are not mentioned as Boundary Non-Interrupting. Furthermore, 
Cancel and Compensations are not mentioned  as Boundary Events that always interrupt.


In (iii) Compensation is not mentioned as an interrupting Event for an Event Sub-Process.



SUGGESTIONS:


In (ii) 
.(only for Message, Signal, Timer and Conditional Events, not for Error Events).   should be replaced by  .(only for Message, 
Signal, Timer, Conditional, Escalation, Multiple and Parallel Multiple Events, not for Error, Cancel and Compensation 
Events).


In (iii) 
.(Error, Escalation, Message, Signal, Timer, Conditional, Multiple, and Parallel Multiple).   should be replaced by  .Error, Escalation, Message, Signal, Timer, Conditional, Compensation, Multiple, and Parallel Multiple).