BPMN2 — Page 255, Message Flow connection for End Event

Reported by dga...@trisotech.com, Jul 29, 2009

The last two structural speficication at bottom of page 255 have errors.
The first one has an extra sentence starting with If the Intermediate
Event...

The second structural specification should not be there.

(BTW bullet should be diamonds here and many other places)

The End Event Message Flow Connection definitions should have a parallel construction as the Start Event Message Flow Connections. Thus, the following changes
will be made to the specification:
(a) Section 10.4.3 End Event, Sub-Section "Message Flow Connections," page 225 (255 pdf), first bullet in section: Delete second sentence of bullet item.
(b) Section 10.4.3 End Event, Sub-Section "Message Flow Connections," page 225 (255 pdf), second bullet in section: Delete entire bullet item and replace with the
following text, "An End Event MAY be the source for Message Flow; it can have 0 (zero) or more outgoing Message Flow. Each Message Flow leaving the End Event
will have a Message sent when the Event is triggered."
(c) Section 10.4.3 End Event, Sub-Section "Message Flow Connections," page 225 (255 pdf), after the second bullet in section: Add a new sub-level bullet with the
following text, "The Result attribute of the End Event MUST be set to Message or Multiple if there are any outgoing Message Flow."
(d) Section 10.4.3 End Event, Sub-Section "Message Flow Connections," page 225 (255 pdf), after the second bullet in section: Add a new sub-level bullet with the
following text, "The Result attribute of the End Event MUST be set to Multiple if there is more than one (1) outgoing Message Flow."