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?

Original Message From: "John Snelson"
> Pete Cordell wrote:
>> Original Message From: "Michael Kay"
>>> Is there an accepted mapping of JSON to XML? And is there a SAX parser?
>> I'm sure I read an article somewhere that suggested XML attributes in
>> would be prefixed with @, and a text node would have a name that was
>> illegal
>> in XML, such as "$".  With that convention it's quite easy to have some
>> data and convert it to XML, e.g.:
>> "foo" : { "@id" : "???", "$" : "yyy" }
>> gives:
>> <foo id="???">yyy</foo>
> What happens when the map key contains a space, or is otherwise not a
> valid NCName?

I was working on the assumption that you'd adopt a naming convention that
would make the mapping to XML easy.  For example, the @ and especially the $
require such a convention.  You could even say that an "@xmlns" parameter's
value captured the single namespace of the message.

To me that doesn't seem too much to ask.  It's then a design decision
whether you make your JSON messages easily convertible to XML or not.

Personally I'd like to see such things considered.  However, at the moment I
think JSON is trying to get some distance between itself and XML, partly so
the XML community don't feel threatened by it, and partly so it doesn't end
up being considered as some form of compact XML notation.  Maybe after JSON
is firmly established some convergence can take place.  But now I'm 


Pete Cordell
Visit http://www.codalogic.com/lmx/ for XML C++ data binding

[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