The standard is to use / for hierarchal data and URL params to alter the resource's content. For instance: /search/ would be an empty search, and for the sake

The standard is to use / for hierarchal data and URL params to alter the resource's content. For instance: /search/ would be an empty search, and for the sake of argument let us say that it returns the entire collection. /search/?query=bass This would restrict the collection to return only records that contain the word "bass". Based on the way that URLs are defined, these are considered separate resources. The same with this URL: /search/?query=bass&page=10 This is a different resource than the previous. In this case, sometimes it feels like the page should be a member of the search collection. It's up to you whether you prefer a URL like this /search/pages/10?query=bass In my head that is incorrect because to me the query string manipulates the last item in the hierarchy which is "pages/10". So the order of operations would look like this: 1. Select the first page from the search collection 2. return only items on the first page that contain the word "bass"