Hi Michael,
> On May 15, 2025, at 6:08 AM, Michael Richardson 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,
Hi Michael,
On 5/15/25 5:08 AM, Michael Richardson 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:
Eliot Lear wrote:
> Not an RFC yet, but see draft-ietf-scim-device-model. While it's not
super
> obvious, the reference should probably be
> https://spec.openapis.org/oas/v3.1.1.html.
and you used YAML rather than JSON representation.
--
Michael Richardson , Sandelman Software Wo
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
Carsten Bormann wrote:
> On 14. May 2025, at 16:23, Paul Duffy (paduffy)
wrote:
>>
>> It was required that both the OpenAPI and Protobuf definitions be
inlined within the draft. It's a mess (not directly usable by developer tools …
> That is indeed a problem.
> I made a q
On 14. May 2025, at 16:23, Paul Duffy (paduffy)
wrote:
>
> It was required that both the OpenAPI and Protobuf definitions be inlined
> within the draft. It's a mess (not directly usable by developer tools …
That is indeed a problem.
I made a quick prototype a while ago how the RPC might want
Hi Michael,
On 5/14/25 7:31 AM, Michael Richardson wrote:
Are there some examples in the RFC series of WG publishing (HTTP)APIs based
upon the Swagger definitions.
[JM] RFC 8743 has an example implementation of an API documented with
OpenAPI using Swagger 2.0 [1]
1. How do we present the
https://datatracker.ietf.org/doc/draft-duffy-csmp/08/
It was required that both the OpenAPI and Protobuf definitions be inlined
within the draft. It's a mess (not directly usable by developer tools ... but
links for direct import are included later in the draft).
This is also a draft strugglin
I suggested to Michael directly, but will repost it here: ask on the HTTPAPI
working group.
___
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
Not an RFC yet, but see draft-ietf-scim-device-model. While it's not
super obvious, the reference should probably be
https://spec.openapis.org/oas/v3.1.1.html.
Eliot
On 14.05.2025 14:31, Michael Richardson wrote:
Are there some examples in the RFC series of WG publishing (HTTP)APIs based
up
10 matches
Mail list logo
