Issue 15401: Qualified name is incorrectly claimed to be unambiguous (uml2-rtf)
Source: Oracle (Mr. Dave Hawkins, dave.hawkins(at)oracle.com)
Nature: Clarification
Severity: Minor
Summary: The description of NamedElement claims that:


A named element also has a qualified name that allows it to be
unambiguously identified within a hierarchy of nested namespaces.

However the validation rules for names within a namespace take, by default, the type into account and, for a behavioral feature, parameters. The qualified name uses only the name and thus isn't unambiguous as claimed.
Resolution: 
Revised Text: 
Actions taken:
August 6, 2010: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 06 Aug 2010 11:47:53 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Dave Hawkins
Employer:        Oracle
mailFrom:        dave.hawkins@oracle.com
Terms_Agreement: I agree
Specification:   UML
Section:         7.3.33
FormalNumber:    09-09-09
Version:         2.3
Doc_Year:        2009
Doc_Month:       September
Doc_Day:         Day
Page:            100
Title:           Qualified name is incorrectly claimed to be unambiguous
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


The description of NamedElement claims that:


A named element also has a qualified name that allows it to be
unambiguously identified within a hierarchy of nested namespaces.

However the validation rules for names within a namespace take, by default, the type into account and, for a behavioral feature, parameters. The qualified name uses only the name and thus isn't unambiguous as claimed.