2010 06 22 omg - obeo
- 2,126 views
The Acceleo project is an OpenSource project created in 2006 aimed at providing an easy-to-use tooling for code generation through the MDA approach. Acceleo 2.x is already a community driven project with a public repository, a website, ... It has become a real success with a vibrant community which shared generative modules for JavaEE, .Net, PHP, C and lots of professional success stories.
As time passed, the Acceleo team was surprised and happy to see the OMG tackling the standardization of an M2T syntax with the MOF Model to Text Language specification. Surprised because of its similarity with the existing Acceleo syntax and happy because it resolves several issues and provides a standard way to describe templates.
Thus, commiters decided to rewrite Acceleo from scratch as an official Eclipse Foundation project, changing the syntax to the standard while keeping the exemplary tooling and pragmatism of Acceleo.org.
With Acceleo 3.0 included in Eclipse 3.6, our new goal is to provide the de facto or reference implementation of the standard; yet some parts of the specification are still quite vague and ambiguous and collaboration with OMG isn't smooth ...
Acceleo could put forward a think tank discussion about both the specification and the implementation; then gather overall thoughts on how to provide a long term and successful communication channel between the Acceleo project and the OMG representatives.
In complement of Acceleo, the Obeo commiters works on several Eclipse projects related to OMG standards :
- ATL: Obeo is co-lead with the AtlanMod Research lab on this famous QVT-like transformation engine
- EMF Compare: Obeo create this extensible diff/compare/patch engine for EMF compliant models, with several metamodels which could become inputs for a future standard
- GMF and Obeo Designer: after several years of contributions in GMF, Obeo creates a "viewpoint oriented" tool to simplify creation of custom Domain Specific Modelers on DSL or standard models. Several interoperability issues exist due to lake of OMG specifications: no activity on a Diagram Description specification to standardise the description of a graphical environment, and no real separation in OMG specifications between the description of the graphical diagrams and the mapping to the semantic (for example, the graphical aspect of a Componant Diagram could be standardised and mapped to UML, SOAML, CCM, and others).
- Total Views
- Views on SlideShare
- Embed Views