1. Describing REST services Ivo Malve 23.03.2015

2. Using WSDL to describe REST APIs While WSDL is flexible in service binding options, it did not originally support HTTP operations other than GET and POST. Since REST services often use other HTTP verbs, such as PUT and DELETE, WSDL was a poor choice for documenting REST services. With version 2.0, WSDL supports all HTTP verbs and it is now considered to be an acceptable method of documenting REST services. LinkLink http://rest.elkstein.org/2008/02/documenting-rest- services-wsdl-and-wadl.html

3. The need for proper REST API documentation An increasing number of Web-based enterprises (Google, Yahoo, Amazon, Flickr to name but a few) are developing HTTP- based applications that provide programatic access to their internal data. http://www.w3.org/Submission/wadl/

4. Textual documentation …Typically these applications are described using textual documentation that is sometimes supplemented with more formal specifications such as XML schema for XML-based data formats. http://www.w3.org/Submission/wadl/

5. Examples of textual documentation Twitter APIs Flickr APIs Tesla Model S  Awesome example Awesome example http://rest.elkstein.org/2008/02/real-rest- examples.html

6. Web Application Description Language …WADL is designed to provide a machine process-able description of such HTTP-based Web applications. W3 WADL style http://www.w3.org/Submission/wadl/

7. Summary WSDL  Flexible (binding to SMTP servers)  Complex WADL  Lightweight (no envelope)  Easier to understand  Easier to write  Sufficient for any web service XRD http://stackoverflow.com/questions/2215646/difference- between-wsdl-2-0-wadl-xrd

8. Thank You! Questions?