Issue 12218: 15.3.14: This paragraph refers to signal and change events (uml2-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: This paragraph refers to signal and change events, but should refer to signal and call events: >>However, relative to its use for signal events (see “SignalEvent (from Communications)” on page 449) and change events (see “ChangeEvent (from Communications)” on page 435), the <assignment-specification> ... Instead it should read: >>However, relative to its use for signal events (see “SignalEvent (from Communications)” on page 449) and call events (see “CallEvent (from Communications)” on page 434), the <assignment-specification> ... ChangeEvents don't even have an assignment specification, but signal an call events do. Resolution: Revised Text: Actions taken: February 8, 2008: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 08 Feb 2008 11:18:49 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Axel Scheithauer Company: oose Innovative Informatik GmbH mailFrom: axel.scheithauer@oose.de Notification: Yes Specification: OMG UML Superstructure Section: 15.3.14 FormalNumber: formal/2007-11-02 Version: 2.1.2 RevisionDate: 11/02/2007 Page: 574 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 Description This paragraph refers to signal and change events, but should refer to signal and call events: >>However, relative to its use for signal events (see .SignalEvent (from Communications). on page 449) and change events (see .ChangeEvent (from Communications). on page 435), the ... Instead it should read: >>However, relative to its use for signal events (see .SignalEvent (from Communications). on page 449) and call events (see .CallEvent (from Communications). on page 434), the ... ChangeEvents don't even have an assignment specification, but signal an call events do.