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] JSONx sent to the IETF

Re: using JSON escapes for non-XML data,
this is what my personal idea of the 'Ideal XML JSON schema' does:


Although its really just a statement ... but then what are specs but
statements ?

David A. Lee

-----Original Message-----
From: John Cowan [mailto:cowan@ccil.org] On Behalf Of John Cowan
Sent: Tuesday, May 03, 2011 2:47 PM
To: David Lee
Cc: 'Richard Salz'; xml-dev@lists.xml.org
Subject: Re: [xml-dev] JSONx sent to the IETF

David Lee scripsit:

> XMLj is the obvious choice for a name.

I like RAJDAX (Representation of All JSON Documents As XML), as distinct
from RAXDAJ, which would be JsonML.

> plus it doesn't handle non XML character data well (say NUL's) ...

I think that's the major deficiency.  Some additional machinery is
needed to be able to escape C0 control characters (other than newlines
in string values, which can be left raw) and unpaired surrogates
represented by JSON escapes.  The obvious choice is to use JSON escapes
in the XML, at least \unnnn and \\.

John Cowan    http://www.ccil.org/~cowan   <cowan@ccil.org>
    "Any legal document draws most of its meaning from context.  A telegram
    that says 'SELL HUNDRED THOUSAND SHARES IBM SHORT' (only 190 bits in
    5-bit Baudot code plus appropriate headers) is as good a legal document
    as any, even sans digital signature." --me

[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