Issue 7663: UML Mapping in DI specification inadequate (issues) Source: (Dr. Guus Ramackers, Guus.Ramackers(at)gmail.com) Nature: Uncategorized Issue Severity: Summary: The current mapping from the Diagram Interchange meta model to UML is inadequately specified in Appendix A of the DI specification. It will not enable a standard encoding of DI models from the UML 2.0 meta model across vendors. Specifically: - the mapping does not cover UML 2.0 - the mapping solely consists of a table listing a subset of UML meta classes - the mapping does not cover the complexities of UML 2.0 decomposition details, as specified in the UML 2.0 specification in the area of Sequence Diagrams, Activity Diagrams and State Machines. Resolution: Revised Text: Actions taken: August 25, 2004: received issue Discussion: Appendix C contains a Nesting Guide which describes the needed nesting of DiagramElements to represent the elements of the semantic model of UML. The Nesting Guide was subject of issue 7257 and is part of ballot 1. (Previously recommended Disposition: Resolved, no change has to be made) Based on the concerns from FTF members and the inability to develop a revised resolution within the given timeframe, this issue has been deferred and should be re-addressed in the future Diagram Interchange RTF. Disposition: Deferred End of Annotations:===== te: Wed, 25 Aug 2004 14:08:40 +0100 From: Guus Ramackers Organization: Oracle Corporation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en To: Juergen Boldt , issues@omg.org Subject: Issue: UML Mapping in DI specification inadequate Juergen, Please could you log the following issue against the Diagram Interchange specification: The current mapping from the Diagram Interchange meta model to UML is inadequately specified in Appendix A of the DI specification. It will not enable a standard encoding of DI models from the UML 2.0 meta model across vendors. Specifically: - the mapping does not cover UML 2.0 - the mapping solely consists of a table listing a subset of UML meta classes - the mapping does not cover the complexities of UML 2.0 decomposition details, as specified in the UML 2.0 specification in the area of Sequence Diagrams, Activity Diagrams and State Machines. Thanks, Guus -- __________________________________________________________ Guus Ramackers Product Manager UML and Web Services, Oracle JDeveloper Tools group e-mail: guus.ramackers@oracle.com 520 Oracle Parkway, TVP work: +44-(0)1189-245101 Reading RG6 1RA, UK fax: +44-(0)1189-245148