EXPRESS_ — Associations that should be composite

Many associations in the specification should be specified as "composite", in order to facilitate XMI export and other implementation technologies. The following is a list of associations (by their end names) that are clearly 'composite' in intent, as their definitions indicate:

(Core, clause 8)
EntityType:unique-rules
LocalScope:local-elements
NamedType:type-elements
NamedType:domain-rules
Schema:schema-elements
Schema:interfaces EntityType:declares
SingleEntityType:declares
SingleEntityValue:properties

(Instances, clause 9)
ARRAYValue:member-slot
BAGValue:member-slot
EnumerationType:declared-items
LISTValue:member-slot

(Algorithms, clause 10)
Algorithm:formal-parameters
Algorithm:actual-types
Algorithm:body
AlgorithmScope:variables
Function:result
Parameter:type-constraints
Parameter:structure-constraints

(Rules, clause 11)
GlobalRule:supporting-body
GlobalRule:contains-rules
SupertypeRule:constraints

(Expressions, clause 12)
AggregateInitializer:bindings
FunctionCall:actual-parameters
PartialEntityConstructor:bindings
QueryExpression:query-variable

(Statements, clause 13)
CaseAction:action
CaseStatement:cases
IfStatement:then-actions
IfStatement:else-actions
ProcedureCall:actual-parameters
RepeatStatement:body
RepeatStatement:control-variable
StatementBlock:body-statements

Proposed Resolution:
For each of the above, modify the UML diagram to show the 'composition' association and modify the text specification of the association end by adding:
Properties: composite

As proposed, and fix related association properties. In particular, Scope:named-elements, LocalScope:local-elements, NamedType:type-elements are composites and derived unions.
Document ParameterType: constraints, which is also a composite derived union.
Figures 2, 12, 19, 27, 29, 30, 44 are further modified by other issues.