UMLR — Odd restriction on state machine redefinition context

The StateMachine metaclass’s redefinition of the "isRedefinitionContextValid(redefinedElement : RedefinableElement) : Boolean" operation is oddly over-constrained, requiring that the context classifier of a redefining state machine redefine the context classifier of the redefined state machine.  It seems more plausible that this constraint should only require, or should also allow, that the context classifier of the redefining state machine be a specialization of the context classifier of the redefined state machine.  Otherwise, state machine redefinition can only be valid for state machines that are owned behaviours of classifiers that are nested in other classifiers, because these context classifiers are required to have their own valid redefinition contexts.

That is to say, one might expect an OCL formulation more like this:

body:
redefinedElement.oclIsKindOf(StateMachine) and
let redefinedStateMachine : StateMachine = redefinedElement.oclAsType(StateMachine) in
self.'context'().allParents()->includes(redefinedStateMachine.'context'())