Team titan will be implementing this, and the "values" array was one of the discussion points at the conference that didn't come to an immediate resolution. We will try to put together a reasonable approach that balances the goals of the "values" attributes as well as the goals of "jsonic" json using some approaches discussed at the conference.
Gabe On Tuesday, May 3, 2011 7:29pm, "Eldar Nugaev" <enug...@griddynamics.com> said: > 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
