IETF Logo Mail Archive

Re: [Json] Differences between RFC 4627 or the current ECMAScript specification

R S <sayrer@gmail.com> Fri, 27 September 2013 16:34 UTC

Return-Path: <sayrer@gmail.com>
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 F0B4321F9611 for <json@ietfa.amsl.com>; Fri, 27 Sep 2013 09:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 DpNDkJzFq+2G for <json@ietfa.amsl.com>; Fri, 27 Sep 2013 09:34:16 -0700 (PDT)
Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF5621F99DD for <json@ietf.org>; Fri, 27 Sep 2013 09:34:09 -0700 (PDT)
Received: by mail-qe0-f50.google.com with SMTP id a11so1993285qen.9 for <json@ietf.org>; Fri, 27 Sep 2013 09:34:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YEjZJ9UEbU4lEduJJPagoFtgdyrBPcr2mvzNGVSgcnY=; b=nYzzfW+Kc4hYdYVVCc9+Zo8am+fTIivIZu/RGS2IYFK9bd7vEqKaYYaRRwiZpGuwUf TRGI0eBjOzm0fgWb6ReHvQr6VhIOcYTEdgrVdwC8Ov6nb6v/T6owvTBzJkPPDFZ9nRbB YmXGdylB19bC/81V5z6258PiOQx30hc10qosPmoxJlQBW7YLTyf7OqXKanjITcfYMg3L lxFDfuME1ddIQCq2kB7jHs+RSq8dptefXi+bNq5pOmX0mGcgOY2AVR2ru0JS8AiKkeL5 6b1Q5IBuc83FM/27PFaihVr2bomQJNbWpMl1H2AVPCpEcQCiWZmHDmehgtc/Y6u3zSFU 3LQg==
MIME-Version: 1.0
X-Received: by 10.49.132.233 with SMTP id ox9mr10476133qeb.36.1380299641544; Fri, 27 Sep 2013 09:34:01 -0700 (PDT)
Received: by 10.140.86.147 with HTTP; Fri, 27 Sep 2013 09:34:01 -0700 (PDT)
In-Reply-To: <5245A56D.4080205@att.com>
References: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com> <CAChr6SyznBktmOLpT-EiZ5Nm_0jZ16M0tOo4aZ_jhSDb=HHDqg@mail.gmail.com> <23C96FBA-3419-4C97-A075-462F7443013A@vpnc.org> <CAChr6SxCpvGaZSGUDs+6vR4A5xv3NfzpRSkwsE_7c8ep+EX=YA@mail.gmail.com> <0FA0EFFF-2109-4D78-8723-2ECD990C0F82@vpnc.org> <CAChr6SwxgG=P2CYSfHkviG8+2vz6yK1fZQNMCvyWXrM1NgzLZQ@mail.gmail.com> <7058DBBD-9DCE-4A5C-B11D-5FC41A839407@vpnc.org> <CAChr6SwR+04Dcwy=WSf-zVgQ_Nwj_Ke5_dppuqk=CLz8BmdMiA@mail.gmail.com> <5245A56D.4080205@att.com>
Date: Fri, 27 Sep 2013 09:34:01 -0700
Message-ID: <CAChr6SziP6b0Zk63tmnvrmKq+Fgw7Kgcg7Z+=tCpDSLUa8YMYg@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Tony Hansen <tony@att.com>
Content-Type: multipart/alternative; boundary="047d7bdc7ffad1652404e7600d11"
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] Differences between RFC 4627 or the current ECMAScript specification
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: Fri, 27 Sep 2013 16:34:17 -0000

On Fri, Sep 27, 2013 at 8:34 AM, Tony Hansen <tony@att.com> wrote:

> RFC 4627 does not allow trailing commas in objects. Nor does 4627-bis.
>

RFC 4627 allows parsers to accept non-JSON if they wish, while ECMAScript
does not allow this.

- Rob

v2.23.0 | Report a Bug | By Email