►
From YouTube: CNCF Serverless WG Meeting - 2018-07-26
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
Anyway,
it's
three
past
the
hour:
why
do
we
go
and
get
started?
Who
can
join
as
they
join?
It's
just
think
here.
Anything
on
the
AI
is
worth
mentioning.
I
think
Austin
he's
not
gonna
like
the
call
today
and
I
haven't
heard
back
for
him
on
the
logo,
yet
so
I'm
assuming
he's
still
working
on
it.
You
mentioned
that
they're
going
through
some
deadlines
and
stuff
internally.
A
A
B
Forgive
me
if
I
do
this
to
please
but
first
time
I've
done
screen
share
on
zoom
in
zoom
us
am
I
presenting.
Yes,
you
are
cool
okay,
so
for
those
of
you
who
are
not
aware,
Google
just
revealed
that
we've
been
working
with
a
handful
of
industry
partners
to
look
at
this
whole
surrealist
thing:
it
has
three
pillars
that
are
usable
independently.
They
are
build
serving
and
venting.
B
So
today,
I'm
gonna
be
talking
about
the
eventing
repo.
One
of
the
things
that
I
will
do
that
you
did
not
see
on
stage
is
I
will
be
not
using
the
build
repo.
So
this
is
one
of
the
design
principles.
Is
that
all
three?
These
components
can
come
together
to
have
more
value,
but
they
are
independent.
So
instead,
today,
I
use
a
tool
I
like
called
Co,
so
for
those
eager
not
familiar
with
kubernetes,
you
apply
mo
files,
you
have
to
already
have
docker
available
somewhere.
B
Co
is
go
kubernetes,
so
you
can
I
check
out
my
function.
Amel
you'll,
see
in
here
that
were
supposed
to
have
an
image.
It
actually
just
lists
a
go
namespace,
and
so,
if
I
co
apply
instead
of
a
coop
cuddle,
apply,
I
will
actually
build,
create
the
docker
image
and
deploy
for
me,
that's
even
when
I'm
just
doing
a
tech
demo,
that's
an
even
easier
mode,
so
I
don't
have
to
use
the
build
version
or
the
build
product
in
order
to
use
the
eventing
product.
B
B
Okay,
so
first
I'm
going
to
do
is
show
that
the
system
is
fully
extensible.
So
if
I
do
tube
cuddle
get
that
type,
it
doesn't
know
any
event
type
doesn't
actually
ship
with
unit
types
or
event
sources,
but
if
I
wanted
to
I,
actually
we
have
some
sample
ones
already
available,
so
cuddle
fly
actually
Co
applying
some
build
process.
These.
B
Sources
will
do
kids
events
so
now
this
basically
created
these
pluggable
event,
sources
and
event
types.
The
whole
system
now
knows
what
a
dev,
K,
natives
and
so
you're
following
the
cloud
cloud
event
standard
we're
going
to
namespace
our
own
things
that
you
made
up
dead,
duck
a
native
Kate's
defense
step
by
citizen
command,
coupe
cuddle
get
event
type.
It
knows
that
there
is
one
available.
B
What
this
does
is
it
teaches
future
commands
that
if
I
have
a
flow,
which
is
our
binding
between
an
event
source
and
an
action,
I
can
now
reference
those
same
type
of
men,
types
and
I
can
have
a
declarative
system
where
I
want
to
reach
into
this,
and
now
K
native
eventing
knows
the
docker
jobs
or
the
docker
images
for
the
kubernetes
jobs,
or
to
have
to
run
the
set
up
this
in
the
structure.
So
let's
actually
create
an
action.
So
I
have.
B
So
for
this
we
actually
created
a
go
SDK.
This
is
an
evolution
of
the
SDK.
We
open
sourced
at
the
copenhagen
demo,
which,
actually
to
the
best
of
my
knowledge,
was
secretly.
The
first
live
demo
of
k
native.
So
at
copenhagen
we
were
actually
running
canada
for
the
google
sample,
so
the,
but
we
rewrote
it
to
be
a
bit
more.
We
go
idiomatic
so
right
here
we
have
something
where
it
takes
a
goal
in
context
or
anyone
who's
familiar
with
go
you'll,
this
be
very
familiar
class.
Pretty
much.
B
Every
function
has
a
context,
a
context
and
then
the
second
parameter
is
whatever
that
you
want.
You
can
your
hand
we're
gonna,
have
0
1
or
2
functions.
If
it
is
to
its
in
this
order,
we
do
the
automatic
on
marshalling.
You
can
also
return
either
nothing
an
error
or
anything
you
want
that
would
be
used
for
that
continuation
and
an
error.
B
A
B
B
C
C
B
Shh
cadence
starts,
although
it
looks
like
I
have.
Let
me
figure
out
what
went
wrong
here.
Real
quick.
B
A
B
B
See
what's,
okay,
I
might
follow
up
on
on
slack
with
why,
if
I
figure
out
why
the
image
is
being
pulled,
but
if
it's
failing
to
download
the
image,
I'm
not
sure,
what's
going
on
right
now,
I
apologize,
but
that
this.
D
D
D
B
Okay,
if
this
is
going
to
have
us,
be
rebuilding
a
couple
of
files,
I
don't
want
to
hold
the
whole
group
hostage.
I
will
do
either
recording
or
show
off
a
pre
victim
at
the
end.
Okay,.
E
Have
a
question:
Thomas
is
the
on
goal
of
this
kinetise
event.
Is
it
to
produce
an
event
or
to
find
the
event
through
a
function
or
to
create
a
back
I
would
say:
oh
I,
will
it's
or
I
assume
the
I
mean
the
goal
is
to
find
the
event
through
the
function
right,
crazy,
even
just
for
simulation.
You
have
a
grant,
so
it's
not
in
real
situation
right
the
event
source
could
be
any
anything
right
could
be
an
IOT
device
or
could
be
a
middleware
or
any
storage
or
streaming
source.
E
B
So
there's
multiple
personas
involved
in
this.
So
if
someone
wanted
to
make
their
event
source
available,
they
could
create
the
the
yamo
files
that
describe
their
event
source
and
the
doctor
images
that
would
actually
execute
that
intent.
That
would
be
able
to
create
any
registration
or
to
clean
it
up
and
then
any
actual
cluster
operator
could
now
add
that
capability
to
their
entire
cluster
and
the.
B
B
B
That
right,
this
is
actually
the
thing
that
I
think
I
forgot
to
set
up
correctly,
which
is
why
I
think
the
demos
are
failing.
Is
that
just
like
it
meant
sources
are
pluggable
transports,
our
pluggable
as
well
so
flow
is
the
top
level
like
friendliest
abstraction,
underneath
it
there's
different
buses
that
you
can
install
and
busses
can
have
instances
of
channels
that
will
deliver
the
actual
events,
and
so
we
are
trying
to
stay
completely
agnostic
to
what
the
transport
that
is
actually
used.
E
B
E
Flow
yum
Oh
fire
is
a
key
functionality
eager
and
the
connective
you're
polite
right,
okay,
so
even
source
itself
is
outside
of
that
and
this
creative
project
right
correct.
It
is
any
and.
B
Sauce:
okay,
yes,
it's
an
explicit
goal
that
came
in
it
will
support
event
sources
without
recompiling
can
native.
Similarly,
it
will
support
different
transports
without
recompiling
cañedo
and
that
the
cluster
operator
can
make
decisions
about
how
that
cluster
would
operate
and
default,
that
you
could,
even
theoretically,
using
the
lower
level
components
set
up
exactly
one
event
stream
to
use.
You
know
cloud
pub/sub,
for
example,
and
the
rest
of
them
might
use
Kafka
and.
E
B
A
B
So
I
personally,
you
know
I,
like
those
abstractions
I,
could
see
myself
sticking
at
that
level,
especially
because
K
native
has
even
in
its
on
its
own
kind
of
an
above
and
below
the
fold
set
of
abstractions
so
on
serving,
for
example,
there's
just
the
service
type,
and
that's
this
nice
friendly
rapper.
You
only
have
to
deploy
one,
but
underneath
it
it
actually
has
things
like
the
route,
which
is
the
load
balancing
URI.
It
has
the
configuration,
which
is
your
current
state
of,
what's
been
deployed
and
has
the
revisions.
B
F
B
E
So,
basically,
are
you
if
the
event
source
format,
it's
not
even
format,
I
mean
you
are
going
to
translate
it
right.
It's
that's
part
of
your
functionality.
B
B
A
All
right
cool
all
right.
Thank
you
very
much,
Thomas,
okay,
moving
forward
I
know,
Austin,
isn't
on
the
call,
and
there
was
no
SDK
call
this
week.
Also
hope,
there's
anything
enough
date
here,
all
right
Cathy!
Is
there
anything
you'd
like
to
take
the
group
on
relative
to
your
work
for
a
work
group.
E
A
All
right,
cool,
Thank,
You,
Kathy,
moving
forward,
I,
don't
think,
there's
anything
else
you
may
need
to
deal
with,
so
we
can
jump
right
into
PRS.
Now.
Last
week
we
were
talking
about
Clemens
PR
about
qualifying
profiles,
basically
setting
the
bar
for
when
we're
gonna,
accept
new
specifications
around
civilizations
and
transport
bindings,
and
then
Ryan
have
a
suggestion
for
some
changes.
Ryan.
You
want
to
talk
to
your
suggest
changes
here.
G
G
A
G
A
G
A
E
G
If
de
facto
standard
is
to
be
honest,
it's
also
not
that
clean
cut,
but
as
we
discussed
things
like
Kafka
or
like
Cooper
Cady
community
in
terms
of
container
orchestration,
those
are
type
of
things
that
become
pretty
much
for
a
long
time.
I
think
it's
called
any
reasonable
people
would
think
that's
a
standard,
it's
not
as
clean
cut
as
I
want,
but
seems
like.
We
cannot
get
away
with
that
and
I'm
not
expert
in
all
these
forms.
Right,
like
these
standard,
poems
I
just
copy.
G
Whatever
cameras
list
sit
there,
he
seems
to
know
all
these
standard
bodies
and
if,
if
you
think,
that's
the
exhaustive
list-
and
that's
it
if
it's
not
I
would
like
to
see
a
exhaustive
list,
because
that
at
least
makes
it
again.
I
my
purposes
really
just
want
to
make
a
clean
cut
so
that
they're
less
argument
all
things
down
line
down
the
road.
You
know,
then
people
would
say.
Oh
this
is
a
standard
party
yeah
that
that's
the
type
of
conversation
trying
to
avoid.
Given
this
I'm.
A
A
C
I
am
just
added
a
comment
to
propose
I.
Think
I,
like
somebody
said
that
maybe
we
should
attempt
to
make
a
little
more
of
a
definition
of
de
facto
and
so
I
added
a
comment.
While
we
were
talking,
which
is
something
that
has
an
open-source
implementation
as
in
end,
is
in
use
by
services
or
products
from
independent
vendors,
meaning
that,
like
it's
out
there,
different
people
are
using
it.
G
B
G
Yeah
yeah
I
was
worried
about
I
try
I
spent
some
time
looking
at.
The
third
paragraph
is
whether
to
try
to
I
try
to
rephrase
the
third
paragraph
to
make
it
more
inclusive
but
still
clean-cut,
but
at
the
end
I
cannot
do
that
so
I
get
it
away
with,
because
seems
like
the
the
Thomas
thing
is
belongs
to
a
third
paragraph
and.
G
G
Second,
paragraph
sorry
yeah,
the
second
paragraph
yeah,
it's
it's
kind
of
become
a
slippery
slope.
When
we
just
say
I,
initially
I
thought
we
could
say
any
service
that
is
used
by
at
least
three
more
independent
parties,
something
like
that.
But
then
it's
still
kind
of
hard
to
define
used
by
three.
What
does
use
mean?
Who
do
you
need
to
find
three
different
projects
or
I'm?
Not
a
hundred
percent?
Sure,
okay,.
A
I
I
think
the
third
paragraph
is
actually
kind
of
important,
because
it's
trying
to
make
sure
I
mean
I
know
we
all
love
Kafka
and
stuff.
But
the
thing
to
remember
about
Kafka
is
there's
part
of
it.
That's
an
open
protocol
and
part
of
it.
That's
actually
like
an
implementation,
and
that
works,
because
that
protocol
allows
alternate
implementations
so
I
think
that's
what
Clements
is
just
the
third
paragraph
is
I.
Do.
J
This
is,
this
is
Colin.
You
know,
I
missed
some
of
the
early
history
of
this.
Why?
Why
are
protocols?
Even
you
know,
blaster
defined
in
the
first
place
you
know
and
thinking
in
terms
of
separation
of
concerns.
Why
not
just
a
specification
of
what
a
binding
whole
protocol
is
required
to
do
and
then
organically,
just
let
whatever
people
want
to
use
use
and
the
most
popular
will
be
the
most
popular
or
you
know
the
favored
it'll
be
the
favorite.
J
B
The
I
think
the
big
question
is
whether
we
gave
them
space
in
our
our
formal
github
for
advertising.
So
we
everyone
should,
like
you
know,
to
bring
it
up
again
we're
going
to
have
a
formal.
You
know
back
at
how
Google
says
cloud:
pub/sub
should
have
cloud
events
go
on
them,
but
Google
is
gonna,
have
to
use
its
own
website
to
advertise
that
documentation,
and
then
we
can
have
a
link
from
it
here,
but
not
a
full
markdown
page.
Oh
yeah,.
C
What
what
I
don't
want
it
like,
like
nobody,
owns
httpd
right
and
I,
think
there
there
are
other
ones
where,
if
it's
a
de
facto
standard,
the
person
like
the
community
may
want
to
create
a
protocol
expression
for
cloud
events
without
whatever
entity
originally
made.
That
thing
being
involved
right
and
then
there
are
other
things
where,
like
the
company
wants
to
promote
their
company,
and
so
we
want
to
be
like
okay,
that's
your
business,
not
the
community's
business
right.
A
So
trying
to
figure
out
the
best
way
to
make
progress
here
and
I
think
a
couple
different
things
here.
One
is
stick
a
DG
in
front
of
the
list
here
two
is
to
see
if
we
can
firm
up
the
definition
of
the
facto
standard
and
I
think
Ryan
or
I
guess
their
else
on
the
call
needs
to
think
about
whether
Sarah's
proposed
text
errors
is
sufficient
to
define
that.
A
I
A
I
A
K
I
have
a
quick
question
on
that.
My
understanding
was
that
the
bindings
are
on
a
transport
or
something
like
a
casket
to
me
is
more
of
a
product
than
a
transport
like
you're
not
going
to
see
somebody
going
I'm
going
to
use.
You
know
a
pub/sub
using
the
casket
transport
without
all
the
other
kappa
you.
I
A
C
G
Yeah
I
was
thinking
just
like
this.
It
was
say
used
by
not
just
by
other
services
but
for
the
quantitatively
say
more
than
five
services,
a
tough
car
again,
whether
it's
a
the
original
cop
car,
the
pub/sub
product,
definitely
is
used
very
widely.
Ten
is
not
even
a
it's
a
fear
power.
We
can
say
more
than
ten
different
companies
used
community
using
it.
It
seems
to
me
we
should
put
a
quantitative
number
there,
not
just
by
others
other
than
otherwise
people
can
say.
G
K
But
again,
is
it
talking
about
a
transport
which
we're
binding
to
or
a
product
because
nobody's
going
to
implement
a,
for
example,
a
captive
transport?
But
there
are
transports
that
are
emerging,
for
example
in
the
IOT
world
that
are
becoming
things
ZigBee,
plus
and
co-op,
and
all
these
other,
which
really
are
transports
that
are
not
necessarily
standard,
but
are
a
lot
of
products
out
there
using
them
as
transports,
as
opposed
to
a
full
suite
of
products
that
have
to
work
together,
because
without
a
example,
a
Kafka
client
which
everything
is
in
the
quiet.
G
G
Transports
its
that's
about
I'm,
not
a
hundred
percent
sure
I
want
to
hear
others
thought
I,
don't
know
if
this
is
only
transport
only
oh,
it
actually
applies
to
some
other
things
for
the
CAF
conversion.
The
reason
I
I
think
the
clearest
mention
that
it
was
all
so
I
thought
it
because
it's
pops
up.
So
when
the
the
events
coming
in
out,
that's
the
the
format
we
won't
use
like
we
can
work
with
half-caste
pub
and
sub
events.
A
G
A
Yeah
and
then
people
can
come
back,
I
mean
just
people
mind,
but
the
odds
of
us
getting
the
exact
right
text-
100%
accurate,
pretty
slim.
So
you
mean
it
said.
You
know
say
what
is
good
enough
to
get
the
point
across
just
so
that
people
when
we
come
when
we
come
back
to
say
no
to
their
proposed
spec,
you
one
add
we
can
be
clear
to
say:
look
you
didn't
get
the
bar.
We
defined
here,
yeah
we're
trying
to
do
yeah.
D
A
A
A
A
A
A
K
A
A
All
right
any
other
questions.
Okay,
so
please
review
this.
When
you
get
a
chance,
we'll
see
we
can
put
on
next
week
something
there.
No
major
comments,
all
right.
Next
sorry
I
hear
they're,
probably
my
throat
alright.
So
let's
talk
about
extensions,
so
I'd
opened
have
a
PR
earlier
and
then
I
closed
it
in
favor
of
this
one.
It's
it's
almost
the
exact
same
thing:
I
just
thought
to
be
cleaner
to
do
any
P
new
PR.
So
this
PR
does
a
couple
of
things.
A
First,
it
takes
the
step
towards
making
our
specification
or
our
course
back
into
more
of
an
info
set
as
Clemens
liked
to
call
it
where
we
pretty
much
defined
in
the
abstract
form.
What
are
the
properties
that
we're
going
to
define
and
leaves
the
entire
notion
of
serialization
concerns
for
the
other
specifications
right,
so
the
Jason
spec
spec
all
deal
with
serialization
of
the
info
set
is
defined,
inspect
that
MD.
A
That's
the
one
thing
that
we
do
you'd
add
some
text
to
the
primer
to
make
it
clear
or
try
to
get
clear
when
people
should
consider
adding
things
to
the
cloud
event
as
an
extension
versus
stick
it
inside
the
data
in
the
real
event
itself.
Try
to
provide
some
guidance
there
that
way.
People
don't
think
that
Oh
everything
was
going
to
the
cloud
of
an
extension
and
really
it's
not
used
for
that
around
Baudelaire
that
we're
trying
to
solve.
A
It's
really
part
of
the
event
date
itself
make
some
put
some
clarity
around
that
next
I
heard
some
confusion
about
the
word
extensions
as
a
file
name,
because
some
people
seem
to
think
that
when
we
talk
about
extensions
for
our
specification,
the
those
extensions
only
came
from
the
extensions
that
MD
file,
as
opposed
to
they
can
come
from
pretty
much
anywhere
and
so
to
try
to
address
that.
If
I'm,
okay,
maybe
we
renamed
it
experimental.
Some
like
that
Thomas
expressed
some
concerns
about
that
person.
A
I
don't
care
about
the
name,
but
if
there
is
some
confusion
around
that,
we
may
want
to
consider
an
alternative
name
to
extensions.
So
I'd
like
to
get
some
feedback
about
whether
that's
a
concern
for
people
or
not.
Let
me
just
finish
going
through.
Listen
at
all,
just
don't
go
back
to
you,
it's
a
second
and
they
said
it
left
the
serialization
for
the
transport
and
binding
specs
and
then
based
upon
the
discussions
that
was
going
on
in
that
Google
Doc.
A
That
looked
forward
about
which
use
cases
around
extensions
support,
while
it
wasn't
unanimous
I,
did
get
the
sense
that
a
fair
number
people
were
saying:
okay,
let's
it's
okay
to
put
for
the
Jason
civilization,
extends
to
the
top
level,
and
that
may
be
a
contentious
decision,
but
I
flipped
the
coin
and
landed
a
match.
So
we
can
discuss
that
and
that's
so
that's
another
part
of
the
PR.
So
those
are
the
main
point
of
the
PR
itself.
Thomas
I
think
you
might
had
a
question.
Oh
just.
B
A
A
So
in
the
primer
again,
I
talked
about
a
little
bit
about
when
things
might
appear
as
extensions
versus
in
the
data
and
that
the
data's
meant
lease
is
meant
data.
This
mention
trick
reviews
by
the
component
process
in
the
event
file
extension
is
mainly
used
for
the
transport
type
of
operations.
If
that's,
what
we're
concerned
about
I
do
I
do
go
a
little
bit
into
about
extensions
themselves
in
the
extensions
section
to
make
it
clear
that
pretty
much
put
anything
you
want
into
the
extensions
stuff
that
worried
that
we
allow
for
there's
something
I
wanted.
A
Mr.
Kermit,
it
was,
though
yeah.
A
In
the
spec
itself,
I
deleted
the
extensions
property
here
and
just
basically
add
text
that
says,
producers
may
add
additional
extensions
and
at
the
theater
specs
will
define
how
to
get
serialize.
That
way,
we
don't
get
into
this
whole
question
of
you
know
our
extensions
under
our
bags
or
not
that
bag
info
set
level
isn't
part
of
our
discussion
here
now,
that's
not
to
say
that
a
civilization
cannot
add
a
bag
for
them.
That's
completely
up
to
the
serialization
at
the
info
spec
level.
We
don't
talk
about
it.
A
C
A
C
A
And
I
actually
put
together
a
document
explaining
why
that's
all
goodness,
I
not
sure
we
have
time
to
walk
through
the
whole
thing,
but
in
the
agenda
doc
under
this,
whatever
extensions
I,
put
a
link
to
a
document
here
and
I
actually
put
through
I,
put
three
little
pages
together
to
explain
why
that's
actually
a
good
thing,
if
you
will
want
they
can
quickly
walk
through
some
of
the
highlights
of
that,
and
we
have
a
layout
five
minutes
left
I.
Don't
we're
gonna
get
to
keep
topic
anyway,
so
let
me
just
quickly
touch
on
it.
A
So
first
I
want
to
make
sure
that
we
level
said
a
little
about
water
extensions.
So
first
I
want
to
make
sure
if
you
understand
that
or
agree
that,
for
an
extension,
you've
used
properly.
Typically,
the
person
who
defines
the
extension
is
gonna.
Have
it's
got
to
do
certain
things
right,
they're,
gonna,
first
of
all
have
to
do
things
like
define
its
name.
You
know.
How
is
it
gonna
appear,
you
know,
is
it
who
vs.
who
does
properly?
You
know
what
is
it?
A
What
does
it
call
the
how's
it
gonna
cure
when
it's
sterilized
that
kind
of
stuff
they
obviously
need
to
find
the
semantics
of
it.
I
mean
what
does
this
thing
actually
mean?
What
is
its
value
represents
right
if
it's
just
or
it's
not
if
you're
useful
people,
and
then
of
course,
they
have
to
find
it's
tight
right
is
an
integer
string.
Is
it
a
complex
structure
where
with
Vallon
is
if
there
is
a
fixed
list,
those
kind
of
things
all
right
so
basically
need
to
fully
define
what
this
property
is.
A
Basically,
the
same
way,
we've
done
for
our
core
spec
all
right.
Otherwise,
if
they
don't
do
that,
there's
a
very
big
possibility
that
it's
not
going
to
be
widely
used
at
all
or
popularly
used.
You
will
misinterpret
it.
They
really
should
be
clear
about
this
stuff.
In
my
mind,
they
almost
need
to
write
a
spec
okay.
Now
extensions
for
the
perspective
are
basically
anything
that's
not
to
find
inspect
that
MD
right.
A
Those
are
what
our
extensions
are
so
eating
outside
expect
that
MD,
the
reason
I'm
mentioning
this
is
because
there
have
gone
the
sinister
through
some
confusion,
that
only
certain
other
properties
are
quote
extensions
and
there
may
be
different
classifications
of
extensions
and
I
want
to
make
it
clear
that,
from
our
specs
perspective,
extensions
or
extensions
or
extensions,
there
is
no
specialization
of
extensions
they're,
all
not
inspect
that,
be
it's
an
extension
and
that's
what
this
last
get
down
here
is
basically
trying
to
say.
A
B
If
the
spec,
like
there's,
obviously
things
where
you
take
an
existing
well-defined
field-
and
you
put,
it
doesn't
comply
this
back,
but
there's
also
different
theories
on
whether
or
not
someone
conforms
to
our
spec
if
they
have
any
super
set
of
data
at
all
that
we
that
we
described
or
it
used
the
sandbox
like
it.
So
if
our
spec
has
a
map
property
or
a
structured
object
property,
are
they
allowed
to
add
new
fields
that
are
part
of
that
structured
property?
I
would
strongly
strongly
strongly
say.
B
A
Saw
you're,
saying
correctly,
is
if
we
define
a
property
in
the
fact
that
is
a
map
that
games
there's
a
natural
expense
ability
point
in
there
that
people
may
think
is
exists
and
you're
saying
we
should
not
allow
people
to
add
additional
properties
to
that
map,
because
we
own
that
map
trying
to
think
quickly
and
I.
Think
if
so,
that's
a
for
us
to
decide.
So
when
we
define
that
property
I
think
it's
our
job
to
be
clear
about
whether
people
can
add
additional
properties
to
that
map
or
not.
E
I'm
Dom,
yes,
question:
ok
for
all
this
right,
so
the
your
I
think
your
PRI
is
trying
to
define
the
serialization
right.
I
think
we
need
to
separate
these
things.
You
know.
So
there
are
some
attributes
that
belong
to
the
main
stack,
which
is
in
the
spectra
and
V
right,
and
then
there
are
some
attributes
which
have
stations,
which
means
they
do
not
have
official
standing.
They
do
not
run
to
the
men's
back.
So
that's
one
thing:
we
need
to
to
discuss
or
decide
right
to
be
clear
to
everyone.
E
Another
thing
is
how
we
see
relies
on
those
attributes
and
I
think
the
serialization
should
be
the
same,
no
matter
whether
that
actually
was
easy
in
the
men's
spec
or
is
in
the
extension
and
where
they
see
in
station
spec
or
not
on
that
civilization
should
be
the
same.
It
doesn't
matter
whether
the
attributes
is
in
the
mass
spec
or
in
extension,
so
our
our
like
serialization
pr2,
address
the
sterilization
and
then
maybe
there's
another
extension
PR
to
address.
What's
like
the
criteria
to
decide,
what
kind
of
attributes
could
should
be
in
the
men's
spec?
E
What
happens
just
like
lino
I
think
we
have
a
SPR
to
define
the
criteria
for
the
for
the
particle
which
the
civilization
particle
right,
which
will
be
part
of
this
workgroup
as
standard
I
think
we
should
have
to
not
be
confused.
Otherwise,
if
we
confuse
the
serialization,
we
say
no,
we
say
information,
the
extension
or
in
the
main,
that's
a
that's.
That's
why
I'm
only
discussed
so
many
time
times
in
so
many
in
multiple
meetings.
We
still
have
not
sorted
out,
because
I
think
people
are
coming
from
different
perspective.
Understand
it
differently.
A
E
E
That's
my
my
my
that's
my
my
my
thought.
For
example:
I
should
clean
okay
of
the
of
this
incarnation,
this
identification
label
for
correlation
I.
Think
if
it's
a
car,
if
it's
needed
by
a
lot
of
you,
excuses
it's
going
to
be
common
and
used
it
doesn't
matter.
What's
the
format
we're
going
to
decide
as
a
group
I
think
you
should
be
in
the
mass
spec,
but
if
it
is
not
widely
used,
it's
only
used
by
you
know
very
specific,
specific
use
case
right.
Oh
it's
the
only
you
spell
vendor
there.
E
A
E
E
You
have
different
identification
labels
associate
with
that
event,
because
I
was
enough
for
different
use
case
for
different
event
sources,
because
those
event
sources
are
all
different
right:
the
identification
label,
additional
identification,
labor
or
social
is
that
event
could
be
different,
for
example,
for
some
event,
it
could
be
a
house
address
for
another
event.
It
could
be
a
travel
request
ID
and
for
another
event,
it
could
be
like
how
to
say
a
stock
trade
stock
trade
for
such
a
stock
trade
ID.
Something
like
that
right.
F
E
F
A
Kathy,
okay,
yeah
now
does
it
stop
just
because
we're
out
of
time?
Please
don't
yeah
everybody!
Please
take
a
look
at
the
PR
I.
Think
I
actually
did
try
to
address
your
concerns
in
there
Kathy,
but
everybody
else.
Please
take
a
look
at
the
PR
and
in
particular
also
take
a
look
at
this
short
little
PowerPoint
thing.
I
put
together
explaining
why
I
think
a
little
things
are
right
way
to
go,
but
very
quickly.
I
could
just
gets
the
funnel
world
coca-cola
I.
A
Think
Louie
I
heard
you
Dan
I
heard
you
Chris
port
Rose,
you
still
there
I'm
here
all
right,
Stanley
I'm,
here,
Colin
I,
think
I
heard
calling
already
right.
Yep
I'm
here,
yep
siobhan
ringin
apologize,
okay,
Simon
you
there.
Yes,
sir
and
Baram
you
there
Baram
you
still
there
yep
you
got
it
and
I
know:
Dan
was
on
Jamie
the
offline,
so
I
know
he
was
there
all
right,
I
miss
anybody
on
the
roll
call,
all
right
cool.
Thank
you,
sir.