Open Community (TDC) Meeting, Thursday 12 October 2023

[github-actions]

NOTE: This meeting is on Thursday at 9am - 10am PT

Zoom Meeting link: https://zoom.us/j/975841675. Dial-in passcode: 763054 - Code-of-Conduct

In order to give some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. Feel free to suggest other potential agenda topics.

Please submit comments below for topics or proposals that you wish to present in the TDC meeting

The agenda backlog is currently maintained in issue #2482

Topic	Owner	Decision/NextStep
Reports from Special Interest Groups	TDC
AOB (see below)	TDC
Approved spec PRs	TDC
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[handrews]

[EDIT: I will not be able to attend today, removing my items]

Agenda items:

• Update on processing model differences in OAS 3.0 vs 3.1 and what we might do about them: @handrews
• (Related to above) Processing non-OAS document fragments as valid OAS - a proposal @MikeRalphson
• Update on fixing internal links: @MikeRalphson - ensure this doesn't break md2html ("pretty" specs)
• Update on schema revision publication process, including dates for URIs that don't have dates right now: @MikeRalphson
• Does yaml2json preserve object property key order? @MikeRalphson => Yes
• Do we opt-in to Hacktoberfest? Maybe not for the specs, but for learn.openapis.org, styleguide etc?
• Rename repo to "learn" or "Learn-OpenAPI" learn.openapis.org#68 @handrews / @MikeRalphson

[handrews]

[EDIT: I will not be able to attend today]

Potentially discuss my report on processing models, although we could do that next week if folks actually want more time to read it first.

The summary I linked here is only 1000 words. It links to a much longer document with details and examples.

[earth2marsh]

I'd love to discuss: OAI/sig-moonwalk#63

[lornajane]

Discussed with the group and the general feeling is that we're unlikely to get valuable contributions from doing Hacktoberfest, since we're not a particularly beginner project.

[lornajane]

Documentation repository renamed to learn.openapis.org

[lornajane]

Extensive discussion of the consumer format suggestion from @earth2marsh . In summary:

• the Learn project needs a glossary of terms, including what a bundled/dereferenced API description is, and what publishing means
• we need better resources for users on what they are supposed to do with the version field, as most problems in this space stem from that
• further specifications for packaging APIs in a single, publishable unit may be forthcoming, and there was also some discussion of how those could be catalogued, discovered, and/or distributed. For further discussion, add your thoughts to future agendas.

[handrews]

Thanks for the notes, @lornajane !

I have just posted a PR for a glossary and a WIP guide to referencing at OAI/learn.openapis.org#69

I expect that the glossary will be split off to a non-WIP PR once folks agree on what should be in it, as it's more straightforward. The referencing guide also serves as additional background material for my detailed report on processing models which in turn supports the 1000-word summary.