[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[m2m-dev] Need sub-lists 
Hi All

We clearly have a serious problem with this list, as evidenced by the attached correspondence.

We are all respecting the limited interest of various subscribers to the detailed correspondence of individual projects and as a result almost all technical discussions are happening off-list.

We need per-component sub-lists. I find it perverse that my very limited
participation GMT/UMLX sub-sub-project has its own list and newsgroup,
yet ATL and QVT and ... must share the same list/group.

	Regards

		Ed Willink

--- Begin Message --- 
Hi Adolfo,

I would also consider the name space URIs of the metamodels (in addition to the plugin versions) ;) 

I'm not keep on this, since both 0.7.0 and 0.7.1 are aiming to be as
sensibly compliant with QVT 1.0 as possible.

Two different URIs would imply different structure and semantics. Note that Ecore.ecore is still http://www.eclipse.org/emf/2002/Ecore even though there were no generics in 2002!

If both 0.7.0 and 0.7.1 are available the platform should choose 0.7.1.

--------------------

All:

In the same way that Ecore adds utility operations such as eAllClassifiers, it may be appropriate to add these to QVT as well.
Perhaps the main constraint on my doing this has been spelling.
For Ecore it was easy, everything with an e/E is not EMOF.
MDT-OCL and QVT use direct OMG spelling, so anything we add
could be a compatibility hindrance for QVT 1.1/2.0. I provided
a few such as

	QVTBase::Transformation.getFunction(String name)
	QVTBase::Transformation.getModelParameter(String name)

But since their availability is very patchy in M2M/QVT and not that
coherent in Ecore (where is EPackage.getSubPackage(name)? I tend
not to use them, preferring EcoreUtils.getNamedElement(list, name);

If you have an obviously useful and obviously safe set of suggestions
we might as well make them available.

----------------------

Radek:

In the last month or two I have been adding QVTBase, QVTTemplate,
QVTCore and QVTRelational validation. This is work in progress.
It shouldn't have much effect on QVTo since you don't use Patterns and Predicates where most of my specification difficulties arise.

	Regards

		Ed Willink



--- End Message ---