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] json v. xml

derek denny-brown said:

> Aside from the cross-domain issue, I think XML also missed the boat by
> not providing a canonical 'object serialization', akin to JSON.  Part
> of the explosion of JSON is due to it's low barrier to entry.

"Missed the boat" suggests that canonical object serialization should have
been a goal of XML in the first place, which it wasn't. (But perhaps Denny
is right: if we'd gonge with the instance-based type annotation ideas that
IIRC Charles Goldfarb suggested, this would be a different discussion.)

The world is big enough for more than one syntax for things. JSON is to
XML what IDL is to DTDs.

Ultimately, the XML methodology is markup: annotation. (And arbitrary,
unlimited annotation with arbitrary constraint checking.) Not everything
should be markup.

We are better off with two (or ten) small, distinct languages that
developers can master rather than multiplying the complexity of XML in
futile attempts to make it useful for everything. The opposite of
complexity is not simplicity but modesty.

As I understand JSON, it is merely client-side programmers saying "Hey, we
already have a syntax for representing data structures in JavaScript, why
not just use that so we don't need any special API for naming and
navigating?" That is an utterly reasonable position, it seems to me.

Rick Jelliffe

[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