Issue 15920: OCL 2.3.TupleType semantics and AST (ocl2-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Uncategorized Issue Severity: Summary: 8.2 Does the lack of restriction on feature types for a TupleType extend to InvalidType and VoidType? With an InvalidType feature the tuple could only be 'well-formed' when containing an invalid value. Surely a tuple with an invalid value is itself invalid and not well-formed? 8.2.2 TupleType has some ASCII code corruptions in the OCL. 8.2.2 TupleType uses unqualified names for feature types allowing an ambiguity when package path is significant. 10.2 TupleValue surely values must not be invalid? 13 TupleLiteralExp has a TupleLiteralPart which has a Property, not accommodating the OclExpression of an initExpression provided by the concrete syntax. Surely a TupleLiteralPart is a derived VariableDeclaration adding an initExpression? Resolution: Revised Text: Actions taken: January 8, 2011: received issue Discussion: End of Annotations:===== ronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: At4FAJfJJ01UXeb6/2dsb2JhbACWNY4Oc7tvhUwE Date: Sat, 08 Jan 2011 10:20:10 +0000 From: Ed Willink User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 To: issues@omg.org Subject: OCL 2.3.TupleType semantics and AST Hi 8.2 Does the lack of restriction on feature types for a TupleType extend to InvalidType and VoidType? With an InvalidType feature the tuple could only be 'well-formed' when containing an invalid value. Surely a tuple with an invalid value is itself invalid and not well-formed? 8.2.2 TupleType has some ASCII code corruptions in the OCL. 8.2.2 TupleType uses unqualified names for feature types allowing an ambiguity when package path is significant. 10.2 TupleValue surely values must not be invalid? 13 TupleLiteralExp has a TupleLiteralPart which has a Property, not accommodating the OclExpression of an initExpression provided by the concrete syntax. Surely a TupleLiteralPart is a derived VariableDeclaration adding an initExpression? Regards Ed Willink