New XQuery and XSLT Working Drafts: We are making progress!
The XML Query and XSL Working Groups have released the following Working Drafts of XML Query 1.0, XSL 2.0, XPath 2.0 and supporting documents. The goal of this release is to permit public review of changes made in response to Last Call comments. These documents are very close to the so called Candiate Recommendation that we hope to be able to publish soon. Yeah! We are making progress! Even though my issue with the spec has been closed without making the proposed change (minority opinion, here I come)...
- XQuery 1.0: An XML Query Language
- XQuery 1.0 and XPath 2.0 Data Model
- XQuery 1.0 and XPath 2.0 Functions and Operators
- XSLT 2.0 and XQuery 1.0 Serialization
- XML Syntax for XQuery 1.0 (XQueryX)
- XQuery 1.0 and XPath 2.0 Formal Semantics
- XML Query Use Cases
- XML Path Language (XPath) 2.0
- XSL Transformations (XSLT) Version 2.0
Also published are the following updated Working Drafts which have not yet reached Last Call:
Comments are as always welcome through the W3C's Bugzilla interface or the public comment mailing list.
PS: Thanks to the editors and especially Norm who again did a terrific job on getting the docs ready...
Comments
- Anonymous
September 16, 2005
Once XQuery is ready, can we talk about getting that added into the .NET runtime?
I'm already sick of interfacing to external XQuery engines for my client-side applications. - Anonymous
September 19, 2005
Thanks for the feedback. The System.XML team certainly wants to hear from you (I forwarded your comment to them). I recommend that you provide more details on your requirements on XQuery in the .Net framework per email either to me (http://blogs.msdn.com/mrys/contact.aspx), Mike Champion (http://blogs.msdn.com/mikechampion/archive/2005/09/15/467179.aspx) or the XML Team (http://blogs.msdn.com/xmlteam/default.aspx). Some interesting questions would be on what do you see as your personal killer-scenario of using XQuery in .Net. Why are you not using XSLT? Would you consider using XLinq instead or in addition to XQuery (and if not, why not)?