The Web Application Description Language (WADL) is basically the equivalent to WSDL for RESTful services but there’s been an ongoing controversy whether something like this is needed at all.
Joe Gregorio has written a nice article about that topic which is worth a read.
More Related Contents:
- 400 BAD request HTTP error code meaning?
- SOAP vs REST (differences)
- How to design RESTful search/filtering? [closed]
- What are best practices for REST nested resources?
- How can I handle many-to-many relationships in a RESTful API?
- How to version REST URIs
- How to create REST URLs without verbs?
- XDebug and RESTful server using PHPStorm or POSTman
- REST Complex/Composite/Nested Resources [closed]
- What is the advantage of using REST instead of non-REST HTTP?
- What is REST? Slightly confused [closed]
- powershell invoke-restmethod multipart/form-data
- Transactions across REST microservices?
- Designing URI for current logged in user in REST applications
- How to send a message successfully using the new Gmail REST API?
- Rest Standard: Path parameters or Request parameters
- Making a PowerShell POST request if a body param starts with ‘@’
- How to use object filter with softlayer rest api?
- Does Karate DSL Framework have the capability to pass a POST Request as a url encoded format?
- Difference between Swagger & HATEOAS
- Is That REST API Really RPC? Roy Fielding Seems to Think So
- Flutter fetched Japanese character from server decoded wrong
- REST web service WSDL? [duplicate]
- HTTP PATCH support in browsers
- VSTS use API to set build parameters at queue time
- Can I change the headers of the HTTP request sent by the browser?
- When in my REST API should I use an envelope? If I use it in one place, should I always use it?
- Swagger UI passing authentication token to API call in header
- Hyphen, underscore, or camelCase as word delimiter in URIs?
- REST API DESIGN – Getting a resource through REST with different parameters but same url pattern