|[mdt-uml2.dev] UML 2.5 progress|
HiI have reviewed the latest UML 2.5 XMI and successfully used UML and OCL validation so that a few difficulties, but unfortunately not all, are being resolved 'editorially' before the final XMI for UML 2.5.
It looks like the final UML XMI will have two known bugs, the first of which UML validation detects:
ExtensionEnd::/lower has a bad cardinality override; fix is to change multiplicity to [1..1] Lifeline::interaction_uses_share_lifeline has an OCL semantic error; fix is to perhaps change "select" to "exists"
Similarly the UMLDI XMI will have two known bugs, the first of which UML validation detects:
There is diamond inheritance for which the two inheritance paths provide 11 conflicts; fix re-redefine at the diamond join. UMLAssociationOrConnectorOrLinkShape::edge_instancespec has an OCL semantic error; fix is perhaps to change "e.modelElement" to "e".
The ability to validate the UML 2.5 with Eclipse UML '2.4.1' is very encouraging. It is however really tedious to have to change all the namespaces by XMI text edit. Is there no way we can support a user-defined mapping from e.g. http://www.omg.org/spec/UML/20131001/PrimitiveTypes to PrimitiveTypes.uml? With the UML metamodel and serialization increasingly stable, use of Eclipse tooling for UML version N to support N+1 may become increasingly practical and useful.
Back to the top