But there are 2 disadvantages for this approach:
- I do not know of any good support for editing that format in terms of context help or even type checking.
- Create an XSD for your data (write it by hand or get it generated from an exiting XML)
- Use Jsonix to create a so called mappingfile from the XSD
- Use the XSD in e.g. visual studio to generate an XML file, which contains data which is valid against the XSD
I prepared a littel stand-alone example of this szenario. You can find it here. Basically, the clsimplexsd.xsd was created. The provided batchjob createjsfilesfromxsd.bat was used to generate the mappings. The clsimple.xml file holds data generated with the help of visual studio and the XSD. The Jsonixexample.html file then demonstrates the usage of the generated mappingfile and the xml file to read the data. On the Jsonix pages, there is a lot of documentation on this.
Of course, in our CRM development, all the files including the XML are hosted as webresources.
PS: yes, XSD is cumbersome, but there is help on this.