Case sensitive stereotypes

[qwerty]

Although the UML spec tells us that the stereotypes are not case sensitive, EA wants the correct case when you define entries in your toolbox. E.g. if you add "UML::association" it will show the guillements only and not create a connector. Only when you type "UML::Association" it will create a correct entry. Same with any other entry here (like Dependency etc.).

Could that be fixed? (I guess not, but at least it's noted here.)

q.

[Eve]

Although the UML spec tells us that the stereotypes are not case sensitive,

Citation needed. I'll agree that EA treats stereotype names as case insensitive, but I can't see anything in UML saying that they should be.

EA wants the correct case when you define entries in your toolbox. E.g. if you add "UML::association" it will show the guillements only and not create a connector. Only when you type "UML::Association" it will create a correct entry. Same with any other entry here (like Dependency etc.).

Unrelated to stereotypes. In this case you have a UML metaclass.

[qwerty]

Uhm, yes. You are right about the metaclass. But this seems to be only wrong for relations. I had both UML::class and Class working. I also remember some quirks with that for other metaclasses.

I come back with the citation. I had this in an answer somewhere on StackOverflow.

q.

P.S. p. 260:

Normally a Stereotypes name starts with an upper-case letter, to follow the convention for naming Classes. However Profiles may use different conventions. Matching between the names of Stereotype definitions and applications is case- insensitive, ...

(I got this em-dash bug here again asking to report it to whom ever. I just copy/pasted from the PDF. Removed a "suspicious" apostrophe)