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] ten years later, time to repeat it?


> From: petexmldev@codalogic.com
> To: len.bullard@uai.com; simonstl@simonstl.com; xml-dev@lists.xml.org
> Date: Tue, 12 Feb 2008 12:31:59 +0000
> Subject: Re: [xml-dev] ten years later, time to repeat it?
>
> I don't have the breadth of experience that many on this list have, but to
> me mixed content seems pretty important to a document oriented view. In
> that scenario, in a world where few things are ever perfect, XML seems about
> as good as you can get (entities, namespaces and other things that people
> grumble about aside).
>
> This provision for document features does compromise XML for purely
> data-applications though, where JSON seems to be better.
>
> My view is that the world could do with 2 data formats, something XML-like
> primarily for documents and something JSON-like for pure data. In this
> view, tools like XSLT would be able to consume both formats (possibly using
> some form of auto-detection and using some form of XML infoset common
> intermediate form) and maybe even be able to output both formats (via some
> kind of switch).
>
> That said, JSON seems to be contaminated with JavaScript cruft. For
> example, instead of:
>
> "foo": 123
>
> you should be able to do:
>
> foo: 123
>
You can use that in JSON if you prefer, the quotes are only needed for property names with spaces.

Joe
http://joe.fawcett.name


[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