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",
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.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
