Add alternative annotation API path ?

Asked on matrix.

The annotation api are for the moment /api/collections/{collectionId}/items/{itemId}/annotations (and /api/collections/{collectionId}/items/{itemId}/annotations/{annotationId} if you want to change an annotation) (doc).

it's done to be coherent with stac routes (changing semantic on a picture is done with /api/collections/{collectionId}/items/{itemId}, but it's true that only 1 id is usefull here (either the {itemId} or the {annotationId}.

Should we also have alternative routes for those (like /api/pictures/{id} or /api/annotations/{id}) to ease clients integration (no need for 2 round trips fetching the other ids)? Or maybe we could do hacks like supporting either special characters for useless ID, or even not check them at all and document it?

What are you thoughts on this @PanierAvide ?

I'd say alternative routes are fine for me and should not be difficult to do