Re: [Lager] AD review of draft-ietf-lager-specification-10

Asmus Freytag <asmusf@ix.netcom.com> Mon, 14 March 2016 20:59 UTC

Return-Path: <asmusf@ix.netcom.com>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA96412D714; Mon, 14 Mar 2016 13:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-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 uXk59pLD4n_g; Mon, 14 Mar 2016 13:59:47 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5F612D6C4; Mon, 14 Mar 2016 13:59:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=Kb2QUjMEn0GUYd2+vizdncLmMHKoKy0RyaAqQcXltjlZyd9ulhSaQWpg1p3JNs5s; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [4.35.247.19] (helo=[172.31.99.19]) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1afZaG-0005a2-5U; Mon, 14 Mar 2016 16:59:24 -0400
To: Barry Leiba <barryleiba@computer.org>
References: <CALaySJJP0deDOxCs8YSPr72pfyRUsbZBVE9XO=_4d2AvEhVEtQ@mail.gmail.com> <56E669B1.5090108@ix.netcom.com> <CALaySJ+23n0RxvHNE7jCx4Msy5-2m0t=Z=GiPuw3wMPaX7xpjw@mail.gmail.com>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <56E72646.9080607@ix.netcom.com>
Date: Mon, 14 Mar 2016 13:59:50 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+23n0RxvHNE7jCx4Msy5-2m0t=Z=GiPuw3wMPaX7xpjw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc8dab008232ce03bcc285eb9adc178b4a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.35.247.19
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/rv0uUeR2cPw7ZUiXdh9c3TiVmco>
Cc: draft-ietf-lager-specification@ietf.org, lager WG <lager@ietf.org>
Subject: Re: [Lager] AD review of draft-ietf-lager-specification-10
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Label Generation Rules <lager.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lager>, <mailto:lager-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lager/>
List-Post: <mailto:lager@ietf.org>
List-Help: <mailto:lager-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lager>, <mailto:lager-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2016 20:59:49 -0000

Kim,

two items I am passing to you:

On 3/14/2016 11:05 AM, Barry Leiba wrote:
>> -- Section 5.3.5 --
>> >
>> >    Two contexts may be complementary, as in the following example, which
>> >    shows ARABIC LETTER TEH MARBUTA (U+0629) as a variant of ARABIC
>> >    LETTER ALEF MAKSURA (U+0649), but with two different types.
>> >
>> >        <char cp="0647" >
>> >          <var cp="0629" not-when="arabic-final" type="blocked" />
>> >          <var cp="0629" when="arabic-final" type="allocatable" />
>> >        </char>
>> >
>> >There's an error here: the text says "ALEF MAKSURA (U+0649)", but the
>> >example says "<char cp="0647" >"
>> >
>> >==> changed 0649 to 0647
> Is that the right direction?  Unicode says that U+0647 is ARABIC
> LETTER HEH, and that U+0649 is ARABIC LETTER ALEF MAKSURA.

 From the Root zone LGR:

  <char cp="0629" tag="sc:Arab" ref="0 100">
       <var cp="0647" type="allocatable" comment="In the Arabic 
language, U+0647 HEH may be substituted for U+0629 TEH MARBUTA. [RFC 
6365]" />

so it should be U+0647 and  ARABIC LETTER HEH...I missed fixing the name.

Kim, can you make this change?

(aside: the root zone LGR gave up on this kind of mutually-exclusive 
conditional context for positional variants because we found the task of 
verifying them mechanically to be intractable in the general case - 
however, there are different types of contexts in other scripts that are 
much more straightforward and that aren't as problematic, hence the 
warning instead of a request to remove the feature.)
>
>> >-- Section 5.5 --
>> >
>> >    Formally, it MUST correspond to
>> >    the XML 1.0 Nmtoken (Name token) production.
>> >
>> >Because conforming to Nmtoken is a requirement, it would be good to
>> >have a citation to where in the XML spec Nmtoken is defined.
>> >
>> >==> not done - could use help locating
> Sure:
> NEW
>     Formally, it MUST correspond to the XML 1.0 Nmtoken (Name token)
>     production (see [XML] Section 2.3).
> END
Kim, can you make that change?

A./