IETF Logo Mail Archive

Re: [Json] UTF-8 for application/json contexts, UTF-8/16/32 for other contexts

Carsten Bormann <cabo@tzi.org> Thu, 28 November 2013 04:00 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 42A1A1AE1C4 for <json@ietfa.amsl.com>; Wed, 27 Nov 2013 20:00:58 -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 0iXoltDIH0Vz for <json@ietfa.amsl.com>; Wed, 27 Nov 2013 20:00:57 -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 473C91AE1C9 for <json@ietf.org>; Wed, 27 Nov 2013 20:00:57 -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 rAS40nbo013572; Thu, 28 Nov 2013 05:00:50 +0100 (CET)
Received: from [192.168.217.105] (p54891F61.dip0.t-ipconnect.de [84.137.31.97]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 27D2614F; Thu, 28 Nov 2013 05:00:42 +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: <CAGrxA26N7YY-aDVJqD_qADhJ9wF3HAQM4dgeVYzG3WF8h+SKXA@mail.gmail.com>
Date: Thu, 28 Nov 2013 05:00:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C3C8ADB-DE73-4B1F-A4FC-D70BE87FA0DA@tzi.org>
References: <87FBA1C2000449EBBED94BDB0485829F@codalogic> <CAK3OfOjJDO0GbCoyD9Lyd86AkHD6-fSQcptcJ_=qRH+BT+6Cbw@mail.gmail.com> <8FFA65BA9ACB45F9BFEECC205C7FAF30@codalogic> <6D24653D-C98B-4FDE-801D-9759FBD696FF@tzi.org> <CAGrxA26N7YY-aDVJqD_qADhJ9wF3HAQM4dgeVYzG3WF8h+SKXA@mail.gmail.com>
To: Tatu Saloranta <tsaloranta@gmail.com>
X-Mailer: Apple Mail (2.1822)
Cc: Pete Cordell <petejson@codalogic.com>, JSON WG <json@ietf.org>
Subject: Re: [Json] UTF-8 for application/json contexts, UTF-8/16/32 for other contexts
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: Thu, 28 Nov 2013 04:00:58 -0000

On 28 Nov 2013, at 00:40, Tatu Saloranta <tsaloranta@gmail.com> wrote:

> Same goes for UTF-16 

No, that’s completely different.

BOM tolerance was never in JSON, and arguing that you should add it is like arguing that you should accept tabs in strings or trailing commas.

UTF-16 *was* in the spec.  We have just learned in the intervening time that there is no point.  Completely different situations.  I’m still arguing that now is the time to simplify and recognize UTF-16 as a legacy part of the spec that is going away, but that is a completely different, more tenuous argument.

Yes, I know that “serious” implementations can be made to support all this (including trailing commas), and you have all reasons to be proud that yours is a serious one.  But that doesn’t detract one iota from my point.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email