I like to fix the API specification for following functionalities in http://api.openstorage.org.
All of them have trailing / after {uuid} as {uuid}/.
Delete Volume
Inspect Volume
Change Volume state
Retrieve Volume *
In general most REST services /resource/ indicates set of resources.
Here in above methods, interest is particular volume described by uuid.
So trailing / is confusing, which should be removed.
I like to fix the API specification for following functionalities in http://api.openstorage.org. All of them have trailing / after {uuid} as {uuid}/.
In general most REST services/resource/ indicates set of resources.
Here in above methods, interest is particular volume described by uuid.
So trailing / is confusing, which should be removed.
There are few good examples describing why trailing slash confuses and should be avoided while describing a specific resource. (1) http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#restful (2) Applied Web Services section in https://en.wikipedia.org/wiki/Representational_state_transfer#Example (3) https://softwareengineering.stackexchange.com/questions/186959/trailing-slash-in-restful-api
Who are the author of the http://api.openstorage.org? As this is more of documentation bug, I like to contact the author(s).