Issue 8489: ExpansionRegion (behavior in the shorthand notation) (uml2-rtf) Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Clarification Severity: Minor Summary: In ExpansionRegion, clarify that the behavior in the shorthand notation must have exactly one return parameter Resolution: The shorthand notation does not actually require that the behavior have exactly one return parameter. However, it should be clarified that the expansion nodes shown in the shorthand notation should correspond one to one to the input and output pins of the behavior. Revised Text: In Section 12.3.27 (ExpansionRegion), under Notation, at the end of the paragraph immediately preceding Figure 12.83, add: In the shorthand notation, there must be one input expansion node corresponding to each in or inout parameter of the behavior (which must have at least one such parameter) and one output expansion node corresponding to each out or inout parameter of the behavior. Actions taken: March 6, 2005: received issue Discussion: Disposition: Deferred to UML 2.4 RTF End of Annotations:===== m: webmaster@omg.org Date: 06 Mar 2005 10:20:39 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Notification: No Specification: UML 2 Superstructure Section: Activities FormalNumber: ptc/04-10-02 Version: RevisionDate: Page: Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322) Description In ExpansionRegion, clarify that the behavior in the shorthand notation must have exactly one return parameter. Subject: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes Date: Sun, 1 Feb 2009 23:25:51 -0500 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Proposed issue resolutions, Set 2: Activities -- Low and trivial effort changes thread-index: AcmE7lQ9kq9LsV5zRgKwNovhcAlo8A== From: "Ed Seidewitz" To: Attached are proposed resolutions to 21 additional Activity issues that only required low or trivial effort changes (though there are a few that, on further analysis, I decided to propose to close or identified as duplicate). -- Ed UML 2.3 Resolutions 090201 Seidewitz 2.doc OMG Issue No: 8489 Title: ExpansionRegion (behavior in the shorthand notation) Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@nist.gov) Summary: In ExpansionRegion, clarify that the behavior in the shorthand notation must have exactly one return parameter Resolution: The shorthand notation does not actually require that the behavior have exactly one return parameter. However, it should be clarified that the expansion nodes shown in the shorthand notation should correspond one to one to the input and output pins of the behavior. Revised Text: In Section 12.3.27 (ExpansionRegion), under Notation, at the end of the paragraph immediately preceding Figure 12.83, add: In the shorthand notation, there must be one input expansion node corresponding to each in or inout parameter of the behavior (which must have at least one such parameter) and one output expansion node corresponding to each out or inout parameter of the behavior. Disposition: Resolved