Issue 15740: None Intermediate Event: “catch” or “throw” (bpmn2-rtf)
Source:  (, )
Nature: Revision
Severity: Significant
Summary: Description:


ANTECEDENTS:
i) Chapter/Section  10.4.4. Page 259. Table  10.89.  Row “None”. It says:
“The None Intermediate Event is only valid in normal flow, i.e., it MAY NOT be used on the boundary of an Activity. Although there is no specific trigger for this Event, it is defined as throw Event.”


ii) Chapter/Section  10.4.5. Page 269. Table  10.93.  Row “None”.
None Intermediate Event is shown as a throw Event



iii) Chapter/Section  10.4.5. Page 280. It says:
“There are three (3) variations of None Events: a Start Event, a catch Intermediate Event, and …”


“The catch None Intermediate Event MUST only be used in normal flow and, thus, MAY NOT be attached to the boundary of an Activity.”



COMMENTS:


In (i) and (ii) None Intermediate Event is defined as a throw Event, but in (iii) it is considered to be a catch Event



SUGGESTIONS:


It seems that it is not important which type (throw or catch) would be chosen, but  it is necessary to define one and be consistent in its use. 

Note: see Issue 15687
Resolution: 
Revised Text: 
Actions taken:
October 15, 2010: received issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
Date: 15 Oct 2010 00:26:07 -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.4
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         Day
Page:            259
Title:           None Intermediate Event: .catch. or .throw.
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


ANTECEDENTS:
i) Chapter/Section  10.4.4. Page 259. Table  10.89.  Row .None.. It says:
.The None Intermediate Event is only valid in normal flow, i.e., it MAY NOT be used on the boundary of an Activity. Although there is no specific trigger for this Event, it is defined as throw Event..


ii) Chapter/Section  10.4.5. Page 269. Table  10.93.  Row .None..
None Intermediate Event is shown as a throw Event



iii) Chapter/Section  10.4.5. Page 280. It says:
.There are three (3) variations of None Events: a Start Event, a catch Intermediate Event, and ..


.The catch None Intermediate Event MUST only be used in normal flow and, thus, MAY NOT be attached to the boundary of an Activity..



COMMENTS:


In (i) and (ii) None Intermediate Event is defined as a throw Event, but in (iii) it is considered to be a catch Event



SUGGESTIONS:


It seems that it is not important which type (throw or catch) would be chosen, but  it is necessary to define one and be consistent in its use. 

Note: see Issue 15687