• From: Bjoern Hoehrmann <derhoermi@g...>
• To: David Lee <dlee@c...>
• Date: Sun, 10 Nov 2013 18:16:48 +0100

* 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��H��ann · mailto:bjoern@h... · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dageb��· PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

• References:
  • Best options for converting JSON to XML
    • From: Ihe Onwuka <ihe.onwuka@g...>
  • RE: Best options for converting JSON to XML
    • From: David Lee <dlee@c...>
  • Re: Best options for converting JSON to XML
    • From: Ihe Onwuka <ihe.onwuka@g...>
  • Re: Best options for converting JSON to XML
    • From: "Timothy W. Cook" <tim@m...>
  • RE: Best options for converting JSON to XML
    • From: David Lee <dlee@c...>