Issue 6635: ISSUE: XMI for MOF 2 should address models, not just metamodels (mof2xmi-ftf) Source: Escape Velocity (Mr. Don Baisley, donbaisley(at)live.com) Nature: Uncategorized Issue Severity: Summary: The XMI for MOF 2 specification has not been updated to reflect one of the key goals in the alignment of MOF 2 with UML 2, which is that XMI becomes applicable to UML class models in general rather than to MOF-based metamodels only. Recommended Resolution: Replace "metamodel" with "model" in most places within the XMI for MOF 2 specification. Also, in describing the mapping from classes, properties, etc. to XML, do not use wording that implies a restriction to a MOF context except where MOF is , such as for elements of the MOF Type Library. Resolution: Revised Text: Actions taken: November 20, 2003: received issue Discussion: End of Annotations:===== ubject: ISSUE: XMI for MOF 2 should address models, not just metamodels Date: Thu, 20 Nov 2003 14:37:59 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ISSUE: XMI for MOF 2 should address models, not just metamodels Thread-Index: AcOvtvKMty1UPx4nTTC0Q5ipqjEpOQ== From: "Baisley, Donald E" To: X-OriginalArrivalTime: 20 Nov 2003 22:38:00.0268 (UTC) FILETIME=[F39EB8C0:01C3AFB6] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id hAKMbTNA011544 The XMI for MOF 2 specification has not been updated to reflect one of the key goals in the alignment of MOF 2 with UML 2, which is that XMI becomes applicable to UML class models in general rather than to MOF-based metamodels only. Recommended Resolution: Replace "metamodel" with "model" in most places within the XMI for MOF 2 specification. Also, in describing the mapping from classes, properties, etc. to XML, do not use wording that implies a restriction to a MOF context except where MOF is , such as for elements of the MOF Type Library. Don Baisley Unisys