-
Key: UML14-518
-
Legacy Issue Number: 7135
-
Status: closed
-
Source: X-Change Technologies ( Joaquin Miller)
-
Summary:
There are three different ways to specify text strings used in the notation and two variations.
The three ways:
1. a sort of Bakus-Naur form as in: multiplicity ::= <multiplicity_range> [ ‘
{‘ <order_designator> ‘}’ ] see Super 7.4.1
2. a second way as in: [visibility] [/] name [: type] [multiplicity] [= default] [
{ property-string }] see Super 7.8.1 The characters that are a part of the notation (virgule, colon, equals and braces) are simply shown.
3. a third way, combining features of both as in: visibility name ‘<‘ template-parameter-list ‘>’ ‘<<‘binding-expression-list ‘>>’‘( ‘ parameter-list ‘)’ ‘:’ property-string see Super 17.5.12 The characters that are a part of the notation (angle bracket, parens, colon) are enclosed in single quotes. (The inverted comma and apostrophe are not consistently used as opening and closing single quotes.)
Both the second and the third ways are sometimes used at the same place as in: [visibility] [/] name [: type] [multiplicity] [= default] [{ property-string }] {{ [ name ] ‘:’ classname } | name } [ ‘[‘ multiplicity ‘]’ ] see Super 17.5.7
The two variations:
a. Sometimes a single bracket does double duty as in: direction name : type-expression [multiplicity] = default-value [
{ property-string }] see Super 7.10.1 Here, the brackets around multiplicity indicate both that multiplicity is optional, and that the multiplicity is to be shown inside brackets. see Super 7.10.1
b. Sometimes the brackets are not used when an item is optional as in: visibility name ( parameter-list ) : property-string see Super 7.10.1
-
Reported: XMI 2.0 — Tue, 9 Mar 2004 05:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML14 — adopt a single notation to specify text strings used in the notation
- Key: UML14-518
- OMG Task Force: UML 1.4 RTF