RE: [xml-dev] List of differences between XML and JSON?

[William Velasquez <wvelasquez@visiontecnologica.com>]

-          XML requires only one root-element, JSON allows many

-          XML has mixed-context, JSON not

-          XML requires a name for elements and attributes, JSON allows unnamed items

-          XML allows creation of new datatypes (if you can represent them as strings), JSON has a fixed set of datatypes

 

 

I like to think of XML as a try to unify the Hollerith (data) and the Morse (document) worlds (http://www.cmswire.com/cms/information-management/the-battle-for-data-supremacy-the-cost-of-ignoring-xml-017865.php) born from the Morse World, JSON is response from the Hollerith world.

 

But in essence, both of them show us the need to unify the data-processing world with the document-processing world.

 

 

 

De: HILLMAN, Tomos [mailto:tomos.hillman@oup.com]
Enviado el: jueves, 30 de abril de 2015 9:28 a. m.
Para: xml-dev@lists.xml.org
Asunto: Re: [xml-dev] List of differences between XML and JSON?

 

As a document-head rather than a data-head, how about "XML is designed as a mark-up language, JSON is not"

 

That’s not meant to be denigration, by the way: you can mark up a mixed text document using JSON, but it’s not particularly comfortable.

 

T

 

From: <Costello>, "Roger L." <costello@mitre.org>
Date: Thursday, 30 April 2015 15:23
To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
Subject: [xml-dev] List of differences between XML and JSON?

 

Hi Folks,

 

I am putting together a list of differences between XML and JSON. Below is the list that I currently have. Are there other differences, that I haven’t listed?

 

JSON is often compared to XML. However, there are significant differences:

-          XML supports comments, JSON does not.

-          XML supports processing instructions, JSON does not.

-          XML provides multiple syntaxes to express things (e.g., attribute values can be delimited by either a single or double quote, attributes can be in any order), JSON does not have such flexibility.

-          XML uses canonicalization to convert the XML into a standard form, JSON does not need canonicalization since multiple forms are not allowed.

-          XML has namespaces, JSON does not.

Any other differences?

/Roger

Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.