-
Key: QVT13-52
-
Status: closed
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
The QVTo Standard Library has no model and consequently no namespace.
This encourages a major confusion:
The QVToLib::Model and QVToLib::Transformation types used in the QVTo Standard Library are at a different meta-level to UML::Model and QVTbase::Transformation. We have the uncomfortable situation that a QVToLib::Model is an instance of a QVTbase::TypedModel and a QVToLib::Transformation is an instance of a QVTbase::Transformation.
As a minimum the distinct namespaces should be identified and modeled.
Possibly QVToLib::Model and QVToLib::Transformation should be renamed. Since they have no namespace they are currently unuseable in code; their sole purpose is for specification of implementation behavior.
-
Reported: QVT 1.2 — Thu, 30 Apr 2015 08:21 GMT
-
Disposition: Deferred — QVT 1.3
-
Disposition Summary:
QVTo Standard Library mode and namespace
The QVTo Standard Library has no model and consequently no namespace.
This encourages a major confusion:
The QVToLib::Model and QVToLib::Transformation types used in the QVTo Standard Library are at a different meta-level to UML::Model and QVTbase::Transformation. We have the uncomfortable situation that a QVToLib::Model is an instance of a QVTbase::TypedModel and a QVToLib::Transformation is an instance of a QVTbase::Transformation.
As a minimum the distinct namespaces should be identified and modeled.
Possibly QVToLib::Model and QVToLib::Transformation should be renamed. Since they have no namespace they are currently unuseable in code; their sole purpose is for specification of implementation behavior.
Discussion
It is difficult to make sensible progress until the OCL work in progress modeling libraries provides the solution.
-
Updated: Tue, 29 Mar 2016 15:09 GMT