Should EADS include a small section about resource naming anti-patterns? Sometimes it's informative to see bad examples of anti-patterns in the "wild". Maybe include examples of poor RESTful URIs and what NOT to do.
Possible Examples
Using query-string parameters to specify the requested operation and/or HTTP verb.
GET http://api.example.com/services?op=update_artist&id=12345&format=json
Using a route name for a specific operation.
GET http://api.example.com/update_artist/12345GET http://api.example.com/artists/12345/update
Redundancy (both HTTP verb and path).
PUT http://api.example.com/artists/12345/update
Should EADS include a small section about resource naming anti-patterns? Sometimes it's informative to see bad examples of anti-patterns in the "wild". Maybe include examples of poor RESTful URIs and what NOT to do.
Possible Examples
Using query-string parameters to specify the requested operation and/or HTTP verb.
GET http://api.example.com/services?op=update_artist&id=12345&format=json
Using a route name for a specific operation.
GET http://api.example.com/update_artist/12345
GET http://api.example.com/artists/12345/update
Redundancy (both HTTP verb and path).
PUT http://api.example.com/artists/12345/update