Re: [precis] Category changes with Unicode 6.3
John C Klensin <klensin@jck.com> Wed, 16 October 2013 13:47 UTC
Return-Path: <klensin@jck.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61AB11E81D1 for <precis@ietfa.amsl.com>; Wed, 16 Oct 2013 06:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.285
X-Spam-Level:
X-Spam-Status: No, score=-3.285 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Him+5Bykkwf for <precis@ietfa.amsl.com>; Wed, 16 Oct 2013 06:47:02 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D8BB921F9E98 for <precis@ietf.org>; Wed, 16 Oct 2013 06:47:01 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1VWRRA-0000PF-HR; Wed, 16 Oct 2013 09:46:56 -0400
Date: Wed, 16 Oct 2013 09:46:51 -0400
From: John C Klensin <klensin@jck.com>
To: Patrik Fältström <paf@frobbit.se>, "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Message-ID: <11194FD50DDFBDB190254386@JcK-HP8200.jck.com>
In-Reply-To: <DA8691AD-408B-409B-B6B6-3ECC048AB09A@frobbit.se>
References: <525DFB1F.8040401@it.aoyama.ac.jp> <7693B3B4-7204-48F0-8C42-EBF5D701BAF4@frobbit.se> <525E3A7F.9040204@it.aoyama.ac.jp> <DA8691AD-408B-409B-B6B6-3ECC048AB09A@frobbit.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Mailman-Approved-At: Wed, 16 Oct 2013 07:06:19 -0700
Cc: idna-update@alvestrand.no, precis@ietf.org
Subject: Re: [precis] Category changes with Unicode 6.3
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 13:47:07 -0000
--On Wednesday, October 16, 2013 10:16 +0300 Patrik Fältström <paf@frobbit.se> wrote: > Yeah, I had to do it anyways -- as I am expert reviewer of the > IANA tables. New versions of the IANA tables where created by > IANA the other day, and I just approved them as they match my > own calculations. I.e. we have two completely independent > implementations of IDNA2008 (one at IANA, one that I have -- > see link below) and I compare the output of the two. If the > output matches, then we are pretty sure we are correct. This is great. To a considerable extent, it reinforces the utility and importance of the IDNA2008 approach. YOu (and IANA) reapply the rules to a new version of Unicode, verify that nothing significant has changed and your results are the same, and we move on. In addition, because mapping is defined on top of those rules and the collection of allowable code points they create, we don't end up with different profiles for different domains or applications. It remains to be seen whether the PRECIS approach will work as well. On the one hand, generation rules have replaced the normative Stringprep table. On the other, that system leads, not to a definitive list but to string classes that are then profiled, potentially on an application-by-application or even implementation-by-implementation basis, to yield actual practices. Different behavior in different applications may be inevitable but it is certain that it will confuse at least some users. And, because different profiles will address different parts of the basic PRECIS code space, it is possible that the same evaluations that are run against the generation rules for IDNA (and exceptional adjustments added if needed) will need to be performed for each profile, resulting in temporal instability. Perhaps it will all work out and the profiles will be completely stable, but it is hard to be completely confident about that. best, john
- Re: [precis] Category changes with Unicode 6.3 Peter Saint-Andre
- [precis] Category changes with Unicode 6.3 Martin J. Dürst
- Re: [precis] Category changes with Unicode 6.3 Patrik Fältström
- Re: [precis] Category changes with Unicode 6.3 Patrik Fältström
- Re: [precis] Category changes with Unicode 6.3 Martin J. Dürst
- Re: [precis] Category changes with Unicode 6.3 Patrik Fältström
- Re: [precis] Category changes with Unicode 6.3 Mark Davis ☕
- Re: [precis] Category changes with Unicode 6.3 Patrik Fältström
- Re: [precis] Category changes with Unicode 6.3 John C Klensin
- Re: [precis] Category changes with Unicode 6.3 Martin J. Dürst
- Re: [precis] Category changes with Unicode 6.3 Patrik Fältström
- Re: [precis] Category changes with Unicode 6.3 Peter Saint-Andre
- Re: [precis] Category changes with Unicode 6.3 Peter Saint-Andre
- Re: [precis] Category changes with Unicode 6.3 Patrik Fältström
- Re: [precis] Category changes with Unicode 6.3 Peter Saint-Andre
- Re: [precis] Category changes with Unicode 6.3 John C Klensin