Issue 16032: multiple inheritance for MOF shown in Figure F.4 (odm-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: The multiple inheritance for MOF shown in Figure F.4 results in PropertyOWLClass and IndividualPropertyOWLClass having 2 distinct properties called isDeprecated inherited from OWLClass and OWLProperty – which is an error in MOF (and UML). Either they should be redefined in the subclasses or one of the original properties renamed – depending on whether the same element can be separately deprecated as a property and as a Class). Resolution: Revised Text: Actions taken: February 16, 2011: received issue April 25, 2014: closed issue Discussion: The RTF has determined that due to SMOF, Annex F is no longer required and the Annex should be deleted, per the resolution to issue 18834. Thus, this issue is closed to the resolution of 18834. Disposition: Resolved End of Annotations:===== ubject: Issues on ODM metamodel Date: Wed, 16 Feb 2011 11:07:01 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issues on ODM metamodel Thread-Index: AcvODJGE0bKWyV4TTVamVfqNduRiaQ== From: "Pete Rivett" To: Cc: , , I.d appreciate early feedback on these, especially the following where I.m less sure of my ground: 6, 9. This is issue # 16032 multiple inheritance for MOF shown in Figure F.4 The multiple inheritance for MOF shown in Figure F.4 results in PropertyOWLClass and IndividualPropertyOWLClass having 2 distinct properties called isDeprecated inherited from OWLClass and OWLProperty . which is an error in MOF (and UML). Either they should be redefined in the subclasses or one of the original properties renamed . depending on whether the same element can be separately deprecated as a property and as a Class).