Ambiguity of paths

Since the {collection} resource is optional now there might be an issue with ambigous route paths. Especially when there are collections in collections. While implementing a general bundle for the TextAPI I thought it might lead to some confusion where you might not know if that resource is a manifest or a collection.

So I thought of having something like /collection/{id}/collection/{id}/manifest/{id}/manifest.json (by looking at these GDZ routes for IIIF).

EDIT: Ok, maybe its not necessary. The implemententors would know their structure and this might lead to a more bloated URL.