John Klassa wrote:
> >>>>> On Mon, 5 Mar 2001, "Brian" == Brian Clapper wrote:
> Brian> That's as may be, but XML is a crappy configuration file syntax
> Brian> to foist on people. The one thing I dislike about "ant" is
> Brian> that its build file is in XML. It's a highly annoying and
> Brian> inappropriate syntax to have to read and edit. If you're going
> Brian> to make someone edit a configuration file by hand (as opposed
> Brian> to supplying a UI or translator that hides the XML), why not
> Brian> choose a syntax that's less visually cluttered and easier to
> Brian> read?
> *Exactly*! :-)
> John Klassa / firstname.lastname@example.org
Suggest something. Something like IETF headers? With the new CMIP
rules (mainly to avoid the silly restrictions on line length and
annoying continuance stuff) it's ok for flat things. What about
sections (a la .ini files)?
It is conceivable that a consensus could be built for some simple
equivalence for simple cases that could allow full XML for nesting,
extension, and more complicated cases.
I think many involved in XML assume you'll use a nice editor to hide the
It's not that much of a stretch to say that if you are outside any tags
or inside a specially tagged area, IETF headers or .ini format or
whatever are syntactically equivalent to simple XML tagging. Getting
everyone to change their parsers is another story, however for config
situations you only need the parsing in the app to be extended.
-- email@example.com firstname.lastname@example.org swilliams@Jabber.com Stephen D. Williams Insta, Inc./Jabber.Com, Inc./CCI http://sdw.st 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax Dec2000
This archive was generated by hypermail 2b29 : Fri Apr 27 2001 - 23:13:29 PDT