-
Key: UML22-1061
-
Legacy Issue Number: 9183
-
Status: closed
-
Source: Simula Research Laboratory ( Dr. Bran Selic)
-
Summary:
Package::appliedProfile should not subset packageImport. Why not? A profile can be imported without being applied, but any applied profile is also implicitly imported in order to make the namespace visible. (The current assumption that a package import implies a profile application does not allow importing of profiles without application – which might be required just for namespace purposes.)
The simplest solution is to define ProfileApplication to be a subclass of DirectedRelationship with a meta-association (Profile::appliedProfile : Profile) indicating the applied profile
-
Reported: UML 2.0 — Mon, 28 Nov 2005 05:00 GMT
-
Disposition: Resolved — UML 2.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — UML 2.0: separate profile application from profile importing
- Key: UML22-1061
- OMG Task Force: UML 2.2 RTF