Stereotype Names not Case-Senstive???

[Jayson]

Hey all

If we look under the covers of the Archimate2 MDG, we get:

This Stereotype:

<Stereotype name="ArchiMate_BusinessRole" metatype="BusinessRole" notes="" bgcolor="10092543" fontcolor="0" bordercolor="0" borderwidth="1" hideicon="0">

This Toolbox Item:

<Tag name="Archimate2::Archimate_BusinessRole" type="" description="" unit="" values="" default="Business Role"/>

If you look at the Stereotype Names used, the Stereotype has 'ArchiMate' with a capital M but the Toolbox Item has 'Archimate' with a lower case 'm'.

Does this meant that Sparx doesn't check for case when resolving Toolbox Items against Stereotypes?
If so, what if I have two stereotypes that differ only in case???

Or does Sparx not care about case for Stereotype Names in general?

Cheers :-)

[qwerty]

Well, in most (!) cases it does not care. But in some cases it does. Sounds strange? It's Sparxian. One example is where you define stereotypes in your Toolbox the case DOES matter. But not for all stereotypes :-/ In former days you were allowed to manually type stereotypes and EA did not care. Now it's when you import from XMI that EA will "magically match" stereotypes to what it thinks is best. I always try to stick to the case EA shows when displaying a stereotype.

q.

[Jayson]

Hmmm

But in my example it doesn't care regarding the stereotype in the Toolbox!
Argh! Eve, KP any hints?

Cheers :-)

[qwerty]

Well, EA is consistently inconsistent. An often it just leads me in circles and I don't know what's wrong or right. IIRC I had issues with UML::Metaclass where the upper case M was crucial (or was it lower case? It's late and too much wine already; definitely I had issues). Maybe the Sparxians can see through it.

q.