W3C home > Mailing lists > Public > public-forms@w3.org > March 2015

Re: Minutes 2015-03-25

From: Alain Couthures <alain.couthures@agencexml.com>
Date: Thu, 26 Mar 2015 21:27:59 +0100
Message-ID: <55146BCF.80700@agencexml.com>
To: Forms WG <public-forms@w3.org>

A failed JSON serialization can be obtained in many situations because 
JSON support is based on an implicit schema: a document element named 
"json",  attributes with a limited list of possible values.

For example, trying to generate a JSON object, authors might misspell an 
attribute value or forget to insert one of them. Serialization becomes 
impossible. Instead of an error being raised, an empty string might be 
returned (for the parse() function, an empty sequence is returned if 
parsing fails).

Example #1 ("bool" instead of "boolean"):
    <json object="true"><selected type="bool">true</selected></json>

Example #2 ("OK" instead of "true"):
<json object="true"><selected type="boolean">OK</selected></json>

Example #3 ("array" instead of "object"):
<json array="true"><selected type="boolean">true</selected></json>


Le 25/03/2015 17:04, Steven Pemberton a écrit :
> http://www.w3.org/2015/03/25-forms-minutes.html
> [NEW] ACTION: Erik to confirm that min() and max() are compatible with 
> the ones in XPath 2 [recorded in 
> http://www.w3.org/2015/03/25-forms-minutes.html#action01]
> [NEW] ACTION: Erik to propose what to do if serialization in 
> serialize() fails [recorded in 
> http://www.w3.org/2015/03/25-forms-minutes.html#action03]
> [NEW] ACTION: Steven to fix up the definition of power() [recorded in 
> http://www.w3.org/2015/03/25-forms-minutes.html#action02]
> Also: Alain to post an example of a failed JSON serialization
> Next week: rest of the Expressions spec
> Steven
Received on Thursday, 26 March 2015 20:28:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:00 UTC