| ATL metamodel: conceptual question [message #19688] |
Wed, 28 February 2007 14:30  |
Eclipse User |
|
|
|
Originally posted by: kehrer.hdm-stuttgart.de
Hello,
In the ATL metamodel, in- and out-models are of type OCLModel. OCLModels
conform to a metamodel, which is itself a OCLModel.
In the ATL user manual however, metamodels (e.g. MMAuthor oder MMPerson,
section 2.2 of the User Manual) are instances of the Ecore-metametamodel.
Now, why does the atl metamodel introduce the term OCLModel?
Isn't this a conflict?
thanks for any hints and ideas
Timo Kehrer
|
|
|
| Re: ATL metamodel: conceptual question [message #20475 is a reply to message #19688] |
Fri, 02 March 2007 12:58  |
| Eclipse User |
|
|
|
Originally posted by: marcos.didonet-del-fabro.univ-nantes.fr
Hello,
The MMAuthor and MMPerson metamodels from the ATL user manual conform to the Ecore
metametamodel.
The OCLModel elements from the ATL metamodel are generic elements that are used as
"wrappers" to write expressions that refers to the models and metamodels in an ATL
transformation.
For instance, when you write MMAuthor!Author in an ATL transformation, the "MMAuthor"
token corresponds to an OCLModel element in the ATL model.
It is in the moment of execution of the ATL transformation that the ATL engine evaluates
this expression, and then accesses the "real" model and model elements (e.g., it matches a
MMAuthor!Author).
Marcos.
Timo Kehrer wrote:
> Hello,
>
> In the ATL metamodel, in- and out-models are of type OCLModel. OCLModels
> conform to a metamodel, which is itself a OCLModel.
> In the ATL user manual however, metamodels (e.g. MMAuthor oder MMPerson,
> section 2.2 of the User Manual) are instances of the Ecore-metametamodel.
> Now, why does the atl metamodel introduce the term OCLModel?
> Isn't this a conflict?
>
>
> thanks for any hints and ideas
>
> Timo Kehrer
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03095 seconds
] 
Search
Help
Register
Login
Home
