We discussed the "values" debacle at the design summit last week. The existence of values is due to the ability of lists in xml to have attributes and to allow for extensibility. The solution is ugly and we're looking at a way to fix it. The Rackspace Titan team (https://launchpad.net/~rackspace-titan) is coming up with a proposal for standardizing the json and making conversion to and from XML easier.
Vish On May 3, 2011, at 4:29 PM, Eldar Nugaev wrote: > Hi gents. > > At this moment we have problem in OS API 1.1. Any JSON response with > "values" doesn't meet specification. > Could you please provide information - why we want to see "values" > field in JSON and who is responsable for implementation this > specification in OS API 1.1? > > Also we have broken documentation on openstack.org OS API 1.0 > http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.0/content/index.html > > -- > Eldar > Skype: eldar.nugaev > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
