openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #02123
Re: Problem with "values" in JSON responses
I'm referring to the
http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.1/
documentation. There are examples of json responses with "values". I
suppose we should change documentation to the actual state or change
actual state to the documentation.
On Tue, May 3, 2011 at 4:58 PM, Jorge Williams
<jorge.williams@xxxxxxxxxxxxx> wrote:
>
> On May 3, 2011, at 6: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.
>
> What specification are you referring to?
>
>> 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?
>>
>
> We use "values" as a first attempt to add extensibility to collections in JSON. We had a lengthy discussion about this at the summit. To summarize: there's no really easy/clean way of doing this as JSON is not extensible. We're currently exploring other approaches, so values may go away in the long term. The 1.1 spec is not set in stone in this regard.
>
>
>> 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
>>
>
> Right, Anne -- can you look into this?
>
>
>> --
>> Eldar
>> Skype: eldar.nugaev
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>
>
>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of the
> individual or entity to which this message is addressed, and unless otherwise
> expressly indicated, is confidential and privileged information of Rackspace.
> Any dissemination, distribution or copying of the enclosed material is prohibited.
> If you receive this transmission in error, please notify us immediately by e-mail
> at abuse@xxxxxxxxxxxxx, and delete the original message.
> Your cooperation is appreciated.
>
>
--
Eldar
Skype: eldar.nugaev
References