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] Towards XML 2.0

On Thu, Dec 9, 2010 at 6:12 AM, David Carlisle <davidc@nag.co.uk> wrote:

> Clearly I'm missing something, because I can't see how  lone < and & messing
> up an XML document is really any different from mismatched { or [ messing up
> json?  I can see a qualitative difference between xml and html parsing,
> where html (especially html5 flavoured html) is designed to silently recover
> from more or less any arbitrary rubbish thrown at it, but json, like
> javascript (and xml) has stricter parsing rules doesn't it? and so
> consequently requires some more care in construction.

The difference is that XML contains text and JSON doesn't. (And I mean
text as writers mean it, not as programmers mean it.) Since no one
tries to write novels/blog posts/form letters/ poetry / etc. in JSON
they don't care about this there but do in XML.

Furthermore { and [ are less likely to appear in ordinary folks' text
than &, <, and >. Only programmers and occasionally mathematicians
regularly use { and [.  Many, many folks use & and not a few use < and
>.

-- 
Elliotte Rusty Harold
elharo@ibiblio.org


[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