UML 2.4 RTF Avatar
  1. OMG Issue

UML24 — UML2 - definition of Property.opposite is wrong

Open Closed All
  • Key: UML24-8
  • Legacy Issue Number: 14626
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Steve Cook)
  • Summary:

    Currently the spec says:

    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

    This is wrong. The opposite should be calculated properly whatever the property is owned by. It should say “if the property is an association end of a binary association, opposite gives the other end”.
  • Reported: UML 2.3 — Fri, 13 Nov 2009 05:00 GMT
  • Disposition: Resolved — UML 2.4
  • Disposition Summary:

    This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
    Disposition: Closed - No Change
  • Updated: Fri, 6 Mar 2015 20:58 GMT