UML22 — AcceptEventAction - inconsistent multiplicities

AcceptEventAction - inconsistent multiplicities "• result: OutputPin [1] Pin holding the event object that has been received. Event objects may be copied in transmission, so identity might not be preserved." Multiplicity should be "0..", not "1", because - in case of an accept signal action (see Semantics on the next page), the output pin holds a signal - in case of an time action (see Semantics on the next page), the output pin holds the time at which the event occured - in case of ChangeTrigger, "... there are no output pins." (see Semantics on the next page) - in case of an AcceptCallEventAction (which is a specialization of AcceptEventAction), the output pins hold 0.. argument values of a call. Thus, the multiplicity "0..*" in Figure 150 is probably correct and the respective multiplicity on page 207 should be updated.

See resolution to 6236.