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 vs JSON

> 
> A document-oriented XML document looks more like an HTML page with mixed content, XHTML and docbook being two prominent examples:
> 
> <paragraph>This is <bold>bold</bold> text and this is <italic>italic</italic> text</paragraph>
> 


I like to say that the defining characteristic of pure document-oriented XML (I sometimes call it "narrative XML") is that if you remove the markup, you are left with meaningful human-readable text.

And I always felt that the reason XML became so popular was not its ability to handle pure narrative XML, but its ability to mix structured data and textual narrative in a single message. So often (consider a CV/resume) you want to handle both at the same time. XML thus brought document processing capability to the data processing masses; and by reverting to JSON, the data processing masses are saying "that's too difficult for us to cope with".

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