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

Peter Saint-Andre <stpeter@stpeter.im> Thu, 10 October 2013 01:36 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 9765C21E824F for <precis@ietfa.amsl.com>; Wed, 9 Oct 2013 18:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.094
X-Spam-Level:
X-Spam-Status: No, score=-102.094 tagged_above=-999 required=5 tests=[AWL=0.205, 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 vMqRc6mKNlOx for <precis@ietfa.amsl.com>; Wed, 9 Oct 2013 18:36:30 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C285621F9EF0 for <precis@ietf.org>; Wed, 9 Oct 2013 18:36:27 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id AEAFD414CD; Wed, 9 Oct 2013 19:42:26 -0600 (MDT)
Message-ID: <52560499.5000508@stpeter.im>
Date: Wed, 09 Oct 2013 19:36:25 -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> <52554D5A.7060300@stpeter.im> <525600C7.1020703@it.aoyama.ac.jp>
In-Reply-To: <525600C7.1020703@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: Thu, 10 Oct 2013 01:36:35 -0000

On 10/9/13 7:20 PM, "Martin J. Dürst" wrote:
> On 2013/10/09 21:34, Peter Saint-Andre wrote:
>> On 10/9/13 3:12 AM, "Martin J. Dürst" wrote:
> 
>>> 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".
> 
> Well, that wouldn't be wrong, but it would be extremely generic. There's
> nothing in the document that isn't about characters, or is there?
> 
> I think something like
> 
> 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) and the handling of right-to-left characters
>     as the responsibility of application protocols, as was done for
>     IDNA2008 through an IDNA-specific mapping document [RFC5895].
> 
> Would be at least slightly better.

Sure, that works for me.

Peter

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