UML241 — Implicit parameter assignment may cause name clashes

The textual syntax of CallEvent and SignalEvents states the following:

"<call-event> :: <name> [‘(‘ [<assignment-specification>] ‘)’]
<assignment-specification> ::= <attr-name> [‘,’ <attr-name>]*

<attr-name> is an implicit assignment of the corresponding parameter of the operation to an attribute (with this name)
UML Superstructure Specification, of the context object owning the triggered behavior"

This may lead to a situation where name clashes can occurr, if the context object already contains an identically named attibute.
How should situations like a name clashes be resolved?

The corresponding wording in the UML 2.5 specification is (from Subclause 13.3.4):
“<assigned-name> is an implicit assignment of the argument value for the corresponding Parameter of the Operation
to a Property or Variable of the context object for the triggered Behavior.”
The “assigned-name” is the name of a Property or Variable that the context object already contains, not a definition of
a new attribute. There is therefore no possibility of “name clash”.
Disposition: Closed - No Change