search

opengeospatial / ogcapi-records

An open standard for the discovery of geospatial resources on the Web.
https://ogcapi.ogc.org/records
Other
59 stars 28 forks source link

Do we still have/need to concept of element set from CSW 2/3? #141

Closed pvretano closed 2 years ago

pvretano commented 3 years ago

Uwe asked whether the concept of "element set" from csw 2/3 has been considered. The short answer is no.

Adding the parameter itself would be fairly easy:

GET /collections/{catalogueId}/items?elementset=<some name>

The trickier part is discovering which properties are part of a specific element set. For that, we can probably leverage and extend/modify the feature schema mechanism being defined in Features Part 4. Right now Features defines a parameter called type with values create,replace,update to get the schema of various views of the feature. We could generalize type or reuse elementset to get the schema of a particular element set. For example GET /collections/{catalogueId}/schema?elementset=brief would return the schema of the brief element set. Which element sets are available would be something that could be discovered from the Open API document; the definition of the elementset parameter would include an enum of the possible values. There is also the possibility of using the OPTIONS method on the .../schema endpoint to discover that information too (see issue #92).

pvretano commented 2 years ago

20-NOV-2021: The consensus of the people on the call is that we don't need to have named subsets of presentables especially considering that features or common will be introducing projection capabilities so people can explicitly list which properties they want to see in the output. For sure this is not a core requirement and unless there is a more cogent case, we will close this issues for now. If anyone feels strongly that we need this capability, they can reopen the issue and provide more feedback.