Issue 19673: Rewind Issues 9379, 10938 (qvt-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Clarification Severity: Significant Summary: The author of Issue 9379 misunderstood the poor description of Pattern::bindsTo and consequently removed the {composes} qualifier. Issue 10938 observed that this totally broke QVTc and introduced CorePattern::variables to compensate. The QVTr to QVTc transformation remains broken since it continues to assume that bindsTo {composes}. There was actually nothing wrong with bindsTo that could not have been fixed by clearer wording to the effect that bindsTo was a dustbin container for variables not contained elsewhere. The above kind of emphasises the benefits of an ownedPlurals naming policy. Therefore suggest that: a) the AST bloat from the redundant bindsTo be replaced by definition of a suitable derived property that satisfies the intent of all variables. b) that variables be renamed ownedVariables and used throughout the QVTr to QVTc trnasformation Resolution: Rewind Issues 9379, 10938 The author of Issue 9379 misunderstood the poor description of Pattern::bindsTo and consequently removed the{composes} qualifier. Issue 10938 observed that this totally broke QVTc and introduced CorePattern::variables to compensate. The QVTr to QVTc transformation remains broken since it continues to assume that bindsTo {composes} . There was actually nothing wrong with bindsTo that could not have been fixed by clearer wording to the effect that bindsTo was a dustbin container for variables not contained elsewhere. The above kind of emphasises the benefits of an ownedPlurals naming policy. Therefore suggest that: a) the AST bloat from the redundant bindsTo be replaced by definition of a suitable derived property that satisfies the intent of all variables. b) that variables be renamed ownedVariables and used throughout the QVTr to QVTc transformation Discussion The problem is genuine, but further Eclipse QVTr prototyping reveals two distinct cases, one requiring containment, another not. Further work is needed to specify these accurately. Revised Text: Actions taken: December 9, 2014: received issue December 22, 2015: Deferred March 29, 2016: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 09 Dec 2014 11:02:00 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Ed Willink Employer: mailFrom: ed@willink.me.uk Terms_Agreement: I agree Specification: QVT 1.2 Section: 7.11.1.8 FormalNumber: - Version: 1.2 Beta Doc_Year: Year Doc_Month: Month Doc_Day: Day Page: 28 Title: Rewind Issues 9379, 10938 Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: edwillink.plus.com Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 Time: 11:01 AM Description: The author of Issue 9379 misunderstood the poor description of Pattern::bindsTo and consequently removed the {composes} qualifier. Issue 10938 observed that this totally broke QVTc and introduced CorePattern::variables to compensate. The QVTr to QVTc transformation remains broken since it continues to assume that bindsTo {composes}. There was actually nothing wrong with bindsTo that could not have been fixed by clearer wording to the effect that bindsTo was a dustbin container for variables not contained elsewhere. The above kind of emphasises the benefits of an ownedPlurals naming policy. Therefore suggest that: a) the AST bloat from the redundant bindsTo be replaced by definition of a suitable derived property that satisfies the intent of all variables. b) that variables be renamed ownedVariables and used throughout the QVTr to QVTc trnasformation