-
Key: QVT-68
-
Legacy Issue Number: 10077
-
Status: closed
-
Source: Model Driven Solutions ( Dr. Edward Willink)
-
Summary:
I've started looking at implementing QVTrelation->QVTcore in UMLX, but instantly hit problems.
Since UMLX has built in type checking it identifies that:in RelationToTraceclass
RelationDomain has a DomainPattern rather than an ObjectTemplateExp
in SubTemplateToTraceClassProps
ObjectTemplateExp has a PartTemplateItem rather than an ObjectTemplateExp
These are easily fixed, but
in TopLevelRelationToMappingForEnforcement
there are too many discrepancies to resolve without major study; I'm very puzzled by the use of Sets for individual elements.
Is there a revised draft that the FTF are working on that is any more consistent?
FYI, I enclose the first two transformations in UMLX. I think they're a bit more intelligible, type consistent, although there a
fair few UMLX loose ends to sort out. -
Reported: QVT 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
-
Disposition: Resolved — QVT 1.0
-
Disposition Summary:
The relations-to-core transformation spec was out of sync with the meta models. The new updated spec is given in appendix B of this report.
Replace the content of sections 10.3 by the new content in Appendix B of this report. -
Updated: Fri, 6 Mar 2015 22:55 GMT