SMOF 1.0 FTF Avatar
  1. OMG Issue

SMOF_ — SMOF not a subset of UML

  • Key: SMOF_-20
  • Legacy Issue Number: 17163
  • Status: closed  
  • Source: NIST ( Conrad Bock)
  • Summary:

    MOF is a subset /constrained version of UML now, as I understand it, but SMOF is not. MOF subsetting UML had many benefits, why not SMOF?

  • Reported: SMOF 1.0b2 — Thu, 23 Feb 2012 05:00 GMT
  • Disposition: Resolved — SMOF 1.0
  • Disposition Summary:

    The constraint mechanism in SEMOF::Reflection needs to be revised to make SMOF a subset of UML. The classes SEMOF::Refelction::Compatibility and SEMOF::Reflection::Incompatibility shall be removed and replaced by a constraint carrying an OpaqueExpression with language = “SMOF” and the body holding the values “equivalent” and “disjoint”.
    As a consequence of this change, regular UML tooling is sufficient to create and maintain SMOF metamodels, therefore the SMOF Profile is no longer needed and shall be removed.
    SMOF reuses and completes the latent support for multiple classification and reclassification existing in UML. However, a more detailed description of the semantics and side effects of multiple and/or dynamic classification is needed.

  • Updated: Sat, 7 Mar 2015 08:56 GMT