Lists Home |
Date Index |
> 1. Xquery is not XML
I was always puzzled by this argument that people use in
favor of XSLT and against XQuery.
First, please let me remember you that XSLT is not XML
in it's entirety EITHER. Do you forget that the path
expressions remain unparsed strings and appear as
attribute values !?
For me this dual representation of XSLT (half pre-parsed XML,
half unparsed strings) doesn't bring any advantage.
I love the *semantics* of templates in XSLT. I find it really useful.
But I would prefer to also have an angle brackets free syntax for it.
As such (with the current XSLT syntax) it makes it harder for me
as a developer (I tend to dislike programming with angle brackets
--- it's not readable enough), and due to the fact it is XML only half
it doesn't make it easier for automatic processing either.
So Dave, we had this argument a couple of times, and I never understood
your answer: what exact benefit do you get from the the fact that XSLT
represented in it's current XML syntax ?
And why don't you get the same benefits from XQueryX (the pure XML
variant of XQuery) ?