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] Best options for converting JSON to XML

Did  Crockford and co emit any cautionary noises when people decided
this was a suitable vocabulary for a database repository ?

On Sun, Nov 10, 2013 at 9:04 AM, Michael Kay <mike@saxonica.com> wrote:
>>>
>>> Looks like the JSON people (or can I just blame Crockford) screwed up
>>> by not thinking about interoperability with XML
>
> No, I don't think they screwed up. I think they made it simple deliberately, knowing full well that when you keep a design simple, you make easy things easier, and difficult things more difficult. But not all JSON users realise the latter consequence until they get to that point.
>
> 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