Issue 14991: Expansion nodes using all the tokens in them as a single collection (uml2-rtf) Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Revision Severity: Significant Summary: UML expansion regions currently treat each input as a collection, rather than all the inputs as members of a single collection, as the execution engine currently assumes. The description of Expansion Region says "Each input is a collection of values. If there are multiple inputs, each of them must hold the same kind of collection, although the types of the elements in the different collections may vary. The expansion region is executed once for each element (or position) in the input collection." If it is decided that the execution engine should not reflect the above semantics, then UML needs an additional attribute on ExpansionRegion to indicate whether the individual tokens of the input and out expansion nodes are taken as collections, or whether all the tokens in the nodes are taken as one collection. In ExecUML this attribute value would always be for the second option. Resolution: Revised Text: Actions taken: January 19, 2010: received issue January 28, 2010: transferred to the UML 2.4 RTF from the fUML FTF Discussion: End of Annotations:===== m: webmaster@omg.org Date: 19 Jan 2010 16:48:17 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Notification: Yes Specification: fUML Beta 2 Section: FormalNumber: ptc/2009-10-05 Version: RevisionDate: Page: Title: Expansion nodes using all the tokens in them as a single collection Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: UML expansion regions currently treat each input as a collection, rather than all the inputs as members of a single collection, as the execution engine currently assumes. The description of Expansion Region says "Each input is a collection of values. If there are multiple inputs, each of them must hold the same kind of collection, although the types of the elements in the different collections may vary. The expansion region is executed once for each element (or position) in the input collection." If it is decided that the execution engine should not reflect the above semantics, then UML needs an additional attribute on ExpansionRegion to indicate whether the individual tokens of the input and out expansion nodes are taken as collections, or whether all the tokens in the nodes are taken as one collection. In ExecUML this attribute value would Subject: RE: issue 14991 -- fuml FTF issue Date: Wed, 20 Jan 2010 12:32:40 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 14991 -- fuml FTF issue thread-index: AcqZ8VtYCuvRHn7kQ7mPK18OTExMLAABM82Q From: "Ed Seidewitz" To: Conrad . You submitted this as an fUML issue, but it looks like you are really requesting a change to the UML superstructure. Without a change to the UML superstructure as you suggest, I can.t see dealing with it in fUML since, despite the statement of expansion region semantics currently in the superstructure, no definition is given on what a .collection value. would be. Should this issue be moved to the UML 2.4 RTF? (Where I am pretty sure it will be deferred, but at least it will be on the list for future consideration.) -- Ed -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Wednesday, January 20, 2010 11:53 AM To: issues@omg.org; fuml-ftf@omg.org Subject: issue 14991 -- fuml FTF issue From: webmaster@omg.org Date: 19 Jan 2010 16:48:17 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Notification: Yes Specification: fUML Beta 2 Section: FormalNumber: ptc/2009-10-05 Version: RevisionDate: Page: Title: Expansion nodes using all the tokens in them as a single collection Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: UML expansion regions currently treat each input as a collection, rather than all the inputs as members of a single collection, as the execution engine currently assumes. The description of Expansion Region says "Each input is a collection of values. If there are multiple inputs, each of them must hold the same kind of collection, although the types of the elements in the different collections may vary. The expansion region is executed once for each element (or position) in the input collection." If it is decided that the execution engine should not reflect the above semantics, then UML needs an additional attribute on ExpansionRegion to indicate whether the individual tokens of the input and out expansion nodes are taken as collections, or whether all the tokens in the nodes are taken as one collection. In ExecUML this attribute value would always be for the second option. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org From: "Bock, Conrad" To: "fuml-ftf@omg.org" Date: Thu, 28 Jan 2010 10:01:56 -0500 Subject: RE: issue 14991 -- fuml FTF issue Thread-Topic: issue 14991 -- fuml FTF issue Thread-Index: AcqZ8VtYCuvRHn7kQ7mPK18OTExMLAABM82QAY0aSAA= Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-NIST-MailScanner: Found to be clean X-NIST-MailScanner-From: conrad.bock@nist.gov X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id o0SEtXwM029744 Ed, uld be. > > Should this issue be moved to the UML 2.4 RTF? (Where I am > pretty sure it will be deferred, but at least it will be on > the list for future consideration.) Also fine with me, thx, Conrad ________________________________ From: Juergen Boldt [mailto:juergen@omg.org] Sent: Wednesday, January 20, 2010 11:53 AM To: issues@omg.org; fuml-ftf@omg.org Subject: issue 14991 -- fuml FTF issue From: webmaster@omg.org Date: 19 Jan 2010 16:48:17 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Conrad Bock Company: NIST mailFrom: conrad.bock@nist.gov Notification: Yes Specification: fUML Beta 2 Section: FormalNumber: ptc/2009-10-05 Version: RevisionDate: Page: Title: Expansion nodes using all the tokens in them as a single collection Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: UML expansion regions currently treat each input as a collection, rather than all the inputs as members of a single collection, as the execution engine currently assumes. The description of Expansion Region says "Each input is a collection of values. If there are multiple inputs, each of them must hold the same kind of collection, although the types of the elements in the different collections may vary. The expansion region is executed once for each element (or position) in the input collection." If it is decided that the execution engine should not reflect the above semantics, then UML needs an additional attribute on ExpansionRegion to indicate whether the individual tokens of the input and out expansion nodes are taken as collections, or whether all the tokens in the nodes are taken as one collection. In ExecUML this attribute value would always be for the second option. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org [] n value > statement of expansion region semantics currently in the > superstructure, no definition is given on what a > > You submitted this as an fUML issue, but it looks like you > are really requesting a change to the UML superstructure. > Without a change to the UML superstructure as you suggest, always be for the second option.