W3C home > Mailing lists > Public > public-xformsusers@w3.org > February 2016

Re: JSON: empty number and boolean values

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Thu, 04 Feb 2016 21:43:00 +0100
To: "Erik Bruchez" <erik@bruchez.org>, "Nick Van den Bleeken" <Nick.Van.den.Bleeken@inventivegroup.com>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Message-ID: <op.ycbs5yu4smjzpq@steven-aspire-s7>
On Wed, 03 Feb 2016 22:21:51 +0100, Nick Van den Bleeken  
<Nick.Van.den.Bleeken@inventivegroup.com> wrote:

>
> Option 2 is also my favorite.
Agree.

Steven

> On 3 Feb 2016 8:59 p.m., Erik Bruchez <erik@bruchez.org> wrote:
>> All,
>>
>> Say we receive the following JSON:
>>
>>    { "name": "Mark", "age": 21 }
>>
>> which converts to:
>>
>>    <json type="object">
>>        <name>Mark</name>
>>        <age type="number">21</age>
>>    </json>
>>
>> We have an input field bound to:
>>
>>    instance()/age
>>
>> Then the user blanks the field, which, say, is not required. So we have:
>>
>>    <json type="object">
>>        <name>Mark</name>
>>        <age type="number"></age>
>>    </json>
>>
>> Now when we try to serialize back the XML to JSON, what should happen?
>> I see 3 options:
>>
>> 1. Generate an empty string for "age".
>> 2. Generate `null` "age".
>> 3. Raise an error.
>>
>> I don't like #1 because that changes types in an unexpected way.
>>
>> I don't like #3 because it seems like we should have the possibility
>> to handle optional values.
>>
>> My preference would go to #2:
>>
>>    { "name": "Mark", "age": null }
>>
>> The rule would be: "if we have a `number` or `boolean` element whose
>> string value cannot be converted back to a number or a boolean JSON
>> value, either because it is empty or blank or because it doesn't match
>> the lexical value of a JSON number of boolean, then generate a
>> `null`".
>>
>> Feedback welcome.
>>
>> -Erik
Received on Thursday, 4 February 2016 20:43:40 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 4 February 2016 20:43:41 UTC