SMOF restricts itself to dynamically classifying elements, and requires links to have a single static Association. The problem with that will show up as soon as we want to use SMOF for profiles. We might, for example, have metaclasses C1 and C2 connected by an association A. Apply the profile and it automatically infers that C1 needs also to be classified by P1 and C2 by P2 – and A by B. But SMOF doesn’t allow the “A by B” part.

I could not get the UML Profile XMI to load, and it has MagicDraw specifics.

The profile XMI also has a stereotype called Constraint which had no base class and was not in the spec – so it should be deleted.

Create a correct profile XMI

SMOF should be updated to 2.4 before finalization to be consistent with UML, MOF and XMI.

The primary change needed to update to 2.4 is to change the way that SMOF merges the MOF packages to incorporate the fact that MOF 2.4 is based on UML::Classes::Kernel, from Superstructure, instead of Infrastructure packages used to define earlier revisions of MOF.
Various cross-references need to be changed. While we are at it, let’s use the latest available version of OCL

In clause 12 of SMOF, the namespaces (such as xmlns:xmi=http://www.omg.org/spec/XMI/20100101) do not refer to any actual published specification. Furthermore, the xmlns:uml namespace inconsistently refers to the XMI spec.

Correct the namespaces to refer to valid specifications.