Open Community (TDC) Meeting, Thursday 01 May 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.

[handrews]

• Infrastructure:
  • highlight.js: support for JSONL, JSON-Seq, basic multipart, improve text/event-stream #4553 (syntax highlighting for a bunch of additional formats)
• Minor (hopefully quick) changes:
  • v3.2 Respect encoding in all Media Type Objects #4559 (respect Encoding Object everywhere, not just Request Body Objects)
    • The restriction appears to be a vestige of the Encoding Object being an analogue to web form implementations, but people use multipart in particular for responses as well, and having to special-case the handling is more burdensome
• $self alternative PRs:
  • Add $self for self-identifying documents #4389 (original PR, more prosed-based, $self can be relative)
  • v3.2: $self field (Alternative Approach) #4556 (less prose, more examples (that could be moved to the learn site), $self MUST be absolute)
• sequential / streaming media types
  • v3.2: Sequential/streaming media types (take 2) #4554 (re-do based on @karenetheridge 's suggestions)
    • @hudlow has asked if we can require tools to detect when schema is being used with a portion of a stream — this is certainly possible, but is it feasible in all scenarios? I wasn't sure, which is why I made it a warning to OAD authors, but it would be nicer if it were a requirement.
  • new registry PR TBD — should more of the guidance on media types move to the registry?
    • We could also move a lot of the application/x-www-form-urlencoded and multipart/* guidance that currently takes up a lot of space

[lornajane]

• In discussion of v3.2: $self field (Alternative Approach) #4556 , we agreed that the (excellent!) extra content in the appendix needs to go to the learn site. However we don't feel that the site is ready to publish to, so we'll later move all the excellent supporting material to create a more slimmed down spec in the future.
• We'll keep this version of the PR in preference to the previous one.