RE: SOAP Encoding: Default values

Proposal [10] for dealing with issue 177 [11] suggests that section 3.6
either be removed or downgraded to a note rather than a section.

Henrik Frystyk Nielsen


>-----Original Message-----
>From: Marc Hadley [] 
>Sent: Monday, February 18, 2002 02:59
>To: Martin Gudgin
>Cc: XML Protocol Discussion
>Subject: Re: SOAP Encoding: Default values
>I think its trying to say: An omitted accessor is equivalent to an 
>included accessor with an xsi:nil attribute. The interpretation is 
>application dependent.
>Typical interpretation would be to substitue NULL or some application 
>dependent default value.
>Martin Gudgin wrote:
>> Section 3.6[1] of Part 2[2] states;
>> 'An omitted accessor element implies either a default value 
>or that no 
>> value is known. The specifics depend on the accessor, 
>method, and its 
>> context. For example, an omitted accessor typically implies a Null 
>> value for polymorphic accessors (with the exact meaning of Null 
>> accessor-dependent). Likewise, an omitted Boolean accessor typically 
>> implies either a False value or that no value is known, and 
>an omitted 
>> numeric accessor typically implies either that the value is zero or 
>> that no value is known.' I'm not convinced that this text is at all 
>> useful. It seems to say
>> 'If the accessor isn't there, then any number of things might be 
>> true...' and doesn't say much about what those things might be.
>> What is the paragraph *supposed* to be saying?
>> Gudge
>> [1]
>> [2]

Received on Monday, 18 February 2002 17:39:18 UTC