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

Peter Cordell <petejson@codalogic.com> Mon, 20 March 2017 17:59 UTC

Return-Path: <petejson@codalogic.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 557C013163A for <json@ietfa.amsl.com>; Mon, 20 Mar 2017 10:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 fvmR6qYgvGz9 for <json@ietfa.amsl.com>; Mon, 20 Mar 2017 10:59:08 -0700 (PDT)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 732DA13163C for <json@ietf.org>; Mon, 20 Mar 2017 10:58:05 -0700 (PDT)
Received: (qmail 19382 invoked from network); 20 Mar 2017 17:50:45 +0000
Received: from host109-158-230-32.range109-158.btcentralplus.com (HELO ?192.168.1.72?) (109.158.230.32) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 20 Mar 2017 17:50:45 +0000
To: Julian Reschke <julian.reschke@gmx.de>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>, "json@ietf.org" <json@ietf.org>
References: <1fb5849e-8dbf-835d-65b7-2403686248f9@outer-planes.net> <0E32A94D-CE12-4F52-9ED6-8743C49751B4@vpnc.org> <4d2f0fb3-a729-0c17-2394-bc1e005dd612@gmx.de> <d09f9a59-2411-45a0-470c-ea95072fe4fd@outer-planes.net> <dad91b19-e774-e239-36d2-9d086cca8e0d@gmx.de> <ac432615-ee84-3cdf-6b37-480626bd18c1@gmx.de> <804f9930-26a5-a565-0607-452b386cfeb5@outer-planes.net> <b7cc7f5d-e614-3c90-8ea2-62441fa3d9e6@gmx.de>
Cc: The IESG <iesg@ietf.org>
From: Peter Cordell <petejson@codalogic.com>
Message-ID: <a788a64a-25c2-7271-fcda-3d6c1e5b0e03@codalogic.com>
Date: Mon, 20 Mar 2017 17:58:03 +0000
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: <b7cc7f5d-e614-3c90-8ea2-62441fa3d9e6@gmx.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/8rH_mV1Jbu1-NHxnZ2c6IwPR0w0>
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: Mon, 20 Mar 2017 17:59:10 -0000

On 20/03/2017 16:46, Julian Reschke wrote:
> On 2017-03-20 17:26, Matthew A. Miller wrote:
>> encoded in UTF-8 are interoperable in the sense that they will be
>> read successfully by the maximum number of implementations; there are
>> many implementations that cannot successfully read texts in other
>> encodings (such as UTF-16 and UTF-32).  Text encoded in character
>
> Replace "in other encodings (such as UTF-16 and UTF-32)" by just "in
> other encodings". The proposed text implies that there encodings other
> than UTF-16 or UTF-32 which could be allowed.

If that's what you want, instead of:

     there are many implementations that cannot successfully read
     texts in other encodings (such as UTF-16 and UTF-32).

Or:

     there are many implementations that cannot successfully read
     texts in other encodings.

I think it would be even clearer to say:

     there are many implementations that cannot successfully read
     texts encoded in UTF-16 or UTF-32.

Regards,

Pete Cordell
Codalogic Ltd
Rules for Describing JSON Content, http://json-content-rules.org