Darrel

@Hoffs This validation rule is supposed to be checking the component names with the regex https://github.com/microsoft/OpenAPI.NET/blob/75bb4ef3fb7029b99152b6fd05bb678eaef40d06/src/Microsoft.OpenApi/Validations/Rules/OpenApiComponentsRules.cs#L20 I tested it and it does return an error in the diagnostics object. 

This new wording completely changes the semantics of the format. Currently the words do not infer that a response payload is going to be changed to not include the password....

@mikekistler These look good but we should also talk about what to do with sf-list and sf-dictionary and more complex headers. /cc @handrews

We discussed this at the TDC meeting. Additional guidance is needed to let the developer know that they are responsible for pre-encoding parameter values so that characters do not conflict...

Security considerations PR https://github.com/OAI/OpenAPI-Specification/pull/3488

I think it is worth clarifying the deprecation policy. My understanding is that our deprecation of OAS concepts would use the same approach as an API description's use of the...

I do not believe this is a helpful example. I do not believe we have ever talked about how a JSON model should be serialized in text/plain payloads. We should...

Only allowing two media types makes no sense to me, especially considering we claim to allow wildcards. Considering the JSON schema mentions media-range my guess is that we were expecting...

Hi @AxelNennker Thank you for the submission. However, we do not make changes to published versions of the specification. We could consider adding this to our 3.0.4 and 3.1.1 patch...

Are formats for defining semantics? https://github.com/OAI/OpenAPI-Specification/issues/3572