search

INSPIRE-MIF / gp-ogc-api-features

Good Practice document for INSPIRE download services based on OGC API - Features
13 stars 12 forks source link

How to deal with 406 Not Acceptable error reports? #7

Closed michellutz closed 4 years ago

michellutz commented 4 years ago

Would the approach discussed in https://github.com/opengeospatial/oapi_common/issues/75 be a good way of dealing with errors (incl. INSPIRE-specific ones)?

cportele commented 4 years ago

Since OGC API Feature Core does not require this or any other specific response content for 4xx/5xx codes, this should not become a requirement in INSPIRE, if it is the goal to support off-the-shelf software implementing the standard.

This could change, if there would be a standard extension that prescribes the content of such responses and that is widely implemented.

In general clients need to be prepared anyhow to receive responses that are not generated by the API, but by some other component in the network (e.g. 502, 503, 504).

jsaligoe commented 4 years ago

@cportele Agreed. Let's be pragmatic in our approach and enable commercial and open source software providers to implement OGC API Features core without concern that the initial implementations will fail INSPIRE requirements.