IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Wed, 10 May 2017 13:08 UTC

Return-Path: <julian.reschke@gmx.de>
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 3901F1201FA for <json@ietfa.amsl.com>; Wed, 10 May 2017 06:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-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 TXEapEm6mUfX for <json@ietfa.amsl.com>; Wed, 10 May 2017 06:08:42 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 788E6126DFB for <json@ietf.org>; Wed, 10 May 2017 06:08:41 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ld3t6-1dqboM0kvQ-00iCC8; Wed, 10 May 2017 15:08:38 +0200
To: Pete Cordell <petejson@codalogic.com>, "json@ietf.org" <json@ietf.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>
Cc: Matthew Miller <linuxwolf+ietf@outer-planes.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <bb1ef6a8-506c-344b-b903-980ed50ad2d3@gmx.de>
Date: Wed, 10 May 2017 15:08:39 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a3805f67-620b-67f0-9c06-c865b71029e7@codalogic.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:1IkzpjIzs5yNAj+AMMbS301q3iC656FYRNEGO2aUSEPXbZnggBS xqmzXgM5eEqPV+f2G5O3hxWmeQ7ySOrtwjW4fgB9mQ8qkQyAiTYVOVNFr+b//e2Cj7KvVvY quY94fyKTwxnIo60Lwjs3aK4z4sHeRsTgsLaTuD2cz6UdtSpjazE7hCUOgQ2vgA7ZFcq9VZ 3N1ezju+8Y8+C62cDFwLg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:SAh5L9vGlns=:miKZkDKPyHTLAwC5qoCzbW 2rn1GRTLvIPG2eTi9Sjre0SuSncEUUnesTl4ipNDXaC+GSKvAm6PbYHkhDH9CLODpgSf5t3rj xl+QMJKnXCfural8dUfAyN8O52225r8qbQ2UVAcIVluMZm44xVUSgai9K7t2ydihToisN721b 4BGjq5HtqnvJhMydR/2S902zxCa4m7TKhT+EC/c8AY1SBp2SA/mwVWoFcgU0Z/XH+uaBavFwh gZWDMu6vbwF+t1aXEHUqYqfXyngjZjkAS1UUNUTiTkvhLH4l//cTJUqQzrmNkP7nA37Ay0Agc 8GmQ7eB9XUpeFicH+jQvyy33mAukDZ4UlpuVe9Khy5BzZ/h1Y9AJ8WeQfhDPg2sjFheT4rsw/ rMgKj9Cxk9cZmjuF9UcbuCuzBJSuvEeeia25hxZRM0GGp4ShWjLFFAaSnHxTW9a7usj6i2Y3A aMVoiBCWnwtHNYlFVKq3Q1G4CNKAz25CrdGKvRV7FkAq8DwLGlFLgwdf6u6rxpR8lRgk+Jdxi b9HcylccJGv0J3x9S1coCB8u5ixr7RwrnhhMElLluFY7GHuQDMTI9EDR5pRsKVm4HK8zKARyZ 028+f8D/6hhnNja9KpGs+YoaMhgAJQ4gwPZreTb132o340wI2BBbvcoBktJoNhYm5LRQFsg7r 98rbo3qiv8ZZ5dQh/IIHM7u/Wdb7rqamW8PEV01t4sFF/TxlyT8/HUw2E1m3QbwhLCtcDpY+V eTNsk+qgFexsINaFolJ6Yl4HiTl6gU3CLaZQAGil75bDrzCJs2krD+XDojuokgxcI/9y7Hcyv 7dmE5Bx
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/o781AQTX79XItqtOwH2oVEt_oJI>
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:08:43 -0000

On 2017-05-10 14:53, Pete Cordell wrote:
> On 08/05/2017 17:37, Julian Reschke wrote:
>> Here's a question that might be relevant wrt what we say in Section 8.
>>
>> Is "JSON text" the same thing as what can be labelled
>> "application/json"? Is "our" spec (as opposed to ECMA's) solely about
>> what gets transferred as "application/json", or does it define more?
>
> What would your input be for each of those two options?  (I know what
> mine would be.)

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.

I think it's ok for the spec to talk about both, but it really needs to 
be clear what we are talking about in each section.

Best regards, Julian

v2.23.0 | Report a Bug | By Email