On 06/20/2013 01:22 PM, Brant Knudson wrote:
How about a mapping of JSON concepts to XML like:
collections:
<object> <pair name="pair-name"> the-value </pair> ... </object>
<array> <element> the-value </element> ... </array>
values:
<string>text</string>
<true/>
<false/>
<null/>
<number>number</number>
This type of mapping would remove any ambiguities. Ambiguities and
complexity are problems I've seen with the XML-JSON mapping in
Keystone. Plus the fact that it's so not-XML would convince users to
switch to JSON. With a simple mapping, I don't think it would be
necessary to test all the interfaces for both XML and JSON, just test
the mapping code.
+1, if it can be fully realized. This might also allow projects with no
xml support to have it. It is really odd that some OpenStack integrated
projects support xml and others do not. The cost of maintaining both
"natively" is just two high. I think Amazon and Google just pick one
(different ones :-) ).
-David
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
