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

[Thomas Passin <list1@tompassin.net>]

You can make subsets of XML that do pretty much the same things as JSON, 
when interpreted properly.  That doesn't mean you get to say that they 
have the same capabilities in general.

With JSON, you can send me objects (sets of name-value pairs) and value 
lists, where "values" can be objects, numbers, lists, or strings. 
That's what you can do.

You can use XML to send those things too, but an XML document isn't 
limited to only that.  So JSON is essentially similar to a subset of 
XML.  If these capabilities happen to be what you want, then fine, and 
you'll probably be happier with JSON.

If you are examining differences between JASON and XML, it isn't going 
to be helpful to start by pruning away things that make them different.

On 5/2/2015 10:19 AM, Costello, Roger L. wrote:
> Thomas Passin wrote:
>
> > Remember that XML is not actually a language but a toolkit for
> > specifying languages.
> By that I believe you mean that I can define an XML vocabulary and
> then create many XML instances which use that vocabulary. For
> example, I can define a BookStore XML vocabulary and then create many
> Bookstore instances, I can define a Cellphone XML vocabulary and then
> create many Cellphone instances. I use XML Schema to define each XML
> vocabulary.
>
> Right?
>
> > JSON is a language.
> With JSON I can define a JSON vocabulary and then create many JSON
> instances which use that vocabulary. For example, I can define a
> BookStore JSON vocabulary and then create many Bookstore instances, I
> can define a Cellphone JSON vocabulary and then create many Cellphone
> instances. I use JSON Schema to define each JSON vocabulary.
>
> Aren't XML and JSON equivalent in the sense that they are syntaxes
> from which many XML-formatted/JSON-formatted languages may be
> created?
>
> /Roger