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's greatest cultural advantage over JSON

>> XML had a chance with an open-minded crowd of people eager to embrace
>> it.  By and large, we utterly failed to convince them.  Once other
>> options emerged, they ran there.
>
> I think that story is different. Javascript in browser doesn't have
> usable XML API (DOM is simply ... DOM), but evaluating JSON with eval()
> at that time was very easy (do you still remember E4X?). Also given the
> browser security model you are unable to fetch cross-site XML resources,
> but you can do the same with JSON-P. So with JSON it was possible to
> walk around limitations in browser, nothing more. With better XML API in
> browser and more reasonable security model situation between JSON/XML in
> Web front-end development could be very different.

That is essentially it - processing xml using javascript in the
browser was hard, processing json was easier.   It's all about the
apis.

If only there was a simple api for xml... that was actually simple :)
 I'm sure the list could come up with a new one.


-- 
Andrew Welch
http://andrewjwelch.com


[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