Use of the UML Metamodel

The metaclasses from the UML 1.4 metamodel that are listed in Table 6, are referenced in the abstract syntax of this submission. These or similar classes are expected to be part of the UML 2.0 metamodel. The list is divided into classes that should be present in a core metamodel, and metaclasses that should be present in an extension to this core that deals with states and messaging. Preferably the core metaclasses are present in the infrastructure of UML, and in the core of the MOF.

Potentially there is an overlap between the UML 2.0 infrastructure submissions and this submission in the definition of literal expressions. A final issue is that this submission would be helped if there is a way in the UML to define template classes. This feature is used in the definition of the OCL standard library to define collection types..

Table 6 - Overview of UML 1.4. metaclasses used in this submission
Metaclass  Expected in MOF and UML  Expected in UML Needed for state and message values Assumptions
AssociationClass X
AssociationEnd X
Attribute X
Classifier X
DataType X
Enumeration X
EnumLiteral X
ModelElement X
Primitive X
StructuralFeature X
Operation X Operations have Parameters and each parameter hasa direction kind (Parameter-DirectionKind).
CallAction
SendAction
Signal Signals have attributes.