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

I'd like to round up the various questions and concerns around $self in an attempt to get PR #4389 resolved one way or the other:

• Issue v3.2: Consider requiring $self to be an absolute-URI #4548 (should $self be required to be an absolute URI? This would simplify quite a few things)
• Issue v3.2: Should API URLs in general, and the Server Object url field in particular, still only use the retrieval URL as the base URL #4541 (should API URLs ignore $self? This is particularly important if we make $self absolute)

The two ideas above are related, as the identity of an OAD document generally should not change, which would suggest requiring an absolute-URI for $self, while the same OAD might apply to many different deployments of the API, each with a different location regardless of the OAD's identity.

• Issue v3.2: Consider additional guidance around $self usage #4539 (how much to explain how to read/use RFC3986 — I wish we didn't have to but experience suggests this is needed)
• Issue v3.2: Consider moving guidance on supplying a retrieval URL (and other parts of the spec that justify various features) to the Learn site #4540 (how much explanation goes in main spec sections vs appendices vs learn site — a recurring question for us)

These last two issues are about how much explanation to put where, which I find challenging. Less info is more readable, and technically sufficient. But people really seem to struggle with base URIs and relative reference resolution, and often disregard requirements because they don't see the point in supporting them.

[lornajane]

• small housekeeping PR around our markdown linting Improve Markdown linting and use it on more files #4515