►
From YouTube: AsyncAPI SIG meeting 5 (Apr 2, 2019)
Description
This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #5.
Attendees:
- Dirk Rejahl
- Emmelyn Wang
- Fran Méndez
- Jonathan Schabowsky
- Michael Davis
- Raisel Melian
Moderation:
- Fran Méndez
Agenda:
* AsyncAPI 2.0.0-rc1, what's missing?
* Roadmap to AsyncAPI 2.0.0 release.
* Q&A
B
A
A
C
A
Know
telling
openly
everyone
hey,
you
can
come
here
and
then
uses
this
back,
and
let
me
know
what
you
think,
for
instance,
James
Higginbotham
already
did
he
hear
the
opener
a
bunch
of
issues
all
related
to
documentation,
but
they
actually
important
and
and
now
that
and
regarding
documentation,
that's
something
that
I
wanted
to
clarify
as
well
right
now.
The
only
thing
that's
done,
let's
say
is
the
spec
I
know,
there's
nothing
to
help
anyone
getting
started
with
version
2,
so
I
understand.
A
To
be
honest,
it's
it's
already
done
it's
already
on
the
on
the
website,
repo
I
added
it
to
the
website.
So
if
any
of
you
can
please
review,
especially
especially
my
wording
and
my
English
I
was
not
feeling
inspired
this
day,
so
so
that's
what
that
would
be
amazing
and
and
also
if
anyone
has
ideas
and
what
what
explain
what
would
be
nice
to
have
as
a
mini
tutorial
of
something
that
takes
like
five
minutes
to
read
and
into
and
to
apply
it
somewhere.
A
C
A
It's
not
match,
but
this
is.
This
is
the
kind
of
things
that
I'm
talking
about
like
we
have
to
change,
or
it's
the
minute
thing.
It
would
be
nice
if
we
could
explain
somehow
a
so.
This
is.
This
is
how
you
make
great
from
version
one
to
version
two
or
even
provide
the
script
at
some
point,
so
you
can
run
the
script
and
migrate
your
version,
one
documents
to
person.
That
would
be
amazing,
but
it's
a
person
and
regarding
documentation
that
would
be
us.
We
have
the
we
have
the
the
changelog
with
all
the
details.
A
We
also
have
the
github
commit
history,
but
this
is
I.
Don't
recommend
I
actually
took
this
change,
look
from
the
github
commit
history
and
it's
it
can
be
a
pain
so
so
yeah.
Starting
from
this
change
look
it
would
be
nice
to
read
something
more
consumable
than
saying
right
and
what
else
yeah
regarding
features
for
question
two,
there
are
still
two
things
missing
from
that
are
not
implemented
in
the
spec
because
they
are
not
part
of
the
spec,
but
they're
they're
gonna
be
part
of
person
too.
A
So
one
is
over
lace
overlay
for
those
who
know
Ronald
it's
a
feature
of
Ronald
that
it's
very
useful.
It
allows
you
to
overlay,
I
think
APA
documents
in
this
case,
and
so
you
can
replace
things,
and
this
is
very
useful
for
translations
or
for
API
management
solutions
where
you
have
to
change
things
in
the
document
on
the
fly
at
the
runtime.
So
this
these
kind
of
things
and
the
other
one
that's
missing
is
is
extensions.
Catalog,
so
extensions
catalog
is
is
something
that
we're
still
drafting
how
it's
gonna
work.
A
A
Obviously
it's
not
mandatory,
like
you
can
have
a
next
tension
which
is
not
on
the
on
the
on
the
central
repository
or
in
the
in
the
catalog,
but
if
we
could
have
a
place
where
we
can
share
these
things,
yourself
would
be
awesome
plus
because
I
mean
because
then
that
helps
standardizing
things,
that
the
specification
doesn't
provide
yet
and
that
will
help
us
as
well
understand
how
people
are
using
async.
Api
and
what
they
want
to
do
with
async
API
and
probably
incorporate
things
in
person
3
right.
A
So
that's
that's
the
whole
idea
plus
then
there's
something
new
called
protocol
link
for
objects,
and
this
is
protocol
specific
information
which
is
not
part
of
the
spec,
but
the
spec
provides
a
way
for
you
to
specify
this
protocol
specific
information,
and
these
aren't
gonna
be
on
the
under
catalogue
as
well.
So
in
the
catalog
you
will
have
specification
extensions,
X,
whatever
and
protocol
team
objects,
which
we
will
provide,
at
least
at
the
the
most
common
Protocol's
right,
like
Kafka,
h-2b,
WebSockets
and
all
of
this.
A
A
So
the
roadmap
regarding
the
roadmap
for
for
the
Ison
KPI
aggression
to
release-
that's
not
clear,
I
mean
III,
have
the
the
milestones
clear,
but
I
don't
have
the
times
clear
and
I
explain
why?
So
right
now
we
open
the
review
period,
but
we
don't
know
yet
how
many
feedback
we're
gonna
be
safe
right
and
how
many
things
we
will
have
to
change
from
the
spec
because
of
this
feedback,
because
we
don't
know,
we
will
see
it.
Obviously
there
so
there's
a
deadline.
A
If
you
want
I'm
planning
to
have
I
was
I
was
planning
to
have
May
first
as
the
deadline,
but
it
may
be
too
soon.
I
don't
know.
Let's
see
depends
on
how
the
feedback
is.
If
there
are
many
things
that
will
require
changing
that
the
spec
completely
right,
then
in
this
case
we
will
have
to
wait
more.
We
would
have
to
postpone
it,
but
I
would
like,
as
James
said
once
is
the
version
to
a
facing
convene
is
gonna,
be
out
for
quite
some
time.
Let's
make
sure
that
it
is
good
enough.
A
D
A
I
was
planning
on
announcing
it
on
Kefka
summit,
but
I'm
not
sure
if
I
will
be
able
to
do
it
or
not.
Yet
so,
I'll
tell
you
more
following
weeks,
but
I
think
it's
a
it's
a
good
idea,
and
probably
we
even
even
though
we
might
want
to
announce
it
for
cucum
Europe.
We
will
want
to
announce
it
before
right.
A
Know
about
it,
it
will
be
too
late
to
schedule
a
call
with
them
or
to
schedule
a
meeting
here
in
Barcelona
with
them
right.
So
that's
why
I'm
gonna
take
advantage
of
people
coming
to
Barcelona
and
announcing
it
announce
it
before
so
I
can
take.
I
can
take
advantage
of
scheduling
meetings
here
in
West,
LA
and
and
probably
recordings
video
recordings
interviews
and
this
kind
of
stuff.
So
on
too
many
fronts
regarding
tooling.
A
So
today,
great
news
is
today:
I
managed
to
compile
the
parser
that
we
created
in
go,
or
at
least
what
we
have
so
far.
I
compile
the
person
for
many
different
platforms,
say
window
windows,
linux
and
even
Android
in
areas,
but
I'm
not
gonna,
put
some
any
effort
there
yet,
and
so
things
are
progressing
well.
A
I'm
also
almost
done
with
the
wrapper,
with
the
nodejs
wrapper
around
this
C
library.
You
know
this.
You
live
right
that
is
produced
from
the
go
library.
This
is
its
it.
It
sounds
like
a
like
a
very
complicated
build.
You
can
say
the
stuff,
and
on
top
of
that
I
have
a
friend
of
mine
who's
gonna,
be
joining
the
team
in
the
next
weeks.
A
He's
an
expert
in
go
so
you'll
be
able
to
help
us
much
better
he's
already
doing
some
stuff,
but
he
will
be
joining
the
the
next
call
for
sure,
and
he's
probably
I
mean
I
asked
him
depends
on
the
time
he
has
is
gonna,
be
taking
the
the
lead
on
the
tooling
development,
so
so
yeah
I'll
introduce
him
next
week.
Just
for
you
to
know
it's,
and
so
things
I'm
trying
to
do
to
make
things
to
move
faster
and
and
and
so
they
don't
depend
so
much
on
you
right.
A
A
That's
fine,
but
you
know
I
wanted
to
become
a
community
project,
and,
and
so
let
me
know
what
what
do
I
have
to
do
for
you
to
participate
it
to
be
and
to
make
it
easy
to
to
participate
and
I
need
to
jump
to
this
cold
and
for
me
to
get
something
to
the
rest
of
the
group.
So
I
think
Michael
has
some
stuff
to
tell
us
right.
Michael,
yes,.
E
Can
you
hear
me
yeah
very
low,
but
oh
yeah
I'll
try
and
turn
it
up
a
bit
I'm
using
a
different
heads
at
this
time
and
I:
don't
have
a
camera
today,
I'm,
sorry
but
okay,
so
I
haven't
done
too
much
yet.
But
what
I
did
do
a
couple
of
nights
ago,
I
I
forked,
a
bunch
of
the
repos
I,
got
into
the
parser
project
and
just
tried
to
get
that
up
and
running,
and
it
was
remarkably
easy.
You
know,
I
just
noticed.
Yeah
I
had
a
couple
of
missing
packages.
E
I
just
had
to
run
the
Go
Get
Command
on
three
things,
and
then
it
just
worked.
So
you
know
there
wouldn't
be
much
there
to
put
in
for
developer
documentation.
I
guess
you
know.
If
somebody
is
working
on
that
one.
Presumably
they
know
go
well
enough
to
know
how
to
install
go
and
such
packages
that
are
missing
so
I
didn't
really
find
any
issues
really
worth
documenting
yet,
but
I'll
go
through
the
other,
the
other
repos
one
by
one
and
see.
If
there
is,
you
know
any
anything,
that's
worth
documenting,
I
guess.
E
The
question
I
have,
though,
is
that
what
level
of
understanding
do
you
expect
people
to
have
when
they
get
into
it
like,
for
example,
a
go
project?
Do
they
you
know?
Should
there
be
a
short
paragraph
about
how
to
install
go,
or
do
you
just
assume
that
hey
if
they're
there,
they
already
know
that
stuff?
You
know.
A
You
know
I
will
right
now
it
also,
it
all
depends
on
their
priorities.
Right
I
will
not
spend
so
much
time
right
now
documenting
how
things
still
go
and
all
these
things
like
we
can
assume
that
someone
using
the
goal
parser
knows
how
to
use
go
because
100%
of
these
people
will
be
just
asked
for
now.
So
so
I'll
probably
put
more
effort
in
developing
the
the
parser,
but
if
but
the
communication,
wise
yeah,
maybe
explaining
how
the
how
the
parser
is
structured
or
what's
the
architecture,
use
I
think
well.
A
I
I
added
that
technical
proposal
to
documented
to
the
Draper,
but
yeah
I
think
some
stuff
like
just
how
to
install
it
and
how
to
make
it
work.
I
mean
that
will
be
fine.
It
all
depends
on
on
the
on
your
preference,
actually
like
a
50.
If
you
prefer
to
be
writing
documentation
now,
it's
it's
okay,
I
think
it's
a
good
idea,
maybe.
F
Maybe
maybe
from
from
my
perspective
and
III,
try
to
be
I'm
coming
from
a
JavaScript
world
right,
so
no
js',
and
so
on
and
I
try
to
get
going
with
a
positive
product
and
I
actually
failed,
and
it
was
really
about
how
to
how
to
install
these
packages.
I
mean
I
was
looking
for
something
like
NPM,
which
makes
this
kind
of
challenge
is
very
easy
in
the
JavaScript
world
and
I
actually
couldn't
found,
find
anything
I
think
these
kind
of
hints
would
be
actually
quite
quite
useful.
Yeah.
A
A
We
now
have
modules.
Your
models
is
something
that's
built
in
to
go
as
a
anything
else.
You
just
run
go
run
or
go
build.
It
will
take
all
the
dependencies
for
you,
okay
and
that
that's
really
there.
So
it's
a
work
and
I.
If
I,
don't
if
I
recall
correctly,
you
were
trying
to
do
the
result,
and
so
there's
this
there's
a
guy
there's
a
guy.
A
F
A
No,
no,
we
we
have
this.
We
took
this
into
account.
The
problem
is,
and
probably
we
will
deliver
at
no
GS
person
soon,
a
parallel,
not
yes
person
to,
but
the
problem
is
that
we,
if
we
want
to
generate
the
parser
for
many
languages
and
that's
what
we
want
right
now,
because
people
are
asking
for
the
for
the
parser
and
in
Java
or
in
PHP.
You
know,
I
know
in
many
languages
we
cannot
afford.
F
No,
no
I
I
get
the
the
idea
why
using
go
I
get
this
from
what
I'm
trying
to
say
was
actually
looking
into
these
kind
of
implementations
and
basically
adapted
their
way
of
how
they
implemented
the
algorithm
or
which
algorithm
they
actually
implemented,
and
then
basically
do
the
same
thing
and
go
because
I
saw
some
discard
discussions,
whether
you
can
do
a
kind
of
global
change
or
these
kind
of
stuff,
right
and
I
think
there's.
There
are
some
comes
some
quite
good
term
javascript
libraries
to
look
into
how
they
did
you.
A
Because
it's
it's
actually
the
best
one
right
now
so
make
sense,
and
just
for
the
record
the
other
day
I
was
playing
a
little
bit
with
the
generator,
which
is
the
one
which
put
in
rates
the
documentation
and
the
code
and
just
to
see
how
difficult
it
will
be
to
adapt
it
to
worse
into,
and
it
took
me
like,
like
two
or
three
hours,
to
have
something
decent
with
no
genius.
This
is
done
in
dodgiest.
A
It
took
me
yeah
like
two
or
three
hours,
obviously
missing
some
features
from
from
from
person
too,
but
the
same
features
said
from
version.
One
I
was
able
to
replicate
it
on
person
to
very
easily.
So
that's
most
probably.
What
will
we
will
provide
initially
for
people
to
use
it
on
the
on
the
editor
as
well
right?
A
E
Yes,
I,
like
I,
said
so
far.
There
wasn't
really
much
to
discuss
about
the
parser.
You
know
getting
up
and
running.
That
was
really
easy,
so
didn't
have
any
issues
there.
But
if
you
like
a
look
at
the
other
repos
one
by
one
and
see
what
it
takes
to
get
to
the
point
where
you
can,
you
know
edit
code
build
it
run
it
unless
there's
something
more
urgent
or
important
that
you
want
me
to
work
on
a.
A
Little
bit
friction
here
and
there
the
problem
is
that
I'm
not
so
used
to
messaging,
which
I
don't
think
it's
your
cases.
It's
you
work
it.
So
that's
right,
but
I'm
not
familiar
with
with
messaging.
That's
that's
a
problem
or
I'm
coming
from
open,
API
and
I'm,
expecting
things
in
a
different
way.
I,
don't
know!
E
A
E
A
E
A
I
will
not
dive
to
match
in
tooling
right
now,
because
the
state
of
the
dueling
currently
is
is
very
poor
and
we
just
we're
just
starting
with
that.
So
I
will
not
worry
about
so
much
about
it,
but
more
about
probably
about
that.
The
specification
itself
like
so
how
how
to
understand
the
specification
right
writing.
E
A
If
the
specification
is
like
a
very
long
document,
but
nobody
wants
to
really
I
mean
I,
never
have
read
the
whole
document
myself,
I
go
from
time
to
time
to
one
piece
and
really
tan
and
I've
never
sit
down
and
start
reading
from
the
from
top
to
bottom
right,
because
this
is
huge
and
it's
boring
it's
a
reference
right.
It's
not
is
I
like
like
a
like
reading
a
phone
guy
right
so
sounds
like
it's
hard
to
read
now.
A
A
A
A
E
A
A
A
C
Guess,
with
stream
data
you
know
now
they're
part
of
us.
We,
it
sounds
like
they're
wanting
to
work
more
with
you
and
so
I'm
gonna
try
to
encourage
them
to
use
this
open-source
model
so
that
there's
kind
of
more
visibility
for
what's
happening
so
I'm,
just
gonna,
encourage
them
to
use
slack
and
to
you
know,
attend
and
to
contribute
in
the
open
source
way.
Is
that
a
good
idea.
A
A
C
A
A
A
C
It's
just
a
short
goal,
so,
for
example,
I'm
starting
to
I've
been
learning
go
just
at
the
very
beginning,
and
I
went
to
kind
of
a
casual
hackathon
with
women
who
code
and
they
had
about
eight
different
kinds
of
experts
there
on
different
topics
and
so
I
had
a
you
know,
specific
things,
I
wanted
to
learn,
Inga
and
so
for
three
hours
I
was
able
to.
You
know,
work
on
that
and
it
was
very
focused
and
I
was
able
to
get
the
things
done
that
I
wanted
to.
So
maybe
it's
something
like
that.
C
E
A
C
Yeah
I
think
I
feel
the
same
as
Michael
I
mean
I'm
coming
at
it
from
a
oh,
you
know,
pretend
I'm
an
API
product
manager
and
typically
everything
is
centered
around
a
spec
right.
That's
the
single
source
of
truth
and
pretend
I'm
an
API
product
manager
and
I'm
able
to
write
some
epics
and
features
and
stories
so
that
my
you
know,
hypothetical
development
team
can
create
and
or
consume
the
spec
so
that
that's
the
the
angle
that
I'm
looking
at
it
from
is
helping
the
business
side
adopt.
C
You
know,
be
champions
for
and
adopt
the
spec.
It's
it's
so
technical
that
I'm
trying
to
understand
how
to
communicate
the
business
value
and
and
I
think
there's.
You
know
so
much
business
value
and
I'd
like
to
get
better
at
communicating
that
and
showing
that
with
you
know
real
examples
and
the
and
impairing
the
business
side
with
architectural,
which
everyone
involved
is
really
good
at
the
architectural
and
I
hope.
I
can
contribute
to
you
know
the
use
cases
and
evangelize
about
them.
A
C
And
I
actually
have
a
couple,
because
you
know
because
of
this
dream
data
ax
way
sort
of
the
acquisition
they
talk
about
streaming
and
how
real
time
does
it
need
to
be
right.
So
there's
finding
you
know
financial
trading
aspects
and
there's
kind
of
some
standards
that
you
have
to
meet
globally,
but
then
you
might
not
need
as
real
time
of
a
streaming
for
other
situations
such
as
you
know,
social,
some,
social
aspects
and
so
there's
kind
of
like
this
spectrum
of
you
cases.
A
C
Know
I
try
to
explain
to
everyone
that,
oh
you
know
the
school
home
or
you
know
lambda
function.
These
are
related
to
a
sink
API,
that's
kind
of
the
gate.
You
know,
I
call
like
gateway
drug
or
the
entry
point
for
the
common
person
to
say.
Oh,
why?
Why
should
I
care
about
a
sink
API?
Oh,
did
you
know
IOT,
you
need
this
kind
of
messaging.
Api
is
to
be
able
to
have
successful.
Iot
ecosystems,
for
example,.
A
C
A
A
A
A
E
A
A
A
E
A
E
E
Should
read
it
because
because
that's
a
really
powerful
sort
of
I
guess
a
paradigm
of
of
event-driven
architecture
that
that
we
think
you
know
could
be
a
much
better
way
of
connecting
micro
services
and
rest
and
it
you
know,
really
centers
around
messaging.
So
you
know
there's
some
great
examples
in
there.
So.
E
C
C
E
A
C
E
A
A
E
D
C
A
B
C
I
did
have
one
short
thing:
I'll,
be
speaking
at
API
days
in
Singapore,
and
that
starts
off
the
whole
round
of
the
API
days.
Tour,
so
I'll
definitely
talk
about
async
API
and
make
sure
I'm
on
the
same
page
with
you
know
this
group
that
I'm
introducing
it
properly
over
there
they've
got
a
lot
of
kind
of
open
baking
standards
and
heavy
in
the
financial
sector,
and
so
you
know
I
would
like
to
mention
async
there.
So
I
just
thought
I
would
that's
a
April
night.
Well,
sorry,
I'll
be
leaving
April,
19th
and
I'll.
D
D
You
know
our
background,
if
you
didn't
know
anything
about
Sol's
like
our
biggest
arm
by
far
industries
financial
services,
so,
okay,
the
Barclays
standard
charter.
You
know
we
have
a
big
office
in
Singapore
because
of
financial
services,
and
so
our
field
sales
engineering
is
in
Singapore,
so
he
could
even
help
if
you
want.
You
know
it
provides
an
additional
financial
services
context
into
the
event
in
space.
Like
I.
Didn't
look
like
you
know
your
as
an
acquisition,
obviously
even
just
way
different
than
like
what
we
do
from
a
solace
perspective,
so
it.
C
D
D
Talked
to
your
partner
partnership
team
before
ax
way
about
you
know
doing
something
you
know
you
know
related
to
have
been
driven
in
this
space
as
well.
So
I,
don't
think
that
that
should
affect
any
of
that
anyway,
but
yeah
like
we
definitely
are
chock-full
of
financial
services,
use
cases
that
I
think
okay.