Open Community (TDC) Meeting, Thursday 27 April 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
DCO - Boo	Darrel
Update on Compliance Parser	Henry
Links in moonwalk	MikeK
AOB (see below)	TDC
Approved spec PRs	TDC
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[handrews]

• OAS 3.x schemas and the Compliance Parser project — I would like to make a few small changes (which I will try to post as a PR today) to support this project.
  • Is there any reason not to backport applicable changes to the 3.1 schema to the 3.0 schema?
  • We should also discuss what additional things related to compliance should be added to the schemas vs added to a schema patch that will be kept with the compliance code.
  • Some things have to be handled with the compliance code because the 3.0 schema needs to be migrated from draft-04 to 2020-12 (using alterschema, not manually) in order for it to be usable for what the project needs.
  • What are the conditions for publishing a schema update? We have published at least one in-place update in the past
• Path templating rules: Issue Formally define 3.x URL templating behavior #3256 - can we do this in 3.0.4 and 3.1.1? I'm happy to write the PR as it is useful for the compliance parser project
• Callback example: Issue Linked callback example appears to be non-conformant #3257 - am I missing something or is the example non-compliant?

[handrews]

@webron is there any update on fixing the anchors and whatever else we agreed was a typo we could correct in the already-published versions of the spec?

[handrews]

Also, I'm currently developing the OAS compliance parser in a private repo, and don't have permissions to set anything else up. Should it be moved under OAI? Or somewhere else? This isn't particularly urgent, but I am using issues in the repo to document what I'm working on, and hold ideas that may or may not fit into the project schedule, which might be of interest to folks.

h/t @MikeRalphson for "compliance parser", which is less ambiguous/confusing than "reference parser" 😁