Issue 10893: Names, unique names. (odm-ftf)
Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Critical
Summary: Names, unique names. In Section 16.5.2 (Names), the first two paragraph implies UML assumes unqiue names. M1 instance specifications in UML can have different names, but refer to the same M0 individual. They can also have the same name and refer to different M0 individuals. The third paragraph implies UML does not have name management (given the title of Section 16.5), which of course it does in namespaces. 

Resolution: 
Revised Text: 
Actions taken:
March 30, 2007: received issue
Discussion: 
FTF resources were scarce and priority was given to issues against normative sections, hence many issues such as this were left unresolved.

Disposition:	Deferred to RTF

End of Annotations:=====

m: webmaster@omg.org
Date: 30 Mar 2007 01:04:33 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.giv
Notification: No
Specification: Ontology Definition Metamodel
Section: Chapter 16
FormalNumber: ptc/06-10-11
Version: 
RevisionDate: 
Page: 
Nature: Revision
Severity: Critical
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
Description
Names, unique names. In Section 16.5.2 (Names), the first two paragraph implies UML assumes unqiue names. M1 instance specifications in UML can have different names, but refer to the same M0 individual. They can also have the same name and refer to different M0 individuals. The third paragraph implies UML does not have name management (given the title of Section 16.5), which of course it does in namespaces.