Sorry, I meant an example of how the JSON looks with these cases. I am less concerned with the XML.
Ralph On May 13, 2014, at 10:23 PM, Gary Gregory <[email protected]> wrote: > Here is an example for the current XML: http://pastebin.com/cLbuwe4b > > Gary > > > On Tue, May 13, 2014 at 10:53 PM, Ralph Goers <[email protected]> wrote: > Can you post an example? > > Sent from my iPad > > On May 13, 2014, at 6:51 PM, Gary Gregory <[email protected]> wrote: > >> This messages is about the format of tag names, not the shape of the >> elements. >> >> Right now, I have XML elements names in CamelCase format and XML attributes >> in camelCase format. Pretty standard. >> >> For JSON, I have both types of names as camelCase, but it makes the code a >> little awkward to undertamd and maintain. >> >> So what I think I'm going to do is use the CamelCase for objects and >> camelCase for primitives. >> >> This will give both the code and documents the same feel and it will make it >> easier to understand (IMO). >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> JUnit in Action, Second Edition >> Spring Batch in Action >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
