Issue 18287: Fixed-point issues with the definition of default values for literals (uml25-ftf)
Source: Microsoft (Mr. Steve Cook, stcook(at)microsoft.com)
Nature: Uncategorized Issue
Severity: 
Summary: The definition of LiteralBoolean in the XMI for UML1.5 includes the following:

 

    <packagedElement xmi:type="uml:Class" xmi:id="LiteralBoolean" name="LiteralBoolean">

      …

      <ownedAttribute xmi:type="uml:Property" xmi:id="LiteralBoolean-value" name="value" visibility="public">

        …

        <defaultValue xmi:type="uml:LiteralBoolean" xmi:id="LiteralBoolean-value-_defaultValue"/>

      </ownedAttribute>

…

 

So the default value for value, which is correctly specified as false in the model, is specified by the absence of a value attribute as “the default value for LiteralBoolean::value” in the XMI. This is circular and ill-defined.

 

One issue is with the XMI specification.  The rule that property values should not be serialized when they have their default value should not apply when those properties are being used to define default values for themselves.                                             Another issue is with the UML xmi.  This needs to serialize the value for the default value of literals, regardless of other considerations. In the case above, value=”false”.



Resolution: 
Revised Text: 
Actions taken:
December 5, 2012: received issue
Discussion: 

End of Annotations:=====

nt-Antispam-Report: CIP:131.107.125.8;KIP:(null);UIP:(null);IPV:NLI;H:TK5EX14MLTC104.redmond.corp.microsoft.com;RD:autodiscover.service.exchange.microsoft.com;EFVD:NLI
X-SpamScore: 0
X-BigFish: VS0(zzc85fhzz1de0h1202h1d1ah1d2ahzz17326ah8275bh8275dh18c673hz2fh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1155h)
From: Steve Cook <Steve.Cook@microsoft.com>
To: "issues@omg.org" <issues@omg.org>,
        "uml25-ftf@omg.org"
	<uml25-ftf@omg.org>,
        "mof2xmi-rtf@omg.org" <mof2xmi-rtf@omg.org>
Subject: Fixed-point issues with the definition of default values for
 literals
Thread-Topic: Fixed-point issues with the definition of default values for
 literals
Thread-Index: Ac3TCu577f9Ed/QnQeWKIvuLKn0AbA==
Date: Wed, 5 Dec 2012 17:06:58 +0000
Accept-Language: en-GB, en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.166.18.104]
X-OriginatorOrg: microsoft.com
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-Tracker: AAAAAA==

The definition of LiteralBoolean in the XMI for UML1.5 includes the following:
 
    <packagedElement xmi:type="uml:Class" xmi:id="LiteralBoolean" name="LiteralBoolean">
      .
      <ownedAttribute xmi:type="uml:Property" xmi:id="LiteralBoolean-value" name="value" visibility="public">
        .
        <defaultValue xmi:type="uml:LiteralBoolean" xmi:id="LiteralBoolean-value-_defaultValue"/>
      </ownedAttribute>
.
 
So the default value for value, which is correctly specified as false in the model, is specified by the absence of a value attribute as .the default value for LiteralBoolean::value. in the XMI. This is circular and ill-defined.
 
 
Another issue is with the UML xmi.  This needs to serialize the value for the default value of literals, regardless of other considerations. In the case above, value=.false..
 
-- Steve