-
Key: SMOF_-18
-
Legacy Issue Number: 17159
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
The profile uses very different language from the metamodel extensions to describe what presumably is the same semantics. For example, the semantics of Compatibility constraint specifications is much more spelled out in the metamodel extensions than that the profile, (and also see the previous issue). It would help prevent misinterpretation and improve consistency if the same text is used in both sections as much as possible.
-
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