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

Peter Saint-Andre <stpeter@stpeter.im> Wed, 09 October 2013 12:34 UTC

Return-Path: <stpeter@stpeter.im>
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 C33DB21F9C3A for <precis@ietfa.amsl.com>; Wed, 9 Oct 2013 05:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 rHHqknj4-aPl for <precis@ietfa.amsl.com>; Wed, 9 Oct 2013 05:34:45 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BCA9821F9B7E for <precis@ietf.org>; Wed, 9 Oct 2013 05:34:45 -0700 (PDT)
Received: from ergon.local (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E8811414CD; Wed, 9 Oct 2013 06:40:42 -0600 (MDT)
Message-ID: <52554D5A.7060300@stpeter.im>
Date: Wed, 09 Oct 2013 06:34:34 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
References: <20130828154603.a94201dea74f29229b4767b2@jprs.co.jp> <20130904162558.7fad8dd5d2304591166dd37a@jprs.co.jp> <CADRqEyrNmY=RTVpUuVmj4qG2d5jy8LsL5uJuXHX7+YtGqkFxrA@mail.gmail.com> <52547128.5070909@stpeter.im> <52551BB3.4080407@it.aoyama.ac.jp> <52551DFE.8000608@it.aoyama.ac.jp>
In-Reply-To: <52551DFE.8000608@it.aoyama.ac.jp>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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: Wed, 09 Oct 2013 12:34:50 -0000

On 10/9/13 3:12 AM, "Martin J. Dürst" wrote:
> On 2013/10/09 18:02, "Martin J. Dürst" wrote:
>> On 2013/10/09 5:55, Peter Saint-Andre wrote:
>>> On 9/11/13 8:06 PM, Joseph Yee wrote:
>>
>>>> Reviewed the draft, think the approach is good. Just one minor comment.
>>>>
>>>> Same as Florian, had the 'hmm' reaction when reading about
>>>> directionality and application behaviour at Section 3.1. It seems that
>>>> the only application behaviour is permitted pattern. It doesn't deal
>>>> with visual appearance I believed. Maybe replace 'application
>>>> behaviour' with 'permitted patther of the string' (or 'allowed
>>>> combination of the string')?
>>>
>>> Hmm, I see why you and Florian don't like that text. :-)
>>>
>>> How about this?
>>>
>>> OLD
>>> Directionality: defines application behavior in the presence of code
>>> points that have directionality, in particular right-to-left code
>>> points as defined in the Unicode database (see [UAX9]).
>>>
>>> NEW
>>> Directionality: defines which strings are to be considered
>>> left-to-right (LTR) and right-to-left (RTL), and the allowable
>>> sequences of characters in LTR and RTL strings.
>>
>> That may be an improvement, but it's missing the fact that LTR and RTL
>> strings are the only two alternatives allowed.
>>
>> Also, it would be good to somewhere say that there is currently no
>> widely accepted and implemented solution for the display of constructs
>> with mixed pieces (e.g. domain names with LTR and RTL components
>> (labels), because the problem is inherently extremely hard.
> 
> In addition, in the introduction, there is a paragraph:
> 
>    5.  Leave various mapping operations (e.g., case preservation or
>        lowercasing, Unicode normalization, mapping of certain characters
>        to other characters or to nothing, handling of full-width and
>        half-width characters, handling of right-to-left characters) as
>        the responsibility of application protocols, as was done for
>        IDNA2008 through an IDNA-specific mapping document [RFC5895].
> 
> where "handling of right-to-left characters" is described as a mapping
> operation. That doesn't make sense to me, I think it should be moved out
> to a separate point.


I think we can change "mapping operations" to "character-related
operations".

Peter

-- 
Peter Saint-Andre
https://stpeter.im/