On Wed, Jan 9, 2013 at 7:39 PM, Alex Heneveld <alex.henev...@cloudsoftcorp.com> wrote: > Wow JSON seems popular so far. And yet YAML is more concise and expressive. > Designed to be easy for people to read and write configuration just like > this. Whereas JSON is designed for serializing objects, in a way that isn't > too hard for people. YAML seems the right language for this purpose to me > -- and my experience has been that it is easier to read and to write, > without the litter of curly braces and quotes. > > But I don't want to be a language bigot! I can go with JSON if that's what > people want. :)
I'd lean toward JSON as the native serialization format for the objects coming into and out of the API. My reasoning for this is: (1) CloudStack using JSON today, so this would be consistent with the rest of the API functions, and (2) JSON is generally easier to work with in a UI layer, which is one of the primary use cases for the API itself.
