Skip to content

Settle on "OpenAPI Description" (3.0.4) #3384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 28, 2023
Merged

Conversation

handrews
Copy link
Member

This follows up from a discussion on the OAI slack that decided:

  • redefining "document" to sometimes mean multiple documents is confusing
  • "description" has more support than "definition"


An OpenAPI document MAY be made up of a single document or be divided into multiple, connected parts at the discretion of the user. In the latter case, `$ref` fields MUST be used in the specification to reference those parts as follows from the [JSON Schema](https://json-schema.org) definitions.
An OpenAPI Description MAY be made up of a single document or be divided into multiple, connected parts at the discretion of the author. In the latter case, `$ref` fields MUST be used in the specification to reference those parts as follows from the [JSON Schema](https://json-schema.org) definitions. In a multi-document description, the document containing the [OpenAPI Object](#oasObject) is known as the **root OpenAPI document.**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

entry instead of root.

This follows up from a discussion on the OAI slack that decided:

* redefining "document" to sometimes mean multiple documents is confusing
* "description" has more support than "definition"
@webron webron merged commit 8397a89 into OAI:v3.0.4-dev Sep 28, 2023
@handrews handrews deleted the desc-304 branch March 5, 2024 21:36
@handrews handrews added this to the v3.0.4 milestone May 17, 2024
@handrews handrews added the clarification requests to clarify, but not change, part of the spec label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification requests to clarify, but not change, part of the spec
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants