singleton = "a"-"w" / "y"-"z" / "0"-"9" ; single alphanumerics; 'x' reserved for private-use Although.... > I may add that every ABNF implementation I know of treats strings in a > case-insensitive way (as required by the RFC).I note that people seem to have an incredibly difficult time actually reading one RFC, not to mention understanding ANBF, so we'll probably have to SAY LOUDLY that ABNF is case-insensitive in our own document.
Addison Stephane Bortzmeyer wrote:
On Wed, Dec 13, 2006 at 05:56:41AM -0800,Doug Ewell <dewell at adelphia.net> wrote a message of 27 lines which said:At some point during the development of 4646, somebody argued that both cases needed to be specified.He was clearly wrong. (But I sympathetize, I made the same mistake at the beginning.)Can you find an RFC that states unequivocally that ABNF strings are case-insensitive?Besides the good reference given by John Cowan, I would like to add that RFC which do want case-sensitivity have to use numeric values. See for instance how RFC 4627 describes the string "false" (lowercase only): false = %x66.61.6c.73.65 ; false I may add that every ABNF implementation I know of treats strings in a case-insensitive way (as required by the RFC). _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
-- Addison Phillips Globalization Architect -- Yahoo! Inc. Internationalization is an architecture. It is not a feature. _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.