►
From YouTube: Spec 3.0 - Discussion about Collection of Applications
Description
Related GitHub issue: https://github.com/asyncapi/spec/issues/658
A
So
this
is
just
a
public
discussion
about
one
of
the
one
of
the
issues
that
we
are
currently
or
one
of
the
feature
requests
we're
currently
evaluating
for
the
specification,
and
one
of
them
are
when
you
have
this
kind
of
system
with
multiple
different
applications.
How
can
you
define
what
is
it
within
your
system
and.
A
A
A
A
Sends
the
event
over
this
channel
once
a
comment
has
been
liked,
and
then
we
have
our
backgand
application
that
is
receiving.
A
A
Perfect
but
yeah,
the
syntax
is
a
little
bit
weird
because
I
adapted
some
of
the
changes
that
are
being
proposed
currently
for
the
specification,
but
it
is
to
make
it
a
lot
more
simple
to
understand
it's
just
as
this
application
receives
it
and
the
other
one
sends
it's.
It's
nothing
more.
B
Okay,
so
I
was
like
a
pretty.
I
was
thinking
about
what
operations
are,
so
you
clearly
that
it
is
a
new
specification:
okay,
yeah
yeah,
exactly.
A
So
it's
in
order
to
enable
reusability
of
channels
we
have
there's
a
proposal
of
introducing
this
operations
concept,
which
is
like
I
want
to
do
this
operation
over
this
specific
channel.
That
is
all
this
is,
and
the
reason
I
included.
This
is
because
it's
more
easy
to
comprehend
in
terms
of
instead
of
publish
and
subscribe,
because
it
has
a
lot
of
confusion
involved.
A
A
A
A
B
Yeah
so
like
we
are
just
we
have
this
file
in
which
we
are
defining
what
services
we
have
like,
for
example,
let's
say
in
social
media
service
we
have,
for
example,
let's
say
backend
and
front
end,
so
we
are
just
putting
them
in
this
file
yep,
exactly
okay,
okay,
so
like,
and
what
is
the
use
case
for
this.
A
Then
we
have
in
this
case
frontend
and
the
same
goes
for
all
other
services
or
applications
that
you
have
that
interact
with
each
other.
How
can
you
like
the
use
cases?
How
can
you,
how
can
you
group
these
applications
together
to
form
a
system?
How
would
you
be
able
to
do
that
in
async
api,
for
example?
Should
you
be
able
to
do
that?
B
B
Yeah
and
do
we
have
some
kind
of
versioning
on
this
system
file
as
well
like,
let's
see,
if
I
add
something
on
the
backend
using
api
file,
so
should
we
update
the
some
kind
of
should
we
update
the
system
file
with
some
kind
of
version
as
well.
A
B
A
C
A
F
D
We
should
avoid
this
completely
right,
like
just
or
at
most
like,
for
instance,
like
we
just
accept
applications
and
if
applications
is
specified,
we
cannot
accept
channels
and
operations.
That's
the
only
thing
like
you
either
make
it
a
system
file
or
an
application
file,
but
not
both.
I
mean
that's
kinda,
fine,
like
it's.
It's
easy
to
understand,
but
yeah
like
nested
keys
like
inside
info
version,
is
not
mandatory.
Unless
no,
no,
that's
to
me.
That's
like
a
logo.
D
D
I
will
say
even
more
like
in
a
regular
async
bear
file
when
you
add
a
new
change
when
you
change
something
on
an
existing
file,
not
an
existing
channel
or
a
message,
an
operation
or
something
do
you
have
to
increase?
Do
you
have
to
change
the
version.
D
D
A
Don't
know
I
mean
it,
it's
that's
not
a
good
like
discussion
to
have,
but
for
like
for
now
version
is
there.
We
have
to
address
like
how
that
affects
it.
Right,
yeah,
because,
like
I
overuse
version
like
I
use
conventional
versioning
throughout
all
of
my
applications
but-
and
I
actually
use
what's
called
conventional
release
and
the
github
action
that
so
when
I
make
a
feature
to
backend,
it
automatically
bumps
my
vision
right,
okay,
but
it's
also
because
I
use
it
for
more
advanced
automation
later
down
the
line.
That
requires
my
application
to
have
a
vision.
A
D
D
As
as
it
is
right
now
like,
unless
I'm
I
mean
maybe
unless
I'm
wrong
here,
I
think
this
in
kpi
doesn't
define
what
this
version
means.
Maybe
let
me
just.
C
D
C
D
Right
so
I
guess
in
this
cases
it's
up
to
the
and
the
user
to
decide
if
it
gets
updated
on
them
right.
B
A
B
So
like
we
can
use
separate
versioning
for
system
file,
let's
say
initially,
it
should
be
1.0.0.
B
D
D
F
D
D
D
F
D
D
A
A
A
D
D
D
Then
it's
like
okay,
so
then
a
channel
like
comment
must
exist
on
the
context.
D
I
mean,
as
far
as
I
know,
all
the
requests
we've
got
so
far
have
been
around
people
wanting
to
have
like
a
menu
of
channels
and
servers
or
brokers
right.
A
D
A
If
but
if
you
don't
have,
if
you
don't
have,
for
example,
this
some
keyword
that
reference
back
to
the
system
context,
you
wouldn't
be
able
to
use
this
async
api
file
on
its
own,
you
would
have
to
use
a
play
for
the
system
right,
yeah.
D
That's
what
I
was
saying
like
like
comment
channel,
doesn't
spread
this
file
definition.
Yes,
it
doesn't
exist.
That's
why
you
need
the
context
or
you
need
to
about
either
have
channels.
I
don't
know.
Maybe
channels
can
be
either
a
string
or
a
map,
and
if
it's
a
string,
it
will
reference
the
file
with
all
the
definitions.
D
D
You
know
what
I
mean
that
another
thing
that
we
can
do
is
that
on
the
well:
it's
actually
similar
like
on
the
backend
file
and
on
the
frontend
file.
We
have
channels
column
and
then
a
string
which
is
actually
a
dollar
graph
right.
D
D
So
it's
only
that
you
have
to
provide
this
with
channels
and
and
servers
and
so
on,
like
it's
a
more
granular
control
but
yeah
that
can
end
up
badly,
because
you
can
have
channels
pointed
to
one
system
and
servers
pointing
to
analysis.
D
Yeah,
no
of
course,
but
then
you
need
to
you
need
to
have
the
comments
like
a
comment
like
the
name
right.
It's
not
that
bad,
but.
A
D
A
A
For
sure
you
can
use
system
to
define
these
things,
but
you
can
also
do
it
externally
and
like
through
another
file.
It
can
be.
You
can
even
do
comment
like
that
yaml
right
right,
at
least
how,
with
the
current
reference
system
etc,
but
yeah,
I
I
can
understand
if
somebody
wants
to
define
stuff
from
this
system
perspective
like
this
and
and
not
do
this.
E
A
D
A
A
Yeah,
like
you,
can
define
this,
however,
you
like
through
whatever
means
necessary,
if
you
want
it
in
a
database
that
groups
these
two
application
files
together,
you
do
it
through
a
database.
You
can
use
a
normal
directory
that
if
the
two
files
are
within
the
same
directory,
these
two
are
within
the
same
system.
A
A
A
A
B
I
guess,
from
the
back
end
engineer
perspective.
I
have
to
also
look
at
the
front-end
file
as
well
right
like
how
does
the
front-end
file
work
and
what
kind
of
messages
it
sends
so
isn't
that
I
guess
bad
thing
or
like
he
does
have
to
go
to
go
out
on
his
way
and
to
see
the
front-end
file
how
it
works.
C
A
What
you're
doing
right,
so
you
are
receiving
you're
receiving
over
this
channel
an
event.
D
Also,
let's
not
confuse
like
the
fact
that
you're
receiving
a
channel
doesn't
mean
that
the
other
side
is
sending
you
to
this
channel
right.
So
there
might
there
may
be
systems
in
the
middle
doing
some
routing
some
kind
of
routing,
so
the
front
end
might
be
something
here:
there's
a
system
in
the
middle,
doing
some
routing
and
then.
C
D
D
So
the
fact
that
you
listen,
let's
say
on
a
on
a
channel
doesn't
mean
that
people
can
publish
to
the
channel
to
communicate
with
you.
Maybe
they
are
publishing
to
a
different
channel
and
there
is
some
kind
of
routing
system
in
the.
C
D
Making
it
work
so,
let's
say
or
multiple,
not
just
one,
so
with
some
kind
of
business
logic
and
so
on
so
yeah.
The
fact
that
you
listening
to
a
channel
doesn't
mean
that
people
will.
D
So
that's
why
I
mean
I
want
to
clarify
this
because
maybe
front
end
might
not
be
sending
or
you
don't
have
to
listen
where
phone
where
front
end
is
sending
because
maybe
you
don't
have
permissions
to
listen
there
I
mean
when
it's
an
http
or
websocket
api
yeah.
That's
it's
clear!
It's
a
point-to-point,
communications
kind
of
server,
that's
easy,
but
yeah!
Another
system
is,
it
might
not
be
the
case.
D
A
F
A
To
understand
how
the
content
like
who
are,
who
are
the
team
that
are
behind
the
front
end,
for
example,
or
whoever
interact
with
me
through
this
channel,
whatever
that
might
be,
it
might
be
a
gateway
like.
However,
this
this
system
was
structured,
that
would
probably
be
one
of
the
reasons
I
would
care
about
this
system
file
and
not
only
care
about
my
own
async
api
file.
D
Yeah,
that's
a
way
for
you
to
understand,
like
the
connections
right
like
how
your
system
is
interconnected,
but
again
like
let's
be
careful
with
this,
because
what
I
just
said
like
by
looking
at
the
other
files,
you
might
be
seeing
that
someone
is
publishing
to
topic
a
or
channel
a
right
and
you
think
it's
you
don't
care
because
you're
not
listening
to
its
channel,
but
there
is
some
esb
or
system
in
the
middle
that
will
route
from
channel
a
to
comment
like
channel,
and
you
will
not
be
able
to
perceive
this
relationship
because
we
don't
have
a
way
to
define
this
thing
yet
right
right,
so
yeah
so
yeah.
D
Now
maybe
this
will
be
defined
on
the
file
itself
on
the
back
end
or
front
end
or
whatever,
and
then
on
a
channel
the
channel,
maybe
the
channel
can
be
like.
Can
we
have
some
kind
of
rule
or
something
like
that?
D
That
let's
say
it's
like
I
don't
know
like
messages
published
into
this
channel,
might
end
up
might
end
up
into
these
three
different
channels
in
one
of
them
or
in
all
of
them
at
the
same
time
or
in
two
of
them
or
like
you
know,
like
you,
don't
know,
what's
going
to
happen,.
D
A
D
Or
multiple
yeah
and
there
can
be
like
business
rules
like
from
day
from
this
day
to
this
another
day
or
from
this
hour
to
this
other
hour
every
day
wrote
these
messages
to
this
other
channel
and.
D
The
only
thing
that
we
could
do
maybe
is
allow
for
expressing
that
this
message
might
be
routed
to
a
set
of
different
channels,
or
we
don't
know
the
channel
in
advance,
so
it
might
be
routed
somewhere
in
case
it's
useful
information.
A
Do
we
see
any
like
not
consequences
but
like
any
negative
sides
of
of
allowing
like
from
the
engineers
perspective?
Do
we
see
any
negatives
regarding
like
defining
it
through
a
simple
applications?
Keyword
here
still
do
I
have
any
negative
side.
D
Yeah,
like
it's
eccentric,
it's
a
central
place
where
you
define
all
the
or
I
mean
that
you
have
to
go
and
update.
Whenever
you
make
a
change
in
your
file,
you
have
to
go
and
update
the
system
file
right
or
at
least
re-evaluate
it.
So
you
know
because
it's
gonna
it
needs
to
be
updated
right,
because
these
dollar
graphs
need
to
be
resolved.
D
So,
even
though
the
change
the
file
doesn't
change,
you
need
to
reevaluate
the
dollar
address
and
apply
them
just
so
you
get
the
new
one
right,
but
yeah
like
I
think,
that's
a
problem
of
the
tool
there
like
depends
on
what
are
you
going
to
use
the
tool
for
the
the
system
for,
for
instance,
if
you're
gonna
use
it
for
drawing
a
real-time
map?
Real-Time
diagram
on
a
screen
right,
then
yeah?
C
D
A
All
right,
we
have
less
than
a
minute,
because
I
can't
make
any
meetings
longer
than
40
minutes,
so
we
are
cutting
it
shortly.