UMLR — consistent ordering of Association::memberEnd and ownedEnd

Given that these are both

, indicating that ordering is important, then it seems only sensible that the ordering should be consistent, i.e. if Property p appears before Property q in memberEnd then that should also be the case for ownedEnd.
There should therefore be a constraint added to this effect.

There should probably also be a review of other cases where an ordered Property subsets another ordered property.
Or should there be a more general constraint defined at the meta-level?