Issue 15646: Bad description of set() (mof2core-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: In section 9.1 the description of the exceptions refer to ‘element’ instead of ‘object’ as the parameter. And the whole section needs clarification of null e.g. does C.isInstance(null) = true for any class or datatype? Resolution: Agreed. Correct the operation signature to return Boolean. C.isInstance(null) should return false at all time. Null is not a valid classifier and violates the constrains of UML::Type on which MOF::Reflection::Type is based. Revised Text: Clause 9.4.1 – operation set() In the second Exception: bullet point, replace the signature: isInstance(element) by: isInstance(object) Perform the same change in the MOF model. Actions taken: September 27, 2010: received issue April 6, 2015: closed issue Discussion: End of Annotations:===== ubject: MOF 2 Core issue Date: Mon, 27 Sep 2010 12:13:37 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MOF 2 Core issue Thread-Index: Acteb3C+FmkXp4+XQ9SDmXdbBf8oMw== From: "Pete Rivett" To: Bad description of set() In section 9.1 the description of the exceptions refer to .element. instead of .object. as the parameter. And the whole section needs clarification of null e.g. does C.isInstance(null) = true for any class or datatype? -- Pete Rivett (pete.rivett@adaptive.com) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp