IETF Logo Mail Archive

Re: [I18ndir] [art] Just uploaded draft-bray-unichars-03

Carsten Bormann <cabo@tzi.org> Sun, 10 September 2023 23:36 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08CB0C151094; Sun, 10 Sep 2023 16:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIYj7kgzIr_t; Sun, 10 Sep 2023 16:36:08 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C492C151062; Sun, 10 Sep 2023 16:36:06 -0700 (PDT)
Received: from smtpclient.apple (unknown [80.90.87.241]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RkR7742MFzDCbJ; Mon, 11 Sep 2023 01:36:03 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-9501DBDC-54A6-48D3-871A-1CCDD6CF5389"
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Mime-Version: 1.0 (1.0)
Date: Mon, 11 Sep 2023 01:35:52 +0200
Message-Id: <B033EE3E-DEC4-4A30-BFD1-633738E9F914@tzi.org>
References: <CAHBU6isneG874m8vJixwB0y3E_1p_E15vDH4gB4uuegkpA1tCg@mail.gmail.com>
Cc: "Manger, James" <James.H.Manger@team.telstra.com>, Asmus Freytag <asmusf@ix.netcom.com>, i18ndir@ietf.org, ART Area <art@ietf.org>
In-Reply-To: <CAHBU6isneG874m8vJixwB0y3E_1p_E15vDH4gB4uuegkpA1tCg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: iPhone Mail (20G81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/y5OBZeMFK3pxwVdoBbMgzMbd46U>
Subject: Re: [I18ndir] [art] Just uploaded draft-bray-unichars-03
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Sep 2023 23:36:14 -0000


Sent from mobile, sorry for terse

There indeed is no problem with utf-8.
Writing a document that says “when implementing x please do read the document defining x” is not a productive use of time. In particular when that new document presents not reading document-x as a valid alternative that is available as a choice to the protocol designer. (Adding confusion such as stating that surrogates can be part of a character Repertoire doesn’t help either.)

The json problem is indeed there, and we knew how to fix it all along but didn’t for political reasons. If you want to build a robust system, you use grammar that is like the one we put in Jsonpath for Jsonpath itself instead of copying the old JSON grammar. Publishing that might be a great little document on its own, except we just did.

v2.23.0 | Report a Bug | By Email