W3C home > Mailing lists > Public > public-forms@w3.org > November 2010

Re: First write up of JSON

From: John Boyer <boyerj@ca.ibm.com>
Date: Tue, 2 Nov 2010 05:32:53 -0700
To: "Steven Pemberton" <Steven.Pemberton@cwi.nl>
Cc: "Forms WG" <public-forms@w3.org>
Message-ID: <OFA1E457F4.B4137F09-ON882577CF.0044323C-882577CF.0044EE96@ca.ibm.com>
Hi Steven,

1) New MIPs bad, extra attributes good :-)

2) Perhaps the json attributes should be namespace qualified so that they 
are easily seen to not be part of the data, e.g. <location 
json:type="array">Lyon</location> and <_foo json:name="$foo">...</_foo>. 
Obviously not strictly necessary since there can be no attributes for 
other reasons; also, if done, would mean declaring the json namespace on 
the root json element.

3) I think you meant to send the wiki link to the readable version (
http://www.w3.org/MarkUp/Forms/wiki/Json) rather than the wiki link to the 
editable version.


"Steven Pemberton" <Steven.Pemberton@cwi.nl>
"Forms WG" <public-forms@w3.org>
11/02/2010 02:09 AM
First write up of JSON

Following on our productive JSON discussion yesterday 
(http://www.w3.org/2010/11/01-forms-minutes.html#item03) I have written it 
up on the wiki page


However, in writing it up, I came to some slightly different conclusions.

The main discussions was on how to deal with empty and single-element 
arrays. Since an array like

                 {"company":"example.com", "locations":[{"place": 

gets transformed to


                 {"company":"example.com", "locations":[{"place": 

would appear as


which would be indistinguishable from

                 {"company":"example.com", "locations":{"place": 

So, in order to be able to re-serialise correctly, the system needs to be 
able to distinguish the two cases. The conclusion we came to in the 
meeting was to use new sorts of MIP, usually used internally to the 
system, so that the system knows that an element actually represents an 
array. But then when the instance doesn't originate from externally, but 
is created from within the form, you need a way to set the MIP:

                 <bind ref="locations" json-array="true()"/>

which means new XForms facilities.

While writing it up, I realised that the alternative solution of using 
attributes would not require new XForms facilities. The knowledge is then 
exclusively in the parse and synchronise parts. So now the above array 
gets read as


There is no chance of name clashes, since there are no attributes in JSON.

Received on Tuesday, 2 November 2010 12:33:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:04 UTC