Issue 18511: The ReadLine::result parameter should have direction "return" (fuml-rtf) Source: Ivar Jacobson International AB (Mr. Ed Seidewitz, eseidewitz(at)ivarjacobson.com) Nature: Uncategorized Issue Severity: Summary: Specification: Semantics of a Foundational Subset for Executable UML Models (fUML), v1.1, RTF Beta (ptc/2012-10-18) Subclause: 9.4.2 Pre-defined ReadLine and WriteLine Behaviors The definitions for ReadLine and WriteLine in Subclause 9.4.2 do not give the multiplicity and direction for the parameters of those activities. However, one would expect them to be consistent with the multiplicity and direction for the corresponding parameters of the TextInputChannel::readLine and TextOutputChannel::writeLine operations. This is indeed the case as given in the normative fUML_Library.xmi, except for the result parameter of the ReadLine, which has direction “out”, while the readLine operation result parameter has direction “return”. Resolution: Revised Text: Actions taken: February 27, 2013: received issue Discussion: End of Annotations:===== m: Ed Seidewitz To: "issues@omg.org" Date: Wed, 27 Feb 2013 17:29:44 -0500 Subject: The ReadLine::result parameter should have direction "return" Thread-Topic: The ReadLine::result parameter should have direction "return" Thread-Index: Ac4VOXX7fo0bs7VnSIeCqVAnH4teKw== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.226]|10.1.50.226|outbound.mailprotector.net|0.0|0.0|0|||0|0|0|0 X-Mailprotector-Results: null_ptr subject_50_chars clean X-Mailprotector-Score: 60 X-Mailprotector-IP-Analysis: 0, 10.1.50.226, Ugly c=0.749064 p=-0.991638 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-6289-c X-Mailprotector-ID: 30298de1-d7a3-4eb5-b3e9-4338d28e0151 X-Virus-Scanned: amavisd-new at omg.org Specification: Semantics of a Foundational Subset for Executable UML Models (fUML), v1.1, RTF Beta (ptc/2012-10-18) Subclause: 9.4.2 Pre-defined ReadLine and WriteLine Behaviors The definitions for ReadLine and WriteLine in Subclause 9.4.2 do not give the multiplicity and direction for the parameters of those activities. However, one would expect them to be consistent with the multiplicity and direction for the corresponding parameters of the TextInputChannel::readLine and TextOutputChannel::writeLine operations. This is indeed the case as given in the normative fUML_Library.xmi, except for the result parameter of the ReadLine, which has direction .out., while the readLine operation result parameter has direction .return..