Issue 16489: Because MOF merges UML, UML as an instance of MOF is ill-formed (mof2core-rtf)
Source: Microsoft (Mr. Steve Cook, stcook(at)microsoft.com)
Nature: Uncategorized Issue
Severity: 
Summary: In MOF 2.4, Reflection::Element merges UML::Element.  Then it is stated that Reflection::Element is an implicit superclass of all metaclasses defined using MOF.  Hence UML::Element is a subclass of Reflection::Element which merges UML::Element.  Reflection::Element has all  of the properties of UML::Element (e.g. ownedComment) and so UML::Element may not validly have these properties.

 

The solution is for MOF not to merge any part of UML, because there is no need to do so.  MOF should simply refer to UML for its definitions.

 


Resolution: 

Revised Text: 
Actions taken:
August 10, 2011: received issue
Discussion: 

End of Annotations:=====

m: Steve Cook <Steve.Cook@microsoft.com>
To: "issues@omg.org" <issues@omg.org>
Subject: MOF 2.4 issue: Because MOF merges UML, UML as an instance of MOF is
 ill-formed
Thread-Topic: MOF 2.4 issue: Because MOF merges UML, UML as an instance of
 MOF is ill-formed
Thread-Index: AcxXRJdmt3Wcjbe+QhWdWDMJ6DTgtw==
Date: Wed, 10 Aug 2011 10:03:30 +0000
Accept-Language: en-GB, en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.166.18.102]


In MOF 2.4, Reflection::Element merges UML::Element.  Then it is stated that Reflection::Element is an implicit superclass of all metaclasses defined using MOF.  Hence UML::Element is a subclass of Reflection::Element which merges UML::Element.  Reflection::Element has all  of the properties of UML::Element (e.g. ownedComment) and so UML::Element may not validly have these properties.

 

The solution is for MOF not to merge any part of UML, because there is no need to do so.  MOF should simply refer to UML for its definitions.

 

-- Steve