[aidos]

It's interesting to see how differently these are all implemented. I guess it depends on what's at the other side of the api and how much work the developer wants to put in to data conversion.

When you flick through the first few examples you see that the result from querying a lib could be a nested dict, a bunch of objects or an lxml.etree. Every time you approach a new api, even with the help of a library so you don't have to deal with the transport, you still need to learn a unique set of data structures.

[smailq]

At Cosmic(http://www.cosmic-api.com/), we are working toward making web APIs more consistent and easier to build/consume with higher level framework. We take care of transport work, as well as data structure work. The data structure work(https://github.com/cosmic-api/teleport.py) is similar to Thrift, Protobuf, Avro, etc but with more emphasis on 'information on web' rather than dealing with raw bytes.

Cosmic is trying to achieve similar goal as Docker, as we are trying to build a framework/tools/services which solves APIs X languages matrix(Slide 14 of http://www.slideshare.net/dotCloud/why-docker).

FYI, the project is still in very early design stage, any feedback is very appreciated.