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

R S <sayrer@gmail.com> Fri, 27 September 2013 00:54 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 D5AE321F91F2 for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 17:54:35 -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 6bCYjiTRZ9+d for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 17:54:35 -0700 (PDT)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id C492E21F963F for <json@ietf.org>; Thu, 26 Sep 2013 17:54:34 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id t7so1282437qcv.21 for <json@ietf.org>; Thu, 26 Sep 2013 17:54:29 -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=Us19mLF7uocV1+9vcL7Kc/FuAVOHilqB1azA8n4eR4M=; b=fJ8sXKRr5EgB7Uxdob0noDZPYQe9skROQvhxPwmU36Ti9tVklnZrt+bi8LE3Al0NYp NK3rBb6v65UafqgVgFyWS89V1uceJXVULLJ8Pz1YKnTJRecHXHKPg1Urr4QZsqNspjvK ZLokvk6E3rlEh1erZJFFKGMNXS3VAhl/LGUigiv48fWRzvMuTZyQbq9OSAqhzaMvdBKm TC2Ra/ALHX/KTpV984l+1up6UjR+tB+UhTH9B6gmjQ0ClwnuuNN+Ixk9bc6JRjX3bf1D oneQ6p25WTuKxSxtE57pW6nWvZPvuuBu6g7ThRFJQuWBNZNZwbTma31+IF2j7hXMT+bM F2AA==
MIME-Version: 1.0
X-Received: by 10.224.89.1 with SMTP id c1mr10597704qam.100.1380243269213; Thu, 26 Sep 2013 17:54:29 -0700 (PDT)
Received: by 10.140.86.147 with HTTP; Thu, 26 Sep 2013 17:54:29 -0700 (PDT)
In-Reply-To: <0FA0EFFF-2109-4D78-8723-2ECD990C0F82@vpnc.org>
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>
Date: Thu, 26 Sep 2013 17:54:29 -0700
Message-ID: <CAChr6SwxgG=P2CYSfHkviG8+2vz6yK1fZQNMCvyWXrM1NgzLZQ@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="001a11c3c798c3e68a04e752ed2d"
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 00:54:36 -0000

On Thu, Sep 26, 2013 at 5:20 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Sep 26, 2013, at 4:23 PM, R S <sayrer@gmail.com> wrote:
>
> > Are you saying the concerns you list below warrant a recharter? If so, I
> disagree.
>
> No, I was suggesting we ignore the charter and beg for forgiveness.
>

Bad suggestion--the charter means what it says. If it doesn't, integrity
would compel us to consider all of the suggestions that fall outside of the
charter.



>
> A different thought is to (a) assume that version 5.1 is the "current
> ECMAScript" and (b) simply mimic the two bullets from the beginning of
> Section 15.12. This worries me because the JSON definition in 5.1 is not
> exactly the same as 3 (which is what 4627 was based on),


There is no JSON definition in ECMAScript 3.




> and it is not exactly the same as the JSON definition in the current draft
> of 6. Therefore, us saying "here are some differences" seems to be of more
> danger than actual value.
>


We are free to cite the current version of ECMAScript, as Tim points out.



>
> > - Some of what ECMAscript says about JSON is intertwingled with the
> definition of ECMAscript, such as "exactly how to interpret numbers"
> >
> >
> > We wouldn't even need to add a reference to explain this:
> >
> > "4.3.19 Number value
> > primitive value corresponding to a double-precision 64-bit binary format
> IEEE 754 value"
> >
> > <http://www.ecma-international.org/ecma-262/5.1/#sec-4.3.19>
>
> That seems irrelevant.


Disagree.



> Section 15.12.2 and 15.12.3 talk about "Numbers", not "number values".


It's the same:
<http://www.ecma-international.org/ecma-262/5.1/#sec-8.5>



> TC39 might change this in version 6, or they might not; we cannot tell.
>

Again, we won't be citing a future version with hypothetical changes.

> But you seem keen on us having such a section. Please provide the full
wording for what you
> think would be valuable to include.

I already have--feel free to reuse it.

- Rob