Francois LASNE

@miqui the deprecation could even occurs in OAS 3.2 or meaning deprecation not beeing a breaking change, it provides an indication for the future non support (even if i am...

From what i have seen the usage of array is quite limited, and even more the usage of object a common use case is about selecting a list of fields...

if the contact fields will be updated as this ticket , https://github.com/OAI/OpenAPI-Specification/issues/1589 This feature could be included as part of the 2024 initiative https://github.com/OAI/OpenAPI-Specification/issues/3516

i would not stop improving the documentation and so not close any version . especially following the semantic versionning and the micro version upgrade . here it is about updating...

should not limited to read, but as well to write operation, the mechanism should follow a kiss principle that would handle 80% use case (even if sometime access control are...

:( starting green field all my spec are 3.1 , leveraging tooling that support it , spectral , api management still even if green field support of oasdiff would have...

@MikeRalphson , @Relequestual , @philsturgeon in this one there is the mentionned of discriminator , is there any clarification toward the statement discriminator deprecate or improve? my personal opinion this...

not sure to understand what you mean here @shiup would you be able to clarify ?

This looks very nice ! one remaining point would be to show on the https://www.openapis.org/ pushing on spot the latest but still having option to look at the past ,...

@handrews we may close this one , notice than accordingly to this page https://oauth.net/3/ oauth3 project has been abandonned toward to Oauth2.1 extensions...