XMI 2.4 RTF Avatar
  1. OMG Issue

XMI24 — Section: 4.9.3

  • Key: XMI24-26
  • Legacy Issue Number: 9557
  • Status: closed  
  • Source: Anonymous
  • Summary:

    The example shows two elements with tags ownedElement which are of types UML:Class and UML:Datatype. Since XML presumes that the tag defines the type it is difficult to see how ownedElement could be defined using XSD. I suggest allowing something like the following as an option: <UML:Model name="model1" xmi:id="id1"> <UML:Class xmi:role="ownedElement" name="class1" xmi:id="id2"> <UML:Attribute xmi:role="feature" name="attribute1" type="type1"/> </UML:Class> <UML:Datatype xmi:role="ownedElement" name="Integer" xmi:id="type1"/> </UML:Model> This would eliminate the need to define an element in XSD, and the need to wait for attributes to determine type when using SAX. And, since an XSL style sheet to convert between to two forms is a trivial exercise, impact should be minimal.

  • Reported: XMI 2.1 — Wed, 12 Apr 2006 04:00 GMT
  • Disposition: Resolved — XMI 2.4
  • Disposition Summary:

    This proposed enhancement would break backward compatibility. Close no change.

    Disposition: Closed – No Change

  • Updated: Fri, 6 Mar 2015 20:59 GMT