Issue 15558: Page 441. “Task” instead of “Activity” (bpmn2-rtf)
Source:  (, )
Nature: Revision
Severity: Minor
Summary: It says: 
“Uncontrolled flow means that, for each token arriving on any incoming Sequence Flows into the Activity, the Task will be enabled independently of the arrival of tokens on other incoming Sequence Flows. The presence of multiple incoming Sequence Flows behaves as an exclusive gateway. If the flow of tokens into the Task needs to be ‘controlled,’ then Gateways (other than Exclusive) should be explicitly included in the Process flow prior to the Task to fully eliminate semantic ambiguities.”


The description is intended for “Activities” in general, not for “Tasks” in particular.


Then, it should say: 
“Uncontrolled flow means that, for each token arriving on any incoming Sequence Flows into the Activity, the Activity will be enabled independently of the arrival of tokens on other incoming Sequence Flows. The presence of multiple incoming Sequence Flows behaves as an exclusive gateway. If the flow of tokens into the Activity needs to be ‘controlled,’ then Gateways (other than Exclusive) should be explicitly included in the Process flow prior to the Activity to fully eliminate semantic ambiguities.”

Three times “Task” should be replaced by “Activity”.
Resolution: 
Revised Text: 
Actions taken:
September 17, 2010: received issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
Date: 16 Sep 2010 22:49:06 -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:         13.2.1
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         Day
Page:            441
Title:           Page 441. .Task. instead of .Activity.
Nature:          Revision
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


It says: 
.Uncontrolled flow means that, for each token arriving on any incoming Sequence Flows into the Activity, the Task will be enabled independently of the arrival of tokens on other incoming Sequence Flows. The presence of multiple incoming Sequence Flows behaves as an exclusive gateway. If the flow of tokens into the Task needs to be .controlled,. then Gateways (other than Exclusive) should be explicitly included in the Process flow prior to the Task to fully eliminate semantic ambiguities..


The description is intended for .Activities. in general, not for .Tasks. in particular.


Then, it should say: 
.Uncontrolled flow means that, for each token arriving on any incoming Sequence Flows into the Activity, the Activity will be enabled independently of the arrival of tokens on other incoming Sequence Flows. The presence of multiple incoming Sequence Flows behaves as an exclusive gateway. If the flow of tokens into the Activity needs to be .controlled,. then Gateways (other than Exclusive) should be explicitly included in the Process flow prior to the Activity to fully eliminate semantic ambiguities..

Three times .Task. should be replaced by .Activity..