-
Key: UMLR-556
-
Legacy Issue Number: 17950
-
Status: open
-
Source: Oracle ( Dave Hawkins)
-
Summary:
The paragraph starting "A PackageMerge can be viewed..." is a bit long-winded and contains lots of parentheses.
Proposed Resolution:
Simplify text, removing parentheses:
A PackageMerge can be viewed as a set of transformations whereby the contents of the merged Package and the receiving Package are combined. Matching elements are merged into a single resulting element according to the formal rules of PackageMerge specified below. This is akin to “copying down” the features of superclasses into a subclass: the fully expanded subclass is the equivalent to the resulting package
-
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
UMLR — Location: Page 265, 12.2.3 Semantics PackageMerge - Long-winded package merge description
- Key: UMLR-556
- OMG Task Force: UML 2.6 RTF