IETF Logo Mail Archive

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

Allen Wirfs-Brock <allen@wirfs-brock.com> Thu, 14 November 2013 15:48 UTC

Return-Path: <allen@wirfs-brock.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 6979721F99DC; Thu, 14 Nov 2013 07:48:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.679
X-Spam-Level:
X-Spam-Status: No, score=-2.679 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599]
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 TuSYzKxRebu7; Thu, 14 Nov 2013 07:48:44 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id 01E9811E814F; Thu, 14 Nov 2013 07:48:39 -0800 (PST)
Received: from 069-064-236-244.pdx.net ([69.64.236.244] helo=[192.168.0.22]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <allen@wirfs-brock.com>) id 1Vgz9p-000Lci-Ln; Thu, 14 Nov 2013 15:48:37 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 69.64.236.244
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/Wen/t904BO/53pbD4DpA2mJ6XT0/wYy8=
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Allen Wirfs-Brock <allen@wirfs-brock.com>
In-Reply-To: <A8176E98-1CFB-4A3D-A8D7-EBBC759152AA@vpnc.org>
Date: Thu, 14 Nov 2013 07:48:30 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <82A4E5F4-FF2F-491F-A5BA-96F7CE04D78E@wirfs-brock.com>
References: <CEA95C60.2CF3C%jhildebr@cisco.com> <2E62DA50-F941-4A0E-A7B3-966A0DDE4C7A@wirfs-brock.com> <A8176E98-1CFB-4A3D-A8D7-EBBC759152AA@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1085)
Cc: John Cowan <cowan@mercury.ccil.org>, IETF Discussion <ietf@ietf.org>, JSON WG <json@ietf.org>, Joe Hildebrand Hildebrand <jhildebr@cisco.com>, Anne van Kesteren <annevk@annevk.nl>, "www-tag@w3.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: Thu, 14 Nov 2013 15:48:50 -0000

On Nov 13, 2013, at 7:15 PM, Paul Hoffman wrote:

>> 
> 
> The question was specifically about ECMA-404, not ECMA-252. It would be great to hear from TC39 whether or not ECMA-404 allows or disallows it.

ECMA=nnn is the correct designation for Ecma standards.  When speaking about the organization "Ecma" is the usage.

Allen

v2.23.0 | Report a Bug | By Email