Issue 19275: Support abstract mappings/relations (qvt-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Clarification Severity: Minor 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. Resolution: 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 Revised Text: In Figure 7.4 and the QVTbase models add Rule::isAbstract : Boolean [1]. In 7.11.1.4 Rule add An abstract rule provides functionality that can be exploited by refined rules. An abstract rule is never matched directly and so never executes directly. In 7.11.1.4 Rule Associations add isAbstract : Boolean[1] indicates that the rule is abstract. Default is false. In 7.13.5 correct <relation> ::= ['top'] ['abstract'] 'relation' <identifier> In 9.18 correct Mapping ::= ['abstract'] 'map' MappingName ['in' TransformationName] ['refines' MappingName] '{' In A.3.1 correct abstract map attributes in umlRdbms refines flattening { In A.3.1 correct abstract map classAttributes in umlRdbms refines attributes { In A.3.1 correct abstract map primitiveAttribute in umlRdbms refines attributes { In A.3.1 correct abstract map complexAttributeAttributes in umlRdbms refines attributes { In A.3.1 correct abstract map complexAttribute in umlRdbms refines attributes { Actions taken: February 27, 2014: received issue December 22, 2015: Resolved March 29, 2016: closed issue Discussion: End of Annotations:===== vered-To: spamcop-net-omg4web@spamcop.net X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on filter8 X-Spam-Level: * X-Spam-Status: hits=1.3 tests=HTML_IMAGE_ONLY_32,HTML_MESSAGE version=3.2.4 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 27 Feb 2014 10:55:07 -0500 To: issues@omg.org, qvt-rtf@omg.org From: Juergen Boldt Subject: issue 19275 -- QVT RTF issue X-Virus-Scanned: amavisd-new at omg.org X-SpamCop-Checked: 23.30.177.17 23.30.177.10 X-SpamCop-Whitelisted: juergen@omg.org Delivered-To: spamcop-net-omg4web@spamcop.net X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on filter8 X-Spam-Level: X-Spam-Status: hits=0.0 tests=none version=3.2.4 From: webmaster@omg.org Date: 27 Feb 2014 02:12:18 -0500 To: Subject: Issue/Bug Report X-SpamCop-Checked: 23.30.177.17 23.30.177.16 ******************************************************************************* Name: Edward Willink Employer: mailFrom: ed@willink.me.uk Terms_Agreement: Specification: QVT 1.1 Section: 7, 9 FormalNumber: 11-01-01 Version: 1.1 Doc_Year: Year Doc_Month: Month Doc_Day: Day Page: n/a Title: Support abstract mappings/relations Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: edwillink.plus.com Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.0; rv:27.0) Gecko/20100101 Firefox/27.0 Time: 02:12 AM Description: 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. Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org []