KERML — validateClassSpecialization is too strict

The documentation for the constraint validateClassSpecializtion states:

A Class must not specialize a DataType and it can only specialize an Association if it is an AssociationStructure.

with the OCL

ownedSpecialization.general->
    forAll(not oclIsKindOf(DataType)) and
not oclIsKindOf(AssociationStructure) implies
    ownedSpecialization.general->
        forAll(not oclIsKindOf(Association))

However, an Interaction is both a Behavior, which is a kind of Class, and an Association, and, for example, the library interaction Transfer specializes both Performance (a behavior) and BinaryLink (an association). But the above constraint disallows this specialization.

The validateClassSpecialization constraint needs to be updated to allow both AssociationStructures and Interactions to specialize Associations.