Hi, Many of these JSON<->XML tools provide a good coverage for some XML/JSON constructs but not for all. The tool [1] you pointed to fails for example when converting the following "simple" JSON example to XML. { "a number": 1 } The reason is rather simple. The qualified name in XML has some restrictions that are more rigid than the JSON fieldnames. Hence, we in the EXI working group worked on a more sophisticated approach when converting JSON to XML infoset [2]. This requires escaping as shown here [3] for the example above. Note1: The Efficient XML Interchange (EXI) format would not have the same restrictions as XML but the working group concluded that any EXI document should be convertible to XML. Note2: The XSLT working group uses yet another scheme [4] which for EXI did not work given that we want to allow for user-defined XML schemas. Having said that, there seem to be many approaches and solutions, -- Daniel [1] www.utilities-online.info/xmltojson/
Von: Mukul Gandhi [gandhi.mukul@gmail.com]
Gesendet: Freitag, 22. September 2017 08:08 An: xml-dev@lists.xml.org Betreff: [xml-dev] Re: XML vs JSON With respect to this thread, I could see that people have written tools to convert between XML and JSON (both ways). This seems to be nice: www.utilities-online.info/xmltojson/
On 1 August 2017 at 17:04, Mukul Gandhi
<gandhi.mukul@gmail.com> wrote:
Regards,
Mukul Gandhi |