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:55 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 495B621F9B8A; Thu, 14 Nov 2013 07:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, J_CHICKENPOX_43=0.6]
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 1vRq20Dm0nHG; Thu, 14 Nov 2013 07:55:01 -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 77F1021F9AE3; Thu, 14 Nov 2013 07:55:01 -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 1VgzG0-0001a2-7X; Thu, 14 Nov 2013 15:55:00 +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: U2FsdGVkX18V1XFciZ9rcYm1/PY/XoMWUdAzfx3T6zU=
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: <20131114153341.GA2165@mercury.ccil.org>
Date: Thu, 14 Nov 2013 07:54:56 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F96C5C0-0531-4C96-8126-EEBB9EE928C0@wirfs-brock.com>
References: <CEA95C60.2CF3C%jhildebr@cisco.com> <2E62DA50-F941-4A0E-A7B3-966A0DDE4C7A@wirfs-brock.com> <A8176E98-1CFB-4A3D-A8D7-EBBC759152AA@vpnc.org> <20131114153341.GA2165@mercury.ccil.org>
To: John Cowan <cowan@mercury.ccil.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Discussion <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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:55:07 -0000

On Nov 14, 2013, at 7:33 AM, John Cowan wrote:

> 
> Per contra, ECMA-404 refers only to text(ual content).  The BOM is
> meaningful when transforming byte sequences into code point sequences,
> but ECMA-404 deals in the latter only.  So it is the furthest thing
> from surprising that it makes no mention of BOMs, and has nothing to
> say about their use outside text.

Exactly ECMA-404 only defines a textual content format.  That was intentional.

Allen

v2.23.0 | Report a Bug | By Email