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] Potential Risks of Migration from XML to JSON


> What criteria one must take into account before making a decision to pursue
> such overhaul?

Rather than a complete list, I would just ask whether you want to rely
on Schema validation. A major drawback of JSON is IMHO that namespaces
are not supported. Is "author" always the same? Does every company
understand the same under "author"? Or "money"? Or "price"?

Why do you care for the data format? Isn't it just negotiated on the
wire? Don't you work internally with Java objects, C# objects, ... -
The separation of the format on the wire and the format a client
processes was the idea of WSDL binding: If an in memory call is made,
the Java objects are not converted to XML and back, but directly sent
to the receiving method (see http://ws.apache.org/wsif/ for a basic
implementation - unfortunately not updated any more)

Further, there is a difference between XML infoset and XML. XML is
just one serialization of XML. CSV and JSON are other serialization
formats (see https://en.wikipedia.org/wiki/XML_Information_Set#Serialization).
I am aware that the tooling of serialization XML infoset as other
formats than XML is not that production ready than other XML tooling.

Side node: MSON (https://github.com/apiaryio/mson also seems not to
support namespaces.

Hope, this is some useful input. Cheers,


[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