-
Key: SMOF_-26
-
Legacy Issue Number: 17171
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
Section 11.2.1 (AspectOf), Description, fourth paragraph (the starting "Applying AspectOf to a Generalization") is "exactly equivalent", but should say "semantically equivalent". Aspect is not exactly equivalent to the CompatibleWith pattern given, or you could just use the CompatibleWith pattern as stated and it would be understood the same way by the modeler. Other uses of the same CompatibleWith pattern are not aspects, see Issue 17149 (AspectOf encourages misuse in common use case).
-
Reported: SMOF 1.0b2 — Thu, 23 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