Hi Michael,
> On May 15, 2025, at 6:08 AM, Michael Richardson <[email protected]> wrote: > > > Thank you for the RFC8743 reference. > I see that the definitions are in an appendix, which I guess is normative. > > Rich said that we should be calling it OpenAPI, because Swagger is the > toolchain, not the format, yet this document says: > > The documentation of APIs is provided in the OpenAPI format, using > Swagger v2.0. See Appendix D. > ... > { > "swagger": "2.0", [TH] Rich is correct. The Swagger Specification was renamed to OpenAPI Specification in 2015 [1]. From that blog post: " • OpenAPI = Specification • Swagger = Tools for implementing the specification” So, Swagger 2.0 is now OpenAPI Specification, Version 2.0 [2] . (Note the section titled “(fka Swagger RESTful API Documentation Specification)” where “fka” means “formerly known as” [3].) > > I also see that you used the JSON format for the OpenAPI, and the NIPC > document says: > > <CODE BEGINS> file "openapi.yml" > openapi: 3.0.3 > info: > > so I guess that transition is now done. > > In that document, I don't see anything in the References that refers to the > specification. This is really the core of my question. > > [TH] The URL Eliot provided is the most recent version of the OpenAPI Specification (Version 3.1.1) [4]. (Note that OpenAPI also provides a “Latest published version” URL which will always point to the most recent published version of the specification [5].) Best regards, Ted Harrison RPC Citation Specialist [1] https://swagger.io/blog/api-strategy/difference-between-swagger-and-openapi/ [2] https://spec.openapis.org/oas/v2.0.html [3] https://spec.openapis.org/oas/v2.0.html#fka-swagger-restful-api-documentation-specification [4] https://spec.openapis.org/oas/v3.1.1.html [5] https://spec.openapis.org/oas/latest.html _______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
