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

• Governance/process/editorial things listed in a specific order this week:
  • What is our authoritative spec URL and how do people find it? #3576 (officially make the HTML renderings the citable source of truth, because they are the only ones with the full contents and we should be able to rearrange our repo to suit our development needs)
  • Move examples to learn.openapis.org or spec.openapis.org #3854 (consolidate examples that aren't in the specification text in one place as, it's confusing to manage example-related issues spread across the spec repo and the learn site, and different contributors could help with examples than with the spec)
  • extension registry management #1806 (are we doing anything from this or can we close it?)
  • Add Security Considerations section #2950 (should we add the Security Considerations to 3.0.4 and 3.1.1? If not, is this done and can we close it?)
  • Documentation for OpenAPI's Header Object should be verbose #1965 (repeat the full list of relevant Parameter Object fields under Header Object or leave as-is?)
  • Usage of field vs property #2660 (do we want to try to sort this out in the patch releases or not?)
• Patch Releases: referencing and identification
  • This week, we really need to resolve the implicit connection PRs, as I have two alternatives to choose from:
    • Clarify resolving implicit connections (3.1.1) #3823 (defines two approaches for two different ways to arrange multi-document OADs)
    • Alternative: Clarify resolving implicit connections (3.1.1- alternative to #3823) #3856 (defines a single recommended approach)
  • Clarify "URI" and "URL" meaning and usage (3.1.1) #3838 (3.1 URL vs URI usage was not well-explained)
  • Path Item $ref change warning (3.1.1) #3860 (we can't just remove the weird Path Item $ref behavior in a minor release)
  • Resolution of relative URLs in CommonMark text (3.0.4) #3858 (relative links in CommonMark text)
• Patch Releases: discriminator
  • Clarify discriminator + oneOf/anyOf/allOf usage (3.1.1 modified port of #3822) #3846 (needs resolution so I can backport merge differences)
• Patch Releases: parameters and encoding
  • Should style: form examples include ? prefix? If so, what about spaceDelimited, pipeDelimited, and deepObject? #3849 (nitpicky but important- how serialized examples work)
    • This is blocking resolution of Ambiguities Regarding Parameter Example Validation #3041 to include serialization examples in Parameter Object example(s) fields in the spec
  • Example of deepObject + explode=false #1322 (I'm not sure deepObject has a clear explanation, but we should clarify this weird gap where the default explode: false is not defined)
  • Doc improvements: query formats (n/a usage, "rendering") #1663 (need clarity around style/explode and "n/a")
  • Appendix on RFC6570-derived behavior + allowReserved (3.0.4) #3818
  • Appendix on converting data types to strings (3.0.4) #3840
  • Warnings for header and cookie serialization (3.0.4) #3841
  • Encoding Object content and header clarifications (3.0.4) #3857
  • Appendix for percent-encoding concerns (3.0.4) #3859

[darrelmiller]

Action: Create a sig-industry-standards repo to maintain a list of organizations who are using OpenAPI to define standards.
Action: Add older specifications to the root page of specs.openapis.org