[Json] {"Height": 125, "Width": "100"} example

"Manger, James H" <James.H.Manger@team.telstra.com> Thu, 10 October 2013 01:03 UTC

From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "json@ietf.org" <json@ietf.org>
Date: Thu, 10 Oct 2013 12:03:21 +1100
Thread-Topic: {"Height": 125, "Width": "100"} example
Thread-Index: Ac7FVINCURNGj9hiS9qr0wwFASRz+w==
Message-ID: <255B9BB34FB7D647A506DC292726F6E11531CC024B@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [Json] {"Height": 125, "Width": "100"} example
Precedence: list

4627 and 4627bis include an example with the following object members:
  {
    "Height": 125,
    "Width":  "100"
  },

This looks like a typo ("100" instead of 100), but it is still valid JSON.

Is this a typo (that -bis should correct)?
Or is this a subtle suggestion to JSON parsers that they should automatically
try to convert strings to numbers if an app asks for, say, the "Width" field
as an int but the parser finds a string in the JSON?

--
James Manger

Re: [Json] {"Height": 125, "Width": "100"} example Tim Bray
[Json] {"Height": 125, "Width": "100"} example Manger, James H
Re: [Json] {"Height": 125, "Width": "100"} example Tim Bray
Re: [Json] {"Height": 125, "Width": "100"} example Martin J. Dürst
Re: [Json] {"Height": 125, "Width": "100"} example Paul Hoffman
Re: [Json] {"Height": 125, "Width": "100"} example Matt Miller (mamille2)