From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a26758eec3c2e1ad X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-05 00:18:39 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!213.73.101.75!eusc.inter.net!cs.tu-berlin.de!not-for-mail From: Volkert Barr Newsgroups: comp.lang.ada Subject: Re: Use of XML for config files Date: Wed, 05 Jun 2002 09:18:37 +0200 Organization: TU Berlin, Fachbereich Informatik Message-ID: <3CFDBB4D.29DAADEF@cs.tu-berlin.de> References: <3CFC5DB2.A21DCF61@cs.tu-berlin.de> <4519e058.0206041129.5b250124@posting.google.com> NNTP-Posting-Host: bolero.cs.tu-berlin.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.cs.tu-berlin.de 1023261518 29854 130.149.19.1 (5 Jun 2002 07:18:38 GMT) X-Complaints-To: news@cs.tu-berlin.de NNTP-Posting-Date: 5 Jun 2002 07:18:38 GMT X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en Xref: archiver1.google.com comp.lang.ada:25330 Date: 2002-06-05T07:18:38+00:00 List-Id: > What that means is that if we were to use XML, we should support both > user-defined configuration item attributes and some kind of object > nesting (configuration items defined within other configuration > items). I haven't really heard anyone seriously arguing the usefulness > of this stuff. > > If we are to stick with simple attribute-value pairs, then XML would > be major overkill. I have set up a first small datamodel for hierarchical configuration data (nested Config_Items containing lists of (Key,Value)-Tupels) and defined a BNF-Grammar for text (file) representation of this data. I hope Stephan Leake will add it to his "Config-Proposal Page"! The grammes defines the following style: -- -- Comment Block -- Config_Item1.Key := Value -- Comment Config_Item1.Inner_Config_Item2.Key := Value The same can be done in XML, but the next you need is an "XML Editor" ;-) (That is one reason, why there is so much Business (and money) around XML.) XML-like Configuration: Key Value Key Value Volkert