Source: Change Vision ( Michael Chonoles)
It appears that Classes, as Namespaces, can contain Packages.
The consequences of this are unclear and a bit confusing.
For example, a package within a class can contain attributes for organization purposes.
It appears that the package can have visibility that is marked private or public, but not protected nor package level visibility.
In this case, when there is a package in the class, it appears that you can't make the package protected (and visible to a specialization of the class) or package level visibility (visible to member of any immediate outer package).
Reported: UML 2.5 — Tue, 4 Nov 2014 03:00 GMT
Updated: Sat, 30 Jan 2016 12:07 GMT