OpenAPI-Specification
OpenAPI-Specification copied to clipboard
The OpenAPI Specification Repository
See PR #3584 from @AxelNennker for the background. We agreed in the TDC meeting 2024-02-22 to add info in security considerations and probably also on the learn site, and link...
- [x] add example for "raw JSON" as a message body - external feedback - [x] prevent line-break in monospaced table cell content (feedback from @handrews)
- [x] Github Workflow: markdownlint after mdv on 3.0.4.md only (because the older files won't pass) - this ensures new pushes comply with our linter rules in the `main` branch...
This pull request is automatically triggered by GitHub action `respec`. The `versions/*.md` files have changed, so the HTML files are automatically being regenerated.
## Weekly meetings happen on Thursdays at 9am - 10am Pacific This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in...
Hi, while I was trying to implement the specification, I ran into some existential questions about security requirements! It's unclear to me if an empty security array (`[]`) is equivalent...
As multi-document OADs become more important due to both new use cases and an increasing number of OADs that are far too large to work with as a single document,...
A partial fix for #3938 (partial because this PR only addresses 3.1.1-dev). Note that I have also created **draft** PRs to port this to the other two `-dev` branches. I...
Port of #4007 to v3.0.4-dev