My 2c on this one: * I worry that allowing users to extend the core on the wire protocol by having something as extensible as XML, will lead them to do so in ways that break interop * I want something where it is really totally bogglingly obvious when the data deviates from the allowed format I note that eg HTTP has a very narrow core for interop, but people have come up with lots of ways to extend its usefulness by convention eg AtomPub On Wed, May 13, 2009 at 3:42 PM, Richard Davies <richard.davies@elastichosts.com> wrote:
Decision 4: For the core wire format(s), is XML or JSON the better syntax ('angle brackets vs. curly brackets') a) XML b) JSON
Important*: This is an independent decision from decision 3 on meta-model
Perspective of myself and Alexis: No strong view. We lean towards JSON, since it feels easier to make a tight specification and hence to easier to guarantee interoperability. Tightly specified use of XML might be equally good. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg