BPMN2 — Page 121, Figures 7.3 and 10-1 ­ Redundant ways to model receiving messages

This is a style suggestion that will make diagrams clearer by removing redundant
notations. There is a "receive event" to receive any kind of communication. For
example, and event to receive a message. Or an event to receive a signal. Events are
circles on the diagram. Additionally, BPMN allows a "receive type" activity, that is a
rounded rectangle that receives messages. Receiving of a message seems more naturally
to be an "event" and not an "activity" because an event is something that happens. An
activity is something you do, and receiving something is really just waiting and not doing
anything. So picturing receive an activity seems unnatural. The redundancy to two ways
to draw this causes confusion.

The spec could encourage the use of a "receive event", and to deprecate the "receive
activity". Receive activity would still be allowed, but "deprecation" would put the
standard on a path to eventually remove it, and would send a message to not use it or
expect it to be there in the future.

The figure 10-1 should be re-drawn to have receive message events instead of "receive
activities".

The doctor/patient example in figure 7-3 should be redrawn to use receive events instead
of the receive activities.

The resolution of issue 14353 will resolve this issue
The spec could encourage the use of a "receive event", and to deprecate the "receive activity". Receive activity would still be allowed, but "deprecation" would put the
standard on a path to eventually remove it, and would send a message to not use it or expect it to be there in the future.
The figure 10-1 should be re-drawn to have receive message events instead of "receive activities".
The doctor/patient example in figure 7-3 should be redrawn to use receive events instead of the receive activities.
Disposition: Duplicate