Requirement 15 `collections` query parameter clarifications

[jerstlouis]

Because the list of collections included may be included in the the tileset metadata (as layers) at /tiles/{tileMatrixSetId}, the collections query parameter would be useful for the tileset so that this list of layers could be returned accordingly.

Requirement 15 is also not clear as to which resource the collections query parameter applies. In the OpenAPI definition currently collections is only defined for the individual tiles.

Requirement 15 A also has grammar issues:

A operation that acts on at the dataset level SHALL

should be

An operation that acts at the dataset level SHALL

[joanma747]

The grammar issue has been fixed.

The other issues with the so called Requirement 15 (https://github.com/opengeospatial/ogcapi-tiles/blob/master/core/standard/requirements/collections-selection/REQ_query-collections.adoc) should be discussed as I'm personally fine with the requirement.

[jerstlouis]

@joanma747 There are 2 aspects to Req 15 that I wanted to clarify:

1. It mentions the "geospatial data resource" which I imagine refers to either an OGC API data set, a collection, or something else undefined. However, for the resource paths that Tiles defines (TileSets list, TileSet, and individual tiles), it does not say for which of these collection= is valid. I assume the original intent was only for individual tiles.
2. The second point I was making is that it would also make sense to accept collections= for the TileSet (metadata) resource, so as to only include those selected collections in the layers descrived within the response.

[joanma747]

Affects: {datasetAPI}/tiles/{tmsId}/{matrix}/{row}/{col} {datasetAPI}/tiles/{TileMatrixSetId}

[joanma747]

Done and agreed in OGC tiles SGW telco today