-
Key: QVT13-40
-
Legacy Issue Number: 19275
-
Status: closed
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
When mapping/relation refinement is used, it should be possible to specify via the abstract keyword that a mapping/relation is only intended for use in a refined form.
Thus in A.3.1, declaring classAttributes abstract could determine whether the execution needs to consider matches not covered by the classPrimitiveAttributes and classComplexAttributes refinements.
-
Reported: QVT 1.1 — Thu, 27 Feb 2014 05:00 GMT
-
Disposition: Resolved — QVT 1.3
-
Disposition Summary:
Support abstract mappings/relations
When mapping/relation refinement is used, it should be possible to specify via the abstract keyword that a mapping/relation is only intended for use in a refined form.
Thus in A.3.1, declaring classAttributes abstract could determine whether the execution needs to consider matches not covered by the classPrimitiveAttributes and classComplexAttributes refinements.
Discussion
A simple enhancement
-
Updated: Tue, 29 Mar 2016 15:09 GMT