[XQuery Talk Mailing List Archive Home] [By Date] [By Thread] [By Subject] [By Author] [Recent Entries] [Reply To This Message]

XML Query Test Suite version 0.8.4

Michael Kay mhk at mhk.me.uk
Wed Jan 11 15:15:53 PST 2006


xslt codes
> Thanks for this, but on reflection I think I won't do that and will
> either do nothing or write some code to explictly convert the 
> xslt codes to xquery ones.

That makes sense. Fortunately the XSLT error codes are generally more
fine-grained than the XQuery ones. It's still possible, though, that there
will be cases where the XSLT code doesn't give you enough information.

There are also situations where XSLT has different run-time semantics from
XQuery, a notable example being

element x {
  attribute a {3}
  attribute a {4}
}

How are you handling that?

Also, how are you handling the XQuery "order by" problem: what XSLT code do
you generate for pathological cases like

for $x in 1 to 10, $y in 100 to 200
order by $y, $x
return $x + $y

Michael Kay




PURCHASE STYLUS STUDIO ONLINE TODAY!

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.
Email
First Name
Last Name
Company
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-2007 All Rights Reserved.