OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
The term _schema_ pops up first in the format section of the specification. Since it is such a central term, I feel it should be explained in the definition section.
JSON-LD
Are there any plans or experiments to integrate somehow OpenAPI and JSON-LD?
_**NOTE:** This is a draft because I was going to make it a proposal, but its **much** shorter to just show the PR than explain it some other way. See...
Currently, to build the HTML versions of the spec, you need to simulate `.github/workflows/respec.yam` by doing (in the root of a checked-out `main` branch of the repository): 1. make sure...
I have not been able to find any documentation that describes with sufficient detail how the `Content-Type` header of a request is matched against the entries of the `Request Body...
Splitting out from #3509 so I can close that massive issue, in a recent(ish) TDC call, we agreed to the following (leaving out points that I already did the day...
Splitting off from #3509, I've been using the milestones as follows: * Issues go in the oldest open milestone to which they are relevant, _if_ it seems likely that they...
OAS 3.0 and 3.1 schemas require the Response Object `description` property but allow it to be empty
The JSON Schema - https://spec.openapis.org/oas/3.0/schema/2021-09-28#/definitions/Response/required for the OpenAPI specification marks `description` as a required property but then allows it to be an empty string. This is causing some strange use...
We've had some understandable confusion on when PRs get merged, as we came up with some exceptions to the "2 TSC approvals" rule in TDC calls. But not everyone is...
## This PR - preliminary review to comply with HTTP specifications RFC9110 ## Notes - payload / body -> content
