Re: Syntax

Julian Reschke <> Wed, 10 January 2007 21:54 UTC

Received: from [] ( by with esmtp (Exim 4.43) id 1H4lPE-0000MA-8j; Wed, 10 Jan 2007 16:54:48 -0500
Received: from [] ( by with esmtp (Exim 4.43) id 1H4lPD-0000ID-EJ for; Wed, 10 Jan 2007 16:54:47 -0500
Received: from ([]) by with smtp (Exim 4.43) id 1H4lPC-0005m7-1F for; Wed, 10 Jan 2007 16:54:47 -0500
Received: (qmail invoked by alias); 10 Jan 2007 21:54:44 -0000
Received: from (EHLO []) [] by (mp010) with SMTP; 10 Jan 2007 22:54:44 +0100
X-Authenticated: #1915285
Message-ID: <>
Date: Wed, 10 Jan 2007 22:54:43 +0100
From: Julian Reschke <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20060516 Thunderbird/ Mnenhy/
MIME-Version: 1.0
To: Frank Ellermann <>
References: <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: Re: Syntax
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: DIscussion on state machine specification in IETF protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

Frank Ellermann schrieb:
> Clive D.W. Feather wrote:
>> The "what's valid UTF-8" syntax isn't complicated.
> While I agree that the code shown below isn't complicated it's not
> what I'd like to copy into any REXX scripts about state machines.
> ...

We are defining a *new* language here. For now, it's for use in IETF 
documents (which are ASCII only). That requirement may change. Or people 
may want to use it for different target documents, such as the W3C's, or 

Restricting that language because you happen to use a platform which is 
really really old doesn't compute for me. Unicode support has been 
around on all widely deployed platforms for many, many years now.

You would still have the choice to implement your parser without 
supporting non-ASCII characters. That would simple mean that state 
machines authored with non-ASCII characters wouldn't be processable on 
your platform. I don't think that this would be a problem for the 
Internet Community.

I'd really suggest that we defer this problem until later, when more 
implementor feedback is available. Let's focus for now on the key 
features (and I don't think I18N is one of them).

Best regards, Julian

Cosmogol mailing list