►
From YouTube: CNCF Serverless WG Meeting - 2018-03-20
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
B
A
E
A
You
what
let
me
go
ahead
and
share
my
screen,
just
we're
all
look
at
the
same
thing.
A
So
how
do
you
guys
want
to
proceed
honestly,
while
yesterday's
conversation
was
really
really
good?
I
do
kind
of
feel
like
we
could
have
gone
a
little
faster.
We
didn't
necessarily
try
to
wordsmith
every
single
word
and
rather
try
to
look
at
more
broader
picture
that
you
are
trying
to
paint
there
I
agree.
A
C
I'm,
so
sorry,
I
didn't
run
yesterday's
meeting
I
post
some
comments.
Some
suggestions
on
this
PR.
A
C
A
C
B
Okay,
so
four
to
Kathy's
comment
here
for
her
example,
one
event
is
submitted
by
the
motion,
detector
and
the
intermediate
gateway,
and
it
does.
The
transformation
of
the
requests
into
HTTP
is
the
gateway
is
an
actor
in
here,
but
is
not
changing
the
event
person.
It's
not
the
event
producer.
It's
basically
just
a
translator,
that's
transparent.
B
In
a
second
example.
That's
two
in,
in
my
view,
that's
two
distinct
flows.
You
have
a
you,
have
a
event
that's
being
triggered
by
the
the
camp,
but
the
motion
detector,
the
motion,
detector
that
goes
and
trigger
something
in
a
cloud
platform
or
our
source
doesn't
and
something
in
the
cloud
platform.
The
coupling
reacts
to
that
by
emitting
in
event.
These
are
two
distinct
events,
in
my
view,.
C
Okay,
yeah
I
think
you
know
I
think
I
agree
with
that
too.
I
think
Sarah's
point
is
same
right,
so
I
think
here
I
think
the
key
point
is
you
know
what
is
meant
by
semantic
meaning
change
change,
a
semantic
meaning.
If
we
can't
clearly,
you
know
define
that
that
would
be
good
on
this
side.
These
two
are
just
examples
right.
There
are
other
examples,
so
if
we
can
define
that
clearly
that
people
can't
you
know,
you
know
can't
derive
say
which
is
a
producer
which
is
then.
B
I
could
turn
I
can
turn
the
the
write
up
that
I
created
like
this
page
I,
can
only
easily
turn
it
into
50.
I
have
I
have
plenty
of
examples
from
from
every
part
of
this
every
part
of
the
write-up.
It's
just
not
clear
how
much
that
contributes,
because
we
are
looking
for
something
that
kind
of
frames
the
discussion
and
we're
not
making
that
part
of
the
normative
part
of
the
spec,
so
I'm
actually
very
happy
to
write.
B
C
I
I
think
you
know
the
point
you
said
you
know
these,
such
as
suppose.
We
do
not
mean.
My
point
is
that
we
do
not
need
to
keep.
You
know
dive
into
each
example.
There
will
be
a
lot
right,
but
I
would
like
we
define
the
semantic
change,
a
semantic
meaning
clear
in
the
more
clean
way.
So
now
is
you
know,
I
think
we
can
define
that
I.
Think.
B
There's
no
word
in
here
which
allows
semantics
to
be
even
changed
like
this
is
something
this
is
something
where
it's
pretty
clear.
That
in
events
is
originates
from
place
and
then
get
sampled
by
someone
and
gets
forwarded
by
someone,
but
no
one
anywhere
is
allowed
to
change
the
semantics
of
that
event.
So
I.
A
Of
Kathy
I
wonder
if
it
would
be
useful
if,
rather
than
rather
than
talking
about
what
you'd
like
to
see
in
terms
of
changes,
could
you
actually
propose
some
actual
text
that
you
want
to
see?
There
are,
or
minor
wording
changes
to
to
get
this
point
across
because
I?
Do
you
think
you
guys
are
agreeing
yeah.
C
Okay,
I
think
that's
fine
I
can
try
to
propose
them.
Yeah
I
think.
The
key
point
is
in
you
know,
is
how
we
define
the
change
of
semantics,
like
even
for
heb,
API
gateway
right.
Different
implementation
could
do
differently.
Some
implementation
might
not
change.
You
know
the
what
we
what
we
defined
semantics,
but
some
implementation
will
change
it
quite
a
lot.
So
there
is
a
as
also
okay
anyway.
I
think.
My
point
is
that
we
need
to
define
that
otherwise
people
might
reach
might
reach
different
conclusion
about.
You
know
which
is
producer
for
some
scenarios.
C
F
Do
feel
like
this
point
is
the
been
the
biggest
confusion
in
our
discussions
over
the
past
month,
and
so,
if
anywhere,
we
might
add
a
little
more
narrative
to
explain
that
I
think
this
would
be
the
section
so
I
think
Kathy.
If
you
can,
you
know
I
suggested
I
was
the
one
who
used
the
word
semantic
if
that
word
isn't
working
for
you.
Please
just
provide
like
duck
suggestion
if
you
could
propose
a
modification
or
addition
to
this
section
that
would
clarify
it.
That
would
be
great.
Okay,.
C
B
B
C
Okay,
so
so
my
only
my
only
concern
here
is,
you
know,
sometimes
you
know
from
a
summary
scenario
right.
It
would
be
like
some
raised
platform
would
provide,
you
know,
there's
place
framework,
and
then
there
are
service
applications
which
use
a
platform.
B
F
A
C
Yeah,
but
so
I
just
feel
you
know,
applications
right
people
could
mean
on
your
a
in
the
surveys
scenario.
Application
means
some
software,
the
people
development
that
will
use
the
surveys
platform
which,
like
you
know,
either,
is
Google,
Google,
proud
or
like
Amazon
or
Microsoft
Azure,
so
that
I
mean
the
way
I
think
you
know
this
from
what
we
have
been
discussing.
We
call
that
some
of
this
platform,
then
the
the
salt.
Well,
that's
that's
viewed
on
top
of
that
platform
to
form
a
new
application
or
new
service,
that's
called
the
applications
of
this
application.
D
Sorry
Kathy
what
I'm
taking
away
from
all
this
is
the
the
word
here
right
for
individuals
who
don't
have
the
context
of
those
of
us
who've
been
on
the
calls
or
just
take
it
from
the
standpoint
of
just
someone
who's
reading
through
the
spec.
For
the
first
time
like
this,
this
might
rub
someone
the
wrong
way.
What
I
think
we're
leaning
towards
is
even
making
it
more.
D
F
D
C
D
C
D
C
C
C
B
B
C
That's
okay.
We
currently
right,
so
we
need
some.
So
this
is
a
scenario
like
you
know,
for
example,
if,
like
there's
a
burst
of
events,
and
then
you
know
that
event
would
trigger
many
instances
right.
If
that
instance
is
an
echo
workflow
that
many
not
was
perhaps
there,
you
know
if
the
second
event
comes,
then
how
doing
a
burst
of
second
event
comes
from
any
of
that
events,
how
which
one
which
instances
that
which
workflow
instance
that
new
event
should
be
sent
to
so
on
correlation
cocaine,
their
correlation
mechanism?
C
C
That
should
be,
you
know
so,
okay,
so
the
answer
the
where'd
that
come
from
so
for
different
scenario,
right
that
correlation
token
could
be
different.
As
we
said
you
know,
I
gave
it
just
one
example
there.
There
are
other
examples:
I
get
ones
them
in
my
previous
presentation
in
that
in
a
burglary
and
detection.
So
that
event
correlation
cousin
could
be
the
house
address.
C
So,
if,
like
you
know,
the
service
platform
receive
motion,
detection
event
or
a
door
open
event,
they're
the
same
event,
it's
a
door
open
event,
but
inside
that
event
that
event
and
information
that
invents
information
carrier
a
correlation
token,
a
unique
identifier
which
would
be
that
could
be
how
the
house
address.
So
we
know
which
one
is
that
that
information
needs
to
be
in
the
event.
Yes,.
B
The
reason
why
I'm
asking
that
question
is
is
whether
that
correlation
information
is
so
generic
that
it
would
have
to
be
in
the
standardized
sets
of
properties
and
I'm
gonna
I'm
gonna
postulate.
But
that's
not
true
that
this
is
the
correlation
that
you're
seeking
it
is
an.
It
is
an
application
level
concern
that
is
specific
to
your
app,
where
you
have
a
set
of
events
which
are
emitted
from
multiple
related
contexts.
Where
you
define
the
relation
the
relationship,
and
then
you
tell
each
of
these
contexts
a
correlation
ID
ID.
C
So
it's
all
okay,
so
first
I
think
it's
very
the
you
know
a
scenario
that
involves
multiple
events
is
very
common.
It's
not
like
a
very
rare
is
a
common
scenario.
Yes,.
B
A
B
C
B
From
storage
service
events,
the
the
commonality
around
storage
services,
events
are
simply
around
a
container,
so
you
have
a
storage
container
that
is
emitting
events,
you're
interested
in
all
the
events
from
that
storage
container,
and
then
each
of
these
events
from
the
storage
container
and
have
a
further
discriminator,
which
then
tells
you
what
what
exact
object
inside
of
that
service
container
just
race.
You
that
event.
C
Okay,
so
this
is
a
bit
different,
so
so
you
are
talking
assal.
This
events
are
from
the
storage,
so
your
your
system
on
some
other
fields,
a
column
number
to
distinguish
them.
Okay,
whatever
number,
whatever
that
storage
ID.
So
here,
I'm
talking
about,
is
multiple
event,
they're,
not
stories
event.
For
example,
a
scenario
could
involve
a
storage
event
and
the
mother,
like
API
gateway
event,
is.
D
A
So,
just
for
a
second
I
make
sure
I
understand
something
cuz
I
think
Sara
was
saying
in
the
chat:
I
think
you
guys
are
agreeing
and
I
think
Clemons.
You
actually
might
be
okay
with
that
text
that
she's
proposing,
but
you
just
want
to
understand
whether
cap
is
looking
for
additional
attributes
to
be
added.
B
A
B
C
A
B
So
I'm
here
introducing
the
notion
of
middleware
that
is
transfer
effect,
ly
transparent
to
producers
and
consumers.
So
it
plays
a
mediator
role.
That's
why
it's
middleware-
and
this
is
a
few
things
that
the
consumers
that
mostly
consumers,
are
interested
in,
where
consumers
having
are
having
requirements
and
so
I'm
expressing
here
requirements
really
that
stemmed
from
the
consumers
but
I
realized
middleware
in
that
list
and
say
enumerate
them
so
versus
management
of
many
concurrent
interests
as
consumers
for
one
or
multiple
classes
of
origin
in
context
of
events.
B
So
you
have
if
consumers
and
producers
who
progress
in
that
sense,
so
here
a
producer
is
creating,
is
sending
a
lots
of
events.
It
gets
a
lot
lots
of
interests
from
consumers
and
instead
of
having
to
deal
with
all
of
those
consumers
together
and
and
singly,
it
basically
delegates
that
management
of
all
of
these
interests
of
consumers
to
middleware
which
the
which
takes
care
that
for
it
second,
is
the
consumers.
B
All
of
these
consumers
are
given
the
opportunity
to
be
interested
in
the
class
of
events
or
in
certain
contexts,
but
then
that
context
itself
or
the
class
of
events
may
be
a
little
richer.
So
there
may
be
a
desire
to
go
and
filter
on
that
down
further,
and
so
that's
a
delegating.
That's
also
tassets
be
freaking
to
delegated
into
middleware.
To
going
out
of
a
initial
selection,
that's
built
built
over
categorization
that
you
want
to
go
and
filter
out
specific
events,
very
common
processes.
B
Then
you
might
in
some
cases
you
might
have
a
middleware
which
does
transcoding
example.
That
I
gave
here
is
that
you
event
arrives
in
JSON
and
say
you
want
to
have
delivered
a
message
back.
That's
something
that
some
middleware
middlewares
do
transformation
or
you
know
for
or
you
get
just
simply
get
compression
or
over
the
wire,
a
transformation
that
shaves
the
event
structure
like
mapping
from
proprietary
format
to
cloud
events
while
preserving
the
identity
and
semantic
integrity
of
the
event,
also
very
common
tasks
of
middleware.
B
To
give
you
a
semantics,
preserving
transform
from
one
schema
to
the
next.
You
also
may
get
pushed
style
deliveries
in
interest
of
consumers,
so
you
give
the
you
hand
out
the
the
event
to
the
middleware
in
the
middle.
Where
then
it
takes
care
of
delivering
that
out
to
interested
consumers
with
retries
and
all
those
whistles.
It
might
store
events
for
eventual
delivery.
If
the
consumer
is
currently
offline
or
if
there
shall
be
a
delay
for
that
delivery,
not
rare
and
then
the
middleman.
B
G
B
So,
in
the
sense
that
those
needs
there's
a
few
things
in
middleware,
we
need
first
of
all,
it
needs
to
have
a
metadata
discriminator
which
allows
it
to
credit
to
provide
a
coarse-grained
selection
of
events
that
consumers
can
register
interest
in.
So
if
you
want
to
subscribe
to
a
set
of
events,
you
need
to
have
a
an
initial
pre
grouping.
If
you
want
to
build
something
that
is
reasonably
scalable,
that's
what
I
mean
with
the
classification.
B
That's
actually
motivating
the
classification,
it's
also
motivating
more
or
less
the
the
context
and
then
typically,
if
you
have
context
like
the
example
that
I
gave
with
with
the
room
and
the
building
and
the
with
room
floor
building,
these
are
real.
You
know,
structure
context
that
you
will
be
interested
in
depending
on
what
your
applications
is.
B
If
you
wanted
thorns
and
and
kind
of
filter
in,
but
then
there
is
inside
of
that
classification
or
instead
of
that
broader
context,
it's
your
selecting
it
and
getting
all
the
events
from
the
middle
of
where
then
need
a
further
discriminator,
the
most
distinguishing
the
subject
of
a
particular
event
for
that
of
the
subject
of
a
particular
event
of
that
class,
which
means
you're
subscribing
to
events
of
the
storage
container,
which
is
the
first
one.
That's
the
classification
or
context.
B
B
You
need
to
have
a
because
you
want
to
you:
don't
want
to
know
that
it
comes
in
this
application
JSON
and
you
want
to
send
it
out
as
as
message
pack.
So
you
need
to
have
an
indicator
for
this,
and
then
you
also
need
to
have
an
indicator
for
the
structural
layout
schema
for
the
amended
its
data.
If
you
want
to
do
a
transform,
you
need
to
know
what
the
input
schema
is
and
then
he
will
also
declared
with
the
output
schema.
If
you
are
a
schema
person.
B
Whether
an
event
is
available
for
consumption
via
middleware
is
really
a
delegation
source
of
the
producer,
so
it
it's
it's
it's
in
the
hands
of
the
producer,
how
it
makes
its
events
known
and
a
producer
always
kind
of
is
in
control
of
saying
I
deliver
my
events
in
the
following
way
and
either
you
come
here
in
quotes
to
whatever
the
producer
sits
or
the
producer
basically
points
people
also
by
a
documentation
to
a
middleware
where
that
holds
events
available.
On
behalf
of
that,
for
you,
sir
okay.
A
A
Before
I
go,
I
have
a
request
for
you
guys
if
I.
If,
after
this
call,
we
don't
have
significant
progress
yet
on
the
definition
of
source,
can
we
set
up?
Another
call
either
continue
this
one
for
long
people
can
stay
on
or
set
a
brother
call
for
tomorrow
and
just
paste
that
information
into
the
normal
agenda
doc
and
send
that
a
note
or
something
so
people
know,
because
even
if,
even
if
we
can't
get
agreement
today,
I'd
like
to
see
if
we
can
make
more
forward
part
of.
F
A
A
Oh
yeah
I'm
not
I'm,
not
so,
obviously,
if
we
come
up
with
if
we
honor
the
call
tomorrow
and
actually
come
up
with
a
most
spectacular
definition
of
source,
it's
too
soon
to
vote
on
a
Thursday,
but
that
doesn't
mean
we
can't
make
forward
progress.
So
people
can
be
looking
it
over
in
preparation
for
the
following
weeks.
Call
I
just
don't
want
to
lose
the
message.
A
Yeah
I
said:
if
you
guys
finish
the
stock
or
did
this
PR
and
then
start
happy
and
start.
The
discussion
on
source
I
want
to
keep
the
momentum
going
and
say:
let's
have
another
call
tomorrow
and
see
how
much
we
can
plow
through,
but
I
need
to
drop
off.
So
just
does
that,
like
I
said
just
if
you
have
another,
if
you
set
up
another
call,
please
just
let
people
know
about
it,
so
people
can
join
if
they
if
they
are
able
to
okay.
Thank
you
guys,
I'll
talk
to
you
later
Thanks
thank.
C
F
So
I
had
a
question
about
the
middle,
where,
if
you
can
I
just
jump
in
with
a
consumption
of
the
I
like
I,
like
what
you
said
about
the
like,
the
producer
decides
like
how
it's
going
to
communicate
and
we
know
how
it's
events
are
going
to
be
made
available.
I
think
and
there's
a
nuance
there,
which
is
that,
like
if
the
producer
talks
to
a
particular
middleware
like
in
your
presentation,
a
while
back
clemens
like
that
middleware
could
talk
to
another
middleware.
So
it's
not
really
smooth.
B
F
I
think
I,
just
maybe
that
could
be
clarified
a
little
bit
so
that
it's.
How
so
so,
I
think
that
basically,
the
eye.
F
To
separate
the
like
how
events
get
transported
right
from
what
the
event
needs
like
what
the
middleware
needs
to
be
about
the
event,
so
you
could
say
that
the
middleware
says
how
events
you
know
how
it
communicates
with
source
and
consumer
and
or
other
middleware
a
producer
determines
how
it
will
make
its
events
available.
I,
don't.
D
Cathy,
are
you
advocating
for
a
statement
where,
like
when
a
direct
route
from
producer
to
consumer
is
not
available
or
from
producer
to
destination,
is
not
available
that
the
producer
can
send
data
right
route
accordingly,
via
middleware
right
like
so?
Some
destination
has
to
be
at
least
acknowledged
on
the
envelope,
so
that
middleware
can
attempt
to
a
route
accordingly.
Actually.
F
It
takes
a
while
to
understand
everybody's
voices,
so
what
I
was
saying
is
that
I
think
the
producer
decides
how
it's
going
to
make
its
events
available?
Yes,
systems.
The
producer
just
makes
events
available
in
the
you
know,
any
sort
of
classification
might
and
filtering,
or
whatever
might
be
done
by
the
middleware,
depending
on
the
event
system.
F
In
some
cases
the
producer
will
do
filtering
on
its
own
and
in
any
case
the
producer
doesn't
pick
its
middleware
I
mean
it
might,
but
it
it's
just
responsible
for
how
it
produces
events,
but
think
lemon
is
to
basically
capture
a
little
more
of
what
you
said.
Yeah
the
document
seems
to
imply
that
the
producer
chooses
its
middleware.
My.
B
F
Many
weeks
ago
there
was
some
discussion
about
like
a
desire
for
there
to
be
an
ecosystem
of
things
right
and
so
saying
that
the
producer
I
mean
I,
think
sure
there
are
some
systems
where
we
allow
for
the
producer
to
have
some
proprietary
contact
with
some
proprietary
middleware
I.
Just
think
that
there
are
folks
in
the
group
who
would
like
to
see
the
interchangeable,
middleware
yeah.
F
B
F
D
F
F
F
Yes,
somebody
we're
creating
a
producer.
They
communicated
with
a
consumer
via
web
honk
and
those
were
the
producer
and
consumer
were
open
source
software
and
that's
then,
by
definition
over
HTTP,
because
that's
what
we
make
web
hooks
out
of
then
somebody
could
put
a
middleware
in
between
right
that
acts
as
an
observer,
really
the
so.
Basically
the
producer
chooses
how
it
will
communicate
events,
but
not
it
doesn't
actually
choose
its
middleware.
No.
C
I
think
so
I
I
think
Sarah's
point
is
from
the
producers
point
of
view
it
just
it
just
knows.
You
know
how
it's
going
to
publicize
or
omit
that
event.
It's
a
receiver
side.
You
know
that
decides
whether
you
know
it's
going
to
just
act
as
a
middleware
or
act
as
a
consumer.
Is
that
what
you
mean
Sarah
yeah,
the
producer
doesn't
know
who
is
going
to
consume
that
event
or
how
it's
going
to
consume
it,
whether
it
just
ask
as
a
middleware
or
it's
the
real
consumer
of
the
event.
C
Sure,
okay
I
have
a
question
here:
Clement.
Could
you
screw
up
so
for
that
yeah?
So
here
we
talk
about.
You
know
on
the
Middle,
where
all
these
I
mean
the
either
is
a
transcoding
transformation
filtering
right
coming
at
that
you
know
it
will
not
change
the
semantics
of
the
or
the
semantic
integrity
of
the
event.
I
see
that
you
you
you
put
that
into
the
transformation,
but
all
how
about
the
the
other.
B
B
C
B
C
Yeah
I
just
want
to
make
sure
the
middleware
does
not
change
the
semantic
integrity
that
that's
the
whole
point.
Actually,
when
I
read
through
these
points,
I
think
these
away.
It's
you
know
points
when
I
read
through
this
I
feel
the
summaries
platform
Carlos
also
satisfy
all
these.
What
do
you
think.
B
Point
is
the
point:
is
it's
a
it's
a
mill,
altum
Utley,
you
have
a
producer
in
sp
Kota,
you
have
a
consumer
or
a
handler.
If
you
will
that's
piece
of
code
yeah,
our
edges
of
this
whole
thing
all
right
and
then
there's
you
you
call
the
consumer.
Is
the
consumer?
Is
the
thing
that
ghostly
gets
the
event
and
then
and
then
interpret
it
and
then
ultimately
dispatches
it
into
a
function?
And
the
producer
is
the
thing
that
kind
of
captures
the
state.
B
That's
existing
in
its
own
system
renders
an
event
that
goes
and
sends
it
and
then
there's
stuff
that
sits
in
the
middle.
That
makes
sure
that
those
two
parties
can
go
on
there,
save
each
other
and
can
actually
know
see
each
other
if
you
will
so
that
that
event
can
be
brought,
and
then
all
of
that
stuff
that
sits
in
the
middle
of
nowhere
yeah.
C
Okay,
so
so
how
we
positioned
some
transport
in
the
middle
like
some
router
which,
throughout
the
event
from
there,
that's
also
me
the
way
so
I'll
me
the
way,
so
the
middle
we're
here
actually
is
very
broad.
It
could
be.
You
know
a
transport
entity
like
a
router
or
could
be
a
service
platform
which
actually
does
much
more
than
just
you
know.
Isn't
it
doesn't
do
transport
I
actually
ate
it
does
filtering
it?
Does
you
know
some.
B
C
B
In
standard
documents,
what
I'm
trying
to
avoid
is
constraining
the
definition
of
a
wall
to
a
particular
set
of
existing
artifacts
because
fashions
change
like
like
10
years
ago,
you
would
have
you
would
have
written
this
as
the
Enterprise
Service
bus,
that's
the
following
thing,
and
today
you
might
go
and
write
this.
As
you
know,
independent
in
certain
quarters
of
the
industry,
you
might
say
an
API
gateway.
B
Does
the
following
thing:
the
reality
is,
this
definition
of
middleware
has
been
stable
for
the
last
twenty
years
and
you
could
be
going
apply
this
to
IBM
and
cube
from
25
years
ago.
That
would
still
be
true,
and
this
will
likely
also
be
true
in
20
years,
but
the
names
of
things
that
are
implementing
these
patterns
are
all
changing,
because
yeah.
C
Yeah
I
think
I
understand
that
quite
I
think
that's
right,
I'm,
just
thinking
you
know,
in
order
for
other
people
to
better
understand
this,
we
can
just
give
some
examples.
Instead,
you
know
people
are
thinking.
You
know,
oh
because
sometimes
you
know
when
people
think
about
me
the
way
people
think
about
you
know
router.
You
know
some
intermediate
devices
which
does
not
do
anything
about
the
you
know
event
they
just
transport
some
people
to
think
of
that
way,
but
actually
I
think
here.
It's
not
just
that
right.
B
It's
just
not
that
the
spec
needs
to
be
pretty
tight
technical
document
and
what
we're
trying
to
achieve
is
kind
of
consensus
on
on
where
we're
going
and
ultimately
want
to
go
and
speed
up
things
to
get
to
a
stable
thing.
So
I
think
these
are
parallel
efforts
to
go
and
write
some
more
verbose
material
that
illustrates
more
of
the
use
cases
and
I
can
gonna.
D
Make
a
suggestion:
can
we
just
file
an
issue
to
like
I'd
like
to
see
this
proceed
like
this
pull
request,
go
across
and
write
a
separate
issue
to
clarify
you
know
the
the
existing
set
and
make
sure
it's
legally.
You
know,
but
not
limited
to
ya,
know
like
sort
of
thing,
because
you
do
introduce
a
really
interesting
set
of
use
cases
when
you
talk
about
like
an
API
gateway
versus
like
a
message
broker
right
like
you,
have
implicitly
changed
a
one-to-one
versus
like
a
one-to-many
mapping
of
you
know
where
the
event
could
conceivably
go.
D
D
Guarantees
right
like
at
least
once
at
most
once
right,
like
you,
can
we
can,
we
can
create
this
matrix,
but
I
think
it
should
be
very
scoped
and
specific
to
middleware
right.
That's
why
I'm
suggesting
we
rate
a
separate
at
you
to
like
kind
of
explore
the
definition
and
use
cases
related
to
middleware,
but
should
not
be
done
in
this
context,
because
this
should
move
across
and
make
progress
into
bag
and.
B
E
Had
a
quick
question
for
you
seems
like
you've,
got
a
couple
of
levels
of
discriminator,
discriminator,
sort
of
a
coarser
level
which
would
indicate
the
sort
of
a
storage
device
and
another
one
which
should
be
finer,
indicating
that
a
subject
or
a
file
with
hidden
storage
device
that
right
yeah,
I.
Think.
E
B
So
so
let
me
talk
about
those
four,
since
you
asked
and
I
think
that's
it.
That's
that's
where
that
equivalence
comes
from
so
the
first
one.
It's
is
one
where
we've
been
there.
Have
the
discussions
about
that's
this
namespace
thing.
I
think
we
need
to
have
a
way
to
distinguish
between
namespaces
in
the
sense
of
vocabularies.
B
If
you
have
a
event
that
comes
from
Azure
or
you
have
an
event
that
comes
from
AWS
or
an
event
that
comes
from
the
IBM
cloud
or
an
event
that
comes
from
the
Oracle
cloud,
you
will
have
a
specific
notion
of
you
know
what
the
other
fields
are
structured
like
they're,
going
to
have
a,
and
you
will
not
necessarily
all
want
to
interpret
them
as
completely
opaque
fields,
but
they
may
have
structure
in
them.
But
interpreting
that
structure,
you
need
to
have
an
anchor
for
being
able
to
interpret
that
structure
and
having
a
disambiguate
er.
B
That
tells
you.
This
is
an
event
that
comes
from
Azure,
or
this
is
an
event
that
comes
from
the
Oracle
cloud
will
help
you
to
say
like
if
I,
if
I
see
an
event,
that's
from
Azure
I,
look
and
I
look
at
the
fields
that
we're
currently
talking
about
a
source.
Then
I
know
that
that's
gonna
be
a
as
a
resource.
B
E
That
reason,
so
the
name
space
is
essentially
a
top-level
identifier
for
the
whole
context
of
the
the
best
event
I
mean
you
know
there
is
you
know
once
you
have
an
identifier,
whether
it's
Oracle
or
AWS,
or
all
the
other
fields
would
be
interpret
in
the
context
of
that
namespace
value.
Is
that
what
you're
saying
yeah?
That's,
that's!
That's
what.
B
I'm,
that's
effective.
What
I'm
after
to
say:
hey
all
those
events
are
having,
though,
having
this
their
their
meaning
and
their
constraints
as
club
events
defines
them,
but
they
may
they
may
have
incontinence
says
you
know
this
field
is
a
string,
but
inside
of
my
and
everybody
who's
processing
in
a
cloud
event
in
the
standardized
way
will
go
in
to
say
hey.
This
is
a
string.
B
I
can
go
and
use
it,
but
if
I
know
that
that's
a
string
that
has
been
admitted
by
Azure
I
can
also
go
and
interpret
that
string
in
a
particular
way
and
I.
Think
that's
fine
and
that's
the
the
power
that
a
namespace,
a
namespace
declaration
will
give
us
is
to
say
I
now
know
what
the
what
the
structure,
the
substructure
effectively
of
the
data
in
those
fields
is
and
and
I,
can
tell
you
that
we
will
likely
so
from
from
in
Azure.
E
B
B
You
will
be
able
to
go
to
that
respective
blog
account
and
the
file
out,
but
there
will
be
intelligent
about
and
will
help
you
be
able
to
tell
that
this
event
that
you're
looking
at
just
came
from
AWS
as
a
first
order
discriminator.
So
that
became
going
then
dispatch
in
the
respective
code
that
deals
with
mmhmm.
E
C
So
I
have
crutchy
here
is
so
that,
if
that
you
know
the
namespace
we
know
is
either
like
the
soft
or
I
was
all
worth
him
right,
but
if
it
is
liking,
I'm
still
thinking
about
the
IOT
scenario,
it's
not
like
any
well-defined
Emil
Microsoft
Amazon.
Then
you
know
what
is
this
classification
and
what
is
a
subject.
B
I'm
gonna
get
their
name
space
namespace
is
so
the
namespace
is
the
top
order,
the
top
order,
definition
of
all
the
events
that
you're
going
to
that
you're
going
to
admit,
and
if
you
and
and
this
might
be
you
way,
the
CN
for
you
or
Huawei
comm
for
you
and
for
me
it's
Microsoft
commas.
After
about
commenting,
it's
actually
describes
the
you
know:
a
collection
of
systems
that
are
emitting
events
and
in
a
similar
way.
It's
just
the
primary.
B
The
primary
purpose
for
that
is
to
avoid
clashes
and
like
if
you
are
subscribing
in
a
solution
from
X
of
these
systems,
and
you
get
events
from
all
of
them
into
the
same
place
that
you
are
able
to
go
and
dispatch
them
in
a
way
that
you
can
go
in
and
and
deal
with
them
in
buckets.
That's
the
primary
purpose
of
the
namespace
discriminator
yeah.
B
So
the
namespace
identifier,
basically
just
says
just
says
it
just
does
a
broad
classification
event
has
nothing
to
do
with.
Transport
has
basically
just
it's
just
about
how
to
it,
how
to
interpret
those
events
and
how
to
help
you
how
to
cluster
them
as
you
handle
them.
It's
not
about
where
you
go.
So
the
fact
that
there's
a
the
fact
that
there's
a
that
there's
the
main
name
in
there.
It's
just
it's
just
the
name
same
thing
as
with
maximal
namespace,
so.
B
F
B
B
B
C
Actually
so
come
I
think
I
have
the
same
confusion
and
Sara.
So
I
thought
you
know
you
have
the
names
me
I
saw.
You
have
the
classification,
you
have
the
subject
and
then
we
have
a
next
one.
So
this
you
say
are
not
related.
Then
there's
another.
B
So
so
the
requirements,
the
the
the
the
document
that
we
have
here
I
have
requirements.
That's
right,
they're,
actually
already
already
partially
materialized
in
the
document
that
we
have
in
the
forest
in
the
four
properties
that
I
would
like
to
get
to
make
some
progress
on.
So
that's
like
we
have
so
I'm
gonna,
I'm,
gonna,
go
and
and
and
tidy
this
up
this
part,
but
that's
already
pushing
for
some
properties
and
based
on
the
discussion.
That
was
that
we
had
just
so
far.
F
Sorry,
it's
I'm
two
of
I'm,
not
sure
that
I
completely
I'm
a
totally
agree
with
you,
Clemens
or
I'm.
A
kind
of
disagree
and
I
know
how
much
a
questions
about
namespace,
so
I'm
not
I'm
completely
in
support
of
there
being
a
namespace
field,
but
depending
on
how
its
interpreted
I
might
not
want
that
definition
for
it.
Okay,
well,.
F
B
F
E
C
B
C
If
you
can
put
into
the
same
document,
that
would
be
good,
because
the
thing
is
here
we're
talking
about
the
a
crisis,
if
occasion
and
then
subject
right,
but
then
we
were
discussing
the
namespace
looks
right.
Namespace,
it's
our
first
level
and
classification
is
second
level.
Is
that
what
you
have
a
man.
B
Issue,
112
actually
lays
this
out
in
epic
length
what
I
mean
with
what
what
topic
is
and
what
subject
is
why
they
exist
and
all
those
things
that's
a
that's
a
multi-page
right
out
that
I
did
just
for
declarative
clarification
and
also
cite
prior
art
on
how
subject
is
being
used
in
SNS
and
the
graduated
in
GCM
and
FCM
and
Kafka
and
JMS,
and
thank
you
and
thank
you.
Thank
you.
P
and
all
those
things
look
at
issues
ones.
Well,
okay,.