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] Best options for converting JSON to XML

* David Lee wrote:
>Thus the robust and simple way to solve this is to use an XML structure like (or some variation of)
>
>{ "a json name" : 1 }                ->
>
><object>
>    <member name="a json name">< value type="Number">123</value></<member>
></object>
>
>This is very reliable but by its very nature is *always going to be schema valid* !!!
>( atleast with XSD or RNG ... schematron might be able to do something with this)

http://lists.w3.org/Archives/Public/www-validator/2005Aug/0129.html does
something like this for CSS style sheets with a RELAX NG schema that can
be used to validate style sheets through this indirect representation.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


[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