trace vs. Trace

[qwerty]

I just noticed that starting from UML 2.5 the OMG guys use upper case for Trace which had before lower case. That means: models need to be migrated. Or Sparx can sweet talk OMG to take the change back.

q.

[KP]

No need to panic. The stereotype's name is Trace but the text it displays is «trace». EA gets this right.

[qwerty]

But it has been lower case in pre 2.5 versions and now it's upper case. XMI exports should be different then. I'm puzzled.

q.

[Eve]

It's definitely called Trace in UML 2.4.1 too. UML 2.3 it refers to it as Trace and provides the keyword trace, but I can't see a formal definition.

However, the namespace it's part of should vary.

[qwerty]

I don't keep all UML versions, so I looked into 2.0 and 1.5 where trace is written lower case (and EA had been built upon 1.5 I guess). Anyhow, stereotypes are case sensitive. Or is that a wrong assumption? If so, a UML 2.0 <<trace>> would not match a UML 2.5 <<trace>>, would it?

q.

[Ian Mitchell]

I've noticed the same thing when applying other kinds of stereotype: type a stereotype with upper case first letter into the EA properties window, and it comes out lower-case in a diagram. Is this deliberate? Makes it hard to validate diagrams accurately.

[Eve]

I've noticed the same thing when applying other kinds of stereotype: type a stereotype with upper case first letter into the EA properties window, and it comes out lower-case in a diagram. Is this deliberate? Makes it hard to validate diagrams accurately.

EA searches for a matching stereotype case insensitive, then applies the stereotype it applies. If you're in this situation there is already a stereotype defined with the case you don't want.

The good news is that in EA 15 it's a lot harder to be in this situation because you can't type a stereotype name to apply one.