|
| Re: Bug in UML2 specification [message #628234 is a reply to message #628233] |
Sun, 14 February 2010 13:18  |
 Timothy Marc
Messages: 547
Registered: July 2009 |
Senior Member |
|
|
Sorry, again ;-)
Hi all,
i think i've found a bug in the UML2 specification document. Please have
a look at section 15.3.14 Transition, subsection notation (page 592), it
states:
"However, relative to its use for signal events (see “SignalEvent (from
Communications)” on page 450) and change events
(see “ChangeEvent (from Communications)” on page 437), the
<assignment-specification> when used in transitions is
extended as follows:
<assignment-specification> ::= <attr-spec> [‘,’ <attr-spec>]*
<attr-spec> ::= <attr-name> [‘:’ <type-name>]
Note that <attr-name> is the name of an attribute to which the
corresponding parameter value of the event is assigned. If
a <type-name> is included with the attribute name, then it represents an
implicit declaration of a local attribute of that
type in the context of the effect activity to which the corresponding
parameter value of the event is assigned."
Instead of ChangeEvents what doesn't expose any assignable parameters,
it should refer to CallEvent, since a CallEvent is quite similar to
SignalEvents, shouldn't it?
Before raising an issue at the OMG, i'd like to get your opinions
concerning this.
Cheers
Timothy
|
|
|
Powered by
FUDForum. Page generated in 0.01836 seconds
] 
Search
Help
Register
Login
Home
