”type”: “FeatureCollection”be at the root?
properties.@typewithin each record? I think this is now
TMP. From an OGC API - Records perspective, is this agnostic to the actual backend search machinery, and we simply return respective themes/concepts accordingly in the records?
In opengeospatial/ogcapi-records#16 I made this comment, which still is relevant I think:
In opengeospatial/ogcapi-common#116 and opengeospatial/ogcapi-common#8 @cportele suggests to use content negotiation by iana types, this can work when using types such as application/iso19115-3+xml, application/vnd.dcat.rdf+xml, application/vnd.dcat.ld.json, but it is less flexible then prof-conneg