Lists Home |
Date Index |
I'm really suprised that someone with a microsoft.com at the end of their
email would issue this statement:
"(why is an xsl:variable called a variable if it doesn't vary?) "
The response to that query has been around a long time:
And so has the so-called workarounds to that "problem", which really hasn't
been a problem for most XSLT developers once they're comfortable with the
XQuery does indeed look cool, but it's about as cool as XPath 2.0, which is
married to it, and XSLT 2.0, which benefits from that union. Anyone who
can't grok XSLT 1.0 but can grok XQuery will be able to grok XSLT 2.0.
Author, Mastering XSLT, Sybex Books
----- Original Message -----
From: "Dare Obasanjo" <email@example.com>
>A couple of us feel that XQuery will some of the problems with XSLT that
have prevented it >from becoming the lingua franca for processing XML by the
average XML developer. XSLT's >unnecessarily verbose syntax, limited set of
useful builtin functions & operators and unfamiliar >programming model (why
is an xsl:variable called a variable if it doesn't vary?) have always >made
it seem inaccessible to many users who would otherwise benefit from it.
XQuery fixes >these issues which makes it more approachable to the thousands
of developers who have to >process XML data and have thus far limited
themselves to object <->XML technologies , >DOM or streaming APIs because
they couldn't grok XSLT.
XQuery is hot.