UML25 — Message Constraint signature_is_Signal only merely refers to Signal.ownedAttributes as parameters of a Message signature

Message Constraint signature_is_Signal only merely refers to Signal.ownedAttributes as parameters of a Message signature. This is not sufficient, since a Signal may specialize other signals and, thus, the Message should also allow to specify arguments for inherited attributes. Of course, redefined attributes need to be sorted out.

Instead of using the Signal.ownedAttributes directly in the OCL (let signalAttributes : OrderedSet(Property)
= signature.oclAsType(Signal).ownedAttribute->asOrderedSet()) the inherited operation
Classifier::inheritedMember():NamedElement[0..*] ought to be used in the let-statement. The operation
filters redefined inherited elements and delivers the complete set of all inherited members, including the
properties. These need to be extracted from the set of inherited members eventually. The resulting OCL
would look like this:
let signalAttributes : OrderedSet(Property) =
signature.oclAsType(Signal).inheritedMember()->
select(n:NamedElement | n.oclIsTypeOf(Property)->asOrderedSet()