André Cedik

Also for RFC7807 Ruby: https://github.com/nikushi/problem_details

I'd say it depends on each individual case. I would think that the reasons for returning embedded-warning can be manifold. A system could e.g. return warnings due to circumstances in...

Hey @ioggstream if you have a look at https://github.com/dret/I-D/commit/245804bc9d2f7b54eadaf683d4d577f00cbf05e6 and give me feedback if it's easy to understand I'd appreciate it. Also, I'm still on the hunt for use cases...

I've added a few things to address your points: - added section for cache considerations (https://github.com/dret/I-D/commit/2af5ba15c1795cce5488d66ad888484f50477364) - added information about/for intermediaries (https://github.com/dret/I-D/commit/7fb08fac548a45d83d675d1024c5ec1819e03474) I'm still working on them, so for now...

- Added two sections explaining, which HTTP request methods are allowed in combination with the Content-Warning field and the embedded-warning (https://github.com/dret/I-D/commit/a419ba894bad4cd31ae0b16f01adb26fd71161cc)

What we're trying to achieve is to create a standard way of returning warning information to a client. So from my point of view there is only this use case....

Adding on the what @paraskakis [already wrote](https://github.com/OAI/Overlay-Specification/issues/31#issuecomment-1962741223): We are currently thinking about using overlays to help our internal tooling. This is necessary because we need to download the OAS from...