Home » Archived » M2M (model-to-model transformation) » Model format
|
| Re: Model format [message #13381 is a reply to message #13085] |
Tue, 30 January 2007 14:57   |
Eclipse User |
|
|
|
Originally posted by: Hugo.Bruneliere.univ-nantes.fr
Hi Gediminas
>
> Is it correct to say, that models in ATL are handled and stored in Ecore
> format (which is based on XML)?
> Metamodels are, but I ain't sure about models
>
ATL has been designed for being potentially used with different
model-handlers. Currently, two main drivers are provided: Ecore and MDR.
The default (and most used) model-handler with ATL is of course Ecore,
since ATL is an Eclipse/M2M component. So you can say that, in ATL,
models (as well as metamodels) are stored in Ecore format which is a XMI
format (and is thus expressed in XML).
Best regards,
Hugo
--
--------------------------------------------------------
Hugo Bruneliere - R&D Engineer
ATLAS Group (INRIA & LINA) - University of Nantes
2, rue de la Houssiniere
44322 Nantes Cedex 3 - France
office +33 2 51 12 58 10 /\ cell.+33 6 07 42 45 30
EMail: Hugo.Bruneliere@univ-nantes.fr
http://www.sciences.univ-nantes.fr/lina/atl/
--------------------------------------------------------
|
|
|
| Re: Model format [message #13401 is a reply to message #13381] |
Tue, 30 January 2007 16:20 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Hugo,
I don't really like the term "Ecore" format since that term would seem
to narrowly apply just to serializations of Ecore instances and likely
results in confusion (such as the EMF newsgroup thread where someone
suggested renaming My.library, a serialization of a Library model
instance, to Library.ecore, which should be a serialization of an Ecore
instance, not a serializaton of an instance of the Library Ecore
model). Ecore instances can also be serialized as EMOF using
EMOFResourceFactoryImpl and can conversely be deserialized directly from
an EMOF serialization. EMF generally uses XMI format for serialization
of models in general, although options like
OPTION_USE_ENCODED_ATTRIBUTE_STYLE result in a more concise
serialization that's not fully XMI conforming. Perhaps "EMF" format
would be less confusing...
Hugo Bruneliere wrote:
> Hi Gediminas
>
>>
>> Is it correct to say, that models in ATL are handled and stored in
>> Ecore format (which is based on XML)?
>> Metamodels are, but I ain't sure about models
>>
>
> ATL has been designed for being potentially used with different
> model-handlers. Currently, two main drivers are provided: Ecore and MDR.
>
> The default (and most used) model-handler with ATL is of course Ecore,
> since ATL is an Eclipse/M2M component. So you can say that, in ATL,
> models (as well as metamodels) are stored in Ecore format which is a
> XMI format (and is thus expressed in XML).
>
> Best regards,
>
> Hugo
>
|
|
|
| Re: Model format [message #13415 is a reply to message #13401] |
Tue, 30 January 2007 16:53 |
| Eclipse User |
|
|
|
Originally posted by: Hugo.Bruneliere.univ-nantes.fr
Ed,
Ed Merks a écrit :
> Hugo,
>
> I don't really like the term "Ecore" format since that term would seem
> to narrowly apply just to serializations of Ecore instances and likely
> results in confusion (such as the EMF newsgroup thread where someone
> suggested renaming My.library, a serialization of a Library model
> instance, to Library.ecore, which should be a serialization of an Ecore
> instance, not a serializaton of an instance of the Library Ecore
> model). Ecore instances can also be serialized as EMOF using
> EMOFResourceFactoryImpl and can conversely be deserialized directly from
> an EMOF serialization. EMF generally uses XMI format for serialization
> of models in general, although options like
> OPTION_USE_ENCODED_ATTRIBUTE_STYLE result in a more concise
> serialization that's not fully XMI conforming. Perhaps "EMF" format
> would be less confusing...
I fully agree with the fact that it is an abuse of language to reduce
Ecore to a "serialization format".
To summarize, can we say that EMF is a model-handler that provides
facilities including serialization ones (related to XMI formats for
example but not necessarily) and that Ecore is its metametamodel
(provided with the corresponding API)?
>
> Hugo Bruneliere wrote:
>> Hi Gediminas
>>
>>>
>>> Is it correct to say, that models in ATL are handled and stored in
>>> Ecore format (which is based on XML)?
>>> Metamodels are, but I ain't sure about models
>>>
>>
>> ATL has been designed for being potentially used with different
>> model-handlers. Currently, two main drivers are provided: Ecore and MDR.
>>
>> The default (and most used) model-handler with ATL is of course Ecore,
>> since ATL is an Eclipse/M2M component. So you can say that, in ATL,
>> models (as well as metamodels) are stored in Ecore format which is a
>> XMI format (and is thus expressed in XML).
>>
>> Best regards,
>>
>> Hugo
>>
Best regards,
Hugo
--
--------------------------------------------------------
Hugo Bruneliere - R&D Engineer
ATLAS Group (INRIA & LINA) - University of Nantes
2, rue de la Houssiniere
44322 Nantes Cedex 3 - France
office +33 2 51 12 58 10 /\ cell.+33 6 07 42 45 30
EMail: Hugo.Bruneliere@univ-nantes.fr
http://www.sciences.univ-nantes.fr/lina/atl/
--------------------------------------------------------
|
|
|
| Re: Model format [message #14019 is a reply to message #13415] |
Tue, 30 January 2007 17:04 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Hugo,
Comments below.
Hugo Bruneliere wrote:
> Ed,
>
> Ed Merks a écrit :
>> Hugo,
>>
>> I don't really like the term "Ecore" format since that term would
>> seem to narrowly apply just to serializations of Ecore instances and
>> likely results in confusion (such as the EMF newsgroup thread where
>> someone suggested renaming My.library, a serialization of a Library
>> model instance, to Library.ecore, which should be a serialization of
>> an Ecore instance, not a serializaton of an instance of the Library
>> Ecore model). Ecore instances can also be serialized as EMOF using
>> EMOFResourceFactoryImpl and can conversely be deserialized directly
>> from an EMOF serialization. EMF generally uses XMI format for
>> serialization of models in general, although options like
>> OPTION_USE_ENCODED_ATTRIBUTE_STYLE result in a more concise
>> serialization that's not fully XMI conforming. Perhaps "EMF" format
>> would be less confusing...
>
> I fully agree with the fact that it is an abuse of language to reduce
> Ecore to a "serialization format".
>
> To summarize, can we say that EMF is a model-handler that provides
> facilities including serialization ones (related to XMI formats for
> example but not necessarily) and that Ecore is its metametamodel
> (provided with the corresponding API)?
Yes, that sounds very precise. :-)
>
>>
>> Hugo Bruneliere wrote:
>>> Hi Gediminas
>>>
>>>>
>>>> Is it correct to say, that models in ATL are handled and stored in
>>>> Ecore format (which is based on XML)?
>>>> Metamodels are, but I ain't sure about models
>>>>
>>>
>>> ATL has been designed for being potentially used with different
>>> model-handlers. Currently, two main drivers are provided: Ecore and
>>> MDR.
>>>
>>> The default (and most used) model-handler with ATL is of course
>>> Ecore, since ATL is an Eclipse/M2M component. So you can say that,
>>> in ATL, models (as well as metamodels) are stored in Ecore format
>>> which is a XMI format (and is thus expressed in XML).
>>>
>>> Best regards,
>>>
>>> Hugo
>>>
>
> Best regards,
>
> Hugo
>
|
|
|
Goto Forum:
Current Time: Fri Sep 20 12:07:16 GMT 2024
Powered by FUDForum. Page generated in 0.03001 seconds |
] 
Search
Help
Register
Login
Home
