Issue 12524: Errors and anomalies in QVT 1.0 07-07-08 ZIP qvtrelation.ecore (qvt-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Uncategorized Issue Severity: Summary: Use of automated tooling to support comparison of the models developed initially as part of the Eclipse GMT/UMLX project and being transferred to the Eclipse QVT Declarative/QVT Operational Mappings Projects reveals the following errors and anomalies in emof.ecore in the 07-07-08 ZIP. Note that these errors and anomalies are not the same as those separately reported for the QVT_1.0.mdl from which the Ecore was notionally auto-generated. An Ecore file resolving these anomalies is attached Resolution: These changes mostly affect non-normative files which were corrected when QVT 1.1 issued revised files based on Eclipse QVT contributions. However a few changes remain to be resolved in the main text. Revised Text: In Fig 7.7 • Remove the partial diagram artifact at the bottom of the diagram • Correct the RelationImplementation.relation multiplicity to 1 • Correct the RelationCallExp.referredRelation multiplicity to 1 • Correct the RelationCallExp.argument multiplicity to 2..* In 7.11.3.1 RelationalTransformation change key: Key [*] {composes} to ownedKey: Key [*] {composes} In 7.11.3.2 Relation change /domain: Domain [*] {composes} (from Rule) to /domain: RelationDomain [*] {composes} (from Rule) In the non-normative files change • RelationImplementation.relation multiplicity to 1 Actions taken: June 6, 2008: received issue July 15, 2014: closed issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 06 Jun 2008 17:07:40 -0400 To: issues@omg.org, mof-qvt-ftf@omg.org From: Juergen Boldt Subject: issue 12524 -- MOF QVT xTF issue From: "Ed Willink" To: Subject: Errors and anomalies in QVT 1.0 07-07-08 ZIP qvtrelation.ecore Date: Fri, 6 Jun 2008 20:37:12 +0100 X-Mailer: Microsoft Outlook, Build 10.0.6838 Thread-Index: AcjIDLeWY7m3Jt8NR0qT04AimkASbA== X-Plusnet-Relay: 29682826ab581f30d0bbcdc4387657f0 Use of automated tooling to support comparison of the models developed initially as part of the Eclipse GMT/UMLX project and being transferred to the Eclipse QVT Declarative/QVT Operational Mappings Projects reveals the following errors and anomalies in emof.ecore in the 07-07-08 ZIP. Note that these errors and anomalies are not the same as those separately reported for the QVT_1.0.mdl from which the Ecore was notionally auto-generated. An Ecore file resolving these anomalies is attached. 'nsURI' for 'QVTRelation' should be ' http://schema.omg.org/spec/QVT/1.0/qvtrelation.xml' rather than ' http://www.schema.omg.org/spec/QVT/1.0/qvtrelation' 'nsPrefix' for 'QVTRelation' should be 'qvtr' rather than 'qvtrelation' 'name' for 'QVTRelation' should be 'QVTRelation' rather than 'qvtrelation' 'lowerBound' for 'RelationCallExp.argument' should be '2' rather than '0' 'lowerBound' for 'RelationCallExp.referredRelation' should be '1' rather than '0' 'lowerBound' for 'RelationDomain.pattern' should be '1' rather than '0' 'containment' for 'Relation.operationalImpl' should be 'true' rather than 'false' 'transient' for 'RelationImplementation.relation' should be 'true' rather than 'false' 'ordered' for 'Key.part' should be 'false' rather than 'true' 'ordered' for 'Relation.operationalImpl' should be 'false' rather than 'true' 'ordered' for 'Relation.variable' should be 'false' rather than 'true' 'ordered' for 'RelationDomain.defaultAssignment' should be 'false' rather than 'true' 'ordered' for 'RelationalTransformation.ownedKey' should be 'false' rather than 'true' Unnavigable 'opposite' of 'Relation.when' should be modelled Unnavigable 'opposite' of 'Relation.where' should be modelled Unnavigable 'opposite' of 'RelationDomain.defaultAssignment' should be modelled Unnavigable 'opposite' of 'RelationDomainAssignment.valueExp' should be modelled Unnavigable 'opposite' of 'RelationDomainAssignment.variable' should be modelled QVTRelation.ecore1 Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org From: "Ed Willink" To: Cc: "Quentin Glineur" Subject: Re: QVT 1.0 Issue 12524 (and also 12518 to 12527) Date: Sun, 7 Sep 2008 11:35:38 +0100 X-Mailer: Microsoft Outlook, Build 10.0.6838 Thread-Index: AckQ1XfW7+MYoOdaRZqsH383msTnIg== X-Plusnet-Relay: cfc4683e0ac6584088ccb75eec87b977 Hi The submitted models are now available and used by the Eclipse QVT Declarative and QVT OML projects. The basic Rose model may be found at org.eclipse.m2m/org.eclipse.qvt.declarative/plugins/org.eclipse.qvt/model/QVT.mdl in the /cvsroot/modeling module on the CVS server at dev.eclipse.org, which is accessible to an 'anonymous' user. The referenced CAT files are in the same folder. EMOF and Ecore files may be found in the ecore, emof, traditionalEcore, traditionalEmof sub-folders. The non-traditional folders have a PrimitiveTypes package. The traditional folders merge the PrimitiveTypes package into the EMOF package. A FlatQVT is also available for use by the RelToCore example. ------- The QVT Relation model has been updated to incorporate the resolution of Issue 9380. The observation "'lowerBound' for 'RelationDomain.pattern' should be '1' rather than '0'" is therefore retracted. Regards