Open Stack

The JSONSchema library used in the proposed review supports everything 
you see on json-schema.org..

We use it in Moniker (Designate now...) and I personally *love it*. As 
you allude to, we get client side validation for free. I've been looking 
at Pecan+WSME recently and, ignoring "magic" multi-format/protocol 
support, am really not that impressed.

I do see the value in picking a framework and sticking with it - Pecan 
seems like a good fit.. I've just not been won over by WSME.

Thanks,
Kiall

On 13/06/13 22:04, Christopher Armstrong wrote:
> There's been discussion of specifying the input and output JSON schemas
> for APIs, but is this limited to using core JSON-Schema, or has anyone
> considered using JSON Hyper-Schema to specify the API more holistically?
>
> http://json-schema.org/
>
>
> The HyperSchema specification is here:
>
> http://json-schema.org/latest/json-schema-hypermedia.html
>
>  From what I understand, there is a v4 draft of both JSON-Schema and
> JSON Hyper-Schema in progress, and it changes things significantly,
> which is unfortunate. Still, it seems like whole-API specification would
> be a real boon for client libraries and API docs.
>
> --
> IRC: radix
> Christopher Armstrong
> Rackspace