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

Carsten Bormann <cabo@tzi.org> Wed, 10 May 2017 13:38 UTC

Return-Path: <cabo@tzi.org>
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 B5865129464 for <json@ietfa.amsl.com>; Wed, 10 May 2017 06:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] 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 u0s_eIuLb21i for <json@ietfa.amsl.com>; Wed, 10 May 2017 06:38:30 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 0786212944E for <json@ietf.org>; Wed, 10 May 2017 06:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v4ADcQ9t027509; Wed, 10 May 2017 15:38:26 +0200 (CEST)
Received: from client-0144.vpn.uni-bremen.de (client-0144.vpn.uni-bremen.de [134.102.107.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wNHPZ0n6lzDJ9K; Wed, 10 May 2017 15:38:26 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <bb1ef6a8-506c-344b-b903-980ed50ad2d3@gmx.de>
Date: Wed, 10 May 2017 15:38:25 +0200
Cc: Pete Cordell <petejson@codalogic.com>, "json@ietf.org" <json@ietf.org>, Matthew Miller <linuxwolf+ietf@outer-planes.net>
X-Mao-Original-Outgoing-Id: 516116304.977103-3602426bd636d88d64f15c12cac5ebba
Content-Transfer-Encoding: quoted-printable
Message-Id: <31BE9775-1808-45CB-9BA2-3EE4D34E5B26@tzi.org>
References: <e69d7c21-85cb-45f4-c0c2-34c624e63049@outer-planes.net> <05100401-88D4-4158-A3FF-3EF144D85449@att.com> <CAD2gp_T0bfpnsCA_t4BAMtEhr7p8JkZggjnY4F+m9-M2hWLfmw@mail.gmail.com> <1e94516c-9c82-8b0e-0d2d-7dbaa83b21bd@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>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/1U_wA0GxPygqs4uttNZPS5Tfy_w>
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: Wed, 10 May 2017 13:38:33 -0000

On May 10, 2017, at 15:08, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> I believe we should have separate names for JSON represented as a sequence of characters (such as in a string variable in a programming language) and for a JSON-shaped octet sequence inside a "application/json"-typed (HTTP) message. For the latter, enforcing UTF-8 IMHO is attractive.

Do we do this a lot for other media types?
(Just wondering whether there are good parallels to draw.)

Ceterum censeo: the really interesting third level that we should be talking about is the (generic) data model.
(But that is not possible for this round of making the specification into Internet Standard.)

Grüße, Carsten