Open Community (TDC) Meeting, Thursday 02 March 2023

[github-actions]

NOTE: This meeting is on Thursday at 9am - 10am PT

Zoom Meeting link: https://zoom.us/j/975841675. Dial-in passcode: 763054 - Code-of-Conduct

In order to give some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. Feel free to suggest other potential agenda topics.

Please submit comments below for topics or proposals that you wish to present in the TDC meeting

The agenda backlog is currently maintained in issue #2482

Topic	Owner	Decision/NextStep
Reports from Special Interest Groups	TDC
See comments below	TDC
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[pavelkornev]

Discuss: Template paths in security schemas

[pavelkornev]

OpenAPI v3.1 adoption in our Org (SAP) is blocked by Swagger UI v3.1 support. Are there any plans to finalize the support of OAS v3.1 in Swagger UI or we should focus on and wait for OpenAPI v4?

[ralfhandl]

Format registry PR #3167

[handrews]

3.0.4 patch release

A few specifics:

• Clarify "format": "byte" vs "format": "base64" in OAS 3.0.x #3174: Correct the examples to say format: byte instead of format: base64 or add base64 with the same behavior as byte and advise extra care checking vendor support?
• Clarify the utility of base64-encoding of whole payloads or multipart parts #3175: Can we make certain uses of base64 encoding NOT RECOMMENDED as they don't really make sense, or is that too much for a patch release?
• Clarify: "type": "string", "format": "binary" in non-entity-body #1544: I think that noting that format: binary doesn't make sense in certain places (you literally cannot have unencoded binary in JSON) is just a clarification (but one that in my experience is necessary)
• Can we get clarification on how to post multipart/form-data containing an array of items of type X? #2840: this has some irrelevant things in it, but there's a question about mapping data such as true, false, and null in and out of string representations, which points to a more general question of what OAS actually requires in terms of type coercion or translation. Right now the requirements are not clear enough to be testable, nor are they clearly deferring the decision to implementations
• Support for Streams in Responses #1576: I'm just generally confused over what to do with this one.

[handrews]

OpenAPI v3.1 adoption in our Org (SAP) is blocked by swagger-api/swagger-ui#5891. Are there any plans to finalize the support of OAS v3.1 in Swagger UI or we should focus on and wait for OpenAPI v4?

@pavelkornev You'd have to ask the Swagger folks about that, this group does not control Swagger UI.

[ralfhandl]

3.0.4 patch release: fix broken hyperlinks to section headlines?