SMOF_ — AspectOf encourages misuse in common use case

Section (11.2.1) AspectOf, Description, is too strong an interpretation of reclassification to subtypes, and encourages modelers to use aspects when that is not what they mean. For example, if Mammal generalizes Dog, some instances of Mammal might be dogs, but the modeler doesn't know it yet. When it becomes known that a particular instance of Mammal is a dog, it can be reclassified under Dog. This doesn't make Dog an aspect of Mammals. To support this example, modelers would likely think they need to apply the AspectOf stereotype to the generalization between Mammal and Dog, which won't make sense. This construct needs to be rethought in context of other use cases and perhaps additional stereotypes for more cases.

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.
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