XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
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 vs JSON

Michael, when writing  ...

"The key difference is that JSON is designed to make it easy for programs to exchange data with each other, whereas XML is designed to represent documents."

could you venture a definition of the term "document" in this context?

And if

<getFlights>
      <departureAirport>CGN</departureAirport>
      <departureDate>2017-08-18</departureDate>
</getFlights>

is a document, as I would suppose (as it falls into the scope XML has been designed for), is

{
      "getFlights": {
            "departureAirport": "CGN",
            "departureDate": "2017-08-18"
      }
}

less so? If not, are those exchanged data not documents?
     
Kind regards,
Hans-J├╝rgen
 


Michael Kay <mike@saxonica.com> schrieb am 19:09 Freitag, 18.August 2017:


These are universal data structures. Virtually all modern programming languages support them in one form or another. 

Not just modern ones. COBOL records are pretty much isomorphic to JSON objects, give or take a few aberrations like REDEFINES.

The key difference is that JSON is designed to make it easy for programs to exchange data with each other, whereas XML is designed to represent documents.

Michael Kay
Saxonica






[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