Building REST web services with nested collections + collections inside entries

I would like to build a REST webservice that would provide :

1. nested collections,
2. collections inside entries.

Nesting collections would be used to refine a concept from general to particular, for example :

/vehicles/road_vehicles/cars/AB-123-CD

The idea is to limit the number of concepts appearing at the root of the webservice.

Collections inside entries would be used to access parts of the entries, for example :

/cars/AB-123-CD/engine/spark_plugs/1

could be a good URI for the first spark plug of the car whose id is "AB-123-CD". A nested collection makes sense whenever the deletion of the "container" means the deletion of all its parts.

DELETE /cars/AB-123-CD

would obviously delete :

/cars/AB-123-CD/engine/spark_plugs/1

and all other parts of the car (think of the car as being sent to scrap by the DELETE).

Question : while this kind of "clean URIs" are quite a common need, are there any software to simplify the building of such a webservice?

It seems that the Atom Publication Protocol (AtomPub) could have been a good candidate, since their vision of webservices if very close to what I want, but it doesn't seem to support nested collections.