- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 25 Feb 2009 09:59:13 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5771 --- Comment #3 from Michael Kay <mike@saxonica.com> 2009-02-25 09:59:12 --- Well, that seems like a different requirement from reading URIs using the "data" scheme. Incidentally, XSLT has a function unparsed-text() for reading plain text files, there's no intrinsic reason why that shouldn't migrate into XQuery along with other XSLT functions that are going that way. I can see that unparsed-binary() would sometimes be useful too. My main reservation is that it would open up a whole new area for functions and operators dealing with binary data. For example, Saxon currently has extension functions to convert between xs:base64Binary/xs:hexBinary and xs:string/xs:byte*, in both directions, giving 8 functions in all. There have also been requests in the past for functions that do bitwise and/or/xor, or that test/set individual bits or bytes (though converting to xs:byte* is arguably a sufficient enabler for that). -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 25 February 2009 09:59:25 UTC