- From: Steven Pemberton <Steven.Pemberton@cwi.nl>
- Date: Wed, 01 Jun 2011 15:55:52 +0200
- To: "Steven Pemberton" <Steven.Pemberton@cwi.nl>, "Nick Van den Bleeken" <Nick.Van.den.Bleeken@inventivegroup.com>
- Cc: "Forms WG" <public-forms@w3.org>
The reason they are there is to allow serialization to roundtrip the data.
That might work for numbers and boolean, but I don't see how it would work
for arrays. (But I may be wrong).
Steven
On Wed, 01 Jun 2011 11:10:41 +0200, Nick Van den Bleeken
<Nick.Van.den.Bleeken@inventivegroup.com> wrote:
> Steven,
>
> Couldn't we use auto generated binds that attach the type information to
> the nodes for that?
>
> Regards,
>
> Nick van den Bleeken
>
>
> On 30 May 2011, at 14:41, "Steven Pemberton" <Steven.Pemberton@cwi.nl>
> wrote:
>
>> I should note a slight difference with what we had earlier agreed that
>> dawned on me while firming it up, that got in the way of round-tripping.
>>
>> In the transformation of
>> {"size": 50} and {"size": "50"}
>> you can't tell the difference if you transform both to
>> <json><size>50</size></json>
>>
>> So I've use the type attribute to (arbitrarily) mark the numeric case:
>>
>> <json><size type="number">50</size><json>
>>
>> Similarly with the boolean and null cases.
>>
>> Steven
>>
>>
>> On Fri, 27 May 2011 16:51:50 +0200, Steven Pemberton
>> <Steven.Pemberton@cwi.nl> wrote:
>>
>>> I have rewritten the JSON section, according to my action item.
>>>
>>> http://www.w3.org/MarkUp/Forms/wiki/Json
>>>
>>> Comments gladly received.
>>>
>>> Steven
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>
> ________________________________
>
> Inventive Designers' Email Disclaimer:
> http://www.inventivedesigners.com/email-disclaimer
Received on Wednesday, 1 June 2011 13:56:33 UTC