Re: [precis] WGLC: draft-ietf-precis-framework-09.txt

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Thu, 10 October 2013 01:43 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 6931C21E8261 for <precis@ietfa.amsl.com>; Wed, 9 Oct 2013 18:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.19
X-Spam-Level:
X-Spam-Status: No, score=-103.19 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 VNSTrFmKUo3s for <precis@ietfa.amsl.com>; Wed, 9 Oct 2013 18:43:19 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 2EDAF21E825E for <precis@ietf.org>; Wed, 9 Oct 2013 18:43:16 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r9A1h9SI013889; Thu, 10 Oct 2013 10:43:09 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 29cc_1362_50fb7cd8_314d_11e3_be8f_001e6722eec2; Thu, 10 Oct 2013 10:43:08 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id BB894BFBBA; Thu, 10 Oct 2013 10:43:08 +0900 (JST)
Message-ID: <5256061F.1090108@it.aoyama.ac.jp>
Date: Thu, 10 Oct 2013 10:42:55 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <20130828154603.a94201dea74f29229b4767b2@jprs.co.jp> <20131005030751.GB38902@mx1.yitter.info> <5254C12F.90708@stpeter.im> <20131009042358.GB47597@mx1.yitter.info> <52554FE3.70504@stpeter.im> <5255C4FC.4060705@stpeter.im>
In-Reply-To: <5255C4FC.4060705@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: precis@ietf.org
Subject: Re: [precis] WGLC: draft-ietf-precis-framework-09.txt
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: Thu, 10 Oct 2013 01:43:42 -0000

On 2013/10/10 6:05, Peter Saint-Andre wrote:

> Here is proposed text (for the end of section 9.5):
>
>     The challenges inherent in supporting the full range of Unicode code
>     points has in the past led some to hope for a way to programmatically
>     negotiate more restrictive ranges based on locale, script, or other
>     relevant factors.  As a general-purpose internationalization
>     technology, the PRECIS framework does not include such a negotiation
>     mechanism.

Mostly fine up to here, except that in this area, not only negotiation 
mechanisms, but also augmenting the identifiers themselves with 
language/locale information are regularly wished for. Using a specific 
example, that chat[English] and chat[French] would be two separate 
identifiers. We should also clearly warn against this.


>                 Applications requiring a tighter binding to the user's
>     linguistic environment might need to develop extensions to the PRECIS
>     framework, or special-purpose internationalization technologies.

I don't like this, because it essentially says "we don't do this, but 
you may well want to do it". It's something that makes a lot of sense 
e.g. in a content management system. But it does not make sense, and we 
shouldn't give the impression that it does, in the context of 
identifiers and similar stuff (even the PRECIS "FreeformClass" is about 
identifiers, not about content.


Regards,   Martin.