Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [m2m-dev] A home for QVT.mdl

Hi All

I have completed work correlating OMG's Rose, Ecore and EMOF models
and UMLX's Rose, Ecore and EMOF models.

The updated submission to QVT Declarative (https://bugs.eclipse.org/bugs/show_bug.cgi?id=234220)
and a new submission to QVTOML (https://bugs.eclipse.org/bugs/show_bug.cgi?id=236128)
provide a consistent set of Rose, Ecore and EMOF models and HTML compliance statements
detailing the numerous (a couple of hundred) differences with respect to the different
OMG perspectives.

A set of 10 OMG issues have been raised detailing all the errors in the 07-07-08 QVT
Rose, EMOF and Ecore models.

In the absence of any -1's (or +1's), the updated QVT Declarative submission has an
org.eclipse.qvt/model containing the Rose model.

The variant Rose importer and the JUnit tests that do the correlation and generate the
Compliance.html's will be in a future tooling contribution to QVT Declarative (and QVT OML).

The models all now include the https://bugs.eclipse.org/bugs/show_bug.cgi?id=229998
support for unnavigable opposite role names.

Sub-EMOF/Ecore content types are defined for each model, so that the EMOF-based
to Ecore-based conversion just works; no need for my horrible modified ResourceSet
any more.

Definition of validation constraints is currently thin for QVTc and very thin
for QVTr; future work. Open Canarias may contribute the QVTo validation.

I won't be at the OMG/Eclipse symposium in Ottawa (no funding), so it would
be nice if someone could announce the availability of these consistent models
for me.

All the best to everyone attending.

	Regards

		Ed Willink




Back to the top