Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA2/Standard Conformance"
< VIATRA2
m (Standard Conformance of VIATRA2 moved to VIATRA2/Standard Conformance: Move into VIATRA2 namespace.) |
m (link updates) |
||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
We need to point out that the underlying modeling and transformation concepts of VIATRA2 are nonstandard. | We need to point out that the underlying modeling and transformation concepts of VIATRA2 are nonstandard. | ||
− | * the model management framework ([[VIATRA2 | + | * the model management framework ([[VIATRA2/Model_Space]]) is more expressive than MOF / EMF, |
* the [[VIATRA2 Transformation Language]] is not QVT, but combines formal techniques being in use for more than 15 years. | * the [[VIATRA2 Transformation Language]] is not QVT, but combines formal techniques being in use for more than 15 years. | ||
Revision as of 12:29, 23 February 2010
Overview
We need to point out that the underlying modeling and transformation concepts of VIATRA2 are nonstandard.
- the model management framework (VIATRA2/Model_Space) is more expressive than MOF / EMF,
- the VIATRA2 Transformation Language is not QVT, but combines formal techniques being in use for more than 15 years.
Anyhow, VIATRA2 plans to support related standards by offering
- powerful and extensible model importers and exporters
- exporters/importers of other transformation languages (e.g. QVT)
- domain specific languages integrated to the framework as VIATRA2 (and thus Eclipse) plug-ins.