mirror of
https://github.com/marmelab/awesome-rest.git
synced 2026-01-24 04:08:05 -08:00
Replace a dead link with the last archived version
Also remove a link to a nonexistent section
This commit is contained in:
@@ -42,7 +42,7 @@ the Design of Network-based Software Architectures](https://www.ics.uci.edu/~fie
|
||||
* [How to design a REST API?](http://blog.octo.com/en/design-a-rest-api/) - Full guide tackling security, pagination, filtering, versioning, partial answers, CORS, etc.
|
||||
* [Richardson Maturity Model](http://martinfowler.com/articles/richardsonMaturityModel.html) - Explained by Martin Fowler, originally presented by Leonard Richardson at the [QCon 2008](https://www.crummy.com/writing/speaking/2008-QCon/act3.html).
|
||||
* [Enterprise Integration Using REST](http://martinfowler.com/articles/enterpriseREST.html) - Discusses the constraints and flexibility that you have with nonpublic APIs, and lessons learned from doing large scale RESTful integration across multiple teams.
|
||||
* [HATEOAS](http://timelessrepo.com/haters-gonna-hateoas) - Clear explanation on what HATEOAS is, and why you should use it.
|
||||
* [HATEOAS](https://web.archive.org/web/20201111235328/timelessrepo.com/haters-gonna-hateoas) - Clear explanation on what HATEOAS is, and why you should use it.
|
||||
* [How to GET a cup of coffee](http://www.infoq.com/articles/webber-rest-workflow/)
|
||||
* [REST API Tutorial](http://www.restapitutorial.com/) - RestApiTutorial.com is dedicated to tracking REST API best practices and making resources available to enable quick reference and self education for the development crafts-person.
|
||||
* [API-Security-Checklist](https://github.com/shieldfy/API-Security-Checklist) - Best practices about REST API security
|
||||
@@ -63,7 +63,7 @@ the Design of Network-based Software Architectures](https://www.ics.uci.edu/~fie
|
||||
* [RAML](http://raml.org/) - Simple and succinct way to describe RESTful API.
|
||||
* [JSend](http://labs.omniti.com/labs/jsend) - Simple specification that lays down some rules for how JSON responses from web servers should be formatted.
|
||||
* [OData](http://www.odata.org/) - Open protocol to allow the creation and consumption of queryable and interoperable RESTful APIs. Quite complex.
|
||||
* [HAL](https://tools.ietf.org/html/draft-kelly-json-hal-06) - Simple format that gives a consistent and easy way to hyperlink between resources in your API (see: [HATEOAS](#hateoas)).
|
||||
* [HAL](https://tools.ietf.org/html/draft-kelly-json-hal-06) - Simple format that gives a consistent and easy way to hyperlink between resources in your API.
|
||||
* [JSON-LD](http://json-ld.org/) - Standard for describing Linked Data and hypermedia relations in JSON (W3C).
|
||||
* [Hydra](http://www.hydra-cg.com/) - Vocabulary for Hypermedia-Driven Web APIs (W3C).
|
||||
* [Schema.org](http://schema.org) - Collection of schemas describing common data models.
|
||||
|
||||
Reference in New Issue
Block a user