On Fri, 2014-04-04 at 15:07 +0200, Heiko W.Rupp wrote:
Am 04.04.2014 um 14:52 schrieb John Mazzitelli
<mazz(a)redhat.com>:
> What was the reason for not using XML in the first place?
Perhaps because I wrote my first idea page with json.
I think one of the more annoying parts of XML is that (depending on how you set it up)
stuff needs to go into CDATA sections as element content forbids a good number
of characters.
This is a very good point. Are there any character restrictions in yaml?
Character escaping/encoding, or lack thereof, is something that tends to
magnify the human error factor. XML might make sense and be easy for
many web developers but not all users fit into this camp.
That said I should also disclose that I dislike XML for many reasons.
One being that nesting elements and attributes makes diff'ing and
merging more error prone.
And I do not think that the expressions themselves should go
into an attribute - especially as I think that it is vital that the plugin developer
an write them as multiline ones
not
groupby resource.name; resource.plugin.name = bla; ...
but
groupby resource.name
resource.plugin.name = bla
...
You should be able to use multiple lines within XML without issue. I
think your real point was that you don't want to use a line terminator.
In my opinion, the line terminator should be supported as it is common
in any expression or query language.
However, it should be important to note that white spaces in XML
attributes can be normalized. This could be very bad considering the
expression may not evaluate to what the developer expected.
--
Larry O'Leary
https://plus.google.com/+LarryOLeary