Issue 6928: UML 2 Super / Interactions / navigability of enclosingOperation (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: Should InteractionFragment::enclosingOperation be navigable? The association end is named and even has a subset constraint, but the association isn't navigable in that direction for some reason (see Figure 329). Resolution: see above Revised Text: Actions taken: January 25, 2004: received issue March 8, 2005: closed issue Discussion: Change meta-model and Figure 329 to make enclosingOperand property of InteractionFragment navigable. End of Annotations:===== ubject: UML 2 Super / Interactions / navigability of enclosingOperation X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Sun, 25 Jan 2004 18:25:43 -0500 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 01/25/2004 18:25:47, Serialize complete at 01/25/2004 18:25:47 Should InteractionFragment::enclosingOperation be navigable? The association end is named and even has a subset constraint, but the association isn't navigable in that direction for some reason (see Figure 329). Bran Selic Distinguished Engineer IBM Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 e-mail: bselic@ca.ibm.com Issue 6928: UML 2 Super / Interactions / navigability of enclosingOperation (uml2-superstructure-ftf) Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Nature: Uncategorized Issue Severity: Summary: Should InteractionFragment::enclosingOperation be navigable? The association end is named and even has a subset constraint, but the association isn't navigable in that direction for some reason (see Figure 329). Discussion: Change meta-model and Figure 329 to make enclosingOperand property of InteractionFragment navigable. Disposition: Resolved