OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
This script updates the schema IDs in the following YAML files: - schemas/v{major}.{minor}/schema.yaml - schemas/v{major}.{minor}/schema-base.yaml and generates the following JSON files from the updated YAML files: - schemas/v{major}.{minor}/schema.json - schemas/v{major}.{minor}/schema-base.json
Looking on the page here https://spec.openapis.org/registry/format/ as well on the JSON content here https://[spec.openapis.org/api/format.json](https://spec.openapis.org/api/format.json) there are some mistakes in the collumn type for instance : decimal A fixed point decimal...
Docs for the `contentType` field of the Encoding Object in 3.1.0 read (***emphasis added***): > The Content-Type for encoding a specific property. Default value depends on the property type: for...
This is the next step in un-blocking OASComply. Unlike the previous OASComply-related PR, this PR ***does not*** apply to v3.0.4. What, if any, wording about document parsing needs to go...
As I write PRs, I keep finding little things that I'm not sure how to do. Some examples: * What are the rules about which headings go in the TOC...
# (De-)Serializing null, required, and empty values ins OAS parameters At a couple points in the last year, I've tried to understand how to serialize and deserialize parameter values based...
As seen in PR #3688, `scripts/md2html` fails to use the correct revision of the MAINTAINERS.md file for the 3.0 and 3.1 specifications. Specifically, `build.sh` [uses a specific revision for the...
I wonder why these "Optional OAuth2 security" examples were created in the first place. I agree that an API can have several options how the API client authenticates but having...
I want to write an OpenAPI 3.0 swagger API doc for some [OSRM APIs](http://project-osrm.org/docs/v5.15.2/api/#general-options). There is a `coordinates` path parameter which is: > String of format {longitude},{latitude};{longitude},{latitude}[;{longitude},{latitude} ...] . for...
We already use these terms a bit in the spec, but with PRs like these: * #3732 * #3772 * #3758 we are relying more on such descriptions to define...