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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130613/15a9176d/attachment.html>