MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
In-Reply-To: <53EF8C18.3030004@alum.mit.edu>
References: <53E3B22E.5000708@alum.mit.edu>
	<53EF8C18.3030004@alum.mit.edu>
Date: Mon, 18 Aug 2014 19:31:19 -0400
Message-ID: <CAC4RtVCii_j-54ixnuB6CqwQZSO_9rQstjqswDXsfuSy9ChDnA@mail.gmail.com>
Subject: Re: [abnf-discuss] Case-sensitive string constants in ABNF
From: Barry Leiba <barryleiba@computer.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>
Content-Type: text/plain; charset=UTF-8

> http://datatracker.ietf.org/doc/draft-kyzivat-case-sensitive-abnf/
>
> I'm not quite sure what to do with it after this. But I guess we could start
> with comments here.

Thanks, Paul.  The only comment I have is that I would make one thing
more explicit:

OLD
   Another way to define a rule that is case sensitive is to specify the
   individual characters numerically.

   For example:

         rulename    =  %d97 %d98 %d99

   or

         rulename    =  %x61.62.63

   will match only the string that comprises only the lowercase
   characters, abc.

NEW
   The way that has been used in the past to define a rule that
   is case sensitive is to specify the individual characters
   numerically.

   For example:

         rulename    =  %d97 %d98 %d99

   or

         rulename    =  %x61.62.63

   will match only the string that comprises only the lowercase
   characters, abc.  This mechanism has a clear readability
   disadvantage, with respect to using a literal text string with
   a prefix, and new the prefix mechanism is preferred.

END

I will be happy to AD-sponsor this any time you're ready for it to go.

Barry