-
Key: UML22-503
-
Legacy Issue Number: 6492
-
Status: closed
-
Source: David Frankel Consulting ( David Frankel)
-
Summary:
Issue: It appears that associations with neither end names nor
multiplicities on non-navigable ends are used in parts of the UML Core that
are defined via CMOF. See, for example, section 9.9, figure 35, p. 62, for
example. I understand that for elements defined via EMOF, this signifies a
simple property. But is it appropriate for elements defined with CMOF.Recommendation: Either correct this by adding multiplicities and end names
or explain in the specification why it is alright to omit them in these
cases -
Reported: UML 1.5 — Fri, 7 Nov 2003 05:00 GMT
-
Disposition: Resolved — UML 2.1
-
Disposition Summary:
The meaning of this convention should be explained in the document.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — ptc-03-09-15/Non-navigable ends with no role names nor multiplicities
- Key: UML22-503
- OMG Task Force: UML 2.2 RTF