OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Converting other data formats to XML, where the other data formatsallow control characters

Hi Folks,

So, you want to convert this JSON to XML:



\u0000 is a JSON encoding of the NUL (hex 0) character. Recall that the NUL character is not allowed in XML. What will you do with that NUL character? Will you discard it? But that means you have a lossy conversion. Round-tripping will not be possible.


So, you want to convert a JPEG2000 file to XML. The “file type box” contains a series of compatibility list fields. The JPEG2000 standard says this about each field:


This field is encoded as a four-byte string of ISO/IEC 646 characters.


Here is a compatibility list field from one JPEG2000 file (hex bytes):


00 00 00 B5


How will your XML represent that four-byte encoding of a string, given that hex 0 (NUL) is not a valid character in XML?



People are converting JSON to XML. People are converting JPEG2000 to XML. How are they handling characters that are allowed in JSON and JPEG2000 but are not allowed in XML?



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS