W3C home > Mailing lists > Public > uri@w3.org > May 2003

Re: Syntax Issues/Experience with RFC2396bis and abnf2re

From: Graham Klyne <GK@ninebynine.org>
Date: Tue, 06 May 2003 12:06:01 +0100
Message-Id: <5.1.0.14.2.20030506120408.01f5bf28@127.0.0.1>
To: Rob Cameron <cameron@cs.sfu.ca>, uri@w3.org

At 18:33 05/05/2003 -0700, Rob Cameron wrote:
>(2)  The HEXDIG definition of RFC2234 is upper-case only;
>      it's probably not what is wanted.
>        escaped     = "%" HEXDIG HEXDIG

I beg to disagree.

From: http://www.ietf.org/rfc/rfc2234.txt

[[
         HEXDIG         =  DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
]]

and

[[
ABNF permits specifying literal text string directly, enclosed in
    quotation-marks.  Hence:

         command     =  "command string"

    Literal text strings are interpreted as a concatenated set of
    printable characters.

         NOTE:     ABNF strings are case-insensitive and
                   the character set for these strings is us-ascii.

    Hence:

         rulename = "abc"

    and:

         rulename = "aBc"

    will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC" and "ABC".

                 To specify a rule which IS case SENSITIVE,
                    specify the characters individually.
...
]]

#g


-------------------
Graham Klyne
<GK@NineByNine.org>
PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E
Received on Tuesday, 6 May 2003 08:37:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:31 GMT