IETF Logo Mail Archive

Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

Allen Wirfs-Brock <allen@wirfs-brock.com> Tue, 18 July 2017 16:39 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 0A32813154E for <json@ietfa.amsl.com>; Tue, 18 Jul 2017 09:39:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJk1v2IpqfXY for <json@ietfa.amsl.com>; Tue, 18 Jul 2017 09:39:41 -0700 (PDT)
Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A14B3129B26 for <json@ietf.org>; Tue, 18 Jul 2017 09:39:41 -0700 (PDT)
X-MHO-User: a4116db3-6bd7-11e7-a4a1-c9e62e5d9688
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 50.39.217.219
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from [192.168.254.4] (unknown [50.39.217.219]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id a4116db3-6bd7-11e7-a4a1-c9e62e5d9688; Tue, 18 Jul 2017 16:39:17 +0000 (UTC)
From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Message-Id: <4BB9C876-7E28-4626-88F4-6F4AD8AFC870@wirfs-brock.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FCD99F6C-E04D-4CD1-AB4B-FAC329CD74FC"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 18 Jul 2017 09:39:39 -0700
In-Reply-To: <CAHBU6itmYDyBfz0qqr0LAUTuvdR1oBSUnz7VSie=pZRva=Ynzw@mail.gmail.com>
Cc: Pete Cordell <petejson@codalogic.com>, Julian Reschke <julian.reschke@gmx.de>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
To: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
References: <e69d7c21-85cb-45f4-c0c2-34c624e63049@outer-planes.net> <40e3207f-e047-c898-1f0c-4422de1d597a@it.aoyama.ac.jp> <1b3ec14a-927a-8d46-e3d3-9807a9588437@outer-planes.net> <CAHBU6ivsq8+Z=MMkUH+=Q0uwc5NCtaJLYw5cp0Qg8eX2hQQ6sA@mail.gmail.com> <b74cb31b-8e04-17d0-548a-fc164ce07c05@outer-planes.net> <20170417175627.GK23461@localhost> <10B651F1-7FE0-484D-BD2E-FD146BC5FB04@tzi.org> <eabbccb0-8d15-d595-7cd0-37acc0621c57@it.aoyama.ac.jp> <6eb23f90-6623-7888-bc1c-6640a9dababc@codalogic.com> <61bfad2b-850d-a11f-e80b-d5ed9ccb4dc9@codalogic.com> <08a88696-65ef-da05-0d77-1a07d04ebfc8@outer-planes.net> <bb9fead6-23e7-8c1d-bc80-b60c81c4b89a@codalogic.com> <6f047d01-ad72-59ab-9d34-20a8177ab3af@outer-planes.net> <be4d9f12-a4be-3723-e52a-56a60722a75f@gmx.de> <a3805f67-620b-67f0-9c06-c865b71029e7@codalogic.com> <bb1ef6a8-506c-344b-b903-980ed50ad2d3@gmx.de> <44b4523a-5e4b-ccad-af96-931d8b9ad1c2@codalogic.com> <ac1d1b68-67e7-c19f-a556-280df73f465b@outer-planes.net> <db3e4d88-d3bc-2ab5-fd8d-0a9ed90865e9@codalogic.com> <CAHBU6itmYDyBfz0qqr0LAUTuvdR1oBSUnz7VSie=pZRva=Ynzw@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/0TVI13NELfsuC7FscgDvXZThenE>
Subject: Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2017 16:39:43 -0000

> On May 13, 2017, at 10:37 AM, Tim Bray <tbray@textuality.com> wrote:
> 
> I have one source of heartburn.  The stated purpose of 7159bis is to achieve harmony with ECMA 404.  That document does *not* constrain JSON encoding.  I’m fine  with saying that JSON has to be UTF-8, but I think we should consult with ECMA and see if the goal of spec harmonization is still possible if we make the UTF-8 restriction.

Sorry, I didn’t see this when it was originally posted.

I don’t believe that this would be a problem WRT ECMA-404 harmony. as long as the UTF-8 requirement applies to specific use cases such as “network protocols” or “IETF-specified protocols”.  ECMA-404 is only concern with defining which sequences of Unicode code points are well-foirmed JSON texts. It does not concern it self with how the code points might be encoded for transmission or storage. 

Concretely, within ECMAScript programs JSON texts are typically encoded as UTF-16 strings and UTF-8 encodings have to be translated to UTF-16 before the built-in JSON.parse function can be applied to them. But those requirements are part of ECMA-262, the  ECMAScript Language Specification, and not part of ECMA-404. 

Allen Wirts-Brock
Interim Chair, Ecma TC39

v2.23.0 | Report a Bug | By Email