Issue 8761: Arguments of Message (uml2-rtf)
Source: No Magic, Inc. (Mr. Nerijus Jankevicius, nerijus(at)nomagic.com)
Nature: Uncategorized Issue
Severity: 
Summary: arguments of call actions or arguments of message (for example 
> setName(name) where "name" is variable defined in Interaction), but 
> now arguments are simple ValueSpecification, so can't have 
> refference to "real" argument (variable, member, parameter of behavior etc.) 
> Maybe Argument should be in metamodel as in UML 1.4, or at least 
> ValueSpecification should be subclassed in Interactions package and 
> introduce reference to Element that value it represents? 

Resolution: 
Revised Text: 
Actions taken:
May 3, 2005: received issue
Discussion: 
Due to lack of time, the RTF/FTF agrees that the following are problems that need fixing, but decided to defer their resolution to a future RTF working on this specification.
End of Annotations:=====
rguments of Message 
> Variables, members and other "value holders" can be used as 
> arguments of call actions or arguments of message (for example 
> setName(name) where "name" is variable defined in Interaction), but 
> now arguments are simple ValueSpecification, so can't have 
> refference to "real" argument (variable, member, parameter of behavior etc.) 
> Maybe Argument should be in metamodel as in UML 1.4, or at least 
> ValueSpecification should be subclassed in Interactions package and 
> introduce reference to Element that value it represents? 

Again, I suggest checking with Oystein. Your argument makes sense to me. It should be possible to include variable names as arguments, for instance.