1. OMG Issue

XMI12 — Incomplete rules for non-Primitive Datatype values

  • Key: XMI12-39
  • Legacy Issue Number: 4581
  • Status: open  
  • Source: 88solutions ( Pete Rivett)
  • Summary:

    The EBNF for attributes does not make clear how the different MOF types are to be represented: it is clear for the PrimitiveTypes (via rule 7i) but not the others. For example, the use of xmi.field for StructureField values is only mentioned as part of the example in section 5. And it's not clear what difference there should be between multivalued attributes and those defined to be a CollectionType. And the nesting of DataTypes should also be addressed (e.g. a StructureField has as its datatype another Structure or CollectionType). Specifically 7h should make it clearer that XML Elements must be used for model attributes with non-Primitive datatype (except if the DataType is an Alias for a PrimitiveType?), as well as for multi-valued attributes. And 8e wrongly states that if not a PrimitiveDataType then "the <AttribContent> is a Class and the <AttribContent> is the Class object". There should be a clear table for all the MOF DataTypes as provided for the PrimitiveTYpes in 7i.

  • Reported: XMI 1.1 — Sun, 23 Sep 2001 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:12 GMT