Content deleted Content added
TvojaStara (talk | contribs) |
TvojaStara (talk | contribs) Hypertext-driven APIs; Frameworks |
||
Line 6:
There are two previous major description languages, [[Web Services Description Language|WSDL2.0]] (Web Services Description Language) and [[Web Application Description Language|WADL]] (Web Application Description Language). Neither is widely adopted in the industry for describing RESTful APIs, citing poor human readability of both and WADL being actually unable to fully describe a RESTful API.<ref name="slideshare.net">http://www.slideshare.net/SOA_Software/api-description-languages</ref>
== Alternatives ==
===Hypertext-driven APIs===
An alternative approach to building RESTful APIs is known under the acronym HATEOAS ([[Hypermedia as the Engine of Application State]]). It this approach, the client software is not written to a static interface description shared through documentation. Instead, the client is given a set of entry points and the API is being discovered dynamically through interaction with these endpoints. HATEOAS was introduced in [[Roy Fielding]]'s doctoral thesis <i>Architectural Styles and the Design of Network-based Software Architectures</i>. HATEOAS has been the original vision for RESTful APIs which distinguished them from [[Remote Procedure Call|RPC]] mechanisms.<ref>{{cite web|last1=Fielding|first1=Roy|title=REST APIs must be hypertext-driven|url=http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven|accessdate=4 November 2015}}</ref>
==List of RESTful API DLs==
Line 109 ⟶ 113:
|
|}
== Frameworks ==
Many server frameworks interoperate with one or more IDLs.
*Gugamarket REST API framework
**IDLs: Swagger
**URL: https://pliik.github.io/gugamarket/
**developer: https://github.com/pliik
==References==
| |||