Jerome St-Louis

@pvretano In that case, I would strongly suggest that: - The syntax in cql2-text be `ARRAY(1, 2, 3)` to be consistent with everything else such as WKT geometry, time intervals,...

The `(1,2,3)` syntax is nice because it could be consistent with WKT and the `in` syntax. However, I am not sure how we could distinguish a sub-expression`(123)` from an array...

On the last point, leaving aside disagreement on _MultiPolygon X MultiPolygon_ vs. _MultiPolygon X BBOX_ complexity, the number of cases on which to support intersection testing (as well as support...

See also Section 6.4 in _Tiles_: http://docs.ogc.org/DRAFTS/20-057.html#_how_to_approach_an_ogc_api

_(short story: I agree with Peter that `CASEI()` and `ACCENTI()` are not constructors, but standardized text manipulation functions)_ @pvretano @cportele You may be interested in the conceptual work that we...

We are also suggesting the use of PROJJSON in [Coverages as well](https://github.com/opengeospatial/coverage-implementation-schema/issues/7#issuecomment-802171587), and I hope the CRS SWG could standardize the PROJJSON encoding as an OGC standard for use in...

This was previously requested in Testbed 13 for WFS: http://ogc.standardstracker.org/show_request.cgi?id=514 And it is in our opinion a very important capability for any kind of large features intended to be visualized...

@PeterParslow For that use case, in Tiles we have suggested the uses of the Styles API, where style sheets can express filtering rules by attributes. The same could be done...

@cportele I saw your comment about `skipGeometry` in ldproxy on Gitter. Could `omitGeometry` be specified instead? I think it makes sense to include this in the extension specifying `properties` as...

@cportele Cool. speaking of naming, I think I've mentioned before that I really dislike the choice of the `projection` word for this functionality :) In addition to an obvious confusion...