IETF Logo Mail Archive

Re: [Json] ECMA-262 normative?

R S <sayrer@gmail.com> Tue, 01 October 2013 01:55 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 57D8D21F9468 for <json@ietfa.amsl.com>; Mon, 30 Sep 2013 18:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level:
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.005, 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 PjjBU1y95-X1 for <json@ietfa.amsl.com>; Mon, 30 Sep 2013 18:55:55 -0700 (PDT)
Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 45C0621F9928 for <json@ietf.org>; Mon, 30 Sep 2013 18:55:55 -0700 (PDT)
Received: by mail-qa0-f50.google.com with SMTP id j7so2901799qaq.2 for <json@ietf.org>; Mon, 30 Sep 2013 18:55:54 -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=TqDw4Z/YK1WUwlQnPndXrdajMLknNrfr4jjq1aHYp8k=; b=X2+Y5wroTcCSbv28m0t6tlctYuwBxLMfbt1PQ7Ne898lw3M3LYlWliWRLduK5YAQs0 kh5uJ64qlkOtSEAWsAhPlbC7T+6fRQD0JX+Y5+nmfss9BLc2HDnughlKNJArORKDoniQ BYSiBj9bOKuuxTjacMy0sluQAbs/wwZ1uONUNcQ9n3AcfvWE5kw667yfS3GpGPrO0d3o mJ0d4Cr2ZnacPyGDI5yeikD9uxvV0SQRCGn5kp454t0rfGSxYNQsPz3KCoojaA5T0+vP 5XlfvipJy9Tv6D6niX0ftn4fjr+cZZSTxUnrsl8Zip9xEugIkKkPsJ99SUQrP2yVKr2K UQ8Q==
MIME-Version: 1.0
X-Received: by 10.49.107.135 with SMTP id hc7mr32049646qeb.43.1380592554711; Mon, 30 Sep 2013 18:55:54 -0700 (PDT)
Received: by 10.140.86.147 with HTTP; Mon, 30 Sep 2013 18:55:54 -0700 (PDT)
In-Reply-To: <F2D7291B-5E70-459C-885D-B48C5342A8F5@tzi.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com> <CAChr6SyznBktmOLpT-EiZ5Nm_0jZ16M0tOo4aZ_jhSDb=HHDqg@mail.gmail.com> <23C96FBA-3419-4C97-A075-462F7443013A@vpnc.org> <52448254.5090209@cisco.com> <F2D7291B-5E70-459C-885D-B48C5342A8F5@tzi.org>
Date: Mon, 30 Sep 2013 18:55:54 -0700
Message-ID: <CAChr6SxFVk4pGL_2uzOo-nP-k3rb12-Gx+LPyyuuRFuMbtwv7A@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="047d7bdc13eecda2b904e7a44063"
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Eliot Lear <lear@cisco.com>, JSON WG <json@ietf.org>
Subject: Re: [Json] ECMA-262 normative?
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, 01 Oct 2013 01:55:56 -0000

On Mon, Sep 30, 2013 at 7:47 AM, Carsten Bormann <cabo@tzi.org> wrote:

>
> > Normative references specify documents that must be read to understand
> or implement the technology in the new RFC, or whose technology must be
> present for the technology in the new RFC to work.
>
> If we make that true for ECMA-262, we have seriously broken the document.


It is true for RFC 4627. That makes claims that JSON has nothing to do with
ECMAScript rather baseless, at least if one plays the part of spec nerd.

I think we should have a rationale for changing this, since we're not
supposed be changing things without being very careful.

- Rob

v2.23.0 | Report a Bug | By Email