| 词条 | Overview of RESTful API Description Languages | ||||||||||||||||||||||||||||||||||||||||||||||||
| 释义 |
RESTful (representational state transfer) API (application programming interface) DLs (description languages) are formal languages designed to provide a structured description of a RESTful web API that is useful both to a human and for automated machine processing. API Description Languages are sometimes called interface description languages (IDLs). The structured description might be used to generate documentation for human programmers; such documentation may be easier to read than free-form documentation, since all documentation generated by the same tool follows the same formatting conventions. Additionally, the description language is usually precise enough to allow automated generation of various software artifacts, like libraries, to access the API from various programming languages, which takes the burden of manually creating them off the programmers. HistoryThere are two previous major description languages: WSDL2.0 (Web Services Description Language) and 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.[1] AlternativesHypertext-driven APIsAn alternative approach to building RESTful APIs is known under the acronym HATEOAS (Hypermedia as the Engine of Application State). In 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 discovered dynamically through interaction with these endpoints. HATEOAS was introduced in Roy Fielding's doctoral thesis Architectural Styles and the Design of Network-based Software Architectures. HATEOAS has been the original vision for RESTful APIs which distinguished them from RPC mechanisms.[2] List of RESTful API DLs
List of data description languagesA significant part of RESTful API description is the specification of returned data structures. The IDL might either specify its own format or use an existing data description format. A notable example which many RESTful API DLs use is JSON Schema.
Comparison of RESTful API DLsThe community around RESTful API DLs is active and the landscape is still changing. According to a presentation by Akana, the most active projects in this area are OpenAPI, RAML and API Blueprint.[1]
FrameworksMany server frameworks interoperate with one or more IDLs.
References1. ^1 http://www.slideshare.net/SOA_Software/api-description-languages 2. ^{{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}} 3. ^{{cite web|title=OASIS Open Data Protocol (OData) TC - OASIS|url=https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata}} 4. ^{{cite web|title=Barrister RPC - About|url=http://barrister.bitmechanic.com/about.html}} 5. ^{{Cite journal|last=Lira|first=Hermano Albuquerque|last2=Dantas|first2=Jose Renato Villela|last3=Muniz|first3=Bruno de Azevedo|last4=Nunes|first4=Tadeu Matos|last5=Farias|first5=Pedro Porfirio Muniz|date=2015-01-01|title=An Approach to Support Data Integrity for Web Services Using Semantic RESTful Interfaces|url=http://doi.acm.org/10.1145/2740908.2743042|journal=Proceedings of the 24th International Conference on World Wide Web|series=WWW '15 Companion|location=New York, NY, USA|publisher=ACM|pages=1485–1490|doi=10.1145/2740908.2743042|isbn=9781450334730}} 6. ^https://developers.google.com/discovery/v1/reference/apis 7. ^Licenses here are a summary, and are not taken to be complete statements of the licenses. Some packages may use libraries under different licenses. External links
2 : Cloud standards|Software architecture |
||||||||||||||||||||||||||||||||||||||||||||||||
| 随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。