SYSML2_ — SysMLv2 Metadata Annotation Capabilities do Not Hide enough Implementation Details in Textual Representation

When metadata is defined with keyword textual notation allows short syntax of metadata application with #keyword.
Example from the spec:
occurrence def Situation;
occurrence situations : Situation[0..*] nonunique;
metadata def <situation> SituationMetadata :> SemanticMetadata {
:>> baseType = situations meta SysML::Usage;
}

// batteryLow is an OccurrenceUsage that implicitly subsets situations.
#situation occurrence batteryLow;

Unfortunately, the end user still needs to know underlying model element flavor (occurrence in the example above).
This knowledge is difficult to learn for the users of the particular specialized domain.
It could be considered an "implementation detail" of the domain specific modeling provider.

Idealy,
when metadata is defined 1) with keyword 2) with annotatedElement fixed to a single variant,
the end user should not need to specify the model element flavor ("metaclass") in the textual notation and just state the keyword; like this:
#situation batteryLow;

This would be very handy for UAF and other domains.

Pass-through note to Ed: This is one of the issues from the compiled list that we talked about - issue # SYSML2-2899 on DS side