Open Community (TDC) Meeting, Thursday 23 May 2024

[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]

The following PRs are ports of already-approved PRs and should be straightforward to merge - please consider doing so before the call to save us time!:

• 3.1.1 upport of #3801: Link for case insensitivity of auth scheme #3816
• 3.2.0 upport of #3801 and #2644: case insensitivity of auth scheme #3817
• Clarify entry/complete document terminology (3.0.4) #3820 (already approved by @ralfhandl and @miqui , but I had to resolve conflicts which reset it)
• Clarify entry/complete document terminology (3.1.1 port of #3820) #3839
• Clarify allowEmptyValue -> disregard empty values (3.1.1 port of #3812) #3835
• Clarify allowEmptyValue -> disregard empty values (3.2.0 port of #3812) #3836

These PRs are pretty straightforward and probably could be handled prior to the meeting:

• Correctly handle appendicies in md2html #3810 (now with a rendered view available!)
• Clarify discriminator "*Of" and "mapping" usage (3.0.4) #3822 (mostly reorganizing things, with only a few new clarifications)
• Clarify Link Obj parameters as best we can (3.0.4) #3824
• feat(spec): codify Encoding in specific requestBody mediatypes #3837

These PRs are complex and/or will need discussion:

• Encapsulate page layout for extensions #3828 (did we turn off this registry and should it stay off?)
• Clarify resolving implicit connections (3.1.1) #3823
• Clarify "URI" and "URL" meaning and usage (3.1.1) #3838
• Appendix on RFC6570-derived behavior + allowReserved (3.0.4) #3818

These issues need discussion:

• Add appendix "Informative references" to published spec documents #3740
  • Since our allegedly normative Markdown doesn't include the references list, should we shift to the HTML rendering for citations?
  • How do we want to approach classifying and indicating normative vs informative references?
• More issues for review:
  • Meta: How many TSC opinions are necessary to take an issue out of review and work on a PR and not risk the PR being shot down by other TSCers? (of course, sometimes PRs get shot down anyway for good reasons, but in general...?)
  • extension registry management #1806 (comment) (is there anything here we're going to do, or should we just close this?)
  • Did we break 3.2 compatibility by removing the Path Item $ref special case? #3734

[jeremyfiel]

#3837

[frankkilcommins]

Please review and merge #3842 as part of the Arazzo Specification launch preparation 🚀

[hudlow]

Can someone with the proper authority re-open #726? There is clearly still unrest about the clarity of the license field.

[ralfhandl]

How to test changes to the gh-pages build script:

• check out PR branch
• run scripts/md2html/build.sh from the repo root
• this will create a folder deploy/oas with the HTML files inside

Only once:

• check out gh-pages branch
• copy folder js into folder deploy
• folder structure should now be
  • deploy
    • js
      • respec-oai.build.js.map
      • respec-oai.js
      • ...
    • oas
      • latest.html
      • v2.0.html
      • ...

Then open the HTML files with a browser and they will render nicely.

After that it suffices to check out the branch with the modified build script and run it, then open the HTML files with a browser.