UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — Default value for LiteralString

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

    Why does LiteralString have no default value? suggest the Empty string. Discussion:
    If the answer to this relates to problem 8.001, then a detailed explanation is required in the spec.
  • Reported: UML 2.4.1 — Wed, 26 Sep 2012 04:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    The real question is why some LiteralSpecifications have a default value, more than why LiteralString does not. The
    only reason that certain LiteralSpecifications still have default values in UML 2.5 is for backward compatibility with
    the UML 2.4.1. In particular, removing default values for LiteralInteger and LiteralUnlimitedNatural would have a
    significant effect on how multiplicity bound are serialized in user models.
    Disposition: Closed - No Change
  • Updated: Fri, 6 Mar 2015 20:59 GMT