►
From YouTube: CNCF Serverless WG Meeting - 2018-10-11
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
Okay,
we'll
catch
up
with
everybody
else
later.
So,
let's
get
started.
Did
you
hey
eyes,
nothing
too
exciting
there
I
do
not
see
an
Austin
on
the
calls.
We
have
no
update
on
the
SDK,
but
I
don't
think
they
had
a
I'm,
sorry
I
know
we
did
not
have
a
meeting,
so
they
probably
needs
anything
that
they
there
other
than
to
say.
I
will
mention
that
I
bumped
into
mark
peek
who's,
not
gonna,
make
the
call
today
that
lady's
traveling
that
they
did
get
permission
to
transfer
over
there
go
SDK.
A
A
A
Let's
see
coop
con,
so
Kathy,
Clemens
and
I
had
a
discussion
last
week
to
to
talk
about
the
preparations
for
the
deep
dive
and
intro
sessions
for
coop
God.
If
you
guys
are
interested,
there's
a
Google
Doc
here
on
your
update,
my
dip
latigo,
there's
some
very,
very
rough
slides
just
as
an
outline
of
our
various
topics.
A
If
anybody's
interested
in
contributing
to
that,
even
if
you're
not
going
there,
please
feel
free
to
look
it
over
and
correct
things
that
you
see
that
things
are
wrong
as
of
right
now,
the
slides
that
we
won't
have
a
whole
lot
just
sort
of
an
outline
of
what
we
agreed
to
talk
about.
So
I
really
want
to
wait
a
couple
weeks
to
see
something
close
to
the
final
version.
A
You
ready
better
off
anyway
feel
free
to
take
a
look
at
you
guys
want
to
Interop
work
as
far
as
I
can
tell
no
one's
really
put
any
comments
into
the
Interop
demo.
Google
Doc
that
I
put
out
there
I
really
need
to
feedback
here,
in
particular
on
the
type
of
application
we
want
to
do.
The
two
leading
candidates
are
the
natural
language-
translation,
meaning
you
know,
go
from
English
to
French
to
German
back.
A
You
can
go
to
some
like
that
or
a
mad
libs
kind
of
thing
where
each
participant
and
the
demo
just
generates
a
random
adjective
adverb
whatever,
and
we
put
it
into
a
sense.
It's
still
kind
of
funny
things.
We
come
up
with
I
personally
I'm,
leaving
a
little
more
towards
the
mad
libs
thing,
because
I'm
not
sure
how
many
participants
actually
supports
natural
language
translation
and
if
everybody
just
calls
out
to
some
ocular
servers
on
the
internet
and
that
doesn't
really
do
a
whole
lot
for
us.
So
I
really
need
some
feedback
from
you
guys.
A
This
is
probably
not
gonna
be
done
in
time
for
Shanghai,
but
we
are
looking
to
do
something
for
the
KU
concession
in
Seattle,
so
people
probably
need
a
lot
of
time
to
you
know
put
code
together.
So
please
do
comment
on
that.
If
you
get
a
chance,
really
need
some
feedback
there.
Alright,
any
topics
or
any
other
questions
or
comments,
I
need
the
topics
that
we
just
ran
through
all.
A
Right
cool,
in
that
case,
Richard
Hartman,
is
on
the
call
he's
from
the
open
metric
side
of
CN
CF
rotational
while
ago
about
the
possibility
of
some
sort
of
collaboration
between
our
two
groups,
and
we
thought
it
might
be
good
to
just
spend
10
to
15
minutes.
Just
to
have
him
talk
to
this
group
to
share
some
of
the
ideas
that
we
bounced
around
so
Richard.
You
want
to
unmute.
C
Sorry
for
the
background
noise,
but
that
seems
has
subsided
for
apparent
information.
I
will
be
at
both
Q
conch
and
hi
answer
yet
so
we
can
also
sit
down
in
person
if
need
be.
I
also
try
always
to
be
a
little
bit
early,
a
little
bit
late
and
leaving
so
there's
actually
time
to
sit
down
in
peace
and
quiet
outside
of
the
actual
cube
cons.
C
So
all
the
metrics
most
of
you
will
have
heard
of
a
Prometheus,
which
is
the
de-facto
monitoring
solution
within
the
cloud
native
space
in
the
meantime,
especially
since
it's
really
well
integrated,
both
kubernetes
in
premises
or
with
communities
where
the
second
project
to
graduate
within
CNCs
and
there's
quite
some
velocity
behind
what
we
do.
Yet
we
have
the
20
there's
a
ton
of
political
stuff,
around
projects
or
even
vendors,
supporting
a
competing
product,
slash
a
prety,
a
competing
project.
C
We
already
started
to
to
branch
out
a
second
thing,
which
is
not
yet
fully
done,
which
would
probably
called
open
stats
or
something
which
is
more
like
step,
see
where
you
actually
push
data
in
as
opposed
to
there
with
open
metrics
you
pro.
There
there's
also
some
other
operational
differences.
Certain
large
deployments
need
that
kind
of
thing,
so
we
decided
to
split
the
Instituto,
keep
it
nice
and
simple,
but
we
also
plan
to
expand
beyond
that,
and
that
would
then
cover,
for
example,
events,
log
files,
trades
as
all
these
things.
C
So
basically,
what
we
are
doing
is
we
are
defining
a
format
through
which
you
can
transmit
data
from
what
I
can
see
of
cloudy
ones.
Basically,
what
you're
doing
is
you're
defining
what
needs
to
be
transmitted
on
a
wire
by
being
flexible
about
how
the
exact
format
looks
and
that's
basically,
where
I
see
the
potential
for
collaboration
in
as
much
as
we
have
an
opinion
about
how
things
should
look
and
I'll
give
you
things
for
metrics
for
stats
for
logs
for
trades.
C
It
should
look
very,
very
similar,
so
people
learn
it
once
and
then
they
basically
can
you
can
deal
with
that
data,
no
matter
what
type
of
data
it
is
there
is.
You
only
have
minimum
requirements
on
the
certain
data
types
which
need
to
be
exposed,
but
else
you'd
only
care
about
the
form
and
that's
where
I
see
the
intersection
for
the
possible
intersection.
But
basically
you
support
something
which
looks
like
open
metrics
but
for
events,
and
we,
on
the
other
hand,
basically
support
it,
and
then
we
call
it
whatever.
A
I
know
I
think
it
might
be
useful
actually
to
expand
a
little,
because
you
were
very
quick
on
it
and
where
you
see
the
collaboration
have
put
it
in
very
precise
terms,
like
the
word
that
we'll
do
you
see
us
producing
a
out
event,
mapping
for
open
metrics,
or
how
did
you
see
the
collaboration
breeze
or
the
code?
What
would
the
collaboration
result
input
that
way?
Ideally.
C
C
C
If
click
on
that
link,
what
you'll
see
is
current
live
data
from
a
demo
instance
of
committees,
and
this
is
how
the
promises-
expensive
formats
look
form
it
looks
like,
but
basically,
in
this
specific
case
it
would
look
exactly
the
same
if
you're
doing
open
metrics.
So
what
you're
seeing
here
is
a
certain
format
of
how
to
define
data
which
is
attached
to
things.
You
have
the
name
of
five
of
the
time
series.
Then
you
have
certain
label
sets
which
are
basic
key
value
pairs,
and
then
you
feed
different
keys
with
different
values.
C
So
if
you
look
at
that,
you
can
easily
see
how
or
how
you
could
transform
something
which
is
already
now
being
done
in
one
of
the
format's
of
Godwin's,
to
just
look
the
same
in
respect
to
the
format
and
that's
basically
what
what
I'd
like
to
see
come
out
of
this
possible
coordination
and
collaboration.
The.
C
Basically,
in
both
directions
so
again
from
from
what
we
do
at
open
metrics,
we
actually
named
the
group
in
which
we're
doing
this
okay
to
have
open,
observe
ability
to
deliberately
expand
the
purpose
beyond
just
metrics
course.
You
know
more
for
to
observe
ability,
I
don't
have
to
convince
you,
but
and
that
we
say
as
a
CDF
member
project.
C
Okay,
this
can
or
should
look
like
that,
and
he
is
also
a
CNCs
project,
say:
okay,
it
can
also
look
at
that
and
just
by
happenstance,
it's
exactly
the
same,
and
then
we
just
I
say
you
support
the
open,
whatever
format
within
cloudy
winds
and
he
opened
whatever
format
of
cloud
events.
Also
support
seems
sorry,
supports,
cloudy
and
based
on
the
background,
I'm
being
distracted,
yeah.
E
So
so
so
far
or
do
with
followed
events
is
we're
expressing
distinct
events
and
then
are
effectively
dispatching
and
routing
events.
That's,
and,
and-
and
there
are
different
from
so
I-
think
what
were
mostly
would
be
so
so
far
been
focusing
on
also
in
our
interoperability.
Samples
and
most
of
discussions
are
events
which
are
actionable,
which
means
that
you
raise
an
event
from
a
source,
something
just
happens,
and
then
you
dispatch
that
to
a
handler
which
sits
somewhere
on
the
other
side
of
the
world,
and
that
then
goes
and
reacts
to
it.
E
It
looks
like
what
you
have
here
is
more
a
data
stream
of
observability
things
which
are
not
necessarily
immediately
actionable,
but
there
a
robbery
later
processing
which
is
a
bit
of
a
different
pattern
and
which
we've
also
discussed
like
we've.
Had
we
have
extensions
that
are
allowing
to
put
you
know,
sequence
numbers
on
on
events
etc,
but
we're
really
looking
more
at
discrete
events
which
are
individually
handled
and
an
individually
dispatched
for
Puffs
subsystems,
and
there
are
individually
invoking
functions
rather
than
looking
at
streams
of
events.
C
Get
what
you
mean
so
and
that's
where
they
basically
or
to
the
other
other
way
around
your
focus
is
on
a
different
level
than
our
focus.
Our
focus
is
to
have
a
common
format
which
people
can
can
basically
parse
and
rely
on
certain
aspects
of
having
of
having
a
certain
format
for
the
data
to
make
it
easier
to
then,
for
example,
most
most
systems.
Today,
all
the
legacy
systems
are
hierarchical
data
structure.
You
don't
have
them
that's
great.
We
don't
have
them
either.
C
So
that's,
for
example,
something
which
people
should
be
able
to
rely
on
to
have
certain
baseline
assumptions
about
how
data
is
being
structured
at
the
conceptual
level,
but
all
right.
Just
to
finish
your
thought.
If
you
send
something
actual
and
that's
I
know
that
that
is
basically
your
current
focus.
Don't
care
as
much
about
how
the
format
looks.
C
C
C
You
know
this
specific
type
of
data
not
know,
but
this
is
just
for
demonstration
of
how
the
format
looks.
Of
course,
it
makes
easier
to
to
discuss
things
when
you
know
what
isn't
talked
about
specifically,
but
so
basically,
if
you
have-
or
you
have
an
event,
you
want
to
transmit
that
you
end
what
I
would
expect
to
happen.
If
you
are
open
whatever
compatible
is
you
have
a
format
in
which
you
say?
Okay,
this
is
the
name
of
my
rent.
C
Obviously
you
had
a
different
name,
then
all
the
metadata
which
human
date
that
must
be
included
with
an
event
would
come
within
the
curly
braces
penalty
and
he
would
have
the
actual
value
of
the
event
or
maybe,
in
your
case,
you
would
put
everything
into
the
keys
and
key
value
pairs,
and
that's
basically
it
and
you
sent
this
over
the
line,
and
the
only
thing
I
would
care
about
is
that
this
looks
basically
like
that,
so
someone
who's
familiar
with
otometrics
open
stats.
Again,
we
are
also
looking
at
transmitting.
C
Traces
was
the
same
with
the
same
format,
blah
blah
blah
that
this
basically
looks
and
that's
all
I
care
about,
at
least
on
this
level
right.
Well,
you
keep
your
space,
mainly
in
our
head.
Sometimes
it's
a
large
problem
of
where
we
currently
are.
We
have
so.
Basically,
we
have
a
biweekly
hall
and
we're
currently
interface
wherever
you're,
both
implementing
reference
code.
C
Okay,
we
already
have
writing
code,
which
omits
format
and
also
we
are
currently
writing
internet
draft
with
the
purpose,
of
course,
becoming
an
actual
RFC,
but
it's
not
that
yet
time
so
there's
it
some
pieces
of
the
of
the
internet
draft
in
our
repository,
which
I'm
going
to
link
you
in
a
second
but
I
think
this
is
not
done
yet.
So
you
can
look
at
the
full
spectrum
is
a
good
short
and
of
showing
there
the
forum
and
topic
to
just
look
at
demo
demo
traffic.
C
So
basically,
what
you
see
here
is
what
what
we're
doing
so,
it's
always
going
to
be
limited
to
over
HTTP.
Always,
yes,
exactly
I
think
you
do,
and
it
always
is
either
UPF
at
utf-8
encoded
text
or
it
is
proto,
and
then
you
have
what
you
see
there.
That's
the
basic
thing:
there's
a
pull
request
open
for
email
for
the
draft.
I
can
also
think
that
probably
useless
for
you
can
also
link
the
Python
code
for
emitting
for
emitting
now.
E
C
D
C
Yes,
in
the
metric
space
again,
this
is
here
exactly
and
only
for
metrics
and
a
lot
of
the
design
decisions
make
here
are
being
half,
because
this
allows
us
to
to
compress
extremely
well
in
the
database,
but
really
extremely
well.
So
what
you
see
here
would
not
work
for
events,
for
obvious
reasons.
Of
course,
this
is
just
for
metrics,
but
forget
you
ignore
the
the
number
on
the
right
hand,
side
and
basically
look
at
the
name,
and
the
key
value
of
here
is
within
the
current
list.
That's
what
he
would
be
using.
E
Since,
for
both
sister
goes
about
transferring,
so
both
projects
have
a
notion
of
events
and
I
I
assume
that
the
data
that
you
have
in
your
project
is
useful,
potentially
for
people
who
are
using
and
want
to
use
the
elements
from
that.
It'll
be
interesting
to
map
one
one
to
the
other
and
see
when
there's
conversions
potential,
but
we
would
have
to
have.
We
would
have
to
have
a
effectively
a
full
wire
specification
to
look
at
yes,.
C
Agreed
we
don't
have,
but
yet,
and
basically
we
will
have
it
soon.
This
is
a
good
place
where,
when
you
have
a
people,
look
I
can
also
just
take
some
random
demo.
Data
would
have
any
repository
and
transform
it
into
what
I
would
expect
this
to
look
like,
of
course,
this
would
what
basically
short-circuit
the
need
of
having
the
full
spec
already
with
note,
and
we
have
also
already
something
to
look
at
to
go
from
there.
C
F
A
G
C
So,
as
we
have
a
quote,
that's
compatible
with
the
Prometheus
exposition
format.
We
have
over
300
different
exporters
written
by
dozens
or
hundreds
of
different
entities
here,
aware
of
either
thousands
or
tens
of
thousands
of
companies
actively
using
this
wire
fall
within
the
context
of
community.
We
have
several
competing
projects
and
also
competing
values.
I
mean
we
are
project,
so
we
don't
have
the
product
I
sell,
but
still
there
are
vendors
which
have
a
competing
monitoring
solutions
which
either
adapted
our
our
format
or
even
just
food.
C
In
our
libraries
first
Apache
episode,
a
camera,
so
there
are
tons
of
adaption
in
their
Google
is
currently
looking
at.
Making
open
sense
is
compatible
with
open,
metrics
or
they're,
not
looking
at
it.
They
are
actively
working
on
it.
Uber
is
actively
working
on
making
their
stuff
speak.
Open,
metrics
I
had
Apple
contact
me
two
weeks
ago,
there's
tons
of
others.
So
basically
there
is
already
quite
some
adaption
and
also
there
is
quite
some
interest
in
this,
but
this
is
only
for
the
metrics
sudden
for
the
stats
side
course.
C
G
H
You
said
you
are
looking
to
integrate
Prometheus
into
open,
metrics
or
actually
build
open
metrics
on
top
of
that
does
that
include
the
alerting
side
and
surfacing
actual
events
as
we're
speaking
about
them
from
Prometheus
and
the
related
systems
to
users,
because
I
see
that's
where
the
biggest
actual
potential
for
collaboration
would
be
not
in
actual
metrics
clock.
What
happened
because
of
that
yep.
C
So,
basically,
currently
what
what
the
meter
is
doing
so
current
itself
already
is
there's
already
a
branch
which
which
is
able
to
ingest
open
metrics
data.
That's
the
metric
side
on
the
events
of
of
premises.
I
fully
expect
when
we
are
actually
done
with
defining
something
which
which
transmits
events
that
parameters
and
alert
manager
would
migrate
to
that.
C
We
are
also
currently
looking
at
having
a
completely
new
system
for
alert
since
or
events
things
within
the
committee
space
to
not
only
have
an
alert
ninja
which
basically
throws
out
garbage
or
alerts
and
then
to
know
about
them
anymore.
It
doesn't
persist
anything.
So
there
is
more
of
a
user
story
about
every
following
up
about
stuffing
and
persisting
important
information,
bla
bla
bla.
C
It's
like
this
little
data
point
of
something
is
all
I
need
to
fiction
and
I
would
expect
everything
which
happens
in
the
space
to
use,
something
which
looks
basically
but
also
information
where
fauna
is
playing
with
something
for
for
lock
for
not
likes.
Just
like
we
play
isn't,
which
is
also
listen,
and
it
basically
looks
the
same.
You
just
have
text
and
not
enough
numbers
on
the
right-hand
side,
but
else
it
looks
the
same.
So
this
would
all
migrate
to
exactly
this
format
or
with
to
this
format,
family.
Let's
say.
E
C
C
What
we
see,
especially
in
a
cloud
native
space,
is
that
a
HTTP
really
is
the
new
tcp/ip
and
everything
is
an
HTTP
endpoint,
and
that
is
something
which
which
all
of
premises
is
built
upon.
Basically,
income
because
it
comes
from
Google,
is
stolen
from
or
whatever,
and
there
that
it's
already
decays,
but
the
cloud
native
space
is
also
really
really
getting
into
that.
That
corner
where,
basically,
everything
is
an
HTTP
endpoint,
because
it
makes
a
ton
of
things
a
lot
easier.
C
A
All
right,
well
cool!
Thank
you,
Richard
for
doing
that.
I
refer
you're
talking
to
us,
as
I
said
I
think
once
you
gets
out
of
the
specific
went
to
get
the
specification
written,
go
ahead
and
ping
me
or
us,
and
then
we
can
probably
have
another
conversation
at
that
point.
Does
that
sound
fair
sounds
great.
A
C
You
is
it
ok
if
I
drop
off
the
call
curse,
there's
people
waiting
for
me.
Oh
of
course.
Yes,
yes,
please,
ok!
Ok!
Thank
you
very
much.
Whatever
times
dude
you're
in
talk
to
you
soon
come.
A
A
E
E
E
So
effectively
cloud
events
extension,
so
this
is
effectively
creating
an
escape
hatch
and
it's
something.
Someone
raised
that
and
I
I
can't
remember
I,
think
of
to
you
that
if
extensions
may
have
to
specify
their
own
HTTP
headers
and
or
they
may
have
a
different
mapping
rule
for
the
attributes
that
they
define
in
other
ways
and
so
a
this
is
a
vaguely
allowing
and
extending
to
do
that.
So
there
are
because
we're
with
pretty
hard
and
fast
rules
here
and
how
the
melody
that
Hatter
is
actually
mapped
down.
E
J
E
Has
specific
HP
headers
that
must
be
used
and
certainly
in
a
certain
way,
and
this
is
basically
saying
yeah
what
you
should
do
if
you
are
implementing
extension,
you
can
look,
should
look
into
the
extension,
how
it
does
that,
and
so
that's
what
that
first
paragraph
is
it's
more
and
if
you
do
this,
then,
and
that's
what
the
second
Clause
says,
is
you
can't
just
do
that
right
in
P?
You
also
need
to
do
that
for
all
the
other
protocols
that
we
have.
A
A
K
E
So
the
first
year
right,
this
would
have
to
go
and
say
when
used
with
for
a
sheep
in
this,
this
spec
needs
to
define
how
it
wants
to
go
and
happens.
It's
HTTP
headers
look
right
must
be
over
in
code
over
HTTP
as
headers
in
the
following
way,
and
it
needs
to
go
ahead
and
and
define
clearly
how
it
ones,
the
HTTP
headers
to
look
and
I
think
for
interoperability,
even
if
just
HTTP
is
defined
in
distributed
tracing.
K
E
That's
all
I
look
at
like
if
you
have
all
rights.
If
we
allow
override
below
diversion
they're
versions
from
the
standard
mapping,
then
effectively
whatever
we
created
these
extension
plugins,
the
transport
must
be
able
to
go
and
call
in
to
them
right
use
them
to
say.
Oh
yeah
and
I'll
have
some
metadata.
I
know
you
need
to
go,
and
please
translate
that
for
me.
It's
the
headers,
because
I
don't
know
how.
A
E
I
prefer
having
things
in
the
place
where
you
can't
ignore
them:
okay,
that's
right,
which
is
right
in
the
spec
I'm.
Looking
at
this
I
have
another
specs
which
are
all
interdependent
documents
right
now,
within
ATP
and
I'm.
Also,
finding
myself
replicating
a
lot
of
work.
Just
that
you
can.
You
can't
escape
the
the
normative
power
of,
but
want
to
say
by
ignoring
the
document
right.
Okay,.
A
That's
fine,
okay,
I
believe
this
has
actually
been
out
there
for
a
while.
So
hopefully
people
have
a
chance
to
look
at
it,
but
we
haven't
had
just
actually
discuss
it
till
today
and
then
they
put
the
question
out
there.
Do
people
need
more
time
to
review
this
before
I
ask
for
approval.
Do
not
hesitate
to
ask
for
time
is
I,
don't
think
this
is
critical.
So
if
you
need
more
time,
don't
hesitate
to
speak
up,
but
I
also
don't
want
to
pretty
much
surely
or
unnecessarily
to
block
it
either.
A
A
A
A
A
E
The
the
normative
text
is
making
do
the
same
and
unchanged
that
I
just
all
the
work
to
go
through
all
the
documents
and
make
that
change.
Now.
You
also
see
that
the
effects
of
that
that
this
runs
together
and
I
think
that
will
trigger
some
reaction,
who
are
keen
on
having
everything,
nice
and
aesthetic
but
I.
E
E
E
That's
my
point
right,
the
other
supportive,
a
personal,
so
the
actual
score
from
the
ASCII
character
said,
and
you
must
begin
with
the
lowercase
letter
and
then
so
I'm,
just
adding
the
underscore
but
effectively.
Now
that
I
have
the
underscore
separator
or
separator
now
I'm,
also
using
it,
and
that's
what
I'm
doing
in
this
in
this
variation
variation,
where
I'm
now
also
using
event
underscore
type
and
then
do
this
through
the
they
give
you
scroll
down,
I,
just
we
made
rename
them
all
in
appropriate
way.
E
Cloud
events
version
did
that
for
all
those
and
rename
them
through
entire
documents,
and
now
this
looks
a
little
nicer,
especially
if
you're
a
Python
person,
probably
but
it
runs,
have
been
a
bit
longer
and
I
see
yeah
one
of
the
three
characters:
learning
that
one
I'm
okay,
either
way:
I'm
leaning
towards
the
first
one.
But
it's
all
it
was
without
the
underscore
because
of
the
risk
of
the
end,
there's
more
character
overall
and
because
I'm
a
fan
of
staining
a
bike
or
two
of
the
wire.
E
A
D
D
A
Does
that
mean
that
we
should
encourage
people?
You
said
a
word
separate
is
what
I'm
wondering
is
if
someone
defines
an
extension
and
they
choose
not
to
use
underscore
because
they
just
say
they've
up
there
like
you,
they
just
don't
see
the
point
in
underscore,
so
they
choose
not
to.
Is
it
going
to
hurt
the
adoption
of
our
spec?
If
we
don't
encourage
extensions
to
also
use
underscores.
N
This
is
cheb,
not
really
a
question,
but
just
an
observation,
I
I
would
vote
for
the
second
one.
It's
just
a
stylistic
thing
from
my
point
of
view,
I
wonder
at
the
same
time,
if
we
could
normalize
the
sum
of
the
attribute
names,
so
you
know
if
we've
got
event
type,
why
don't
we
have
event
source
and
event
data
and
just
sort
of
keep
it
all
consistent.
E
That's
the
thing
I
didn't
do
wrong
to
talk
to
you
about
last
week
is
to
actually
go
in
and
trim
the
the
names
and
basically
terms
it
so
because
you
know
type
and
ID
and
all
those
things
that
I
thought
of
that.
But
then
that
was
a
bit
much
surgery
for
my
taste,
sure
your
single
PR
but
yeah,
that's
something
like
trivia.
The
names
is
something
that
I'm
in
favor
of
to
which
also
gets
us
out
of
some
of
those
underscore
cases
exactly.
N
N
A
E
Attribute
first
attribute
to
the
MVP
are
case:
sensitive
and
okay
and
Jason
is
case
sensitive.
So
we
have.
The
problem
we
have
is
that
we
have
parts
of
parts
of
the
infrastructure.
Retargeting
is
case,
insensitive
and
parts
of
it
is
case
sensitive
and
we
have
observed
I
think
some
people
have
observed
some
libraries
and
that
they've
been
using,
who
try
to
be
really
clever
about
how
they
do
casing,
with
with
headers
and
and
did
case,
holding
kind
of
all
by
themselves
for
aesthetics,
and
so
that's
all
causing
all
kinds
of
of
confusion.
O
Make
a
PR
for
this
idea,
but
what
would
you
think
of
if
the
go?
If
your
map
goes
into
the
JSON
header,
it
comes
along
with
a
translation
object.
We
use
the
ease
in
the
header
and
it
should
JSON
or
AMQP
into
this
field,
and
we
know
we
can't
do
direct
translation
between
the
two.
So
here's
a
lookup
guide,
I.
A
Actually,
Scott
I
think
that's
similar
to
something
I
was
died
suggested
awhile
ago,
which
was
in
essence
add
another
message
with
the
proper
term
is
of
a
parameter.
Today's
GP
header,
you
know
that
so
the
nhb
header
value
you
see,
semi
colon
name
equals
and
then
the
real
name
in
the
right
case
I
think
it
says
that
sense.
It's
almost
similar
but
you're,
suggesting
there
yeah.
O
L
L
O
E
O
E
It
with
this
so
we're
looking
at
and
the
the
lower
the
underscore
variation
of
this
one
which
I'm
not
preferring
but
the
preferring
the
one
that
is
all
lowercase
all
lowercase.
All
lowercase
will
sense
if
you
are
putting
an
event
on
the
wire
and
no
matter
what
what
what
wire
format
you
everything
has
to
be
lowercase.
E
H
E
E
J
A
J
E
A
I
I
think
Clements
probably
covered
it.
I
just
wanted
to
point
out
that
if
you
adopt
this
proposal,
then
you're
gonna
be
a
hundred
percent
sure
that
the
representation
on
the
wire
and
the
representation
in
the
JSON
blog
you
got
in
the
representation
anywhere
is
always
going
to
be
the
same
bit
for
bit
reducing
one
place
where
somebody
can
get
the
screw
things.
That's
all.
Okay,.
H
A
E
E
And
really
in
the
SDK
is
you
can
go
and
make
it
in
the
SDK
C
will
make
it
a
pneumatic.
You
will
make
it
Pascal
case
were
needed
and
camel
case
were
needed
like
if
you
have
sperm
inside
for
starting
ten
representations,
and
so
this
is
really
just
about
the
wire,
so
I'm
not
too
worried
about
it.
But
it's
something
that
I
mean
I'm,
putting
both
options
up
and
whatever
wins
ways.
A
Okay,
so
I
think
we're
gonna
have
to
call
time
on
this
one
because
we're
on
top
of
the
hour
I,
don't
get
this
sense
from
the
group
that
people
feel
like
they're
ready
to
to
do
something
as
serious
as
take
a
vote
on
the
three
different
proposals
that
are
out
there
I
think
again,
it
says
you
want
a
little
more
time
to
think
a
little
bit
about
this
and
possibly
continue
the
discussion
next
week.
Yeah
is
that
fair
or
zag
agreed
I.
A
Heard
come
and
say
yes,
but
is
there
anybody?
Okay,
I'm
gonna,
make
it
someone's
speaking
up,
I'm
gonna
jump
in
here
say
it.
Let's
do
that
let's
I
was
gonna.
Try
to
force
an
essay
about
today
but
force
a
vote
next
week
and
say
here
are
the
three
choices:
we're
gonna
have
a
voting
scheme
to
decide
that
but
I'm
gonna
hold
off
and
say:
let's
concede
see
if
we
want
to
continue
the
discussion
next
week.
A
Next
week's
call
we
will
decide
on
the
voting
mechanism
to
move
forward
and
one
of
the
choices
could
be
to
do
nothing,
obviously,
because
we
can
close
all
pr's
and
say
find
something
else,
but
we'll
come
up
with
the
voting
strategy
at
next
week's
call.
After
assuming
the
discussion
does
end
and
then
we'll
figure
out
how
to
do
a
vote
at
that
point.
Does
that
sound
fair
to
everybody?
So
we're
not
be
voting
next
week,
we'll
be,
did
we'll
be
deciding
the
voting
mechanism
next
week,
assumingly
in
the
discussion
next
week,
yeah.
A
A
A
A
J
A
F
F
A
D
A
Although
I
don't
see
Cathy,
actually
you
know
what
to
be
honest,
I
was
kind
of
hoping
we
get
on
here
and
say
no
one
actually
did
anything
other
than
me
set
up.
The
templates
and
I'll
say
what
we
cancel
the
call
okay.
E
A
Cathy
welcome
yeah,
I,
guess
I
actually
couldn't
Scott
you're
you're.
Taking
on
that
list
too,
so
I
did
create
the
PowerPoint
slide.
That
I
decided
to
put
both
slides
into
one
long
deck.
That
way
we
can
easily
just
go
from
one
to
the
other
to
make
sure
it
all
flows.
Nicely
I
didn't
put
anything
in
there
other
than
basically
the
outline
that
we
worked
on
from
the
Google
Doc
itself.