Book a Demo

Author Topic: XSDenumeration - to be or not to be?  (Read 2057 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
XSDenumeration - to be or not to be?
« on: October 29, 2007, 10:02:57 pm »
In a related posting: [size=13]XSD round-tripping - anyone succeeded?[/size], I discuss some observations on our recent attempt to round-trip a non-trivial XSD using EA's Import/Export XML Schema functionality.  One interesting anomaly I observed is that although every other type of structure was stereotyped as «XSD<something>», enumerations were simply stereotyped «enumeration».  This struck me as inconsistent.

Would it not be better to stereotype an XSD Enumeration as «XSDenumeration»?  This is especially so since if you drag a normal UML enumeration onto the diagram it behaves differently than if you drag an XSD Enum onto the same diagram!  And why call it Enum on the toolbar when W3C clearly calls it Enumeration (in full)?

Many of the other XSD concepts have similar mappings to more usual UML concepts, but EA has (correctly, in my view) chosen to distinguish the XSD versions from their more prosaic counterparts.

Just to indicate how confusing it can all be to a poor user...  The behaviour of both the XSD Enum and the UML Enumeration toolbar items varies depending upon the physical location of the diagram in the browser!   I won't go into the details here, unless specifically requested but... either an XSDenumeration is an XSDenumeration or it's not (not if it feels like it...)

Consistency, Consistency, Consistency! TM

Paolo
[size=10]Using EA in spite of EA, NOT because of it![/size] TM[/color]
« Last Edit: October 29, 2007, 10:03:49 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!