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

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

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 15AE921E8235 for <json@ietfa.amsl.com>; Wed, 9 Oct 2013 18:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id uPTfUmpx3I+k for <json@ietfa.amsl.com>; Wed, 9 Oct 2013 18:03:29 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au []) by ietfa.amsl.com (Postfix) with ESMTP id 660C421E823D for <json@ietf.org>; Wed, 9 Oct 2013 18:03:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1067,1371045600"; d="scan'208";a="165126428"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([]) by ipobvi.tcif.telstra.com.au with ESMTP; 10 Oct 2013 12:03:22 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,7223"; a="220830933"
Received: from wsmsg3753.srv.dir.telstra.com ([]) by ipcavi.tcif.telstra.com.au with ESMTP; 10 Oct 2013 12:03:22 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([]) by WSMSG3753.srv.dir.telstra.com ([]) with mapi; Thu, 10 Oct 2013 12:03:21 +1100
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
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2013 01:03:35 -0000

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