Peter Van den Bosch
Peter Van den Bosch
feedback of REST WG: 204 could be considered in this particular case (there are arguments for and against it), but the REST guide won't be updated. Sufficient that it covers...
I'll work on a PR
I'll work on a PR. In OpenAPI 3, suggest to create specific type for merge patches with "nullable": true entries. We could deprecate the OpenAPI 3 MergePatch schema. Both openapi...
changes were implemented; published in REST guide; and in openapi-common main branch for next release
Do you have any examples of warnings on output fields? Anomalies in the current state of a resource could also be represented in a specific data structure (e.g. "duplicateRegistration": true)...
"status" wouldn't be used for warnings Could WG members add their own use cases to have warnings to this issue?
to discuss: * how to represent a warning: http header and/or json problem-like representation. Only toplevel warnings or multiple warning blocks... * what's the (functional) definition of a warning (purpose,...
We should probably change to http code 412 for optimistic locking scenarios; there's still open issue #37 for that. For the others, we'll need to evaluate if single level of...
409 Conflict may also be used for PUT operation when a resource can't be updated bc of business rules; similar to the above DELETE scenario. Do we need a generic...
I've opened new issue #217 replacing this one, and also including cases like replacedSsin, mergedEnterprise, etcetera. It doesn't include optimistic locking, which is covered by #37.