REST Service Resource
In any REST service it is good to have all the resources structured by their hierarchy. The resources are then specified in the hierarchical part of the URL. The hierarchical parts are required and unique.
This means that none of them can be omitted and all of them can appear only once. Certain parts of the URL are going to be fixed (such as the server name, port, and endpoint), and certain parts are going to be parameter-based. The parameter-based parts are often denoted in code and in documentation by curly braces.
For example, a web service for a record. Your data might be organized into repository, which contain records, which in turn contain Attributes and Relationships. The resource URL is as follows: http://server:9393/eml/rest/records/{repositoryName}/{id}. Sending a DELETE request to this URL might remove a record from existing repository, while sending a GET request to this URL might retrieve the details of a particular record id.