Open Community (TDC) Meeting, Thursday 20 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]

Schema development

• main: move old schemas to _archive_ #4435
  • fixes Clean up /schemas on main branch #4356

[ralfhandl]

Schema publishing

• v3.1-dev: publish OpenAPI schema iterations #4430
  • fixes tokenUrl in 3.1 schema does not support relative urls as specified #4327

[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

[ralfhandl]

3.2 schemas

• 3.2: bump spec version in schema files #4367
  • fixes 3.2 schema: replace 3.1 with 3.2 #4364

[ralfhandl]

Schema testing

• dev: schema tests output reason if "pass" test fixture fails #4455

[ralfhandl]

3.2 schema test coverage and bug-fix

• 3.2: schema test coverage #4456

3.1 schema bug-fix and test

• 3.1: fix Link Object schema #4465

Together these fix

• 3.1 3.2 schemas: Link Object schema has body property instead of server #4463

[LasneF]

Encountering this topic,

#1034

looks the proposal to have either a single value , either an array is good.
outcome of the discussion could be acceptable for 3.2 , or 3.3 or only in 4.0 , or not usefull at all

[baywet]

adding:

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

[handrews]

• Strawperson proposal for URI-based tag resolution #4390 (URIs and tags)
• Gather data modeling sections into a "Modeling Data" top-level section #4472 (refactoring data modeling guidance)
• Add $self for self-identifying documents #4389 ($self field)