Re: [xml-dev] use of JSON instead of XML

[Ian Graham <ian.graham@utoronto.ca>]

On 28-Jun-18 12:12 PM, Ihe Onwuka wrote:

On Tue, Jun 26, 2018 at 5:58 PM, Peter Flynn <peter@silmaril.ie> wrote:

On 26/06/18 17:16, Ian Graham wrote:
> This has been fun!

Best we've had in weeks :-)
> ................
>
> An XML list is not the best forum for obtaining that answer ;-}

Nor would a JSON forum :-)

We don't need to go to a JSON forum one because we know the answer.

I don't think a JSON forum would give us an answer any more than this one will.  I am also not convinced we know the answer, although I suspect I'm the minority opinion.

The argument was  XML is an over-engineered solution for the development of web apps and services - JSON is simpler and better fit for that task - we don't need all the complexity and power of the XML ecosystem for that.

Perfectly valid argument. 

Then they started applying JSON to more demanding domains that require namespacing and other complexities that are beyond the limited purview of a _javascript_ object but carried on  making the same (or similar) but now fallacious arguments and no-one wants to deal with the vilification that would ensue if they were called out on it.

So now presenting an alternative "for those more familiar with JSON" has entered into the lexicon as uncritical justification for contorting the semantics of a working complex data model into a syntax and representation that is not equipped to deal with it.

These are all reasonable arguments (in particular the first one), but IMO not proven. I wish there were an enthusiastic developer-turned-social scientist who wanted to use JSON vs. XML as case study for how teams make and evolve design decisions.  Of course then we wouldn't have this meme any more, which would be kinda sad ....

Ian

Ian Graham // <http://www.iangraham.org>