Skip to content

Fix: #32. Reference OAS and jsonschema as spec. #43

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix: #32. Reference OAS and jsonschema as spec. #43

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
844dc17
Fix: #32. Reference OAS and jsonschema as spec.
ioggstream May 13, 2022
e14d6f9
Apply suggestions from code review
ioggstream Jun 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions draft-ietf-httpapi-rest-api-mediatypes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ Interoperability considerations:
: None

Published specification:
: this document
: [oas]
Copy link
Contributor

@darrelmiller darrelmiller Jun 19, 2022

Choose a reason for hiding this comment

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

@ioggstream I think this URL https://spec.openapis.org/oas/latest is the most stable one to use to reference the OAS specification.

Copy link
Collaborator Author

@ioggstream ioggstream Jun 20, 2022

Choose a reason for hiding this comment

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

@darrelmiller question: that just references OAS3.1 whereas this media type is intended to support present and future versions of the spec eventually via the version parameter. (e.g. 3.0, 3.1, 4.0, ..).

If you think that https://spec.openapis.org/oas/latest is still correct, we can just explicit that in this registration, and use the latest.

Copy link
Collaborator Author

@ioggstream ioggstream Jun 20, 2022

Choose a reason for hiding this comment

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

See #49 .

Copy link
Collaborator

@handrews handrews Oct 11, 2025

Choose a reason for hiding this comment

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

@ioggstream we now have an overall page for all spec and schema versions if that helps: https://spec.openapis.org/oas/

Copy link
Collaborator Author

@ioggstream ioggstream Nov 4, 2025

Choose a reason for hiding this comment

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

@handrews thanks for the info!

This PR is jsonschema related... Let's file another PR on the latest file, until the jsonschema discussion is open I would focus on openapi only.


Applications that use this media type:
: HTTP
Expand Down Expand Up @@ -217,7 +217,7 @@ Interoperability considerations:
: see {{Section 3 of YAML-MEDIATYPES}}

Published specification:
: this document
: [oas]

Applications that use this media type:
: HTTP
Expand Down Expand Up @@ -424,7 +424,7 @@ Interoperability considerations:
: See the "General Considerations" section of {{jsonschema}}

Published specification:
: this document
: This document specifies dialect identification, but each dialect will have it's own specification. The set of possible dialects is open ended and includes, but is not limited to, those released by the JSON Schema organization ({{jsonschema}}).

Applications that use this media type:
: JSON Schema is used in a variety of
Expand Down