IETF Logo Mail Archive

Re: [Json] JSON: remove gap between Ecma-404 and IETF draft

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 12 November 2013 15:29 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A4B11E8181; Tue, 12 Nov 2013 07:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level:
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWJm8uxRCGxZ; Tue, 12 Nov 2013 07:29:22 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id ABBC621E8182; Tue, 12 Nov 2013 07:29:05 -0800 (PST)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id rACFSTbU024846 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 12 Nov 2013 08:29:00 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CADnb78h8AjPcQLOCwNm0Pt3pObh6uFV5+zy0c_YU6B-u4MtY1Q@mail.gmail.com>
Date: Tue, 12 Nov 2013 07:29:00 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <AA45B3C6-1DC5-4B1E-8045-C9FE76022584@vpnc.org>
References: <CADnb78h8AjPcQLOCwNm0Pt3pObh6uFV5+zy0c_YU6B-u4MtY1Q@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
X-Mailer: Apple Mail (2.1822)
Cc: JSON WG <json@ietf.org>, IETF Discussion <ietf@ietf.org>, www-tag@w3.org, es-discuss <es-discuss@mozilla.org>
Subject: Re: [Json] JSON: remove gap between Ecma-404 and IETF draft
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: Tue, 12 Nov 2013 15:29:23 -0000

[[ Adding the JSON WG to this thread ]]

On Nov 11, 2013, at 11:01 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> To improve JSON interoperability the IETF should not define a more
> restricted version of JSON than defined by Ecma-404.
> 
> Parsers exist that can parse "42" today and parsers that cannot parse
> "42" today can be meaningfully upgraded to do so too. This would not
> break those parsers, unless they depend on parsing 42 as an error,
> which is a far more unlikely scenario than parsing it as 42 given
> precedence.
> 
> (Worth pondering about: what to do about a leading BOM, which
> XMLHttpRequest and browsers allow, but neither IETF nor Ecma-404
> allow.)
> 
> 
> -- 
> http://annevankesteren.nl/
>

v2.23.0 | Report a Bug | By Email