Hi SainTiss and the others, yes, I am absolutely sure on this. Gentleware, DaimlerChrysler, Telelogic, Adaptive, Rational Software and Sun Microsystems submitted the UML 2.0 Diagram Interchange Specification to the OMG. This specification proposes an extension to the UML metamodel so that the diagram elements become part of the model itself.
Upon the first hit, the extension has been applied to the UML 1.4 metamodel so that existing CASE tools can be used to export models based on the new specification. You can find the spec document on the OMG website under the following URL: http://www.omg.org/docs/ptc/03-07-03.pdf In this document, at the beginning of chapter 8 ("Metamodel extension"), it says: --- BEGIN QUOTE --- "This chapter describes the metamodel for diagram information which the diagram interchange mechanism relies on. It is an extension of the UML metamodel and is currently based on UML 1.4. The existing mechanism of XMI[UML] for exchanging models includes only the model information but not the graphical information. The diagram interchange extension allows graphical information to be included for diagrams used in UML models. This extension adds a new package to the current UML metamodel packages. Yet the existing standard is not changed in any way. Also, changes to the UML metamodel due to version updates should not affect this model as long as the highlevel notions of Core::Element (as used in UML 1.x) and Elements::Element (as used in UML 2.0 as well as all metamodels based on the Common Core) are maintained. The extension and the UML metamodel are kept largely independent such that solely links from the extension to the UML metamodel are included. Thus, graphical and model information are cleanly separated." --- END QUOTE --- I think, this makes it absolutely clear, doesn't it? Today, I am going to add this new metamodel (UML 1.4 plus diagram interchange extensions) to AndroMDA 2.x and 3.x so that AndroMDA can load models based on this metamodel, as well as old models without diagram extensions. This change will make AndroMDA completely compatible with Poseidon 2.0. The XSLT style sheet will not be needed any more. Cheers... Matthias P.S.: I am joking here: Does anybody want to generate code from *diagrams* now? This is what the newbies always wanted... :-) > -----Original Message----- > From: SainTiss [mailto:[EMAIL PROTECTED] > Sent: Friday, October 10, 2003 1:18 AM > To: Matthias Bohlen > Subject: Re: Poseidon 2.0 is still UML 1.4! > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Matthias, > > Are you absolutely sure here? Because on their site (http:// > www.gentleware.com/products/descriptions/ce.php4), I found this: > > "Supports all 9 diagrams of the UML. > Compliant to the UML 2.0 standard." > > But maybe "compliant" doesn't mean it *is* UML 2.0 then? > > Cheers, > > Hans > > On Thursday 09 October 2003 23:51, you wrote: > > Hi folks, > > > > don't be fooled: Poseidon 2.0 uses a UML 1.4 metamodel with diagram > > interchange extensions. It is NOT UML 2.0! > > > > Tomorrow, maybe I get a little time to look after this > > incompatibility. The Gentleware people provided me with > some info so > > that there is a fair chance to fix this. > > > > Cheers.... > > Matthias ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
