Comments (7)
By now this is no longer requirement 38. I think this refers to requirement /req/oas30/exceptions-codes
(https://rawgit.com/opengeospatial/WFS_FES/master/docs/17-069.html#exceptions).
I understand the comment and it would be good to have a good understanding what the general practice and expectations are in the OpenAPI community.
PS: To exclude errors raised in the transport between the server and the client by using the wording "error situations that originate from the server".
from ogcapi-features.
Such a listing of status codes should not be normative because they are specified in the HTTP specification(s). See https://tools.ietf.org/html/rfc7231#section-6
from ogcapi-features.
06-MAY-2019 Conference calls: Make it a recommendation. We ended up with: "The API definition SHOULD cover the HTTP error codes for each operation for error situations that originate from the API implementation. Note that error codes originating from the protocol level will not be included in the API definition, but still need to be handled by clients. This is implicit in the requirement for HTTP compliance." Chuck will make a proposal.
from ogcapi-features.
This seems to imply that "API implementation" != "protocol level"
I doubt that such a difference exists or should exist. But I will wait for the proposal.
from ogcapi-features.
@akuckartz - Yes, the notes were a bit brief. "Protocol level" here refers to anything between the API implementation and the client. For example a 504 created by a proxy. If the API implementation will never return a 504 for an operation this status code does not belong into the API definition of that operation, but clients still have to be prepared to receive a 504 (or any other undocumented status code). However, if the API implementation may return a 500, this should be documented in the API definition.
from ogcapi-features.
Please review and comment on pull request #223
from ogcapi-features.
Pull request has been updated. Added a paragraph on how the status codes should be advertised in the API Description Document.
from ogcapi-features.
Related Issues (20)
- Question regarding "Draft proposal "Query by IDs"" HOT 7
- Queryables / Schemas: with $ref or dereferenced HOT 2
- CQL2: Logical operations on indeterminate values HOT 6
- Separation of templated and untemplated links ... HOT 1
- CQL2: Unicode standard version now 15
- CQL2: Additional guidance on CASEI / ACCENTI HOT 17
- Abstract Test 2 of Part 2: CRS By Reference
- CQL2: (AT) Table 9 wrongly expects københavn matching kobenhavn HOT 3
- Part 1 ATS / ETS: Missing antimeridian test? HOT 2
- CQL2: `{geometry queryable}` instead of `geom` in ATS?
- CQL2: Basic Spatial + Logic ATS useful extra tests
- cql2.bnf is it valid BNF? HOT 3
- JSON Schema: unknown keywords HOT 6
- CQL2: conformance class for S_INTERSECTS for geometry, between Basic SO and SO classes HOT 1
- Static API Specification of OGC API Features HOT 7
- Boolean value in scalarExpression HOT 5
- Add support for compound CRSs
- CRS identifier required for geometry less collections HOT 3
- Schemas: oneOf null/single/multi geometry ? HOT 4
- CQL2 (Spatial Functions): Short definitions of boundary/interior/exterior, S_RELATE HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ogcapi-features.