-
With 3.1 released, it's time to revisit the backlog of **possible stories to consider** as the specification continues to evolve. _In cases where a specific TSC or TDC member has indicated interest, t…
-
I was wondering if there is metaplan to formalize bundling of OAS definitions as well. Ben Hutton and Mike Ralphson did a great job of formalizing JSON Schema 2020-12 in their [article](https://json-…
-
Is it possible to remove the restriction of making the field that acts as discriminator required (and assume that when not returned, the object is just of the 'base' type defined in the schema)?
i.e …
-
Currently, some official citation sites point to the rendered HTML rather than the authoritative markdown files. There is also confusion over what the official, authoritative URL for the authoritativ…
-
Relationships are an important part of an API or a data model: People have Friends, People have Hobbies, which are shared by other People, ...
OData represents relationships as a special kind of prop…
-
Support for asciiDoc in the description attribute of the info and pathItem Object
miqui updated
4 months ago
-
**Feature Name**
Path Archetype Property
**Metadata**
|Tag |Value |
|---- | ---------------- |
|Proposal |[2023-09-14-Path-Archetype-Property](https://github.com/OAI/OpenAPI-Specification/tre…
-
currently the button new issue
lead to this page
![image](https://github.com/OAI/OpenAPI-Specification/assets/12461661/71b57e2f-464f-4f96-99fa-18ed873c66f6)
that does contains plenty of link…
-
Inline local works, but in the process you lose the name of the component and therefore passing this code generator will end up generating a different type for every usage. It should be useful for sc…
-
Hi,
I recently came across an OpenAPI Spec file from a customer where some path-level parameters/responses/headers/schemas were defined through an internal reference, but having $ref pointing to a …