Clemens Portele
Clemens Portele
This is feedback from developing a client. The spec currently states: > The feature schema can and often will depend in the operation, so a Schema resource will publish the...
After implementing support for 'Optimistic Locking' we see the need for more guidance or additional requirements regarding ETags for feature resources. In general, a weak ETag seems to be more...
Closes #734 Addresses two of three items in #733
Discussed during the 2021-11 Sprint: * Use a query parameter `scale-denominator` with a numeric value as a hint for the server that the data in the response is intended to...
Raised by @IvanSanchez in the July 2022 Code Sprint while developing a client for Part 4: The feature URIs are unambiguously specified in Part 1, but it would be good...
The HTTP IETFs that we currently reference are now obsolete. We should update our editor drafts to reference the new ones, mainly: * HTTP Semantics: https://www.rfc-editor.org/rfc/rfc9110.html * HTTP 1.1: https://www.rfc-editor.org/rfc/rfc9112.html...
See, for example, https://sookocheff.com/post/api/optimistic-locking-in-a-rest-api/. This should be quite useful for some scenarios. Of course, it should be a separate conformance class.
Meeting 2022-05-23: This topic is not specific to geospatial, so the current thinking is that we should not add much in the OGC API standards, but we should provide links...
Meeting 2021-11-08: * It is two years (part 1) or one year (part 2) since the publication of v1.0.0 and both of the standards have seen some changes to clarify...
This is revisiting #329. The topic came up again during the May 2021 sprint in the context of styles. See https://github.com/opengeospatial/ogcapi-code-sprint-2021-05/issues/36. At least for the general requirements class, a mechanism...