Open Community (TDC) Meeting, Thursday 27 March 2025

[github-actions]

Weekly meetings happen on Thursdays at 9am - 10am Pacific

This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in advance allows people to plan to attend meetings where they have an interest in specific topics.

Whether attending or not, anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals.

Meetings take place over Zoom: https://zoom.us/j/975841675, dial-in passcode: 763054

Accessibility & Etiquette

• Participants must abide by our Code-of-Conduct.

• Meetings are recorded for future reference, and for those who are not able to attend in-person.

• We invite you to feel comfortable to challenge any language or behaviour that is harmful or not inclusive during this meeting.

• We look forward to your participation, but please consider these acts of etiquette:

  • Remain on mute when not speaking to prevent interruptions.
  • Blur your background to reduce visual distractions.
  • Use the Zoom meeting "Raise Hand" feature to notify the group when you wish to speak.

Blur My Background	Raise Hand

Agenda Structure

Topic	Owner	Decision/NextStep
Intros and governance meta-topics (5 mins)	TDC
Reports from Special Interest Groups (5 mins)	SIG members
Any other business (add comments below to suggest topics)	TDC
Approved spec PRs	@OAI/tsc
Active Projects	@OAI/openapi-maintainers
New issues needing attention	@OAI/triage

/cc @OAI/tsc please suggest items for inclusion.

[ralfhandl]

3.2 Normative References

• 3.2: reference RFC 9110 instead of RFCs 7230, 7231, and 7235 #4380
  • fixes RFC 7231 has been obsoleted by RFC 9110 #3800

[baywet]

Adding:

• feat: adds a name field to the server object #4469

[handrews]

I'm just putting in a placeholder comment before this issue gets overwhelmed completely... and now:

• Add $self for self-identifying documents #4389 ($self)
• Gather data modeling sections into a "Modeling Data" top-level section #4472 (consolidating a "Modeling Data" section- general feedback on the direction, this will be reworked substantially before the details are important)
• 3.2 Use human-friendly rendering of JSON Schema I-D #4503 (pick a URL for the JSON Schema spec instead of using 3 different ones- should be done async, really)

Note: There is no need to spend time on #4480 (tag URIs), it's just there to document the rejected idea for posterity

[lornajane]

A couple of PRs were merged that I think needed a second review before merging since they modified the specification. #4380, maybe others. Do we need to take any action on this?

[handrews]

@lornajane Did we enable branch protection for the new branches? I don't have permissions to look at that AFAIK. And yes, I was surprised on some of the merges, although since we're not right at a release point we can easily fix anything in a subsequent PR.

[ralfhandl]

A couple of PRs were merged that I think needed a second review before merging since they modified the specification. #4380, maybe others.

Only #4380, the others had two maintainer approvals or were pure infrastructure.

Leaving #3800 open until we decide whether to revert #4380 or keep it.

[ralfhandl]

@lornajane Did we enable branch protection for the new branches?

The *dev branches are protected. They require PRs and one maintainer approval for merging PRs.

Our current policy is to require only one approval for tooling changes, which permits accidental merging of spec-changing PRs lacking a second approval.

We can change that and always require two approvals.

I checked the new rulesets and couldn't find a way to limit applicability of a ruleset to certain files within a branch.

Push rulesets would prevent pushes to matching files, but we want to allow changing the files in src and just require more approvals for them. Plus, push rulesets are not (yet) available for the OAI repos.

[ralfhandl]

3.2 request for review

• 3.2: update normative reference for JSON to RFC8259 #4499
  • fixes Reference latest JSON RFC8259 instead of RFC7159 #4487

[ralfhandl]

3.2 request for review

• 3.2 Response Object description not required #4500
  • fixes OAS 3.0 and 3.1 schemas require the Response Object description property but allow it to be empty #3538

[ralfhandl]

3.2 request for review

• 3.2: schema test case and schema bug fix for device authorization #4501
  • fixes a schema bug discovered by the new test case

[ralfhandl]

Style Guide

• main: add guidance on bullet lists to style guide #4504
  • fixes Style Guide: Periods at the end of bullet lists? #4502