tileset versus multitiles

[pomakis]

We've been discussing having a tileset as an addressable resource (rel=ogc:tiles:tileset), with the following URL pattern:

  collections/{collectionId}[/map/{styleId}]/tiles/{tileMatrixSetId}

However the current draft of the "OGC API Maps Tiles" specification, section 11, has this endpoint being a "multiple tiles from one collection" endpoint (rel=multitiles).

https://htmlpreview.github.io/?https://github.com/opengeospatial/OGC-API-Maps/blob/master/19-zzz.html#_requirement_class_tiles_multitiles

While it may be possible to overload this endpoint to do both, it's probably not a good idea. We should probably move multitiles to its own endpoint, perhaps:

  collections/{collectionId}[/map/{styleId}\/tiles/{tileMatrixSetId}/multitiles

(although there's probably a better term than "multitiles"...)