XML Metadata Interchange Avatar
  1. OMG Specification

XML Metadata Interchange — Open Issues

  • Acronym: XMI
  • Issues Count: 9
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Extension is only referenced from 1a. However it certainly should be valid within an XMIObjectElement.

  • Key: XMI24-124
  • Legacy Issue Number: 15613
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    3:Extension is only referenced from 1a. However it certainly should be valid within an XMIObjectElement.

    (3:Extension)* should be added to 2a

  • Reported: XMI 2.4 — Tue, 21 Sep 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Canonical XMI (ptc/2013-08-28): need rules for generating xmi:id and xmi:uuid for auxiliary XML elements

  • Key: XMI24-10
  • Legacy Issue Number: 19719
  • Status: open  
  • Source: NASA ( Nicolas Rouquette)
  • Summary:

    Canonical XMI, ptc/2013-08-28, states that xmi:uuid must be always present (B2, #5) except for values that are datatypes (B2, #7).
    What does "values that are datatypes" in B2 #7 mean?

    Are auxiliary XML elements like mofext:Tag and stereotype instances considered "values that are datatypes" ?

    If not, then according to B2 #5, these auxiliary XML elements must have identification attributes (xmi:id and xmi:uuid).

    Historically, the OMG used rather arbitrary conventions for producing the xmi:id of mofext:Tag — not a big deal because nobody really refers to them. However, these arbitrary conventions break the repeatability and reproducibility of Canonical XMI!

    The Canonical XMI document production rules in B4 are incomplete: they should be augmented to specify the serialization, identification and ordering of auxiliary XML elements.

    Consider augmenting the Canonical XMI specification B6 with the following rules:

    Generate the xmi:id and xmi:uuid for mofext:Tag by appending "_mofext.Tag" to the xmi:id and xmi:uuid respectively of the referenced element.

    Generate the xmi:id and xmi:uuid for stereotype instances by concatenating the xmi:id and xmi:uuid respectively of the stereotype with that of the element on which the stereotype is applied.

  • Reported: XMI 2.4 — Sun, 8 Feb 2015 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

[MOF2] and [UML2] not further specified in the document

  • Key: XMI24-9
  • Legacy Issue Number: 19552
  • Status: open  
  • Source: supportgis.de ( Martin Dieblich)
  • Summary:

    The subsection refers to documents [MOF2] and [UML2] which are not further specified in the document.

  • Reported: XMI 2.4 — Wed, 30 Jul 2014 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

MOF/XMI schemaType is incorrectly defined relative to its use and its scope is too restrictive

  • Key: XMI24-8
  • Legacy Issue Number: 18838
  • Status: open  
  • Source: NASA ( Nicolas Rouquette)
  • Summary:

    MOF/XMI defines the schemaType tag as follows: "The name of a datatype defined in the XML Schema Datatype specification."

    First,the examples in the MOF/XMI specification and current use of this tag in OMG's XMI artifacts use datatype URIs, not datatype names.

    Second, the definition of this tag is vague about which datatypes are allowed.

    Consider for example "precision decimal", a datatype that is explicitly mentioned but not explicitly defined in the XML Schema Datatypes spec: http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/#primitive-vs-derived
    This datatype is explicitly defined in a different specification but in the "xs" namespace: http://www.w3.org/TR/xsd-precisionDecimal/#precisionDecimal

    This example illustrates the ambiguity of the scope as currently specified, that is, is "xs:precisionDecimal" allowed as a value for schemaType?

    Third, even if schemaType were to be clarified to be some subset of datatypes defined in the "xs" namespace, there are legitimate business reasons to expect greater flexibility.

    - Several OMG specifications define XSDs (e.g., BPMN, DTV, …) If these include XML Schema datatype definitions, why are we precluded from referring to them via a PrimitiveType that has a schemaType tag pointing to their URI?

  • Reported: XMI 2.4 — Wed, 31 Jul 2013 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

No XML-Schema for UML-XMI

  • Key: XMI24-7
  • Legacy Issue Number: 16582
  • Status: open  
  • Source: Software Systems Engineering ( Holger Eichelberger)
  • Summary:

    While for older versions of XML the concrete syntax for persisting UML models was given in DTD, for newer versions of XMI a related concrete syntax specification e.g. as XML Schema is missing (even if the syntax is described in ptc/2010-12-06). Pure syntax compliance tests for given XMI files cannot be performed.

  • Reported: XMI 2.4 — Wed, 5 Oct 2011 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Revise XMI examples in 9.4

  • Key: XMI24-6
  • Legacy Issue Number: 16341
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    These examples in the XMI spec s have nothing to do with modeling but are related to Departments and stoplights.

    Furthermore they do not show xmi:ids and xmi:types.

    They should also illustrate some of the more sophisticated cases such as that introduced by Issue 16330.

    Finally, the Figures in Section 9.4 are all labeled Figure 1

  • Reported: XMI 2.4 — Tue, 21 Jun 2011 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

XMI should include a name transformation algorithm to convert names e.g. replace spaces by ‘_’

  • Key: XMI24-5
  • Legacy Issue Number: 16257
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Metamodels do not necessarily use names compliant with XML syntax.

    XMI should include a name transformation algorithm to convert names e.g. replace spaces by ‘_’

  • Reported: XMI 2.4 — Thu, 19 May 2011 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Name transformation

  • Key: XMI24-4
  • Legacy Issue Number: 15887
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    MOF/UML does not require names of elements in a metamodel to be valid XML names.

    Therefore the XMI spec should document a transformation to be applied to cope with spaces, punctuation etc to be used for XML element and attribute names.

  • Reported: XMI 2.4 — Thu, 9 Dec 2010 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

XMI issue - root elements for XMI Schemas

  • Key: XMI24-3
  • Legacy Issue Number: 15452
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    At the moment every metaclass has a XML element generated, allowing it to be the root of any interchange.

    While this flexibility might be useful in some cases, it clogs up the XSD with elements that will never get used in practice.

    Proposed resolution:

    Define two boolean XMI Tags:

    1. To define whether root elements should be restricted: org.omg.xmi.restrictRoots (defaults to true)

    2. To mark classifiers (classes or associations) as being potential roots: org.omg.xmi.rootElement (defaults to false)

  • Reported: XMI 2.4 — Wed, 8 Sep 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT