[Oisf-wg-configuration_language] Configuration Structure

[Matt C]

*"In this resect, YAML might be a good middle-ground, despite the fact that
it
cares about whitespace.  It'll provide an easily parsed config file for the
tool writers out there due to the availability of YAML parsers, yet it is
easily edited in a text editor - even easier if you use a YAML aware editor
like emacs in yaml-mode.

Hmm, I had no intention of this sounding like a go yaml post, as I'm on the
fence here still myself.

Jason"*

Here is a direct quote from the YAML specification:

YAML also has flow styles, using explicit indicators rather than indentation
to denote scope. The flow sequence is written as a comma separated list
within square brackets. In a similar manner, the flow mapping uses curly
braces.

If whitespace is THAT much of a concern, flow styles could be used.  In my
opinion using {} and [] and such is just as bad as using <> from XML.  Using
whitespace allows for a clean readable syntax.  Most of my programming is
done in Python, a language that relies heavily on whitespace.  I have used
many editors (including vi/vim) for python programming without any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-wg-configuration_language/attachments/20090807/6da3f8f4/attachment-0002.html>