SMOF 1.0 FTF Avatar
  1. OMG Issue

SMOF_ — Profile compatibility semantics different from metamodel extension

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

    Section 11.2.2 (CompatibleWith) Description, third paragraph, first sentence mentions adding or removing the client classifier, but not the supplier classifier, which isn't the same as Section 9.1.2.2 (Compatibility), Semantics, first, which doesn't distinguish between the constrained types.

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

    The FTF members agreed on removing the SMOF Profile entirely since starting with UML 2.4.1, MOF and UML are based on the same metamodel. Therefore compliant UML tools can be used to create MOF models and a separate SMOF Profile is no longer needed. [See also resolution to issue 17163]
    Revised Text:
    The SMOF Profile (section 11) is removed from the specification; therefore no text change is needed.
    Disposition: Closed – Duplicate / Merged – see issue 17163

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