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

[gregsdennis]

I'd like to add discussion of transferring the format registry to JSON Schema. I think this makes sense since JSON Schema defines the keyword and it only has context within schemas.

Links:

• Discussion: ✨ Proposal: format registry json-schema-org/json-schema-spec#1552
• Initial write-up, including specification requirements for implementations: Gregsdennis/format registry json-schema-org/json-schema-spec#1574
• Preview of website page: ✨ Enhancement: Publication page for new format registry json-schema-org/website#1130

Initial discussion in Slack:

• Aug 2023: https://open-api.slack.com/archives/C0EDH2QKD/p1692368729070939
• Oct 2024: https://open-api.slack.com/archives/C1137F8HF/p1730090796311129
• Jan 2025: https://open-api.slack.com/archives/C1137F8HF/p1736933149883919

Every time this has been brought up, there seems to be general favor for the idea.

The meeting is at 6am for me, so I will not be present.

[ralfhandl]

Registries

• docs: adds ms extensions repo link #4304

Housekeeping

• Use branch-local package-lock.json #4318
• Define style for field names and values in YAML comments / $comment strings #4305

[mikekistler]

Discussions:

• 3.2: allow `openapi` field to just specify MAJOR.MINOR and omit the PATCH number #4233
• Optional discriminator property #4319

[lornajane]

We discussed the question of unpublishing our registry of formats in favour of the one planned by the JSON schema project (thanks @gregsdennis for the explanations and links!). The general feeling is that it's a good idea for JSON Schema to have and maintain a format registry to serve that project, but that there's no requirement for OpenAPI to unpublish ours. We'll watch, cheer you on, and collaborate as we go along!