UML25 — Location: Annex C Keywords P. 777 - Previously unmentioned constraints given in Keywords Annex

The first paragraph gives a number of constraints on model element names, in particular stereotypes. I don't believe this is mentioned in either the NamedElement description or the Stereotype description. I don't think this is a constraint that should be left to an annex, if indeed it should exist: the EJB profile example in figure 12-19 has an Entity stereotype that extends Component as does StandardProfile.

The main problem here is that the “standard stereotypes” are identified as keywords. This gives them
an undeserved primacy. They should have exactly the same privileges as any user-defined stereotypes:
which means they should be removed from Annex C altogether. The constraint on stereotype names is
already defined by name_not_clash in Clause 12, the notation for stereotypes is defined in Clause 12, and
the standard stereotypes themselves are defined in Clause 22. They don’t belong in Annex C at all.