-
Key: UML25-237
-
Legacy Issue Number: 17785
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Type: Clarification of imports
The following are not obvious:
1) Can a non-package namespace, such as a class, have a package
import relationship to a package? From the metamodel yes2) Can a namespace, of any type, do a element import of a package?
From the metamodel yes3) Can a package do an element import of a attribute?
From the metamodel yes -
Reported: UML 2.4.1 — Tue, 25 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
It is not clear why these things are claimed to be “not obvious”. As shown in Figure 7.5 and described in the text of
subclause 7.4.3, any Namespace (including a Class) can have a PackageImport of any Package and any Namespace
can have an ElementImport of a Package. In the former case, the the members of the Package are imported, while, in
the latter case, only the Package is imported.
A Package cannot import an attribute, however, since attributes are Properties, which are not PackageableElements.
Per Figure 7.5 and subclause 7.4.3, only PackageableElements may be imported.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Clarification of imports
- Key: UML25-237
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF