Issue 6135: Pins on structured nodes 1 (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary: Figure 193 - Structured nodes (CompleteStructuredActivities) shows
StructuredActivityNode, LoopNode, and ConditionalNode inheriting from
Action, but LoopNode and ConditionalNode already inherit from
StructuredActivityNode (Figure 192 - Structured nodes).

Resolution: see above
Revised Text: 
Actions taken:
August 30, 2003: received issue
March 8, 2005: closed issue
Discussion: 
In Figure 193, p 278, remove generalizations from ConditionalNode and LoopNode to
Action. The figure makes StructuredActivityNode an Action, and ConditionalNode and
LoopNode are already subtypes of StructuredActivityNode from Figure 192.
End of Annotations:=====
Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Nature: Revision
Severity: Significant
Subject: ExpansionRegion


Why does ExpansionRegion have its own input/output metaassociations,
rather than the ones on actions?  (BTW, these associations are
misnomers, they are not just elements).  ExpansionRegion inherites pins

OMG Issue No: 6134
Title:	ExpansionRegion
Source:
Kabira Technologies, Inc. (Mr. Conrad Bock, conrad.bock@nist.gov)
Summary:
Why does ExpansionRegion have its own input/output metaassociations, rather than the ones on actions?  (BTW, these associations are misnomers, they are not just elements).  ExpansionRegion inherites pins from StructuredActivityNode in complete activities
Discussion:
The input/output associations on ExpansionRegion are the ones with the collections used in the iteration.  The values on input/output pins are constant over the iteration.
Disposition:	Closed no change
from StructuredActivityNode in complete activities.