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]
Re: [xml-dev] XML design for converting to and from JSON?

IBM has a hardware accelerated edge device that goes by the name of Datapower.  Among other things it has a facility for doing exactly this. The XML format is known as JSONX., Basic docs are here:


On Mon Dec 15 2014 at 10:44:36 AM Costello, Roger L. <costello@mitre.org> wrote:
Hi Folks,

The ability to easily convert XML-formatted data into JSON-formatted data and vice versa is a good thing, I think.

If you were setting out to design some XML with a design goal that the XML can be easily converted to JSON, how would you design the XML?

Are there some features of XML that might inhibit its easy conversion to JSON? What about these features:

        - Namespaces?
        - Mixed content?
        - Processing instructions?
        - Comments?
        - Attributes?
        - DOCTYPE declaration?
        - Entities?
        - Other things?

Perhaps you have already created guidelines for XML design to enable easy conversion to JSON? If so, would you share your guidelines please?



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

[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