List view

3.2: schema test coverage

Schemachanges related to the schema(s)changes related to the schema(s)

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4456

#4456 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 22, 2025

3.2: reference latest JSON Schema 2020-12 drafts

editorialWording and stylistic issuesWording and stylistic issues

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4467

#4467 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 22, 2025

feat: adds a name field to the server object

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4469

#4469 In OAI/OpenAPI-Specification;

· by baywet was closed on Mar 27, 2025

3.2: update normative reference for JSON to RFC8259

editorialWording and stylistic issuesWording and stylistic issues

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4499

#4499 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 27, 2025

3.2 Response Object description not required

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4500

#4500 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 27, 2025

3.2: schema test case and schema bug fix for device authorization

Schemachanges related to the schema(s)changes related to the schema(s)

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4501

#4501 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 27, 2025

feat: adds additional operations for path item object

enhancement

httpSupporting HTTP features and interactionsSupporting HTTP features and interactions

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4514

#4514 In OAI/OpenAPI-Specification;

· by baywet was closed on Apr 1, 2025

3.2: reference RFC 9110 instead of RFCs 7230, 7231, and 7235

editorialWording and stylistic issuesWording and stylistic issues

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4380

#4380 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 22, 2025

3.2 schema: new fixed fields in Security Scheme Object

Schemachanges related to the schema(s)changes related to the schema(s)

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4394

#4394 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Mar 6, 2025

Allow URIs for Security Schemes

enhancement

re-use: ref/id resolutionhow $ref, operationId, or anything else is resolvedhow $ref, operationId, or anything else is resolved

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4388

#4388 In OAI/OpenAPI-Specification;

· by handrews was closed on Mar 22, 2025

Proposal: Add JWT audience in security scheme

security

security: authAuthentication including overlap with authorizationAuthentication including overlap with authorization

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 3286

#3286 In OAI/OpenAPI-Specification;

· by emmanuelgautier was closed on Feb 29, 2024

OIDC fixes (3.2.0 port of #3607, #3718)

approved pr portPRs that just port an approved PR to another versionPRs that just port an approved PR to another version

security

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 3891

#3891 In OAI/OpenAPI-Specification;

· by handrews was closed on Jun 19, 2024

3.2.0: replace "property" with "field" or "keyword" where appropriate

approved pr portPRs that just port an approved PR to another versionPRs that just port an approved PR to another version

editorialWording and stylistic issuesWording and stylistic issues

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4035

#4035 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Sep 9, 2024

Explicitly state what <code>security: []</code> means

security

security: configThe mechanics of severs and structure of security-related objectsThe mechanics of severs and structure of security-related objects

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 3995

#3995 In OAI/OpenAPI-Specification;

· by rvedotrc was closed on Aug 29, 2024

Specify that tag names are case-sensitive

review

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 3999

#3999 In OAI/OpenAPI-Specification;

· by rvedotrc was closed on Aug 9, 2024

Markdown updates for 3.2.0

approved pr portPRs that just port an approved PR to another versionPRs that just port an approved PR to another version

editorialWording and stylistic issuesWording and stylistic issues

scriptPull requests that update Bash or JavaScript codePull requests that update Bash or JavaScript code

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4025

#4025 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Aug 29, 2024

3.2.0: minor nits

approved pr portPRs that just port an approved PR to another versionPRs that just port an approved PR to another version

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4026

#4026 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Sep 7, 2024

Port 3.1.1 PRs to 3.2.0

approved pr portPRs that just port an approved PR to another versionPRs that just port an approved PR to another version

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 3987

#3987 In OAI/OpenAPI-Specification;

· by handrews was closed on Aug 13, 2024

New self-identification proposal

draft:proposal

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 3989

#3989 In OAI/OpenAPI-Specification;

· by handrews was closed on Aug 7, 2024

Clarify <code>security</code>; state that <code>[]</code> is undefined behaviour

security

security: configThe mechanics of severs and structure of security-related objectsThe mechanics of severs and structure of security-related objects

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 4011

#4011 In OAI/OpenAPI-Specification;

· by rvedotrc was closed on Aug 29, 2024

3.2.0: back out changes to Path Item Object and bring its <code>$ref</code> field back

enhancement

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 4094

#4094 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Oct 22, 2024

[PROPOSAL] Add summary, parent and kind as optional fields for tags

draft:proposal

metadatatags, info, license, contact, markdown usage, etc.tags, info, license, contact, markdown usage, etc.

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 4063

#4063 In OAI/OpenAPI-Specification;

· by lornajane was closed on Sep 13, 2024

3.2.0: sync with 3.1.1

approved pr portPRs that just port an approved PR to another versionPRs that just port an approved PR to another version

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 4066

#4066 In OAI/OpenAPI-Specification;

· by ralfhandl was closed on Oct 22, 2024

Remove namespace prefix from the XML Object

xml

Status: Closed (abandoned).

OAI/OpenAPI-Specificationnumber 4126

#4126 In OAI/OpenAPI-Specification;

· by saper was closed on Oct 10, 2024

Clarify constraints on Param Obj fields (3.2.0 port of #3760)

clarificationrequests to clarify, but not change, part of the specrequests to clarify, but not change, part of the spec

param serializationIssues related to parameter and/or header serializationIssues related to parameter and/or header serialization

Status: Merged (completed).

OAI/OpenAPI-Specificationnumber 3797

#3797 In OAI/OpenAPI-Specification;

· by handrews was closed on May 14, 2024