I was the one who worked on the GME2EMF transformation.
In fact, the transformation is split into three steps: XML2GME, GME2KM3
then KM32GME.
- The XML2GME produces a GME model from a MetaGME project exported by GME
to an XML format (.xme).
- GME2KM3 produces a KM3 file from this GME model.
- Then, the KM32EMF transformation performs the last step of this bridge.
To realize the GME2KM3 transformation three metamodels are required: XML
metamodel, MGA (MetaGME) metamodel and KM3 metamodel. The XML metamodel is
available on the atlanticZoo.
Our MGA (MultiGraph Architecture) metamodel is not already online but is
strongly inspired from the metamodel supplied in the GME documentation.
However, we just considered the semantic view and ignored the graphical
information like Regnode for example.
The KM3 metamodel used in this transformation is not online yet because it
is a structural metamodel, not a semantic one like in the zoo. I use this
metamodel to include some information like constraint and constraintfunc
in comment form because KM3 does not allow OCL constraint definition in
metamodels (OCL expressions are used in ATL model to model transformation,
not in KM3 metamodel definition).
This transformation is quite complete and will be released soon with some
examples. But some information could not be integrated like aspects and
views definitions.