Should TAG consider XQuery issues?
Tim Bray has posted an interesting question on the TAG public mailing list http://lists.w3.org/Archives/Public/www-tag/2002Oct/0239.html He had (speaking as an individual) made a quite detailed response http://lists.w3.org/Archives/Public/public-qt-comments/2002Jul/0007.html to an earlier XQuery working draft in which he expressed concerns about XQuery's "maximalism", excessive reliance on the complexities of the W3C Schema Definition Language, over-concern with static typing, divergence from the data model implied by other W3C specs, etc. Bray points to the XQuery WG's official response to his concerns: http://lists.w3.org/Archives/Public/public-qt-comments/2002Sep/0019.html and indicates that he found this response unpersuasive, saying "I'm hardly unbiased here because I strongly disagree with the direction the XQuery WG is going here on technical grounds. Furthermore, I think that if this issue were being discussed on purely technical terms, some decisions might be different." He concludes by asking for opinions on whether the TAG should consider the issues in dispute here (and presumably issue a "Finding" to guide the XQuery WG, although as recent discussions have made clear, a TAG Finding is an opinion, not a directive). I suspect that a number of xml-dev subscribers who don't generally follow the TAG list may wish to consider the issues raised in Bray's messages, the XQuery WG's response, and express an opinion to the TAG. Or scream and yell about it here <grin>
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format