Hi Peter,
I’m surprised to hear you characterize UML model exchange as being
problem free. EA makes heavy use of what it tags as “ea-extensions” which I
doubt align very well with MagicDraw.
- Steve
Steven R. Ray, Ph.D.
Distinguished Research Fellow
Carnegie Mellon University
NASA Research Park
Building 23 (MS 23-11)
P.O. Box 1
Moffett Field, CA 94305-0001
Email: [email protected]
Phone: (650) 587-3780
Cell: (202) 316-6481
Skype: steverayconsulting
10yr-logo-sm
From: [email protected] [mailto:[email protected]]
On Behalf Of Peter Denno
Sent: Tuesday, November 18, 2014 7:21 AM
To: [email protected]
Subject: Re: [topbraid-users] Re: Trying to import EA UML into TBC - No go
David,
UML tool interoperability can be viewed in terms of "model exchange" or the
more demanding "diagram exchange." Most UML tools have no problem with model
exchange. I'd be very surprised if I couldn't read the OP's EA XMI into
MagicDraw. Eclipse is an exception -- it doesn't do model exchange as well as
most commercial tools.
UML diagram interchange is another story. It isn't widely supported. The
reputation of "UML interoperability" is tarnished for lack of this capability
that is important to many users.
Best regards,
Peter
On Saturday, November 15, 2014 12:58:29 PM UTC-5, David Price wrote:
Hi Jack,
You’ve bumped into one of the dirty little secrets of the OMG wrt UML - it is
not an interchangeable form of representing knowledge. It seems XMI can be used
in too many ways and UML is too complex a language for most to have implemented
the two properly and get interchange to work in the real world (even ignoring
UML and XMI version mismatches between tools) .
The OMG has a Model Interchange Working Group[1]that has been trying to remedy
that problem for nearly 6 years now, but still not there yet. That said, maybe
there’s a pipeline through the tools involved in that process that can get you
to a file TBC can import. The eclipse UML2 wiki[2] might help.
Note to TQ staff - we should probably update the eclipse UML2 link to be [2] in
the help pages.
Cheers,
David
[1] http://www.omgwiki.org/model-interchange/doku.php
[2] http://wiki.eclipse.org/MDT-UML2
UK +44 7788 561308
US +1 336 283 0606
On 15 Nov 2014, at 16:07, Jack Hodges <[email protected] <javascript:> > wrote:
Irene,
Thank you for the reply. FYI, the EMF link you provided is dead.
You are correct, EA claims that their export cannot be read in Eclipse but the
quote I found on the second link you provided is slightly different:
"Enterprise Architect supports a UML 2 export, which produces an XML file valid
to the OMG’s UML specification. Nevertheless, it is not possible to open it
with an UML editor of Eclipse without any modifications, because the Eclipse
implementation of the UML2 metamodel differs in some places."
Anyway, that isn't terribly important. I had already tried the first link and
the page for one of the downloads is dead so I could not take that path. I had
not seen the second link before and will try that solution out. I have also
found a python approach that converts XMI to UML2 and will try that as well.
On Thursday, November 13, 2014 12:12:56 PM UTC-8, Jack Hodges wrote:
I have a set of UML models created in Enterprise Architect that I'd like to
import into TBC. I have read the various statements here and in the help files,
etc. I have tried exporting from EA to most of its possible file types using
'export model to XMI'. I tried 'export type' XMI 2.1 as well as UML 2.4.1 (XMI
2.4.1), Ecore, UML 2.0 (XMI 2.1), and MOF 1.4 (XMI 1.2). The question I have
is: how do I convert the XMI file into the UML format TBC requires to perform
the import. The documentation doesn't spell this out at least as far as I have
been able to tell so far.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight,
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected] <javascript:>
To unsubscribe from this group, send email to
[email protected] <javascript:>
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected] <javascript:> .
For more options, visit https://groups.google.com/d/optout.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight,
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
_____
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4213/8588 - Release Date: 11/17/14
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight,
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
