Issue 11061: Consider using asTuple instead of tuple keyword for TupleExp (qvt-rtf)
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: 
Summary: Consider using asTuple instead of tuple keyword for TupleExp since asX() is usually 
used for conversions.
Resolution: There is no TupleExp or asTuple() in QVT 1.0 or 1.1 but there is an asOrderedTuple() with the
resolved description. So it appears that a variant of the suggested resolution made it into QVT 1.0.
Disposition: Closed, No Change
Revised Text: 
Actions taken:
May 24, 2007: received issue
July 15, 2014: closed issue
Discussion: 
Comment:
The TupleExp metaclass can in fact be replaced by a simple operation in the standard library.

Resolution
(1)	Remove the TupleExp metaclass section description 8.2.2.21
(2)	Within section 8.3.3 add the description of a new operation named asOrderedTuple defined as: 
     Object::asOrderedTuple : OrderedTuple(T).
           Converts the object into an ordered tuple. If the object is a already an ordered type no change is done. If the object is a OCL Tuple, the list of attributes become the anonymous content of the ordered tuple. Otherwise, the operation creates a new tuple with a unique element being the object.
(3)	Apply diagram update described in Appendix D.

End of Annotations:=====
s is issue # 11061

Consider using asTuple instead of tuple keyword for TupleExp

Consider using asTuple instead of tuple keyword for TupleExp since asX() is usually 
used for conversions.