[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ABNF usage examples, for elevation to Draft Standard
- To: Dave Crocker <dave@tribalwise.com>
- Subject: Re: ABNF usage examples, for elevation to Draft Standard
- From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
- Date: Thu, 11 Jul 2002 09:55:44 +0200
- Cc: sming@ops.ietf.org
- In-reply-to: <5.1.0.14.2.20020709015406.02bf24b8@jay.songbird.com>
- User-agent: tin/1.4.3-20000502 ("Marian") (UNIX) (Linux/2.2.19-6.2.7-autofs4pre9 (i686))
In article <5.1.0.14.2.20020709015406.02bf24b8@jay.songbird.com> you wrote:
> Hence, this note is soliciting comments on use of ABNF features, as
> documented in the current Internet-Draft:
> draft-crocker-abnf-v3-00.txt
> Especially interesting are any features that might be considered unusual,
> obscure or non-normative in the current draft.
The SMIng WG is using ABNF to define the syntax of what might
become SMIv3 at the end. What is kind of ugly in our usage of
ABNF is the fact that literal text strings are case insensitive
while the SMIng language keywords are case sensitive. This requires
to define all keywords in hexadecimal format, which does not really
increase readability and we already had bugs here. For our usage
of ABNF, it would be extremely helpful if there were another literal
text string format (e.g. enclosed in single quotes) which is case
sensitive.
/js
--
Juergen Schoenwaelder <http://www.informatik.uni-osnabrueck.de/schoenw/>