UML 2.6 RTF Avatar
  1. OMG Issue

UMLR — Unnamed elements in a namespace

  • Key: UMLR-325
  • Legacy Issue Number: 19342
  • Status: open  
  • Source: oose Innovative Informatik eG ( Mr. Tim Weilkiens)
  • Summary:

    I’ve asked myself what happens when a namespace owns members that have no name. For example two outgoing include relationships from a use case. A include relationship is a named element that typically has no name.

    NamedElement defines the query isDistinguishableFrom():

    isDistinguishableFrom(n : NamedElement, ns : Namespace) : Boolean The query isDistinguishableFrom() determines whether two NamedElements may logically co-exist within a Namespace. By default, two named elements are distinguishable if (a) they have types neither of which is a kind of the other or (b) they have different names.

    body: (self.oclIsKindOf(n.oclType()) or n.oclIsKindOf(self.oclType())) implies

    ns.getNamesOfMember(self)>intersection(ns.getNamesOfMember)>isEmpty()

    If I call that query at a unnamed include relationship with another unnamed include relationship as paramer n and the owning use case as namespace ns, the query returns true. That means two unnamed elements in a namespace are distinguishable which seems to be wrong from my point of view.

    Is that an issue or did I miss something?

  • Reported: UML 2.5 — Tue, 8 Apr 2014 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT