Issue 11155: Section: Constructs (uml2-rtf)
Source: MEGA International (Mr. Antoine Lonjon, antoine.lonjon(at)mega.com)
Nature: Revision
Severity: Critical
Summary: Package import is defined in the context of Namespace. This has two consequences: 1. Namespaces such as Classe, Node, and UseCase can import Packages. This does not seem to be a good design goal. 2. There is a circular definition between Package and Namespace: Package is a sub-type of Namespace and Namespace requires the definition of Package and PackagedElement. 

Resolution: 
Revised Text: 
Actions taken:
July 16, 2007: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 16 Jul 2007 15:49:38 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



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

Name: Antoine Lonjon
Company: MEGA International
mailFrom: antoine.lonjon@mega.com
Notification: Yes
Specification: Unified Modeling Language: Infrastructure
Section: Constructs
FormalNumber: formal/07-02-06
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
Package import is defined in the context of Namespace. This has two consequences: 1. Namespaces such as Classe, Node, and UseCase can import Packages. This does not seem to be a good design goal. 2. There is a circular definition between Package and Namespace: Package is a sub-type of Namespace and Namespace requires the definition of Package and PackagedElement.