Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Model to Model Transformation - MMT"
(→Questions and Discussions About M2M Usage) |
|||
| Line 1: | Line 1: | ||
{{Backlink|Modeling}} | {{Backlink|Modeling}} | ||
| − | Model-to-model transformation is a key aspect of model-driven development (MDD). The | + | Model-to-model transformation is a key aspect of model-driven development (MDD). The MMT project provides a framework for model-to-model transformation languages. Transformations are executed by transformation engines. There are three transformation engines that are developed in the scope of this project: ATL, QVTo, QVTd. MMT is a subproject of the top-level [[Modeling | Eclipse Modeling Project]]. |
| + | |||
| + | The MMT project was originally known as the M2M project until the Machine-to-Machine became widespread. | ||
__TOC__ | __TOC__ | ||
| − | == | + | ==MMT Transformation Languages and Engines== |
| − | The three languages currently supported by | + | The three languages currently supported by MMT are: |
* [[M2M/Atlas Transformation Language (ATL)|Atlas Transformation Language (ATL)]] | * [[M2M/Atlas Transformation Language (ATL)|Atlas Transformation Language (ATL)]] | ||
* [[M2M/Operational QVT Language (QVTO)|QVT Operational Mappings Language (QVTo)]] | * [[M2M/Operational QVT Language (QVTO)|QVT Operational Mappings Language (QVTo)]] | ||
* [[M2M/QVT_Declarative_(QVTd)|QVT Declarative Languages (QVTd)]], supporting QVT Core (QVTc) and QVT Relations (QVTr) | * [[M2M/QVT_Declarative_(QVTd)|QVT Declarative Languages (QVTd)]], supporting QVT Core (QVTc) and QVT Relations (QVTr) | ||
| − | ==Questions and Discussions About | + | ==Questions and Discussions About MMT Usage== |
| − | Questions and discussions about the | + | Questions and discussions about the MMT projects and/or about its components (i.e., ATL, QVTo, QVTd) should be directed to the [news://news.eclipse.org/eclipse.modeling.m2m eclipse.modeling.m2m] [http://www.eclipse.org/newsgroups/ Eclipse newsgroup]. There are also [http://dev.eclipse.org/newslists/news.eclipse.modeling.m2m/maillist.html archives], as well as a [http://www.eclipse.org/newsportal/thread.php?group=eclipse.modeling.m2m newsportal] (i.e., news access from web browser) available for this newsgroup. |
In order to keep the discussions understandable, the subject of every post should be prefixed with the name of the component it is targeting: | In order to keep the discussions understandable, the subject of every post should be prefixed with the name of the component it is targeting: | ||
| Line 25: | Line 27: | ||
[[Category:Modeling]] | [[Category:Modeling]] | ||
| − | [[Category: | + | [[Category:MMT]] [[Category:MDD]] |
Revision as of 16:18, 16 April 2012
< To: Modeling
Model-to-model transformation is a key aspect of model-driven development (MDD). The MMT project provides a framework for model-to-model transformation languages. Transformations are executed by transformation engines. There are three transformation engines that are developed in the scope of this project: ATL, QVTo, QVTd. MMT is a subproject of the top-level Eclipse Modeling Project.
The MMT project was originally known as the M2M project until the Machine-to-Machine became widespread.
MMT Transformation Languages and Engines
The three languages currently supported by MMT are:
- Atlas Transformation Language (ATL)
- QVT Operational Mappings Language (QVTo)
- QVT Declarative Languages (QVTd), supporting QVT Core (QVTc) and QVT Relations (QVTr)
Questions and Discussions About MMT Usage
Questions and discussions about the MMT projects and/or about its components (i.e., ATL, QVTo, QVTd) should be directed to the eclipse.modeling.m2m Eclipse newsgroup. There are also archives, as well as a newsportal (i.e., news access from web browser) available for this newsgroup.
In order to keep the discussions understandable, the subject of every post should be prefixed with the name of the component it is targeting:
- [ATL] for the ATL component.
- [QVTo] for the QVT Operational component
- [QVTd] (or [QVTc],[QVTr]) for the QVT Declarative component
- or [M2M] if the overall project is targeted.
This last rule is to make sure that erroneously unprefixed messages are not misinterpreted as targeting the overall project.