UML24 — Expansion nodes using all the tokens in them as a single collection

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.

This issue is obsolete. The specification of the semantics of ExpansionRegions in the UML 2.5 beta specification, in
Subclause 16.12.3, covers this.
Disposition: Closed - No Change