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

Tim Bray <tbray@textuality.com> Thu, 10 October 2013 04:56 UTC

MIME-Version: 1.0
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E11531CC024B@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E11531CC024B@WSMSG3153V.srv.dir.telstra.com>
Date: Wed, 09 Oct 2013 21:55:58 -0700
Message-ID: <CAHBU6itKOO94etcQiVYrrjUZw0sKEx6k+sp8c1t5NaSbBUnDWw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary="089e0117622754970204e85bd133"
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] {"Height": 125, "Width": "100"} example
Precedence: list

Don’t know if it’s a typo, but it’s kind of charmingly idiosyncratic and
has lasted all these years... let’s spare it.


On Wed, Oct 9, 2013 at 6:03 PM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

> 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
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

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)