search

opengeospatial / ogcapi-records

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

How to handle empty parameters? #281

Closed m-mohr closed 1 year ago

m-mohr commented 1 year ago

In req. 18 I find the following definition for the q parameter:

If an empty q operator is passed (i.e. q=), the server SHOULD ignore this operator as if it was not specified by the client.

Is this general behavior to be applied to the parameters? It is not explicitly mentioned for externalId and type, thus it is confusing whether the same behavior as for q should be applied. This seems also undefined for the parameters inherited from Features (datetime, bbox, limit).

So either mention it for all parameters (which implies changes to Features), or just add a general note that if a parameter is empty (and nothing else is specified explicitly for individual parameters) it should be ignored.

pvretano commented 1 year ago

@m-mohr I'll remove the premission and add a note as you describe.

m-mohr commented 1 year ago

@pvretano Thanks (and sorry for spamming you with issues recently. I don't expect answers or solutions anytime soon, just wanted to persist the findings so that they can be worked on later.)

pvretano commented 1 year ago

Oh please! Keep the spam coming @m-mohr! We need eyes on the specification to fix all it inconsitencies which we sometimes don't see because we are in the thick of it. Rather I should say, THANK YOU, for taking the time to review and comment! :)