Re: Use of XML for config files

[Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de>]

Ted Dennison <dennison@telepath.com> wrote:
: If we are to stick with simple attribute-value pairs, then XML would
: be major overkill.

Having dealt with samba config files,

# the option 'an option', dependent on foo = value, provided option bar=yes,
# does bla bla bla
 an option = a value

I really enjoy well structured configuration data. This is where
a reasonably small DTD enters the scene, explaining the relations
among configurable items. Being herectic for a moment, I'd say
that you could even

-  support a config API that uses a DTD with XML as input and
   translates this into a program specific useful internal representation
-  "map" an application specific DTD to a common DTD for configurations.

Lists of key:=value are flat, possibly interrupted by section headings
providing a very basic name space, XML data are trees with nodes that
can be individually address by 
- paths,
- IDs
- predicates.

To me this looks somewhat like an asm-listing compared to a 
structured program.

-- Georg