[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: A beef with XSLT Sometimes too complicated

Subject: RE: A beef with XSLT Sometimes too complicated
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Fri, 14 Jul 2006 12:43:54 +0100
xslt avoid duplications
> xpath can exist without xslt but not the other way round. The 
> situation is (exactly) the same in XQuery, but XQuery is 
> usually regarted as an extension of XPath: that is XQuery is 
> a single language, with more constructs than XPath) whereas 
> XSLT is usually described is a two-language construct 
> consisting of xslt constructs and Xpath constructs. It's 
> pretty much a marketing angle which way you describe it 
> really. 

I don't think that's fair: it's a genuine technical difference, which
results in different strengths and weaknesses. In XQuery you have a higher
level of composability of expressions. You can write things like

<a>{2+2}</a> = 4

(which of course you need to do all the time), and you avoid duplication of
control sructures like if and for; but the downside is that you have a more
fragile syntax (harder to extend, harder to report and recover from syntax
errors reliably) and one that means XQuery source text isn't accessible to
XML-based tools.

That's a technical design choice, not a marketing angle.

Michael Kay

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.