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] It's too late to improve XML ... lessons learned?

It is easy to forget  that JSON wasn't intended or designed as a replacement for XML.
Then and much more so now, I don't believe there was an appetite for the engineering and standardisation effort entailed in designing any such format.

I think instead we will continue to see formats designed to address relatively narrow and specific use cases. JSON has shown the pathway to wider adoption, if sought is by hyping the format beyond its intrinsic utility.

On Wed, Jan 5, 2022 at 7:35 AM Stephen D Green <stephengreenubl@gmail.com> wrote:
And how can JSON not count? If something does not have drivers for its success, surely it would not have succeeded? 

I think JSON succeeded because it was already existing and got discovered so it was free and already had traction and some sanction as part of _javascript_. So it did not need the ingredients to success that a new technology would need. It did not need a vacuum to fill, developer adoption, new parsers, bug fixing, security patching and rethinks, lengthy specs, standardisation, expensive consultants, evangelists. These were hurdles XML had to overcome and a new technology would have to overcome. 



[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