UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — Optional String Multiplicity

Open Closed All
  • Key: UML25-263
  • Legacy Issue Number: 17816
  • Status: closed  
  • Source: Change Vision ( Michael Chonoles)
  • Summary:

    Why is the multiplicity for String include 0, but the multiplicities for the other literals do not? LiteralString should be as optional as LiteralBoolean
  • Reported: UML 2.4.1 — Wed, 26 Sep 2012 04:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    LiteralString::value has a multiplicity of 0..1 in UML 2.5 for no other reason than to maintain backward compatibility
    with the UML 2.4.1 metamodel, which was a goal for UML 2.5. A LiteralString with no value essentially represents
    a string of “no characters” and so is equivalent to a LiteralString whose value is the empty string.
    Disposition: Closed - No Change
  • Updated: Fri, 6 Mar 2015 20:59 GMT