Re: [Json] Allow any JSON value at the top level

["Joe Hildebrand (jhildebr)" <[e-mail]>]

I like this change, but it has impact on section three.  These JSON docs:

0
""
"?"

means that the table should probably look like:

   00 00 00 xx  UTF-32BE
   00 xx ?? xx  UTF-16BE
   xx 00 00 00  UTF-32LE
   xx 00 xx ?? UTF-16LE
   xx xx ?? ?? UTF-8

algorithmically:

if length<2
  return UTF-8
if buf[0]
  if buf[1]
    return UTF-8
  if length<4 or buf[2]
    return UTF-16LE
  return UTF-32LE
if buf[1]
  return UTF-16BE
return UTF-32BE



On 6/6/13 9:51 PM, "Manger, James H" <[e-mail]>
wrote:

>The current spec only allows a JSON text to be an object or array.
>Section 2. "JSON Grammar" says:
>
>   A JSON text is a serialized object or array.
>
>   JSON-text = object / array
>
>
>I propose allowing a JSON text to be any JSON value.
>
>   A JSON text is a serialization of any JSON value.
>
>   JSON-text = value
>
>   value = false / null / true / object / array / number / string
>
>
>ECMAScript already allows this.
>http://www.ecma-international.org/ecma-262/5.1/#sec-15.12
>
>   * The top level JSONText production of the ECMAScript JSON grammar
>     may consist of any JSONValue rather than being restricted to being
>     a JSONObject or a JSONArray as specified by RFC 4627.
>
>--
>James Manger
>
>
>_______________________________________________
>json mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/json
>


-- 
Joe Hildebrand