Syntax

Julian Reschke <julian.reschke@gmx.de> Sun, 07 January 2007 17:12 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H3bZE-0000sc-AQ; Sun, 07 Jan 2007 12:12:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H3bZD-0000sH-Cw for cosmogol@ietf.org; Sun, 07 Jan 2007 12:12:19 -0500
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H3bZC-00032T-0G for cosmogol@ietf.org; Sun, 07 Jan 2007 12:12:19 -0500
Received: (qmail invoked by alias); 07 Jan 2007 17:12:12 -0000
Received: from p508FB005.dip0.t-ipconnect.de (EHLO [192.168.178.22]) [80.143.176.5] by mail.gmx.net (mp017) with SMTP; 07 Jan 2007 18:12:12 +0100
X-Authenticated: #1915285
Message-ID: <45A129E9.50905@gmx.de>
Date: Sun, 07 Jan 2007 18:12:09 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cosmogol@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: Syntax
X-BeenThere: cosmogol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: DIscussion on state machine specification in IETF protocols <cosmogol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/cosmogol>, <mailto:cosmogol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/cosmogol>
List-Post: <mailto:cosmogol@ietf.org>
List-Help: <mailto:cosmogol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/cosmogol>, <mailto:cosmogol-request@ietf.org?subject=subscribe>
Errors-To: cosmogol-bounces@ietf.org

Hi,

here are a few thoughts regarding the syntax:

1) Although the language is designed to be used in IDs and RFCs, 
restricting it to ASCII here is IMHO a very bad idea. After all, you may 
want to use it for other specifications, and the IETF may lift the 
current restrictions at some point of time. I would suggest to require a 
specific text encoding such as UTF-8, and try to make the definitions 
for the character set of identifiers much something well understood 
(such as XML 1.0).

2) At a later point, it would be great if the format would define and 
register a mime type (for instance, we would want that for easy 
inclusion into RFC2629 artwork).

3) Although a "compact" syntax is great for readability, an alternate 
syntax in XML would be good for usage within XML tool chains. I've 
written several XSLTs targeting GraphViz in the past, and getting 
escaping right can be a nightmare. Having a separate XML based input 
format would make things much easier (if there's interest in that, I'll 
happily contribute).

Best regards, Julian



_______________________________________________
Cosmogol mailing list
Cosmogol@ietf.org
https://www1.ietf.org/mailman/listinfo/cosmogol