All references made to metaclasses in the UML 1.4 metamodel that are used in the current definition of the abstract syntax of OCL are listed. These or similar metaclasses are expected to be part of the UML 2.0 metamodel.
The references need to be aligned with the UML 2.0 metamodel as soon as that metamodel is stable.
As described in Section 2 "Conformance," on page 1 the OCL specification will define a subset that is MOF compliant, while the complete specification is UML compliant. Because the MOF 2.0 Core and the UML 2.0 Infrastructure are devleoped in parallel with this OCL 2.0 submission, the exact MOF compliant subset of OCL cannot be defined in this document. This needs to be done during alignment when all submission are stable.
Another issue in alignment is where in a model OCL expressions may be used. These placements are governed by the references made in the UML 2.0 metamodel to the metaclasses Expression, Constraint, and similar metaclasses. In Chapter 12 a number of placements in the model where OCL expressions can be useful, have been described, but others may be added. The UML 2.0 metamodel should provide a way to link to an OCL expression in these cases. This chapter lists the contexts already foreseen, and indicates the expectations on the UML 2.0 metamodel in each case.
Finally, this chapter lists a number of aspects of the UML 2.0
metamodel
that are not required but convenient in the specification of OCL.