Re: [I18ndir] [Idna-update] FWD: Last Calls on two IDNA documents

Asmus Freytag <asmusf@ix.netcom.com> Mon, 05 August 2019 22:00 UTC

Return-Path: <asmusf@ix.netcom.com>
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 675261200D6 for <i18ndir@ietfa.amsl.com>; Mon, 5 Aug 2019 15:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ix.netcom.com; domainkeys=pass (2048-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.com
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 kJ5d3VlWKyUE for <i18ndir@ietfa.amsl.com>; Mon, 5 Aug 2019 15:00:13 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) (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 A12631200D7 for <i18ndir@ietf.org>; Mon, 5 Aug 2019 15:00:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ix.netcom.com; s=dk12062016; t=1565042413; bh=1FFCcyIeJAHrOh9lxA+ZhNSfz68D19e7ixTZ ZNKpmRw=; h=Received:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=LUaLshBc/O2pgnfYThbJdql+UeLNtkONo 0cYbbQ5zSZhInLdM2A2XCKX9SaHFKwJor4Lqf6lZ6T/K8SJJApOHNqEj9/4KH4UvsUY sxcRxNNtMD+dmQ1MqXXJWOTigpLIMWP3b60qaTDgwd8UfRgY1s8Y8l13aX0+vtnMA0r hTqJBMH/1Rn5+IPusd94MPVapQ06VSwvFpQO+RWb5yDjfo1LggeIO70HF2vd+yWaUkZ /PyDc1QX7pxmwsoU7DW1Ft9BsbWdiCLzsoGHBYOAFN0sSR1elt53JXcZojqKOqUbZ03 ErMuBXBmD7w7O3Gmc9uSnm3Vom3NDS6cGXaESj0PQ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=ix.netcom.com; b=GVw/R/AFB2xhKAuwyikquIr9M1JkWjvw7h5Lj5eInqL/d4rX2d2b76xgJ/gsT6BfbHXfP8dvK1C5f2L+OVWufYodV1MV4r7+8eVVqC9c1U6FGF+AWE5uSVmOU/QlQLsmXolU8PBhl5ZtsEknOiEqGRIRJycjS1tl0JIZZ4pIRq4TZuKnyIgEjyzTM0heAYm+P0+5bsk/UnQLHQpVZFSnkApgzDeiX/QxFhxvHzRAgwIXgX6O4XJzdLI2udWBZQiJjf41xpy5nxgZh49r0uYsz8dVSqvqF+MbuplzMfDRd6v9DvrLwWP6XakXVLI51GxAa+j21ceOqLq3rpVovq5bFg==; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [50.125.149.14] (helo=[192.168.0.214]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <asmusf@ix.netcom.com>) id 1hul1Y-0000Mq-1R for i18ndir@ietf.org; Mon, 05 Aug 2019 18:00:12 -0400
To: i18ndir@ietf.org
References: <54A888A04C434DE23AAB1A67@PSB> <D07A89030F4AB7A71B6A14FF@PSB>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <a32c000f-dfcf-a46c-d199-b7884f7485d8@ix.netcom.com>
Date: Mon, 5 Aug 2019 15:00:22 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <D07A89030F4AB7A71B6A14FF@PSB>
Content-Type: multipart/alternative; boundary="------------6E16256F7A0B7242C62DE251"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b27dfed51d2184666877cc27627e13f141084e2916724385a1350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 50.125.149.14
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/frPqlYJ7ml_9s9nsiNt7oeetqsg>
Subject: Re: [I18ndir] [Idna-update] FWD: Last Calls on two IDNA documents
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 05 Aug 2019 22:00:17 -0000

On the subject of stability:

If you are thinking in terms of decades - many orthographies have been 
reformed in the last 100 years (many of them more recently).

Encoding stability is not your main concern if you want stable spelling 
of terminology.

(The last reform of German spelling was around 25 years ago and affected 
many words containing sharp-s, or doubled consonants - many of those 
were contractions of triple consonants which are are now spelled out: 
"Schifffahrt". Some other writing systems had rather radical reforms in 
the 60s.).

Unicode is already more stable than what it tries to model.

A./


On 8/3/2019 9:09 PM, John C Klensin wrote:
>
> --On Sunday, August 4, 2019 01:53 +0200 "J-F C. Morfin"
> <jfc@morfin.org>; wrote:
>
>> John,
>> all of us trust Patrick's and your competence and wiseness IRT
>> iDNs. And thank you for your constant updating. However, I
>> observe that the retained solution regularly calls for updates.
> Thanks although more eyes --and different perspectives-- on this
> stuff are always helpful.  Put differently, while I'm glad you
> trust us, I don't :-(.  And it does indeed call for updates.
>
>> I am considering a polynym (strict lingual synonyms) oriented
>> DDDS service (bigdata multilingual database labels for
>> cross-origin data). A first idea is to build it on a similar
>> basis as iDNs. However concerns are about Unicode stability
>> over decades.
> First of all, if you are building a new system, you don't need
> the baggage that IDNs/ IDNA are carrying around as the result of
> the DNS not being well-designed for non-ASCII labels at the
> beginning and of many legacy applications that are even less
> well designed and implemented for those situations.
>
>> The need is for a string in any language returning the its
>> polynym in any other language indicated by its langtag. Would
>> you have a better suggestion? The project is to try to locate
>> the service at a meditarean group of universities.
> You are facing several problems.  One is Unicode itself.  As
> "universal" coding systems goes, it is probably as good or
> better than anything else we can easily imagine, but its design
> and implementation involved design choices that are not optimal
> for all purposes (or all languages and writing systems).  A
> different system might do better for some of those choices, but
> would almost certainly be worse for others.  That is one of the
> reasons for the update problem: as long as new code points (or
> at least new code points that are not symbols or otherwise
> excluded from "words") are being added, some decisions about the
> properties associated with code points are going to involve
> tradeoffs and those tradeoffs may not be optimal for IDNs, for
> your system, or for any other one with its own set of
> constraints and desirable characteristics.   So, if one is going
> to have strict stability and forward compatibility for
> identifiers or other strings, especially if more than just code
> point assignments are involved, regular review of properties and
> property assignments would seem to be a requirement. If you can
> define things so that all you care about is stability of the
> code point assignments and binding to abstract characters
> themselves, and you have no need to define or enforce
> equivalence of different encodings of "the same" string or
> character within that string, then there is probably no issue.
>
> The second problem is one with which I believe you are familiar
> because you've raised equivalent issues before in other
> contexts.  While some technical terms that were invented only
> very recently do work, there are many terms, both mononyms and
> polynyms, for which exact and unique translations do not exist
> or are controversial.  If you want to check that out further,
> looking at the EUROVOC and AGROVOC multilingual controlled
> vocabularies might be a start.  Those two examples are, however,
> specialized vocabularies; more traditional multilingual thesauri
> pose even more complex problems.
>
> best,
>      john'
>
>
>
>> Best
>> jfc
>
>
>