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

[Barry Leiba <[e-mail]>]

> -- 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.

>  I suggest that you put the element names in quotes in the sub-section titles.
>
> ==> not done - we played with "decorating" the section headers but abandoned that.

OK.

> Is there a missing or extra word around "value that used"?
>
> ==> yep. Found a few spare ones and put them in.

:-)

> -- 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

>  -- Section 6.2.5 --
> I don't understand why "intersection" is limited to two classes: the
> intersection of more than two sets is as well defined as the union is.
> Please explain (at least to me).

Your explanation works for me; no change here.

>  -- Section 6.3 --
> Pet peeve (sorry): Correct use of "comprises" [...]
...
> ==> hope you feel better now

Much, and I'm ever grateful.

Barry