UML241 — property.opposite

It seems there is an issue with derived Property.opposite.

Spec says:

/ opposite : Property [0..1] In the case where the property is one navigable end of a binary association with both ends navigable, this gives the other end.

By description, it should keep reference to opposite navigable end, but OCL works only when navigable end is owned by class.
It does not work when navigable end is owned by association:

Constraint #1:
[1] If this property is owned by a class associated with a binary association, and the other end of the association is also owned by a class, then opposite gives the other end.
opposite = if owningAssociation->isEmpty() and association.memberEnd->size() = 2 then let otherEnd = (association.memberEnd - self)>any() in if otherEnd.owningAssociation>isEmpty() then otherEnd else Set{} endif else Set {} endif

Any comments?
Which one is correct? Property description or constraint text?

This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change