UMLR — Message wildcards appear to ignore operation default values

Operations may contain a list of Parameters, which are defined in 9.4.4.

Parameters may an '= <default>' to specify the default value for that parameter.

However, in Messages, argument wi/o values are given wildcard values, representing any legal value.

A wildcard could be representing the default value, but as described, it appears that it need not be – it can be ANY legal value.

This means that it is impossible to specify a message that uses the default values of a parameter wi/o making them explicit. This makes the specification of default values to operation parameters not applicable to messages. This seems unintended. (If intended, then it is wrong)

The discussion of message wildcards should indicate that (at least for input arguments), an unspecified value or wildcard will use the parameter default.

If this is somewho intended the specification needs to be explicit and come up with a way of making the default values useful.