OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
there is a `package.json` with a package name: `oas-schemas` but this package doesn't exist in `npmjs.com` ...
This is alluded to by @kapone89 in [Issue 2015](https://github.com/OAI/OpenAPI-Specification/issues/2015#issuecomment-536460869) but I believe it warrants an issue of its own to get clarification. [The spec states clearly](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#patterned-fields) that "Templated paths with...
### Splitting this out of issue #1576... ...which was originally about binary streaming but later drifted into a discussion of JSON streaming. Several real-world uses for JSON streaming were cited:...
From what I understand it is not possible to use an XML document containing a simple type list like this one: ``` ``` A valid xml is: `value1 value2` With...
In the OpenAPI spec, section "XML Object", https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#xmlObject the examples contain text which appears to me incomprehensible: > The examples of the XML object definitions are included inside a property...
* Fixes #3792 Make it clear that the default value does not do anything, and the non-default value (true) changes the normal expected behavior of the "schema" or "content" fields....
and correct expansion of "auth". Will forward-port this to 3.1.1 and 3.2.0 once accepted.
Looking at https://spec.openapis.org/oas/latest.html it still references RFC 7231 when referring to HTTP. But that specification was obsoleted by RFC 9110 in June 2022. I am not confident enough to make...
Partially addresses https://github.com/OAI/OpenAPI-Specification/issues/1823. This PR has the same changes as the https://github.com/OAI/OpenAPI-Specification/pull/1824 plus the requested changes that were requested here: https://github.com/OAI/OpenAPI-Specification/pull/1824#issuecomment-460532960. Following the same logic as the original PR, it...
Here are 3 possible issues in schemas used in the documentation examples, that could be fixed: - in [upsto](https://github.com/OAI/OpenAPI-Specification/blob/main/examples/v3.0/uspto.json) example, the two `uriref` formats at the end should be `uri-ref`...
