[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Best options for converting JSON to XML

• From: Ihe Onwuka <ihe.onwuka@gmail.com>
• To: David Lee <dlee@calldei.com>
• Date: Sun, 10 Nov 2013 08:15:25 +0000

Seeing as I just want to shell out to XML for validation I'd like to
think I don't have to care about what the converted XML looks like.

Was reading another paper of yours
http://www.balisage.net/Proceedings/vol10/html/Lee01/BalisageVol10-Lee01.html
yesterday as it happens.

So heres my in-depth analysis.

Looks like the JSON people (or can I just blame Crockford) screwed up
by not thinking about interoperability with XML when designing their
format because now they have to erect their own edifice of supporting
tools and architectures. If alot of what they are trying to achieve
can be effected with compression and some transformation tricks you
got to wonder whether the price JSON makes you pay in the lack of
standards, interoperability and tool support/maturity is worth it



On Sat, Nov 9, 2013 at 5:25 PM, David Lee <dlee@calldei.com> wrote:
> You may be interested in this paper which covers in some detail many of the issues of converting between JSON and XML.
>
> http://www.calldei.com/pubs/Balisage2011/index.html
>
> The simple answer is that there are *many* techniques and tools for converting between JSON and XML, but none of them are perfect or fit all desires.
> You need to decide what aspects of conversion are important to your application.
> You can then search the web for various tools and/or libraries to help.
> The tool mentioned in the above paper is available but is only as a POC so I dont recommend it.
> xmlsh has  a very primitive JSON to XML conversion
>
> http://www.xmlsh.org/CommandJson2xml
>
> This style of conversion is quite easy to do in nearly any language that supports both XML and JSON.
> What's hard is to come up with a conversion which produces XML that an XML person would like to read and JSON that a JSON person would like to read simultaneously.
>
>
>
> ----------------------------------------
> David A. Lee
> dlee@calldei.com
> http://www.xmlsh.org
>
> -----Original Message-----
> From: Ihe Onwuka [mailto:ihe.onwuka@gmail.com]
> Sent: Saturday, November 09, 2013 11:26 AM
> To: xml-dev@lists.xml.org
> Subject:  Best options for converting JSON to XML
>
> I am considering alternatives to JSON Schema for validating JSON so
> the natural idea is to convert to XML and use some sort of schema.
>
> I'd be grateful for thoughts on the advisability of this type of
> thinking in the first place and suggestions for converting the JSON to
> XML.
>
> thanks
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

• Follow-Ups:
  • Re: Best options for converting JSON to XML
    • From: "Timothy W. Cook" <tim@mlhim.org>

• References:
  • Best options for converting JSON to XML
    • From: Ihe Onwuka <ihe.onwuka@gmail.com>
  • RE: Best options for converting JSON to XML
    • From: David Lee <dlee@calldei.com>