Issue 11708: 9.17.12, EnforcementOperation.operationCallExp should be composes (qvt-rtf)
Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk)
Nature: Uncategorized Issue
Severity: 
Summary: 9.17.12 EnforcementOperation, Figure 9.3
----------------------------------------


The definition: "operationCallExp : OperationCallExp[1]"
and the corresponding "*" enforcementOperation multiplicity in
Figure 9.3 provides a consistent definition of a shared reference
to a Call expression. There is no indication of where this
expression might be contained. It is unlikely that such
expressions can usefully be shared since they must refer to
invocation-site-specific variables.


Therefore:


Change the definition to:


        operationCallExp : OperationCallExp[1] {composes}


and draw the composition with 0..1 parent multiplicity.

Resolution: Simple change already in QVTcore.xml
Revised Text: Simple change already in QVTcore.xml.
Revised Text:
From 9.17.12 EnforcementOperation change
operationCallExp: OperationCallExp [1]
to
operationCallExp: OperationCallExp [1] {composes}
In Figure 9.2 draw EnforcementOperation.operationCallExp as a 0..1 composition.
Actions taken:
December 3, 2007: received issue
July 15, 2014: closed issue
Discussion: 


End of Annotations:=====

m: "Willink, Ed" <Ed.Willink@thalesgroup.com>
To: "'issues@omg.org'" <issues@omg.org>
Subject: MOF QVT 1.1, 9.17.12, EnforcementOperation.operationCallExp shoul d
 be composes
Date: Mon, 3 Dec 2007 13:23:52 -0000 
X-Mailer: Internet Mail Service (5.5.2656.59)


Hi


[Please add Ed.Willink@thalesgroup.com and ed@willink.me.uk to this the
qvt-rtf list.]


[http://www.omg.org/issues/qvt-rtf does not list the many deferred FTF
issues.]


9.17.12 EnforcementOperation, Figure 9.3
----------------------------------------


The definition: "operationCallExp : OperationCallExp[1]"
and the corresponding "*" enforcementOperation multiplicity in
Figure 9.3 provides a consistent definition of a shared reference
to a Call expression. There is no indication of where this
expression might be contained. It is unlikely that such
expressions can usefully be shared since they must refer to
invocation-site-specific variables.


Therefore:


Change the definition to:


        operationCallExp : OperationCallExp[1] {composes}


and draw the composition with 0..1 parent multiplicity.


        Regards
                        
                Ed Willink


*******************************************************************************
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.
*******************************************************************************