AsyncAPI open meeting, Tuesday June 8 2021 8AM UTC

[derberg]

This is the meeting for the AsyncAPI Special Interest Group (SIG). You're invited to join us and ask questions. The meeting takes place on alternate Tuesdays. Recordings from the previous meetings are available in this playlist on YouTube.

This time we meet at 8AM UTC

If you want to make proposals for the specification and/or the tooling, please reach out in our Slack workspace or just leave a comment below.

Join this mailing list to get an always-up-to-date invite to the meeting in your calendar.

Attendees

Join us if you want to know more about AsyncAPI! The meeting is open to the public.

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. @GeraldLoeffler - Support defining and referencing protocol headers
3. Place for your topic
4. Q&A

Notes

• Fran shared the current status of the 2.1 release. It is scheduled for June. Also plans on the next release that will happen in September.
• Gerald started a discussion about bindings and also the message headers:
  • contentType purpose and meaning
  • userId from amqp binding
  • HTTP binding headers and having common headers (for stuff like content-type and others)
  • correlationID and headers relation + how about the correlationId points to protocol-specific location (when we usually put protocol-specific things into bindings)
• Bindings JSON Schemas are ready, now they need to get integrated with the Parser so it can validate binding information properly. Reference issues are Parse and validate bindings parser-js#315 and [RFC] Support JSON Schema for bindings spec#507

Recording

https://www.youtube.com/watch?v=DLgWdC1mHJI

[GeraldLoeffler]

I am confused about message headers in AsyncAPI message objects and message binding objects. I think there's an omission in the spec that causes my confusion, and so i've created this issue: asyncapi/spec#551 I propose to discuss this topic in this meeting, if possible.

[jonaslagoni]

@GeraldLoeffler added to the agenda 🙂