Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: rlsdutra on March 08, 2006, 10:58:04 am
-
There are any plan to support XMI version 2.1 and QVT ?
best regards,
Renato
-
I really don't know how something like EA would "support" QVT.
That said, I tried importing the QVT metamodel from the XMI file supplied by OMG. Worked the first time! Make sure you're using EA 6.x (I've only tried with 6.1).
As to XMI 2.1, we might have to wait for EA support for XMI 2.0 (which I understand is in the queue). Version 2.1 is essentially the same, with changes made "in response to an urgent issue." You may well see implementations of XMI 2.0 without sensitivity to this change, since there was such a long lead time since the 2.0 draft. I'm sure EA 2.1 support will be concurrent or shortly after the 2.0 stuff comes out, perhaps much like the way EA handles 1.x dialects.
-
XMI 2.0/2.1 support has top priority in my world. The EA vs. MagicDraw war is going on, and the MagicDraw fans have now managed to sneak in that all deliveries in the future must be done in XMI 2.0.
Unless EA speeds up, we are forced to switch to MagicDraw.
-
Note to the Sparx folks on this:
I'm getting some pressure on this too, though perhaps not (yet) as directly as Tuser. Any chance you could provide a clear(er) estimate of when you expect to introduce this? Even a soft target date would go a long ways towards establishing that EA will solve this problem within a "reasonable" time of whatever thevarious gatekeepers imagine to be required.
TIA
-
Rumours mentions a 6.X beta version April/May with XMI 2.0/2.1.
-
This is a very high priority for me too. I'm working on the working group for the next version of an ISO standard for banking/finance (ISO 20022), and UML 2.0 and XMI 2.x are major requirements. I would like this work to support EA, not just MagicDraw, but that will be hard unless EA can step up to the plate with XMI 2.x.
I should add that we are interested in full XMI support, not just support for the interchange format that XMI produces when you apply it to the UML 2.0 MOF model. We want to generate Schemas using the full set of 25 parameters that XMI allows to configure how Schemas are generated from models.
Cheers, Tony.
-
Me too Tony,
Sparx has been pretty clear that we need to wait for 6.5 (or the beta) to get this feature. I suspect details must also wait until then.
Still no word on when that will be. I find that this continues to be a source of angst, but that will not make the date any earlier. I also console myself that it will be better to have this working - with any feature mix - than to have defects. This is one area where bugs are both destructive and difficult to find.
David
-
I'm almost sure, that EA 6.5 won't support all 25 tunable parameters - EA isn't the XML/XMI tool, so to expect such broad functionality (6.5/7.0) is too generous.
There would be 2-3 checkboxes in import/export window at most ;D