►
From YouTube: SIG Events Vocabulary Meeting - Feb 22, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
Sorry
guys,
I
think
I
was
in
the
wrong
meeting.
I
keep
the
enter.
I
I
clicked
whatever
sorry
the
ambassador.
No,
it's
the
outreach
committee
call
which
is
running
at
the
same
time.
A
No
worries
no
worries.
I
think
that
if
bishan
is
also
like
waiting
to
join,
let
me
see
for
some
reason
why
it's
lagging
my
computer
is
not
working,
it's
completely
broken.
Is
it
only
me.
A
Yeah,
I
think
that
that's
like
it's
kind
of
down
here,
like
maybe
in
europe
or
something
because
but
that's
that's
weird,
because
I
guess
that
it's
not
working
on
my
vpn,
but
it's
working
on
my
phone
weird.
So
I
have
no
idea.
What's
going
on.
A
B
Yeah
doing
well
thanks.
Thank
you.
A
That's
great,
we
can
start,
we
can
start
plan
planning
to
to
travel
to
some
conferences
and
stuff.
B
B
Alright,
so
I
have
some
agenda
for
today,
let's
feel
free
to
add
to
it.
If
I
missed
anything,
should
we
get
started,
okay,.
B
So
welcome
to
the
color
discussion,
meeting,
notes
or
cd
events
working
group.
We
should
rename
it
it's
still
relevant
vocabulary.
Discussion
as
well
feel
free
to
add
yourself
to
the
participant
list.
I'd
like
to.
B
Right
in
terms
of
announcements,
there
are
a
couple
of
forms
out
there.
One
is
for
the
event
kubecon
and
one
for
the
event
at
cdcon,
and
we
got
a
few
answers.
But
yeah
if
you
haven't
answered
those
yet
please
do
so
that
we
can
know
if
you're
interested
in
joining
and
get
a
better
idea
how
to
apply
for
those.
B
Zero
event
yeah
clara,
is
out
this
week,
but
it's
something
that
we
need
to
discuss
with
there.
I
don't
think
there
is
any
fixed
day
yet
and
I
usually
there
are
two
days
of
day
zero
events
or
like
co-located
events,
so
maybe
it's
possible
to
avoid
like
overlapping,
but
I
know
there
are
a
lot
of
them,
so
it's
always
difficult
to
like
yeah.
A
Yeah
my
my
first
impression
was
that,
like
cd
events
on
itself,
I
mean,
if
even
if
it
sounds
like
interesting-
I
don't
know
if,
like
we
can
do
like
a
full
day
of
it.
That's
why
maybe
kind
of
like
joining
forces
with
some
other
things
that
might
be
related
might
make
sense,
because
I'm
pretty
sure
that
people
like
on
the
canadian
inventing
side,
they
will
probably
be
interested
in.
You
know,
in
cd
events
and
the
same
thing
with
in
the
other
way
around
right,
like
people
using
cd
events.
C
C
B
A
B
Very
enthusiastic,
you
know
getting
the
community
moving
and
that's
great.
I
I
was
a
bit
concerned
about
filling
the
agenda
for
one
day.
I
think
that's
why
I
was
thinking.
Maybe
we
could
do
like
half
a
day.
Talks
like
having
a
keynote
and
having
some
people
bringing
stories
about
events
or
using
events
in
csd.
B
They're,
not
they're,
not
going
to
probably
going
to
be
about
using
city
events,
because
it's
just
too
new,
I
don't
think
yeah
city
events
or
implementing
city
events,
but
like
but
yeah
we
would
need
to
to
find,
but
I
guess
we
could
do
and
the
other
half
of
the
day
would
be
more
like
we
could
do
like
implementing
city
events
for
project
x
or
working
with
the
community
x
to
implement
an
adapter
or
to
the
events
in
that
project
or
doing
like
design
work
on
the
spec
or
on
the
sdks.
B
You
know
hands-on.
All
those
kind
of
things
make
sense,
so
I
think
we
could
fill
the
day
but
yeah.
We
need
to
have
also
enough
people
around.
Let
me
check
I
can
open
these.
C
So
maybe
I
was
wrong,
but
I
thought
that
the
the
day
was
actually
it's.
The
only
event
that
cdf
at
all
is
is
having
during
yukon
europe
right.
B
C
Yeah,
but
in
in
kubecon
europe,
so
I
think
it
was
this
like
cdf.
So
that's
why
tracy
was
pushing
for
the
big
room,
because
I
was
also
buffed
by
having
a
100
room.
It
was
either
50
or
100
room,
but
she
was
pushing
for
the
100
room
and
I
assumed
that
would
be
yeah.
The
reason
why
was
for
that
it
was
not
only
seed
events
but
the
whole
ocdf.
B
Well,
it's
the
only
event,
it's
the
only
event
organized
by
cdf,
but
I
don't
know
of
any
other
content
that
is
not
cdf
planned
for
that,
but
yeah.
So
we
can.
We
can
ask
her
if
there
is
any
plan
for
any
other
kind
of
content,
but
my
understanding
is
that
yeah,
it
would
be
basically
dedicated
to
cd
events.
C
But
then
it's
yeah,
it's
the
only
event
that
we
have
from
cdf.
So
that's.
Why?
Just
to
be
aware
of
that
one.
B
Yeah,
I
don't
know
that.
Are
you
aware
of
any
other
group
within
the
cdf
that
is
looking
to
to.
C
It
was
just
that
it
was
only
I
mean
if
it's
the
only
event,
then
they
we
might
have
more
people
from
other
parts
of
cdf.
That's
joining
into
the
the
thing,
but
yeah
it's
it's
meant
for
for
seed
events,
but
as
it's
the
only
one
another
city
of
people
might
join
in.
A
B
Projects
that
are
interested
in
implementing
city
events
in
the
project
like
that
would
be
great,
very
stress,
people
from
tecton
people
from
jenkins
or
spinacar
also,
but
we
may
also
have
people
from
projects
that
are
not
cdf
projects
that
want
to
implement
city
events
like
native
captain,
so.
C
B
Yeah
yeah,
that's
a
fair
point,
but
the
only
thing
I
would
say
I
mean
if
you,
if
you
think
of
a
group
or
a
community
that
would
be
interested
in
participating,
feel
free
to
share
the
link
to
the
this
google
form
reach
out
to
the
folks
and
they
let
them
know
that
this
event.
We
are
trying
to
build
this
event.
So
it's
going
to
happen,
so
we
can
get
more
people
involved.
B
Yep
make
sense
all
right,
I
would
say
then,
let's,
let's
move
on.
B
So,
in
terms
of
issues
to
discuss
the
the
first
one
is
the
service
published.
A
D
B
The
discussion
is
about
adding
a
cd
service
published
and
with
a
bit
of
back
and
forth
regarding
whether
it's
generic
enough-
and
I
think
we
we
agree
with
marisa-
that
the
console
can
be
generalized.
B
That
is
deployed,
and
today
we
have
a
few
events.
What
we
call
predicate,
we
call
them
now.
I
think
yes,
predicates,
which
are
deployed,
upgraded
rolled
back
and
removed,
and
the
proposal
needs
to
add,
publish
one
and
the
publish
one
would
represent
when
the
service
becomes
accessible,
accessible
from
outside
kind
of
the
private
context.
Where
it's
deployed
like
it
could
be
a
kubernetes
cluster.
There
could
be
also
some
kind
of
whatever
context,
so
it
kind
of
gets
a
public
ip
address
or
some
obviously
available
way
of
being
contracted.
A
Quick
question
about,
like
the
the
shape
of
the
events
now
like
dev
dot,
cd
events.
Is
that
something
that
we
have
reflected
into
the
sdk?
Not
yet.
B
Yes,
but
we
need
to
also
bring
the
sdk
into
the
city,
events
uh-huh
all
right
into
the
city
events,
github
organization.
I
think
I
have
should
sit
here.
B
A
B
Either
way
whatever
is
most
effective
for
the
people
doing
the
actual
change.
I
I
don't
mind
I
think
it's,
I
suppose
it's
going
to
be
like
search
and
replace
or
something
on
the
code,
hopefully
yeah.
B
A
Yeah
yeah,
if
we
are
going
to
make
the
change
there
in
the
current
repository,
let's
create
an
issue
there,
like
maybe
linking
to
this
issue,
and
I
know
that
each
and
every
is
working
on
this.
So
I'm
pretty
sure
that
you
know
we
can.
We
can
include
that
change
as
part
of
like
including
the
new
event
like
the
published
one.
B
Okay,
so
cool
so
just.
A
B
Right,
I
think
for
now
yeah,
so
the
there
is
the
yeah,
the
event
type
for
sure
and
the
rest
of
the
thing
I'm
working
on.
You
know,
writing
the
spec
and
how
it
will
look
like
in
the
new
format,
but
it's
still
in
progress.
So
I
think
once
once
it's
finished,
hopefully
it's
not
too
far
away
in
the
future.
B
Then
we
can
change
change.
The
sdk
as
well
makes
sense,
but
hopefully
the
the
api
of
the
sdk
I
mean
from
consumer
size
should
not
be
affected
too
much.
So
I
think
it's
just
it's
mainly
the
way
that
the
events
are
serialized
and
into
cloud
events,
I
think,
is
going
to
change.
I
mean
we
might
need
to
pull
in
some
new
information
if
we
set
up
things
like
links
at
some
point.
F
F
B
So,
on
the
on
the
published,
sorry,
where
is
it.
B
On
this
issue,
the
service
published,
the
only
question
I
had
was
whether
we
we
want
to
make
like
to
have
a
large
variety
of
predicates
or
whether
we
should
have
just
a
limited
number
like
created,
updated
removed
and
then
use
a
different
field
for
specifying
further
what
kind
of
updates.
B
So
the
only
concern
that
I
have
is
that
if
we
have
like
a
huge
number
of
events,
so
large
number
of
predicates,
a
large
number
of
events,
then,
if
you
want
to
write
a
filter-
or
if
you
want
to
you
know,
do
some
logic
around
it.
Then
you
have
a
large
number
of
of
events
to
to
manage
a
larger
number,
but
yeah.
I'm.
A
B
B
I
don't
have
really
a
strong
opinion,
one
way
or
the
other.
I
was
just.
I
wanted
to
raise
the
question
and
see
what
people
thought
about
it,
but
I
mean
we
can
also
continue
like
this
for
now
and
at
the
published
event
and
then.
C
B
A
Yeah,
I
really
want
to
unblock
ishan
with
that
published
one,
because
I
think
that
it's
worth
for
the
use
case
that
we're
trying
to
represent.
I
think
that
we
can
reevaluate
that
later
on
right,
like
if
we
need
yeah
yeah,
I
totally
get
what
you
mean
now
like
yeah,
something
as
part
of
the
update.
I
think
that
for
now
like,
let's
keep
it
separated
and
then
we
can
just
review
that
because
update
in
this
case
it's
super
generic,
so
basically
yeah.
A
B
A
separate
discussion
for
that
yeah-
it's
just
I
thought
if
I
like,
I
don't
care,
for
instance,
about
any
updates
on
on
services.
I
can
just
you
know
not
capture
all
the
updates,
but
if
there
are
like
five
different
kind
of
updates,
depending
on
how
it
is
updated,
then
I
need
to
handle
all
five
kinds.
There
were
some
kind
of
yeah
way
to
filter
them
out.
F
B
Yeah,
okay:
let's
do
like
this
anyways.
I
think
we
also
have
other
events
like
this,
and
maybe
we
can
have
this
discussion
for
0.2
version
0.2.
If
we
decide
to
restructure
this
or
not,
okay,.
C
So
my
two
sentence
to
the
discussion:
the
columns
is,
if
we
have
several
events
now
we
have
deployed
and
upgraded,
and
but
if
you
have
published,
then
we
also
need
to
be
aware
and
describe
to
the
users
when
you
should
use
publishing
when
she
is
deployed.
B
B
Okay
sounds
good
yeah.
I
totally
agree
with
you
the
documentation
point
I
think
right
now.
It's
we
have
just.
We
only
have
a
little
bit
of
text,
but
we
should
you
know,
have
some
examples
and
yeah
clear
this
discussion
about
when
to
use
which
events
and
maybe
examples
from
different
platforms
or.
A
C
Because
I
guess
you,
you
wanna,
if
you
read
the
specification,
then
you'll
see
published
in
the
and
deployed
okay,
when
am
I
supposed
to
use,
publish
when
I
used
to
use
deployed,
can
I
use
them
in
conjunction
with
each
other
and
so
on?
So
it's
those
type
of
questions
that
will
pop
up
for
for
a
new
reader.
So
that's
why
we
need
to
be
very
clear
on
when
to
use
one.
B
Yeah
and
they
popped
up
for
me
even
when
I
was
implementing
the
initial
poc,
and
I
think
for
you,
which
is
already
which
event
should
we
use?
Oh,
what
is
this
failed?
Is
it
like
meant
to
be
these
exactly
so
yeah.
A
B
All
right
moving
on
to
the
next
one
I
wanted
to
bring
up
as
this
using
service
and
city
events,
because
yeah
I
was
trying
to
write
the
more
more
documentation
on
the
specs.
Exactly
what,
when
how
do
we
use
the
different
fields
and
so
forth,
and
one
is
the
the
source
which,
in
cloud
event
is
marked
as
a
uri
reference,
and
the
main
thing
is
with
the
source
is
that
it
basically
gives
you
a
namespace
to
make
sure
that
the
event
id
is
unique
globally
right.
B
So
you
make
sure
that
the
source
plus
id
is
global,
unique
and
well
as
long
as
you
use
uuids
for
event,
ids,
that's
probably
already
quite
globally
unique,
but
adding
the
source
in
front
helps
but
yeah
the
way
it
is
implemented.
Phrases
in
tecton
when
sending
cd
events
is
that
for
source.
It
sets
that
this
whole
string,
like
api,
is
stacked
on
v1
data
namespaces
down
to
the
resource.
B
But
as
I
was,
writing
this
pack,
I
was
thinking
that
maybe
this
is
not
entirely
correct,
because
the
the
resource
their
id,
looks
more
like
the
subject.
So
then
I
was
thinking.
Maybe
we
should
do
something
like
this
like
the
sword
should
be
like
simply
tucked
on
the
death
and
the
subject
would
be
then
the
actual
resource
which
is
going
to
be.
B
I
don't
know
if
something
is
happening
to
it,
it's
running
or
okay,
whatever,
but
yeah.
So
the
problem
I
have-
and
I
also
asked
this
question
in
the
slack
for
cloud
events-
is
that
the
the
source
is
supposed
to
be
a
uri
ref,
but
it
should
identify
at
the
end,
a
source
of
events
which
is
likely
to
be
a
platform
like
a
jenkins
or
a
tecton,
or
my
testing
tactic
on
my
production
tactile
or
something
like
that.
And
how
do
I
don't
know
how
to
express
this
using
a
uri?
B
Staging
or
captain
slash
my
fancy
version
of
captain
but
yeah,
it's
not
clear
to
me
and
I
think
we
should
have
a
recommendation
how
to
structure
sources
in
the
spec,
but
I
wanted
to
see
if
well,
at
least
at
least
bring
attention
to
this,
because
maybe
I
don't
know
if
you've
seen
this.
Probably
you
have
not
seen
this
issue
before
so
maybe
at
least
you
can
have
a
look
at
it.
Maybe
we
can
discuss
it
offline
or
if
you
have
some
comments
now.
A
Let
me
know,
I
think
that
looks
really
interesting.
So
basically,
this
is
whoever
is
producing.
The
cloud
event
should
be
setting
up
connect
the
source
right,
and
what
we
are
trying
to
define
here
is:
how
do
we
define
the
source
for
the
producers,
in
this
case
right
yeah?
But
that's
kind
of
like
a
combination
between
subject
and
so
well
subject?
Is
the
entity
right.
B
Yes,
exactly
so
the
subject,
the
way
we
set
it
up
in
detecting
today,
it's
the
the
subject
is
there
in
the
source,
but
I
think
that's
something
that
we
need
to
change
actually,
because
I
think
that's
that's
wrong
and
if
you
see
the
first
option
that
there
is
an
overlap
between
subject
and
source,
so
I
think
the
second
option
is
closer
to
what
it
should
be,
but
the
source
there
might
be
not
very
interesting
to
have
like
the
website
of
tecton.
A
Yeah
yeah,
I
what
I
think
that
the
problem
kind
of
with
the
example
itself,
maybe
kinda
like
it's
a
it's
like
an
example
thing,
because
in
this
case,
like
tecton,
is
spanning
a
task
right
and
the
subject
in
this
case.
Like
this,
your
suggestion
is
that
the
task
you're
like
in
this
case
the
task
reference-
is
the
subject.
So,
basically,
you
are
saying
that
the
one
producer
who
is
producing
this
event
is
not
taken.
It's
actually
the
task
that
is
run
by
tecto
in
this
case
right.
A
B
A
service
right,
yeah
yeah,
it
could
be
the
kubernetes
service.
I
mean
we
could.
A
B
D
B
At
the
end
of
the
day,
I
think,
from
a
consumer
point
of
view,
you
only
need
to
have
some
kind
of
label
that
lets
you
identify
which
events
are
coming
from
the
same
type
of
source.
If
you
want
to
group
them
like
you're
visually
visualizing,
the
pipeline,
for
instance,
you
want
to
know
okay,
these
share
the
same
source,
so
I
need
to
have
a
label
that
I
can
group
them.
You
can
use
to
group
them,
so
I
can
say:
okay,
all
these
events
come
from
this
source
or
yeah,
some
kind
of.
C
B
C
C
You
can
differ
between
two
different,
I'm
thinking
like
if
you
have
two
different
instances
of
tecton
or
something
one
in
a
production
environment
and
one
in
a
staging
environment
that
you
can
actually
differ
between
which
one
of
them
was
the
sent
event,
and
at
least
in
that
level,
I
could
be
that
you
want
to
do
okay,
which
job
was
it
but
yeah.
B
Okay,
I
think
maybe
what
I
can
do.
I
kind
of
try
like
gather
these
ideas
we
discussed
today
and
put
them
in
the
spec
and
without
providing
a
specific
format.
We
can
give
some
suggestions.
Okay,
if
it's
a
kubernetes
entity,
you
can,
you
know,
give
like
the
resource
and
use
some
certain
syntax
like
specify,
I
don't
know
a
cluster
name
and
then
the
resource
or
platform
name
and
so
forth.
B
C
So
a
comment
there
when
it
comes
to
source
in
in
eiffel.
C
B
F
C
Okay,
I
mean
if
we
have
objects,
we
could
probably
have
a
general
discussion
of
okay
if
we
have
object
describing
something.
How
do
we
serialize
these
objects
when
going
to
cloud
events,
but
that
may
might
be
a
cloud
event
specific
discussion
then,
and
we
keep
the
the
the
seed
events
general
done.
C
I
posted
in
the
chat
link
to
an
example
of
how
to
find
source
in
in
iphone.
A
Folks,
sorry,
but
I
need
to
drop
to
another
meeting
in
three
minutes.
I
wanted
just
to
give
quick
heads
up
on
like
the
proof
of
concepts.
I
think
that
eastern
is
making
really
good
progress
on
the
k
native
side
and
we
also
define
that,
for
we
submitted
a
proposal
for
civicon
and
in
that
proposal
we
wanted
to
also
create
like
a
poc
with
crossplane.
A
Eason
is
also
working
on
that
as
well.
So
you
know
more,
we
will
probably
create
an
issue
and
we
will
create
some
flows,
and
then
I
had
a
meeting
with
another
person
from
vmware
that
it's
working
in
this
project.
It's
called
cartographer.
It's
also
like
an
open
source
project
for
supply
chain
stuff,
and
they
were
interested
in
like
joining
these
discussions
as
well.
So
I
will
try
to
bring
them
to
these
meetings
and
I
would
probably
create
an
issue
to
integrate
with
cartographer,
so
this
project
kind
of
gets.
A
Yes,
yeah
yeah
yeah,
I
will
bring
them
to
different
groups
and
then
I
will
let
them
choose
which
ones
they
want
to.
You
know
work
with.
I
am,
I
know
that
they
want
to
integrate
closely
with
k
native
now
like
they
want
to
integrate
the
the
open
source
cartographer
with
canadian
more
closely,
and
that's
why
they
might
start
kind
of
like
here
on
cd
events,
but
yeah.
I'm
just
trying
to
you
know,
make
people
aware
of
these
initiatives.
So
so
you
know
they
can
start
contributing.
B
B
Okay,
moving
on
and.
B
C
Yeah,
that
was,
I
noticed
that,
for
example,
codaconic
we
didn't
include
that
in
the
github
repository
and
but
when
I
looked
at
this
when
contributing,
I
realized
that
those
two
can
actually
be
should
probably
be
in
the
github
in
order
to
just
have
them
for
forget
them
automatically,
including
them.
However,
there
is
no
governance.
B
If
you
open
one
repo
and
you
could
go
to
any
repo,
it's
basically
showing
you
this
kind
of
contact
link
here
and
let's
pick
from
the
github
repo,
which
is
great
yeah
for
the
contributing
one,
but
it's
it's
not
showing
in
the
list
of
files
for
the
code
review,
contributing
ones
so
in
iphone.
You
have
it
here
in
the
readme
contribution
guide.
C
Yeah
we've
added
it
there,
but
if
you,
I
think
that
it
is,
if
you
open
a
pull
request.
B
And
that's
the
first
time
contributor,
it
shows
that
and
I
guess,
if
I
create
new
issue,
let's
see
yeah,
it
shows
shows
it
here.
The
first
time
at
least.
F
B
Yeah,
so
I
think
it's
worth
to
driving
them
there,
then
it's
just
I
I
I
kind
of
dislike
a
bit
the
fact
that
they
don't
show
up
in
the
list
of
files
and
then
in
the
repo
because
then
like,
if
you,
for
instance,
have
this
kind
of
links
and
then
all
need
to
become
absolute
links.
B
Where
is
it
like?
Yeah,
the
readme
or
if
you
had
like
in
the
how
to
contribute,
you
could
include
a
link
to
the
development.md,
but
then
that
doesn't
work,
because
it's
this
file
is
not
actually
in
the
repo.
So
it's
I
thought
it
used
to
work
like
that,
but
it
kind
of
made
it
look
like
the
fire
was
also
in
the
other
repos,
but
I
guess
they.
They
dropped
that
okay,
yeah
anyways
yeah.
I
I
I'm
happy
with
moving
them
to
get
up.
C
Yeah,
I
guess
the
risk
with
compass
is
that
they
diverge
and
if
you
have
multiple
sources,
so
I
don't
know
if
you
could
link
in.
C
B
B
So
because
this
pr
included
the
updates
to
the
readme.md
and
then
what
I'll
do
I'll
do.
A
separate
pr
for
the
gita
people
and
then
I'll
update
this
pr
to
include
the
links
to
the.
E
B
Yeah
and
yeah,
I
also
it
also
adds
a
new
field,
which
is
the
version
where
we
could
have
the
version
of
the
spec
and
the
optional
subject,
and
the
subject
here
is
example
of
subject
is:
is
an
object,
it's
of
type
object,
and
then
we
would
need
to
help
us
to
define
how
to
serialize
this
into
into
the
cloud
events
binding
into
the
caldera
and,
subject
probably,
I
mean
it's
probably
enough
to
adjust
the
id
there
but
yeah.
B
I
wanted
to
keep
it
on
cd
event
side
like
an
object,
because
then
you
can
have
all
the
all
the
fields
like
we
defined
in
this
pack.
C
I
haven't
gotten
the
time
to
take
a
look
at
this.
I'm
gonna
probably
have
some
time
tomorrow.
One
thing
there
I
wondered
about
how
how
much
do
we
want
to
specify
in
details?
C
I
mean
in
certain
cases
as
with,
for
example,
cloud
events,
the
top
layer
doesn't
support,
complex
types
and
and
so,
for
example,
source.
If
we
want
to
have
a
complex
type
there,
we
have
a
subject
when
a
complete
type.
C
It
could
be,
for
example,
the
the
dates
we
want
to
complex
type
in
and
so
on,
yeah.
So
that's
kind
of
like
a
general
question
of
how
much
do
we
want
in
here.
Do
you
want
to
specify
and
how
much
do
we
want
to
leave
up
to
the
the
actual,
like
protocol
indicate
implica
implementation,
like
cloud
events
to
limit
what
we
do
or
yeah
do
we
want
all
of
us
or
maybe
on
the
cloud
on
the
sea
defense
side.
B
Yeah
the
approach
I
was
taking
was
to
kind
of
trying
not
to
think
too
much
about
cloud
events
at
this
level,
even
though
we
borrow
a
lot
of
the
definition
from
from
there,
but
you
know
like
using
objects
where
we
want
to
and
and
then
deciding
which
information
we
want
to
present
in
the
cloud
events
headers
as
part
of
the
cloud
events
finding
and
then,
when
we
make
the
decision
we
you
can
physically
the
reasoning.
B
I
think
it's
if
you
have
cloud
events,
routers
or
clients,
what
information
do
you
want
to
present
them
so
that
they
can
take
decisions
based
on
the
headers
of
the
message
without
having
to
go
into
the
into
the
body,
because
in
in
some
formats,
cloud
events
could
be,
the
body
could
even
be
binary
or
in
quadrant
format.
So
you
want
to
be
able
to
take
like
decisions
like
quick
decisions
like
on
filtering
and
routing
of
these
kind
of
things
without
having
to
look
into
the
body.
So
what
information?
C
Yeah,
I
will,
I
will
read
through
it
and
comment
yeah
the
other
question
there,
but
maybe
it's
because
I
almost
came
through
it
about
what's
the
subject
thing,
and
I
guess
that
is
the
subject
is
the
same
subject
as
the
subject
of
the
event
right.
B
B
Yeah,
I
put
it
as
optional
for
now,
because
during
the
discussion
a
couple
of
weeks
ago,
I
think
we
we
came
to
a
conclusion
saying:
okay,
it
could
be
optional
for
now.
At
least
that
was
a
no
recommendation,
I'm
thinking
we
might
want
to
put
it
mandatory.
B
Because
I'm
not
sure
there
will
be
cases
where
we
don't
provide
a
subject
so
yeah,
maybe
it
probably
makes
sense
to
have
it
mandatory.
C
C
So
hopefully,
if
I
get
time
tomorrow,
I'm
also
going
to
try.
I
think
it
was
thinking
of
trying
to
mainly
for
myself
start
creating
like
full
examples
that
we
might
be
able
to
introduce
in
this
yeah
in
the
spec
in
some
kind
of
way-
and
I
saw
you
had
an
example
of
a
json
there
of
a
subject
yeah,
but
maybe
having
a
full
example
of
the
whole
event.
So
you
can,
you
can
get
a
better
grip
of
what
it
is.
C
C
B
B
A
B
Visualize
them
so
it's
yeah,
but
I
think
that
at
the
at
the
root
you
can
have
things
like
these
or
like
in
my
pr
where
you
just
have
text
and
say:
okay,
these
are
the
objects.
These
are
the
fills,
and
this
is
how
they
behave,
and
then
we
could
even
have
different
serialization
documents.
If
you
want,
if
it
makes
sense,
I
was
thinking
about
it.
B
Sorry,
I'm
trying
to
yeah,
I'm
not
sure
where
my
pr
is
yeah,
we
we
could
have
yeah
serialization
document
or
at
least
a
document
with
json
examples.
B
C
Yeah
I
was
thinking
of
how
generic
should
we
have
it.
I
mean,
of
course,
jason
is
one
thing
I
guess
you
could
draw.
Maybe
you
could
draw
uml
diagrams.
I
don't
know
if
you
want
to
be
stay
out
of
the
json.
B
Yeah
yeah,
we
are
out
of
time,
I
guess
so
yeah.
The
only
thing
I
wanted
to
mention.
If
you
are
interested,
I
started
putting
up
this
acandy
about
the
metrics
with
city
events,
poc
yeah.
If
you
have
some
example
to
read
through
word
comments,
it's
yeah
would
be
very
welcome.
Of
course,.