Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » XMI and "vendor independent" paradigm
XMI and "vendor independent" paradigm [message #664469] Sat, 09 April 2011 08:50 Go to next message
mw  is currently offline mw Friend
Messages: 2
Registered: April 2011
Junior Member
Hi!

I have some problems with understanding real nature of xmi format.

I thought, that XMI is a OMG standard for exchanging UML models between different tool vendors,and it's platform, and vendor independent.

Eclipse Modeling Framework based on ecore format (xmi dialect, I think). Why it's necessary to convert between different xmi format(f.e.ArgoUML,EA) and ecore xmi (via Argo2Ecore or EA Exporter for Ecore Models ).

What about xmi "vendor independent" paradigm?

Thanks for explanation

Best regards
mario

Re: XMI and "vendor independent" paradigm [message #664473 is a reply to message #664469] Sat, 09 April 2011 09:48 Go to previous messageGo to next message
Ed Willink is currently offline Ed WillinkFriend
Messages: 7655
Registered: July 2009
Senior Member
Hi Mario

Consider an analogy:

XMI is like ASCII; it at least ensures that there is commonality wrt to
an alternative character coding such as EBCDIC. It does nothing to
ensure useful content.

XMI is used to serialize a model conforming to a meta-model. These can
be CMOF or EMOF (or, as from UML 2.4, UML) or Ecore or ...; continuing
the anlogy these are like Enghlish or French or German; setiously different.

For each meta-model, there is a namespace such as
http://www.omg.org/spec/UML/20100901; continuing the anology these are
dialects such as UK or US or European English - usually pretty similar
but hostorically (UML 1.x) there may be major variation such as Pigeon
English.

If a tool does not recognise either the meta-model or the namespace the
tool cannot understand the input.

For a long time the UML spec did not have an official namespace so tools
were forced to guess inconsistently. More recently each new UML revision
has a new official namespace, so tools must have translators between
namespaces/dialects. Not all tools support all namespaces, so some
exporters use popular de facto namespaces.

Also XMI evolves to gradually eliminate misinterpretations between tools
in particular the encoding of URIs.

Regards

Ed Willink

On 09/04/2011 09:50, mw wrote:
> Hi!
>
> I have some problems with understanding real nature of xmi format.
> I thought, that XMI is a OMG standard for exchanging UML models
> between different tool vendors,and it's platform, and vendor independent.
> Eclipse Modeling Framework based on ecore format (xmi dialect, I
> think). Why it's necessary to convert between different xmi
> format(f.e.ArgoUML,EA) and ecore xmi (via Argo2Ecore or EA Exporter
> for Ecore Models ).
>
> What about xmi "vendor independent" paradigm?
>
> Thanks for explanation
>
> Best regards
> mario
>
>
Re: XMI and "vendor independent" paradigm [message #664501 is a reply to message #664473] Sun, 10 April 2011 06:01 Go to previous message
mw  is currently offline mw Friend
Messages: 2
Registered: April 2011
Junior Member
Ed, thank you very much Smile


Edward Willink wrote on Sat, 09 April 2011 05:48
Hi Mario

Consider an analogy:

XMI is like ASCII; it at least ensures that there is commonality wrt to
an alternative character coding such as EBCDIC. It does nothing to
ensure useful content.

XMI is used to serialize a model conforming to a meta-model. These can
be CMOF or EMOF (or, as from UML 2.4, UML) or Ecore or ...; continuing
the anlogy these are like Enghlish or French or German; setiously different.

For each meta-model, there is a namespace such as
http://www.omg.org/spec/UML/20100901; continuing the anology these are
dialects such as UK or US or European English - usually pretty similar
but hostorically (UML 1.x) there may be major variation such as Pigeon
English.

If a tool does not recognise either the meta-model or the namespace the
tool cannot understand the input.

For a long time the UML spec did not have an official namespace so tools
were forced to guess inconsistently. More recently each new UML revision
has a new official namespace, so tools must have translators between
namespaces/dialects. Not all tools support all namespaces, so some
exporters use popular de facto namespaces.

Also XMI evolves to gradually eliminate misinterpretations between tools
in particular the encoding of URIs.

Regards

Ed Willink

On 09/04/2011 09:50, mw wrote:
> Hi!
>
> I have some problems with understanding real nature of xmi format.
> I thought, that XMI is a OMG standard for exchanging UML models
> between different tool vendors,and it's platform, and vendor independent.
> Eclipse Modeling Framework based on ecore format (xmi dialect, I
> think). Why it's necessary to convert between different xmi
> format(f.e.ArgoUML,EA) and ecore xmi (via Argo2Ecore or EA Exporter
> for Ecore Models ).
>
> What about xmi "vendor independent" paradigm?
>
> Thanks for explanation
>
> Best regards
> mario
>
>

Previous Topic:model query
Next Topic:losing eContainer when adding EObject to an ArrayList
Goto Forum:
  


Current Time: Tue Apr 16 19:19:08 GMT 2024

Powered by FUDForum. Page generated in 2.65410 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top