Open Community (TDC) Meeting, Thursday 24 March 2022

[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
AOB (see below)	TDC
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[darrelmiller]

Notes from the meeting:

• Attempted to discuss this item Support interdependencies between query parameters #256 about query parameter dependencies. There was some interest in the capability, but there was concern about the complexity that it would introduce.
• There was a discussion about process around allowing people to implement features to prove them out before incorporating the changes into the spec and the draft features process was referenced https://github.com/OAI/OpenAPI-Specification/blob/main/DEVELOPMENT.md#draft-features
• Ben suggested that we could use a issue template to allow community members to propose a topic to be covered in the TDC call.
• Ben referenced the VS Code process as a good example of a project that does a great job of managing many community requests. There was a proposal that someone might present in the TDC how that works so that we can learn from it.
• Darrel raised the concern that even when we sort out the problem of identifying which issues we should discuss in these calls, there is still the problem of understanding what are our principles around introducing complexity in the specification. It was proposed that we spend some of next week discussing this topic.

[karenetheridge]

Attempted to discuss this item #256 about query parameter dependencies. There was some interest in the capability, but there was concern about the complexity that it would introduce.

Sounds like I should have shown up for this one. By my reading of the swagger docs (https://swagger.io/docs/specification/serialization/), validating multiple query parameters in one json schema should be not only supportable, but MUST be supported. I haven't implemented this yet in my OpenAPI validator but it is near the top of the todo list. If you want to discuss it more at a subsequent meeting I can try to come.

[webron]

@karenetheridge you're always welcome to join :) I think though that the two topics you referred to are unrelated, but happy to chat about it in slack/discord/tdc calls.