thought you would like this

https://www6.software.ibm.com/developerworks/education/x-advxquery/index.html

Just to share some of my thoughts on Xquery you can see some of my thoughts on http://contentmangler.wordpress.com

I also though about that a bit, see here:

http://www.martin-probst.com/blog/2008/08/01/higher-order-functions-in-xquery

Rob: I think most XML DB vendors grok that you don’t want to create styles with XQuery. XSLT is great, in particular because of apply-templates. They simply have a different area of application, but I think in most contexts you can very easily integrate XSLT with XQuery, i.e., by post-processing the XQuery result.

Funny you have blogged about high order functions as I have been compiling some specifications myself about Marklogic XQuery extensions that could also make high order functions very useful. One use case that I often find for “functions as first class” would be passing functions to main modules for different strategies for rendering. I was speaking to a few folks from Marklogic last night at the “Customer Appreciation Dinner” and your name seemed to come up as the person to talk to. We should speak more about this topic, as I may contribute a few use cases.

Cheers:-)

Uff… use XQuery when XQuery works best. Use XSL when it works best. They both use XPath. This almost a no-brainer from a user point of view. I do understand that XQuery is more ‘optimizable,’ but at what cost? I really think the XMLDB folk hurt themselves when they ignore the strengths XSL brings to the game.

You are ignoring (dancing around the issue of) the clear advantage of the xsl:apply-templates v. typeswitch. But this would be a non-issue if the XMLDB supported its red-headed stepchild.