Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • But conceptually the same entity is at two different URIs now both in /api/foos/?page=1 and /api/foo/1 , but I see what you are saying and it makes sense if we see it like that. Commented Feb 6, 2015 at 20:19
  • 1
    But you can look at it as two different (not independent) resources - you just need to twist your nomenclature slightly so "resource" is not the same thing as "entity." Commented Feb 7, 2015 at 10:42
  • @EsbenSkovPedersen, no: /api/foos/?page=1 is the first page of the container, it should be a list of elements. /api/foos/1 is one element and still the 'real' URL of the resource. Commented Feb 7, 2015 at 15:42
  • There is no issue with a resource being at two URIs. For example you can have myweatherapp.com/today and myweatherapp.com/2015/feb/09 point to the same resource. A URI should only point to one resource, but a resource can have multiple URIs pointing to it. Commented Feb 9, 2015 at 15:47