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

Re: RE: List of differences between XML and JSON?

• From: "Liam R. E. Quin" <liam@w3.org>
• To: stephengreenubl@gmail.com
• Date: Thu, 30 Apr 2015 13:04:31 -0400

On Thu, 2015-04-30 at 17:01 +0100, Stephen D Green wrote:
> One minor point in JSON's favor: only one label per element compared 
> to (usually) two in XML. That saves a bit of verbosity and space.
It also gives sligtly less error checking in JSON.

Correct the following:
<author>Titus Groan</title>
<title>Mervyn Peake</author>
Is there an error here?
"author": "Titus Groan", "title":"Gormenghast"

(answer: yes).

But this matters less in an object serialization format than in an 
information representation format, because of the way JSON is 
typically generated. I suspect.

Liam

> ----
> Stephen D Green
> 
> 
> On 30 April 2015 at 16:50, Costello, Roger L. <costello@mitre.org> 
> wrote:
> > Thank you for the fantastic feedback!
> > 
> > I updated the list using your feedback. Is there anything else 
> > that should
> > be added?  /Roger
> > 
> > --------------------------------------
> > 
> > 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 child nodes (text, elements, comments, PIs) have 
> > order, the
> > key/value pairs in JSON objects are unordered.
> > 
> > -          XML uses canonicalization to convert XML into a 
> > standard form.
> > Since ordering doesn't exist in JSON objects, a canonical form for 
> > JSON is
> > problematic: with no canonical order, there's no standard byte 
> > stream.
> > 
> > -          XML has namespaces, JSON does not.
> > 
> > -          XML supports mixed content, JSON does not.
> > 
> > -          XML has entities and notations, JSON does not.
> > 
> > -          XML does not have arrays (although they can be 
> > simulated), JSON
> > has arrays. JSON objects inside arrays have position, but no name; 
> > if an array is inside an object, then the name could be mapped 
> > from the key name
> > for the array member; JSON arrays inside arrays inside an object 
> > are somewhat more of a challenge.
> > 
> > -          XML uses different character sets (NCName) for markup 
> > than for
> > content, JSON uses the same character set throughout the entire 
> > document.
> > 
> > -          XML supports any character encoding scheme, JSON 
> > supports
> > exclusively Unicode.
> > 
> > -          XML has pointy brackets, JSON has curly and square ones.
> 
> _______________________________________________________________________
> 
> 
> 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

• References:
  • List of differences between XML and JSON?
    • From: "Costello, Roger L." <costello@mitre.org>
  • RE: List of differences between XML and JSON?
    • From: "Costello, Roger L." <costello@mitre.org>
  • Re: RE: List of differences between XML and JSON?
    • From: Stephen D Green <stephengreenubl@gmail.com>