Issue 13269: Page 75: Section 8.2.1.13 Constructor (qvt-rtf)
Source: Open Canarias, SL (Mr. Adolfo Sanchez-Barbudo Herrera, nobody)
Nature: Revision
Severity: Minor
Summary: Problem's text: "/body: BlockExp [0..1] {composes} (from ImperativeOperation)
The expression serving to populate the object using the given parameters. This expression should necessarily be
an ObjectExp instance.
discussion: This is not coherent with the ImperativeOperation definition. Body is an OperationBody, specifically a ConstructorBody.
Suggestion: Replace the text above by the following:
"/body: OperationBody [0..1] {composes} (from ImperativeOperation)
The operation body of the constructor. It should necessarily be
a ConstructorBody instance.

Resolution: Yes. But we can go all the way by modeling the ConstructorBody constraint
Revised Text: In 8.2.1.13 Constructor change
/body: BlockExp [0..1]{composes}(from ImperativeOperation)
The expression serving to populate the object using the given parameters. This expression should necessarily
be an ObjectExp instance.
to
/body: ConstructorBody [0..1]{composes}(from ImperativeOperation)
The imperative implementation for this constructor.
Actions taken:
January 15, 2009: received issue
July 15, 2014: closed issue
Discussion: 

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

Page 75: Section 8.2.1.13 Constructor

Problem's text: "/body: BlockExp [0..1] {composes} (from ImperativeOperation)
The expression serving to populate the object using the given parameters. This expression should necessarily be
an ObjectExp instance.
discussion: This is not coherent with the ImperativeOperation definition. Body is an OperationBody, specifically a ConstructorBody.
Suggestion: Replace the text above by the following:
"/body: OperationBody [0..1] {composes} (from ImperativeOperation)
The operation body of the constructor. It should necessarily be
a ConstructorBody instance.