MOF 2.4 RTF Avatar
  1. OMG Issue

MOF24 — Fix resolution to issue 15398 from MOF2.4 ballot 2

  • Key: MOF24-36
  • Legacy Issue Number: 15824
  • Status: closed  
  • Source: NASA ( Nicolas Rouquette)
  • Summary:

    MOF::Reflection must merge UML::Classes::Kernel instead of importing it because it defines MOF::Reflection::Element as an increment of UML::Classes::Kernel::Element
    MOF::Identifiers does not need to import PrimitiveTypes since MOF::Common already does and that non-conflicting visible elements are imported transitively
    MOF::Extension needs to import UML::Classes::Kernel, it does not need to import PrimitiveTypes since Kernel does this already via the merge of Core::Constructs, which imports PrimitiveTypes
    MOF::CMOFReflection must merge MOF::Reflection because it uses MOF::Reflection::Object and also defines MOF::CMOFReflection::Element and MOF::CMOF::Reflection::Factory as increments of the classes in MOF::Reflection

  • Reported: MOF 2.0 — Mon, 22 Nov 2010 05:00 GMT
  • Disposition: Resolved — MOF 2.4
  • Disposition Summary:

    Apply the changes to the MOF2.4 metamodel as described in the summary.
    Additionally:

    • MOF::Reflection must import MOF::Common since operations defined in MOF::Reflection depend on types defined in MOF::Common
    • MOF::CMOFReflection does not need to import MOF::Common since it merges MOF::Reflection, which imports MOF::Common
    • MOF::CMOF does not need to merge UML::Classes::Kernel per resolution 15398 because MOF::CMOF merges MOF::CMOFReflection, which merges MOF::Reflection, which merges UML::Classes::Kernel
    • MOF::EMOF does not need to merge UML::Classes::Kernel per resolution 15398 because MOF::EMOF merges MOF::Reflection, which merges UML::Classes::Kernel
  • Updated: Fri, 6 Mar 2015 20:58 GMT