Issue 17607: Clarify ownership vs. membership for NamedElements (uml25-ftf)
Source: Object Management Group (Mr. Andrew Watson, andrew(at)omg.org)
Nature: Clarification
Severity: Minor
Summary: 

"A namespace may also import NamedElements from other Namespaces, in which case these, along with the ownedMembers, are members of the importing Namespace."


A sentence clarifying ownership vs. membership for NamedElements would be useful. As far as I can tell, every NamedElement is owned by the Namespace in which it was created, but is a member of both its owning Namespace and every Namespace into which it has been successfully imported.

(However, where a NamedElement is a PackageableElement, importing it creates an ElementImport which becomes a member of the Namespace instead, to allow for the possibility of aliasing of the PackageableElement's name.)
Resolution: 
Revised Text: 
Actions taken:
September 19, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 19 Sep 2012 16:18:32 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Andrew Watson
Employer:        OMG
mailFrom:        andrew@omg.org
Terms_Agreement: I agree
Specification:   UML Simplification Submission
Section:         7.4.3
FormalNumber:    ad/12-08-01
Version:         2.5
Doc_Year:        2012
Doc_Month:       August
Doc_Day:         Day
Page:            32
Title:           Clarify ownership vs. membership for NamedElements
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


"A namespace may also import NamedElements from other Namespaces, in which case these, along with the ownedMembers, are members of the importing Namespace."


A sentence clarifying ownership vs. membership for NamedElements would be useful. As far as I can tell, every NamedElement is owned by the Namespace in which it was created, but is a member of both its owning Namespace and every Namespace into which it has been successfully imported.

(However, where a NamedElement is a PackageableElement, importing it creates an ElementImport which becomes a member of the Namespace instead, to allow for the possibility of aliasing of the PackageableElement's name.)