Not requiring this means that if the tilesets- links are missing, an implementation may need to make one request for every collections to figure out whether it supports tilesets or not, which significantly slows down access to OGC API - Tiles implementations with a few collections.
We noted that ldproxy (https://demo.ldproxy.net/vineyards/collections?f=json) did not include the tilesets-* links at the /collections level (although it does includes items links there) and this was preventing the GNOSIS client from accessing the API as Tiles, potentially also a reason for issues accessing it from GDAL.
It is not clear from Requirement 13 whether the
tilesets-*links are required to be present in the collection lists in/collections.Not requiring this means that if the
tilesets-links are missing, an implementation may need to make one request for every collections to figure out whether it supports tilesets or not, which significantly slows down access to OGC API - Tiles implementations with a few collections.We noted that ldproxy (https://demo.ldproxy.net/vineyards/collections?f=json) did not include the
tilesets-*links at the/collectionslevel (although it does includesitemslinks there) and this was preventing the GNOSIS client from accessing the API as Tiles, potentially also a reason for issues accessing it from GDAL.@joanma747 @cportele @ghobona