Fixes #118 and #115

core/standard/clause_6_overview.adoc

@@ -5,7 +5,7 @@
 
 The _OGC API - Tiles_ standard defines building blocks which can be used in a Web API to retrieve geospatial data as tiles that follow the structure defined in _2D Tile Matrix Set and Tileset Metadata_ standard (see <<rc_tiles_core>>).
 
-Services and clients are encouraged to support as many of the TileMatrixSets defined in the OGC TileMatrixSet registry as possible to maximize
+Services and clients are encouraged to support as many of the TileMatrixSets defined in the OGC TileMatrixSet registry as possible for all geospatial data resources to maximize
 interoperability, but support is not required for any specific tile matrix set.
 
 This document does not specify any requirement for the type of _geospatial data resource_ that could be delivered as tiles.
@@ -17,7 +17,7 @@ NOTE: The geospatial data resources (e.g., collections) replace the concept of l
 These geospatial data resources can advertise one or more lists of available tilesets (see <<rc_tileSet>> and <<rc_tileSets-list>>).
 This standard also defines how to link to tilesets originating from two specific data resources:
 OGC API datasets (see <<rc_datasetTileSets>>) and collections (see <<rc_geoDataResourceTileSets>>), but other OGC APIs can provide other possibilities.
-Accessing the _geospatial data resource_ content (other than as tiles) or its descriptions is possible out of the scope of this standard.
+Accessing the _geospatial data resource_ content (other than as tiles) or its descriptions is possible but out of the scope of this standard.
 If a description of the _geospatial data resource_ is specified by another standard, and this description has a mechanism to add links to other resources, this standard indicates the need to add a link to the list of available tilesets.
 
 The _OGC API Tiles API_ standard does not specify how to get a Web API definition, the conformance class list or the collections lists.

core/standard/requirements/core/REQ_tc-success.adoc

@@ -4,4 +4,6 @@
 ^|*Requirement {counter:req-id}* |*/req/core/tc-success*
 ^|A |A successful execution of the tile operation with content SHALL be reported as a response with a HTTP status code `200`.
 ^|B |The content of that response SHALL be consistent with the format requested via HTTP content negotiation and represent elements inside or intersecting with the spatial extent of the geographical area of the tile identified by the tile matrix, tile row and tile column of the tileset's tile matrix set.
+^|C |For image tiles, where this behavior is not explicitly overridden by an extension (e.g., a query parameter, or format-specific requirements), the width and height of the image (measured in raster pixels) SHALL be equal to the tileWidth and tileHeight of the corresponding tile matrix.
+^|D |For gridded coverage tiles, where this behavior is not explicitly overridden by an extension (e.g., a query parameter, or format-specific requirements), for coverages whose cells span the whole area of the resolution, the width and height of the coverage tile (measured in cells) SHALL be the tileWidth and tileHeight of the corresponding tile matrix; and for coverages whose cells are measurements or observations for a conceptually infinitely small point the width and height of the coverage tile SHALL be tileWidth + 1 and tileHeight + 1.
 |===