Legacy Issue Number: 7602
Source: ISIS ( Matt Emerson)
This issue is preventing me from implementing an XMI 2.0 Schema generator for a MOF 1.4 metamodeling environment. The specification contradicts itself regarding the type specification of MOF Attributes. >From section 1.8.4: “The XML element corresponding to the attribute is declared in the content of the complexType corresponding to the class that owns the attribute. The type specification is either an XML schema data type, an enumeration data type, or a class from the metamodel.” Then, in section 2.2.1, rule 4d: “The type is “xsd:string” for simple attributes, the name of an enumeration for enumerated attributes, or part of the value of the org.omg.xmi.schemaType tag, if present.” I have no idea what the specification means by “simple attribute” (the phrase appears just that one time in the entire document), but the two statements above are clearly out of sync and confusing. Also, the type of an attribute might be something other than a metamodel Class, PrimitiveType, or EnumerationType in MOF 1.4: it might for example be a CollectionType or an AliasType. Rules are provided for serializing these other DataType subtypes as Classes, but they themselves are not metamodel Classes.
Reported: XMI 2.0 — Tue, 27 Jul 2004 04:00 GMT
Disposition: Resolved — XMI 2.4
(now sections 4.8.4 and 5.2.1)
“simple attribute” is actually a well established term, meaning an attribute which can be represented as a single value.
Also the MOF 1.4 types mentioned in the issue: CollectionType and AliasType are no longer present in MOF 2.x
See resolution for issue 8884 regarding structured DataTypes.
- none -
Proposed Disposition: Closed No Change
Updated: Fri, 6 Mar 2015 20:59 GMT
XMI24 — Type specification of MOF attributes
- Key: XMI24-11
- OMG Task Force: XMI for MOF 2 (XMI 2.1) RTF