Re: using JSON escapes for non-XML data,
this is what my personal idea of the 'Ideal XML JSON schema' does:
http://xml.calldei.com/JsonXML
Although its really just a statement ... but then what are specs but
statements ?
----------------------------------------
David A. Lee
http://www.xmlsh.org
-----Original Message-----
From: John Cowan [mailto:] On Behalf Of John Cowan
Sent: Tuesday, May 03, 2011 2:47 PM
To: David Lee
Cc: 'Richard Salz';
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 <>
"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
