[Home] [By Thread] [By Date] [Recent Entries]

  • From: Jonathan Robie <Jonathan.Robie@S...>
  • To: David Rosenborg <david.rosenborg@p...>, xml-dev@l...
  • Date: Sat, 24 Feb 2001 11:28:36 -0500

At 10:34 PM 2/22/2001 +0100, David Rosenborg wrote:
>By evolutionary I mean this: XSLT and XQuery share a common pattern:
>
>1) select nodes
>2) generate the result tree
>
>In XSLT the first is handled by XPath and the second by template 
>instructions. An evolutionary approach
>had been to extend, and subset (for optimization purposes) each of these 
>to get a comprehensive and yet
>optimizable solution. As I said, XQuery does do this with XPath (modulo 
>namespace handling and case-insensitive keywords),
>but for the generative part nothing is reused. Strange.

XSLT uses one language for selecting nodes, and a different language for 
generating the result tree. XQuery uses one language that can do both. This 
allows XQuery expressions to be more compositional than is possible in XSLT.

Jonathan

These are my opinions right now. They may be quite different from the 
opinions of Software AG, the W3C XML Query Working Group, or the opinions 
that I will have after reading and considering your response.


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member