Issue 12213: Relations Language: how will metamodels get into a transformation scrip (qvt-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: Concerning to Relations Language, how will the metamodels get into a transformation script ? Is there a technique similar to Operational Mappings using metamodel declaration and modeltypes ? The RL sample transformation script in annex A.1 (pp 164) doesn't declare the metamodels. The OM sample (A.2.3) does. There is some syntax for declaring and using metamodels and modeltypes in OM (pp118), there isn't for RL (pp38). Resolution: Revised Text: Actions taken: February 6, 2008: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 06 Feb 2008 08:10:59 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Siegfried Nolte Company: Siegfried Nolte mailFrom: siegfried@siegfried-nolte.de Notification: Yes Specification: MOF 2.0 QVT Section: 7 FormalNumber: ptc/07-07-07 Version: FTF RevisionDate: 07/07/07 Page: 13ff Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648) Description Concerning to Relations Language, how will the metamodels get into a transformation script ? Is there a technique similar to Operational Mappings using metamodel declaration and modeltypes ? The RL sample transformation script in annex A.1 (pp 164) doesn't declare the metamodels. The OM sample (A.2.3) does. There is some syntax for declaring and using metamodels and modeltypes in OM (pp118), there isn't for RL (pp38). From: "Willink, Ed" To: qvt-rtf@omg.org Subject: RE: issue 12213 -- QVT RTF issue Date: Wed, 6 Feb 2008 18:17:08 -0000 X-Mailer: Internet Mail Service (5.5.2656.59) Hi Siegried I don't think QVTo is any different to QVTr. Although A.2.3 happens to provide syntax for metamodels these have names that are distinct from the subsequent transformation and are separated by an explanatory paragraph. How short names such as "UML" are resolved to a particular version, location and representation of a meta-model is tool-specific. http://www.eclipse.org/gmt/umlx/doc/EclipseAndOMG08/ModelRegistry.pdf describes one re-usable solution to the problem. It is used by QVTr and QVTc editors. Regards Ed Willink -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: 06 February 2008 18:05 To: issues@omg.org; qvt-rtf@omg.org Subject: issue 12213 -- QVT RTF issue From: webmaster@omg.org Date: 06 Feb 2008 08:10:59 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Siegfried Nolte Company: Siegfried Nolte mailFrom: siegfried@siegfried-nolte.de Notification: Yes Specification: MOF 2.0 QVT Section: 7 FormalNumber: ptc/07-07-07 Version: FTF RevisionDate: 07/07/07 Page: 13ff Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648) Description Concerning to Relations Language, how will the metamodels get into a transformation script ? Is there a technique similar to Operational Mappings using metamodel declaration and modeltypes ? The RL sample transformation script in annex A.1 (pp 164) doesn't declare the metamodels. The OM sample (A.2.3) does. There is some syntax for declaring and using metamodels and modeltypes in OM (pp118), there isn't for RL (pp38). 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 ******************************************************************************* Please consider the environment before printing this email. ******************************************************************************* This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may not be divulged to any third party without the express permission of the originator. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thales Research & Technology (UK) Limited. *******************************************************************************