RESTful URL design for search

I'm looking for a reasonable way to represent searches as a RESTful URLs. The setup: I have two models, Cars and Garages, where Cars can be in Garages. So my urls look like: /car/xxxx xxx == car id returns car with given id /garage/yyy yyy = garage id returns garage with given id A Car can exist on its own (hence the /car), or it can exist in a garage. What's the right way to represent, say, all t

[kiyo_hiko]

"This is perfectly RESTful: /cars?color=blue&type=sedan&doors = 4"