Home » Modeling » Epsilon » Feasibility of having a megamodel in Epsilon
| Feasibility of having a megamodel in Epsilon [message #1067816] |
Wed, 10 July 2013 12:55  |
Eclipse User |
|
|
|
In the last years I developed a couple of tools heavily based on the
concept of megamodel proposed within the AMMA platform. Now I am
evaluating the possibility to migrate those tools to the Epsilon platform.
Basically, my need can be resumed as this: "I need to have a single
generic metamodel which acts as a registry containing typed references
to any other model within the projects workspace".
My question is about the feasibility of having a generic metamodel in
the Epsilon platform which may have typed references to both models and
model elements. More specifically, by referring to http://goo.gl/CfKmt,
I would like to store all the arrows (both dashed and solid ones) as
typed references in a single model, is it possible in Epsilon?
Thanks in advance for your help,
Ivano
__________________________________________
Ivano Malavolta, PhD
Research Fellow @ Dipartimento di Ingegneria e Scienze
dell'Informazione e Matematica, University of L'Aquila
phone: +393807021600 skype: iivanoo
Academic: http://www.di.univaq.it/malavolta
Professional: http://www.ivanomalavolta.com
|
|
| |
| Re: Feasibility of having a megamodel in Epsilon [message #1067893 is a reply to message #1067843] |
Thu, 11 July 2013 03:30  |
| Eclipse User |
|
|
|
Hi Dimitris,
first of all thank you for the quick reply.
In the following you can find an excerpt of metamodel that I am thinking
to realize:
package registry;
class Registry extends NamedElement { // NamedElement metaclass omitted
val View[*] views;
}
class View extends NamedElement {
val ModelReference[*] models;
}
class ModelReference {
ref T[1] model; // PROBLEM
}
....
By looking at the excerpt of metamodel, I do not know what T may be.
Basically, I would like to know if its feasible to have a ModelType type
in EOL, which can be considered as the equivalent of the
ModelElementType in EOL, but at the model level (not at the model
element level). Also, it could be interesting to have some method to
access the model elements of each instance of ModelType for digging into
the elements of a specific model.
By doing this, I will be able to populate my registry model with a set
of references to each model within the platform. This allows me to
"easily" check, for example, if there are inconsistencies among views
(instances of the View metaclass) by means of some EVL module.
I hope I clarified now my issue, cheers,
Ivano
Il 10/07/2013 22.01, Dimitris Kolovos ha scritto:
> Hi Ivano,
>
> I'm not sure I completely understand your requirements. In particular
> it'd be great if you could elaborate a bit more on what you mean by
> "typed references to models". In case this helps, roughly speaking, the
> counterparts of the AMMA tools in Epsilon are:
>
> KM3 -> Emfatic (Emfatic is in fact a standalone project but it's often
> used by Epsilon users)
> ATL -> ETL
> ModelWeaver -> Modelink
>
> Cheers,
> Dimitris
|
|
|
| Re: Feasibility of having a megamodel in Epsilon [message #1067898 is a reply to message #1067843] |
Thu, 11 July 2013 03:42 |
| Eclipse User |
|
|
|
Hi Dimitris,
first of all thank you for the quick reply.
In the following you can find an excerpt of metamodel that I am thinking
to realize:
package registry;
class Registry extends NamedElement { // NamedElement metaclass omitted
val View[*] views;
}
class View extends NamedElement {
val ModelReference[*] models;
}
class ModelReference {
ref T[1] model; // PROBLEM
}
....
By looking at the excerpt of metamodel, I do not know what T may be.
Basically, I would like to know if its feasible to have a ModelType type
in EOL, which can be considered as the equivalent of the
ModelElementType in EOL, but at the model level (not at the model
element level). Also, it could be interesting to have some method to
access the model elements of each instance of ModelType for digging into
the elements of a specific model.
By doing this, I will be able to populate my registry model with a set
of references to each model within the platform. This allows me to
"easily" check, for example, if there are inconsistencies among views
(instances of the View metaclass) by means of some EVL module.
I hope I clarified now my issue, cheers,
Ivano
Il 10/07/2013 22.01, Dimitris Kolovos ha scritto:
> Hi Ivano,
>
> I'm not sure I completely understand your requirements. In particular
> it'd be great if you could elaborate a bit more on what you mean by
> "typed references to models". In case this helps, roughly speaking, the
> counterparts of the AMMA tools in Epsilon are:
>
> KM3 -> Emfatic (Emfatic is in fact a standalone project but it's often
> used by Epsilon users)
> ATL -> ETL
> ModelWeaver -> Modelink
>
> Cheers,
> Dimitris
|
|
| | | | |
| Re: Feasibility of having a megamodel in Epsilon [message #1067963 is a reply to message #1067942] |
Thu, 11 July 2013 08:55 |
| Eclipse User |
|
|
|
Perfect Dimitris,
I'll read the references you provided and I will come back with
(hopefully good) news.
Cheers,
Ivano
Il 11/07/2013 13.20, Dimitris Kolovos ha scritto:
> Hi Ivano,
>
> On a related note, MTCFlow [1] seems to be related to what you're doing
> and already provides support for Epsilon languages so it might be of
> interest.
>
> Cheers,
> Dimitris
>
> [1] http://mtcflow.com/
|
|
|
Goto Forum:
Current Time: Wed Jul 23 06:37:31 EDT 2025
Powered by FUDForum. Page generated in 0.05627 seconds |
Home