OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
With Swagger inflector and Swagger-node it's now more common to have endpoints that we **don't want to document** but we want to have them in the spec for other uses....
# A Canonical and Extended Forms for OpenAPI Specifications Following the discussion on last TSC and talking about [Traits](#613), [Overlays](#1722) and/or [Mixings](#1843), anyone can agreed these features are strongly oriented...
There are many requests for finer-grained control over both ordering and visibility of elements, etc. These have been implemented in different integrations but might need to be in the spec,...
I am looking for a reference api that contains every feature of the spec so I can test a publishing tool we have developed i.e. links, discriminators, $refs , schemas,...
Hi, It seems confusing that scopes can be specified for ClientCredentials (as we are doing [here](https://github.com/w3c-ccg/traceability-interop/blob/main/docs/openapi/openapi.yml#L50)). This hints that select scopes can be included in the request. However, that is...
Some descriptions can be long or very long. Allowing $ref would be useful to reference an external file with only text, e.g. markdown. It'd be great if **info.description** and **tags.name/description**...
Sorry if this came up before, I searched but could not find anything. Environment variables have become something of the de facto mechanism to set server-specific values, then access them...
How to define reusable headers that can be used in both request and response? if a headers is defined in components.parameters it is not allowing to use in response.headers and...
Currently, every single operation must declare its' own responses. This causes a whole bunch of duplication, which would be better served by having a top-level `responses` section in the spec....
Hi there, I'm wondering if there currently is any way to define language-specific values for the descriptive elements in the specification, such as `description`, or `example`? For example: ``` {...
