Relevance of resource ordering


#1

As far as I know it is possible to create multiple resources that match an incoming request. It is not stated in the spec which resource is going to get invoked. Here is an example:

/items/someAction:

/items/{id}:

For the incoming request /items/someAction the behavior is not defined (assuming all other attributes are the same and besides the fact that the above example really isn’t good API design).

I would suggest to include the relevance of resource ordering into the spec.


#2

OK, we’ll get back to you.