Issue 16570: Message arguments for a Signal signature too restrictive (uml2-rtf)
Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de)
Nature: Revision
Severity: Minor
Summary: Constraint 4 of Message in section 14.3.18 requires that in case of a Signal signature, the arguments of the message must correspond to the properties of the Signal.


We found this constraint too restrictive. A Signal is a classifier, hence it is possible to create an InstanceSpecification for the Signal. A InstanceSpecification can be referenced by an InstanceValue (ValueSpecification) from within the message argument list. 


We suggest to weaken the first sentence of constraint 4 a little from :


In the case when the Message signature is a Signal, the arguments of the Message must correspond to the attributes of the 
Signal.


to


In the case when the Message signature is a Signal, the arguments of the Message must correspond to the attributes of the 
Signal, or to the Signal itself.
Resolution: 
Revised Text: 
Actions taken:
September 29, 2011: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 29 Sep 2011 03:16:36 -0400
To: <issues@omg.org>
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:         14.3.18
FormalNumber:    ptc/2010-11-14
Version:         2.4
Doc_Year:        2011
Doc_Month:       January
Doc_Day:         01
Page:            506 ff.
Title:           Message arguments for a Signal signature too restrictive
Nature:          Revision
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


Constraint 4 of Message in section 14.3.18 requires that in case of a Signal signature, the arguments of the message must correspond to the properties of the Signal.


We found this constraint too restrictive. A Signal is a classifier, hence it is possible to create an InstanceSpecification for the Signal. A InstanceSpecification can be referenced by an InstanceValue (ValueSpecification) from within the message argument list. 


We suggest to weaken the first sentence of constraint 4 a little from :


In the case when the Message signature is a Signal, the arguments of the Message must correspond to the attributes of the 
Signal.


to


In the case when the Message signature is a Signal, the arguments of the Message must correspond to the attributes of the 
Signal, or to the Signal itself.