UML25 — UML2 super/CommonBehavior/Opaque behavior : bad OO modelling

When we see the attributes of OpaqueBehavior :
• body : String [1..*] Specifies the behavior in one or more languages.
• language : String [*] Languages the body strings use in the same order as
the body strings.

We can state that this is bad modelling practice : two attributes are sets,
which elements have to be related 2 by 2 according to an ordering rule. This
is even bad database modeling practice (violation of the 1st normal form
rule).

Proposition :
Create an additional class "Language expression", having 2 attributes :
Language and Body, and relate it to "OpaqueBehavior" instead of these two
guilty attributes.

Discussion
The proposed change may be better OO modeling practice, but it would cause a significant backward incompatibility
for model interchange. Note that the patter of parallel body and language attributes is used not only for OpaqueBehavior,
but also for OpaqueExpression and OpaqueAction. The cost of making such a change in all these cases does
not seem worth the benefit of a marginal improvement in modeling practice.
Disposition: Closed - No Change