- From: <bugzilla@jessica.w3.org>
- Date: Thu, 29 Apr 2010 17:22:21 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8879 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mike@saxonica.com --- Comment #3 from Michael Kay <mike@saxonica.com> 2010-04-29 17:22:21 --- I think binary serialization only makes sense in the context of generally adding better support for binary data to XSLT and XQuery. It's unfortunate that the XML Schema binary datatypes are such a weak foundation for this. Having two data types, hexBinary and base64Binary, that are focused on the lexical representation of the data rather than the value space isn't a good starting point. Perhaps we should do the string/URI trick: define our functionality in terms of one of them (say hexBinary) and have automatic promotion for the other. Operators that are needed include concatenation and slicing (subsequence) of binary values; bitwise and/or/xor/not; conversion to/from a sequence of integers representing the individual bytes (or perhaps other units, such as 1-bit, 8-bit, 16-bit, 32-bit, 64-bit chunks); conversion to/from strings (specifying the character encoding). Then we need the ability to read binary files (unparsed-binary()) and to write binary files. It's not clear to me that writing binary files really comes under the heading of "serialization", but we might like to design it that way. -- 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 Thursday, 29 April 2010 17:22:23 UTC