Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)

Carsten Bormann <cabo@tzi.org> Tue, 26 November 2013 23:20 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 836321AE054 for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 15:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 kAAKfCZjsbLY for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 15:20:33 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 77A621AE052 for <json@ietf.org>; Tue, 26 Nov 2013 15:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id rAQNKSMV007067; Wed, 27 Nov 2013 00:20:28 +0100 (CET)
Received: from [192.168.217.105] (p548937CC.dip0.t-ipconnect.de [84.137.55.204]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4EAB0865; Wed, 27 Nov 2013 00:20:27 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20131126230730.GH21240@localhost>
Date: Wed, 27 Nov 2013 00:20:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F52BEE2-F477-4C5A-AD7E-3FCB5765706C@tzi.org>
References: <20131121165615.GA12138@mercury.ccil.org> <CANXqsRKrcR54TzSFng0ysyTV60-uZZ7QQ-G4xJOB0gO29C7-Ag@mail.gmail.com> <54E53D571E5E4589B2E9FA17DC816002@codalogic> <CANXqsRJi8dv0Giw7CZWP=10qEJEXGyRTb0HFnE9MpeAxc2_0rA@mail.gmail.com> <20131126160127.GE20755@mercury.ccil.org> <CAO1wJ5Qz2-vue_OGp79JZ+DW0ELofwdh8vy=9UZk53SMYs1bOg@mail.gmail.com> <20131126172410.GC21240@localhost> <mev999tgjoao5cj84fuk4t8pvi4t9pj6hs@hive.bjoern.hoehrmann.de> <20131126220036.GG21240@localhost> <95E46767-DBBF-489F-83BD-80BEC697C999@tzi.org> <20131126230730.GH21240@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1822)
Cc: es-discuss <es-discuss@mozilla.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, www-tag <www-tag@w3.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2013 23:20:34 -0000

On 27 Nov 2013, at 00:07, Nico Williams <nico@cryptonector.com> wrote:

> Do you want to say anything about other encodings?  What would that be?

JSON is encoded in UTF-8.

There is no need to discuss JSON in other encodings, because it wouldn’t be JSON.

(And no, I see no need to handle UTF-16LE, UTF-16BE, UTF-32LE or UTF-32BE in any special way, even if RFC 4627 was written at a time when it still seemed useful to pay them lip service.  But I recognize that there appears to be WG consensus to keep these corpses on life support, maybe because UTF-16 is the internal encoding of the programming language that gave JSON its name.)

Grüße, Carsten