Issue 16648: Implicit parameter assignment may cause name clashes (uml2-rtf) Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de) Nature: Clarification Severity: Minor Summary: 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? Resolution: Revised Text: Actions taken: October 31, 2011: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 31 Oct 2011 05:19:21 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Marc-Florian Wendland Employer: Fraunhofer FOKUS mailFrom: marc-florian.wendland@fokus.fraunhofer.de Terms_Agreement: I agree Specification: UML Superstructure Section: 13.3.6/13.3.25 FormalNumber: ptc/2010-11-14 Version: 2.4 Doc_Year: 2010 Doc_Month: November Doc_Day: 14 Page: 450f., 465f. Title: Implicit parameter assignment may cause name clashes Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: The textual syntax of CallEvent and SignalEvents states the following: " :: [.(. [] .).] ::= [.,. ]* 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?