Thomas Degueule

There is currently two ways to define a model type. Either by extracting the exact type of an existing metamodel: ``` metamodel X { ecore "..." exactType XMT //

Multiple inheritance should be supported with a well-defined semantics (e.g. no conflict or left/right-linearization): ``` metamodel X { ... } metamodel Y { ... } metamodel Z { ... }...

Cross-references between different models is only in-the-small, at the Ecore level. However, it would be relevant to allow direct references between models by enabling the definition of metamodels' and model...

Currently, operations are associated to metamodels or model types through the definition of transformations: ``` modeltype A { ... } metamodel X implements A { ... } transformation foo(A a)...

Currently, the abstract syntax of metamodels is defined by importing the corresponding Ecore file: ``` metamodel X { ecore "platform:/.../X.ecore" exactType XMT } ``` An alternative solution would be to...