Spec meeting, 16:00 UTC Wednesday March 25th 2026

[asyncapi-bot]

Meeting Info	Details
Purpose	https://conference.asyncapi.com/
Time	16:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	YouTube Playlist.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

Agenda

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. 3.1 out and some followups needed Work on 3.1 release spec#1176
3. Continue with:
   • Documenting channels with late or out-of-sequence events spec#1143
   • Support AND logic for multiple security schemes in AsyncAPI 3.x spec#1129
   • Discriminator support to be aligned with OAS3 spec#1073
4. Hope we still have time to talk about feat: add CloudEvents Message Traits as a component spec#1161 and even start some convo about CloudEvents
5. Q&A

Notes

Add notes here after the meeting.

[derberg]

Recording: https://www.youtube.com/watch?v=ku-WyyCT9I8

Meeting notes:

• @derberg will jump in April into followup improvements from Work on 3.1 release spec#1176
• @derberg to check if we can complete docs: convert markdown anchors to kebab-case spec#1148 without the initial contributor
• @derberg will check refactor(converter): make file conversion functions async spec#1186
• @fmvilas @char0n @dalelane please look into Handling null values in the trait merge mechanism spec#1178 and share your opinion
• feat: Add AND logic support for multiple security schemes (#1129) spec#1135 (comment) proposal (AND in security scheme) can continue towards stage 2
• Discriminator support to be aligned with OAS3 spec#1073 (discriminator pro support) needs more discussion and actually more people to join it, so we can clarify the cons (which is basically "what about schemas other than JSON Schema based). Atm @derberg is not eager to champion that topic. More input needed.
• @dalelane can continue further with Documenting channels with late or out-of-sequence events spec#1143 just need to take into account initial feedback
• Moving Proposal to add official CloudEvents Traits to the AsyncAPI ownership spec-json-schemas#623 (comment) to a different repo to move forward with idea of official artifactory of the AsyncAPI community. First will be an official trait for CloudEvents. @fmvilas @char0n @dalelane please look at it and share your opinion