Issue 15549: Page 338. Wrong name, multiplicity and description of “messageFlowRefs” (bpmn2-rtf)
Source:  (, )
Nature: Revision
Severity: Significant
Summary: a)  
Table 11.2. Row “messageFlowRef”.


It says: 
“messageFlowRef: Message Flow [1..*]”


It should say: 
“messageFlowRefs: Message Flow [1..2]”


See Figures 11.1 (p.326) and 11.6 (p.332), where the multiplicity [1..2] is clear.
----------------------------------------------------------------------------


b)
In Figures 11.1 (p.326) and 11.6 (p.332) the role name is “messageFlowRef”, but it should be “messageFlowRefs”, because there can be more than one links.
--------------------------------------------------------------------------------------


c) 
In Table 11.2. Row “messageFlowRef”, it says “Although not graphical represented, Choreography Task contain one (1) or more Message Flows that represent the interaction(s) between the Participants referenced by the Choreography Task.”


But, on page 333, it says: 
“A Choreography Task is an atomic Activity in a Choreography Process. It represents an Interaction, which is one (1) or two (2) Message exchanges between two (2) Participants.”  Furthermore, the multiplicity is [1..2].


Then, in Table 11.2. Row “messageFlowRefs”, it should say:
“Although not graphical represented, Choreography Task contain one (1) or two (2)  Message Flows that represent the interaction(s) between the Participants referenced by the Choreography Task.”
Resolution: 
Revised Text: 
Actions taken:
September 17, 2010: received issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
Date: 16 Sep 2010 22:21:12 -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:         11.4.1
FormalNumber:    dtc/2010-06-05
Version:         2.0
Doc_Year:        2010
Doc_Month:       June
Doc_Day:         Day
Page:            338
Title:           Page 338. Wrong name, multiplicity and description of .messageFlowRefs.
Nature:          Revision
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue


Description:


a)  
Table 11.2. Row .messageFlowRef..


It says: 
.messageFlowRef: Message Flow [1..*].


It should say: 
.messageFlowRefs: Message Flow [1..2].


See Figures 11.1 (p.326) and 11.6 (p.332), where the multiplicity [1..2] is clear.
----------------------------------------------------------------------------


b)
In Figures 11.1 (p.326) and 11.6 (p.332) the role name is .messageFlowRef., but it should be .messageFlowRefs., because there can be more than one links.
--------------------------------------------------------------------------------------


c) 
In Table 11.2. Row .messageFlowRef., it says .Although not graphical represented, Choreography Task contain one (1) or more Message Flows that represent the interaction(s) between the Participants referenced by the Choreography Task..


But, on page 333, it says: 
.A Choreography Task is an atomic Activity in a Choreography Process. It represents an Interaction, which is one (1) or two (2) Message exchanges between two (2) Participants..  Furthermore, the multiplicity is [1..2].


Then, in Table 11.2. Row .messageFlowRefs., it should say:
.Although not graphical represented, Choreography Task contain one (1) or two (2)  Message Flows that represent the interaction(s) between the Participants referenced by the Choreography Task..