3 ms·
This is similar in spirit to the Google APIs Discovery Service, an API to describe recent Google APIs. http://code.google.com/apis/discovery/v1/using.html http:
by ImJasonH 15y ago
This is similar in spirit to the Google APIs Discovery Service, an API to describe recent Google APIs. http://code.google.com/apis/discovery/v1/using.html http://code.google.com/apis/discovery/v1/using.html
This is used to power the APIs Explorer, and code/documentation generation for client libraries:
* APIs Explorer: https://code.google.com/apis/explorer https://code.google.com/apis/explorer
* JavaDoc for the generated Java library for Calendar API: http://javadoc.google-api-java-client.googlecode.com/hg/apis/calendar/v3/index.html http://javadoc.google-api-java-client.googlecode.com/hg/apis...
* PyDoc for the Python library: http://api-python-client-doc.appspot.com/calendar/v3 http://api-python-client-doc.appspot.com/calendar/v3
- fehguy 15y agoI think the biggest difference is that this is a framework, not just a spec, and you can implement the server with the libraries. The google explorer makes it easy to consume google apis, which is great if that's what you're trying to do. If you want others to consume your api, you need a framework to facilitate the schema generation.