►
From YouTube: [OCI-WG] Reference Types - 2022-01-25
A
A
I'm
okay:
it's
been
a
lot
of
meetings
today.
I
am
tired.
B
Yeah
and
it's
still
early
in
the
day,
I
guess,
unless
you're
in
a
in
a
later
time
zone,.
C
Yes,
I
don't
do
not
envy
envy
that
you
think
that's
bad
kate
stewart
is
in.
A
B
D
B
B
B
B
B
E
It
is
funny
how
they
make
those
recordings
seem
yeah
like
instantaneous,
yeah
2001
is
in
10.
I
think
is
the
last
time
there's
a
couple
of
movies
that
have
done
a
good
job
with
that
yeah
where's,
the
other
one
where
they
go
into
space
and
they
travel
and
they
end
with
everything's
in
the
bookshelves
and
lost.
Oh.
B
Don't
be
given
spoiler,
that's
that's!
What's
it
called
inter
stellar.
F
E
B
B
Girl
see
folks
joining
I'll,
add
a
link
thanks
for
people
putting
their
name
as
attendees.
Would
anybody
like
to
be
notetaker?
I've
been
trying
to
note
take
myself,
but
I'm
realizing
I'm
hitting
the
limits
of
my
own
capacities,
while
talking
single
threaded
run
queue
of
one
human
being
I
am
so.
Does
anybody
else?
Would
anybody
like
to
take
notes
just
place
your
name
in
there
you
get
the
illustrious
honor
of
having
your
name
in
a
separate
section
called
the
note
taker
section.
B
B
A
B
B
Okay,
I
think
we
we
have
enough
folks
here
to
get
started
hello.
What
day
is
it
today?
Oh
it's,
the
25th
of
january,
didn't
that
go
by
quickly,
25th
of
tuesday,
the
25th
of
january
2022,
just
for
the
recording
sake,
hello
and
welcome
to
the
oci
working
group
for
reference
types.
Welcome
everybody
great
to
see
everybody
here
and
I've
placed
a
link
in
the
chat
with
the
agenda
and
meeting
minutes
if
you'd
kindly
place
your
name
under
the
attendees
list.
B
That
would
be
very
much
appreciated,
first
on
the
agenda
today
and
we're
going
to
get
straight
into
it,
thanks
for
note
taker
of
brandon,
brandon,
mitchell
and
jason
hall
next
week,
if
you're
here
with
the
illustrious
second
gold
silver
metal
emoji,
there
didn't
even
know
there
was
one
of
those,
but
thanks
for
adding
it
agenda-wise.
Today
we
have
three
agenda
items.
First,
one
is
josh
going
to
present
an
idea
for
generic
scenario.
Second,
I
was
going
to
present
feedback
on
the
review
of
the
proposals
documents.
B
There
was
niches
and
dans
which
covered
the
first
two
proposals,
and
then
I
was
going
to
make
a
mention
that
I'm
out
next
week
so
have
somebody
else
run
this
meeting
because
it's
lunar
new
year,
so
I'm
out
doing
some
stuff
for
that
that'll
be
fun
but
we'll
get
into
it.
Josh
you
take
the
take
the
reins.
H
I
In
google
slides
you
have
to
go
to
the
presentation
mode
and
then
share
that
screen
that's
presented,
see
afterwards.
Thank
you
very
much.
H
Let
me
you
just
saw
my
desktop
there
right,
yeah.
B
H
H
J
H
Just
to
put
a
little
background
on
why
I
think
something
like
this
might
be
worth
our
while
to
introduce
basically
over
the
past
few
years
it
feels
like
there
has
been
for
lack
of
better
words
politics
in
trying
to
make
progress
in
these
specs,
and
you
know
I
think
it's
it's
healthy
to
you
know.
H
I
mean
you
can't
claim
you
can't
blame
people
for
wanting
to
succeed,
but
if
we
cannot
detach
what
we're
trying
to
succeed
from
a
business
perspective
from
what
we're
trying
to
achieve
in
the
spec,
then
I
think
we're
put
in
a
position
where
we're
in
a
conflict
of
interest
to
accept
other
people's
proposals,
and
so
I
present
to
you
glen
and
larry's
ice
cream
company.
As
our
friendly
example-
and
I
decided
like
to
look
at
this
first
from
a
persona.
H
Next
is
the
ice
cream
factory
worker,
the
person
who
assembles
the
raw
ingredients
and
puts
it
into
a
container
and
makes
it
by
container,
I
should
say
a
carton
and
makes
it
ready
for
to
be
handed
off
to
to
like
the
truck
drivers
or
the
people,
shipping
it
around
and.
H
The
people
who
are
shipping
containers
to
a
registry,
for
example,
with
custom
software,
the
refrigerated
truck
driver
or
the
person
who's
responsible
for
taking
the
ice
cream
from
the
factory
to
the
person
purchasing
it,
and
this,
I
think,
is
actually
the
hosted
registry
right.
This
is
this
is
taking
the
custom
software
and
getting
it
to
where
it
needs
to
go,
and
so
this
specific
persona,
I
think,
applies
to
people
on
this
call
more
than
the
other
ones.
H
Although
it's,
I
think
what
we're
trying
to
design
is
something
that
touches
all
of
these
different
pieces
of
the
puzzle,
the
owner
of
the
bodega,
so
the
person
who
gets
the
ice
cream
from
the
truck
and
then
puts
it
on
the
shelves
so
that
people
can
consume
it,
and
this
is
a
little
bit
hard
to
like
tie
to
a
person.
But
I
would
say
this
is
like
your
production
environment.
This
is
where
this
is.
What's
actually
hosting
your
application,
you
could
look
at
it
if
you're.
H
If
we're
looking
from
like
a
security
angle,
you
could
say
this
is
like
a
kubernetes
admission
controller,
the
person
who
determines
what's
on
the
shelves
or
what
can
go
on
his
shelves
and
then
the
ice
cream
lover.
This
is
the
person
who
actually
consumes
the
ice
cream,
and
this,
I
think,
is
the
actual
end
user
of
the
software.
This
is
the
person
who's
clicking
through
your
application,
and
you
know.
H
Basically,
using
the
software,
they
don't
know
if
it's
containers,
if
it's
hosted
here
or
there,
they
just
want
it
to
work.
Well,
it
tastes
good
and
then
this
this
is
sort
of
an
interesting
person.
H
This
is
the
last
one
and
it's
the
health
insp,
the
health
inspector-
and
this
is
someone
who
might
at
various
stages
in
the
process
from
the
all
the
way
from
the
farmer
to
the
factory
to
the
truck
to
the
bodega
is
making
sure
that
the
ice
cream
is
safe
for
your
consumption
and
to
me
this
is
like
maybe
your
ciso
or
your
security
team,
or
somebody
who's
auditing,
your
environment,
for
any
issues
with
the
ice
cream,
and
so.
H
H
H
I'm
maybe
want
to
eat
it
more
or
I'm
more
able
to
eat
it.
This
is
a
bad
one,
but
I
was
trying
to
come
up
with
my
what
might
be
the
toppings
and
maybe
that's
things
that
help
it
deploy
so
like
a
helm,
chart
or
a
terraform
module.
H
H
I
would
think
this
is
sort
of
comes
down
to
the
sign
off
between
the
factory
and
the
person
who's
distributing
them.
So
when
I'm
talking
to
the
registry
here
so
the
truck
driver,
I'm
I'm
basically
saying
this
stuff-
is
good.
Okay,
go
take
it
to
the
store,
so
here's
here's
where
I
think
this
is
my
kind
of
call
to
action.
So
so,
oh
no,
the
truck
driver
is
in
trouble.
H
A
disgruntled
ice
cream
lover
has
threatened
the
truck
driver
and
they
said
my
child
ate
some
ice
cream
yesterday
and
now
they
have
a
tummy
ache.
You
have
less
than
10
seconds
to
give
me
a
list
of
every
glenn
and
larry's
plant
produced
in
the
last
month
containing
milk
produced
by
lasker
farms,
or
I
will
end
you.
H
So
in
conclusion,
we
need
better
trucks,
so
we
can
save
lives.
We
need
something
like
this.
We
need
an
ipad
on
the
truck
that
can
tell
you
everything
about
the
what's
in
there
and
any
type
of
information
a
truck
driver
may
need
to
know
in
order
to
not
get
killed
and.
H
E
H
I'm
gonna
assess
this.
I'm
gonna
post
this
in
the
in
the
notes,
so
people
can
peruse.
A
Thanks
lucky,
so,
would
you
recommend
josh
that
we
start
using
these
in
our
proposals.
H
H
I
guess
my
idea
is
that,
instead
of
talking
about
oh,
this
is
going
to.
You
know
enable
an
spdx
thing
here.
This
is
going
to
enable
a
cosine
signature.
Here
we
talk
about
it
in
these
types
of
turns,
so
that
we
don't
get
to.
B
Thanks
josh,
I
was
just
gonna
say
you
know,
I
think
it's
good
to
put
names
to
all
these
things.
I
also
wanted
to
get
a
read
on
the
room.
B
I
need
to
talk
about
the
farmer,
the
dairy
farmer,
or
am
I
really
just
talking
about
the
you
know
the
point
of
ice
cream,
the
ice
cream,
the
toppings,
the
ingredients
and
the
nutritional
facts
in
the
truck.
So
I
was
just
like
what
are
the
actual
vernacular
that
I
need
to
do
the
mapping
in
my
mind,
because
you
know
this
is
one
layer
of
abstraction
that
you
know
I'm.
B
But
really
you
know,
I
think
everybody
would
have
to
agree
and
we'd
have
to
document
at
least
an
example
and
at
least
the
the
most
pertinent
pieces,
because
I
think
you
know
of
mining
feedback
is
there's
a
lot
of
terms
there
and
I'm
not
sure
all
of
them
are
needed
to
describe
this
flow.
They
might
be
so
getting
it
down
to
the
most
succinct
list
of
the
ones
we
actually
need
is
probably
going
to
help
me.
But
you
know
this
is
first
blush.
H
Yeah,
I
agree,
and
I
think
people
certain
people
on
this
call
may
have
better
context
on
what
we're
trying
to
get
at
or
may
have
disagreements
or
what
we're
trying
to
get
at
with
reference
types,
and
my
personas
thing
I
think
I
think
I'm
pretty
proud
of
that
as
like.
I
do
think
that
that
lays
out
the
different
people,
but
it's
like
who
are
we
really
trying
to
help
with
this?
A
Like
yeah,
I
think
I
I
did
lower
my
hand,
because
josh
had
answered
concern
that
I
had.
B
Yeah
I
was
wondering
whether
it
might
make
sense
just
to
pop
that
slide
back
up
with
the
you
know,
one
pineapple
glenn
and
larry's
the
ice
cream
itself
and
just
try
and
talk
through
that
together
and
see
exactly
because
I
felt
like
maybe
some
impedance
mismatches
between
like
nutritional
facts
and
toppings
they're
a
little
little
blurry
for
me
and
do
we
need
both
and
if
the
answer
is
yes
or
no
and
then,
as
the
you
know,
as
the
truck
drivers
pad
of
paper.
A
And
my
hand
up
just
I-
I
still
don't
know
whether
the
rest
of
this
group
is
in
agreement,
that
separating
specific
concerns
into
generic
concerns.
Using
these
terms
is
a
good
idea.
G
G
G
We
won't
have
some
people
talking
about
ice
cream
and
some
people
talking
about
cakes
and
some
people
talking
about
pudding
and
you
know
like
if
we
all
have
the
same
canonical
made
up
one.
We
can
agree
on
what
those
are.
I
really
don't
want
to
get
into
a
conversation
about
whether
toppings
are
helm,
charts
or
dairy
and
milk
or
golang.
G
Like
that's,
not
helpful
to
me
how
they,
how
the
analogies
line
up,
I
think,
is
a
waste
of
time,
but
having
there,
there
will
be
times
where
we
need
to
talk
about
s
bombs
because
s
bombs
are
also
signed,
and
that
breaks
the
analogy.
Any
analogy
we
come
up
with,
so
I'm
all
for
having
a
generic
a
canonical
generic
example
so
that
when
we
go
generic,
we
can
agree
on
what
those
are,
but
it's
going
to
break
down.
G
Sometimes
we
need
to
talk
about
the
specific
thing
I
think
josh
to
your
point
about,
like
I
really
don't
want
to
get.
If
we
ever
find
ourselves
in
a
conversation
about
spdx
versus
cyclone
or
cosine
versus
other
formats,
or
a
specific
format
for
a
versus
specific
format
b,
then,
like
that's,
a
a
rat
hole
that
we
need
to
get
away
from,
but
talking
about
s
bombs
and
signatures
is
useful.
Sometimes
talking
about
dairy
and
nutritional
facts
and
pads
of
paper
is
useful.
G
H
Yeah
I
and
I
I
appreciate
I,
I
appreciate
that,
and
I
think
really
my
goal
here
is
not
to
talk
about
ice
cream.
H
My
goal
is
that,
like
this
working
group
will
make
strides,
because
I
think
there's
some
doubts
about
whether
that's
possible,
given
like
the
history
with
issues
kind
of
ending
up
commented
on
for
years
and
nothing
happening
so
anything
it
like
any
parameters
like
json,
like
you're,
saying
like
once,
we
start
talking
about
spdx
or
cyclone
like
maybe
we
can
have
something
in
this
working
group
where
we
have
like
a
no-no
list,
anything
that
can.
J
I
think
the
the
spirit
is
very
much
in
line
with
how
many
of
these
os
projects
even
came
up
right
like
you,
want
to
be
vendor
neutral.
There
are
competing
oss
projects
here
as
well.
That's
coming
up
in
the
same
light.
So
if
we
call
out
in
the
mission
statement
that
this
is
not
just
vendor
neutral
but
almost
like
specific
opinion
neutral
in
some
way
and
it
takes
oci
forward,
that's
the
motivation
of
this
whole
analogy,
drawing
from
trying
to
avoid
the
specific
implementation.
J
The
way
I
see
it,
so
I
think
it's
good
to
have.
This
is
a
generic.
This
is
generic
enough
and
the
moment
there
are
conversations
that
are
aligning
with
specific
implementations.
We
can
clearly
say
that
the
mission
statement
wants
to
avoid
any
attachment
to
any
of
the
other
projects.
Maybe
that's
that's
a
much
more
clear
definition
for
anybody
coming
to
the
project
itself,
and
these
analogies
will
help
for
generic
scenarios.
J
But
I
do
want
to
thank
josh
for
bringing
together
this,
because
it's
really
easy
to
kind
of
look
at
nutritional
facts
and
say
yes
bombs.
I
just
love
that
analogy.
It's
very
simple.
To
kind
of
take
away
so
that
that
was
that
was
really
cool
thanks.
H
E
You
well,
I
just
add
the
the.
I
agree
that
the
I
think
the
piece
is
like
whether
it's
to
jason's
point
it
doesn't
matter
if
it's
cycle
in
a
cyclone
or
spdx
or
some
other
format,
and
it
shouldn't
matter.
I
think
the
approach
that
we've
been
trying
to
take
it
shouldn't,
even
matter
whether
it's
a
signature,
an
s-bomb,
a
scan
result
a
policy,
an
attestation.
E
Whole
ideas.
Can
I
incrementally
add
things
to
something
in
the
registry,
because
I'd
argue
it
doesn't
have
to
be
container
images.
Also,
the
root
might
be
an
s
bomb.
Is
the
root
artifact
that
got
pushed
to
the
registry
that
I
then
want
to
sign
and
put
out
of
stations
too.
So
the
s
bomb
might
be
the
top
object
regardless
of
it,
but
I
think
we
similar
to
I
can
figure
out
files
on
disk
by
looking
at
the
extension.
E
J
E
We
deal
with
that.
Then
you've
got
the
project
mutual
abstractions,
but
your
analogy
of
the
truck
I
mean.
If
you
look
at
shipping
containers
when
the
shipping
dictator
industry
started,
it
was
like,
don't
really
care
what
you
put
in
it.
Here's
a
definition
and
that's
what
I
think
we're
trying
to
figure
with
reference
types
is:
what
is
the
definition
of
a
reference
type
and
then
does
it
matter
what
the
reference
type
is.
It
could
be
josh's
pictures
of
how
he
used
a
particular
ice
cream
or
something
I
don't
know.
H
Yeah
it's
just
a
just
to
like.
I
think
you
have
a
point
there
and
I
think
probably
why
I
had
trouble
with
this.
Sorry,
for
this
slide
is
because,
when
I
was
had
this
idea
last
week,
it
was
maybe
we
don't
need
to
think
specifically
about
s-bombs
or
specifically
about
signatures,
and
we
talk
more
about
sprinkles
and
whipped
cream
and
like
things
that
don't
really
have
a
parallel.
H
B
B
Where
do
we
take
this
and
put
it
and
document
it
and
just
some
guidelines
around
the
usage
or
something
we
just
want
to
make
it
durable
if
we
agree
on
this
and
I'm
not
sure
if
we
can
agree
on
it
at
the
moment,
but
from
everything
I
hear
you
know,
I'm
I'm
in
alignment
with
what
jason
said.
I
think
the
other
thing
to
encourage
people
with
is
yes.
This
has
taken
a
lot
of
time,
but
you
know
the
u.s
constitution
was
written
in
less
than
a
month,
and
this
is
much
easier
than
that.
B
So
if
we
can't
agree
on
you
know-
and
that
was
ten
rules-
you
know
so
we
you
know
if
we
can't
agree
on
something
like
this-
an
amount
of
time.
I'd,
encourage
us
to
say,
hey,
we
can
all
come
together
and
and
get
something
out
of
this
and
and
work
together
to
to
resolution.
So
you
know
I'm
looking
forward
to
that,
and
I
hope
that
we
can
do
that
and
encourage
each
other
to
to
make
decisions.
A
So
I
was
going
to
say:
can
we
have
this
this
slideshow
somewhere?
So
we
can
comment
on
it.
A
And
one
more
thing:
one
more
thing:
lucky,
I
was
wondering
if
they're
they're,
if
you'd
like
to
encourage
folks
to
you,
know,
maybe
see
yourself
in
an
ice
cream
pipeline
scenario
and
find
yourself
in
there
and
maybe
be
able
to
come
up
with
the
thing
like
you
know:
oh
I'm,
the
health
inspector,
I'm
the
ice
cream
lover
and
the
ice
cream.
B
Yeah,
I
think
that's
what
maybe
it
might
come
to
is
having
just
two
or
three
documented
scenarios
like
josh
had
with
the
truck
driver
using
the
the
words
you
proposed
and
maybe
just
having
them
added
to
the
to
the
repo
their
generic
use
case,
as
as
a
good
next
step.
Unless
we
want
to
give
everybody
a
week
to
comment
on
the
doc
and
any
feedback,
and
then
we
can
make
a
decision
what
we
would
like
to
do
for
next
steps.
H
I
can
try
to
get
some
form
of
this
if
it's
just
the
personas
or
something
else
into
that
repo,
whether
it's
in
the
readme
or
some
other
markdown,
just
just
to
capture
it.
I
think,
like
nisha's,
saying
like
being
able
to
come
into
the
group
and
be
like,
oh
I'm,
actually,
the
dairy
farmer
or
this
or
that.
H
B
Ship
it
thanks
thanks
josh.
I
appreciate
you
putting
the
time
into
that
and
look
forward
to
seeing
the
output
of
your
work
in
the
in
the
repo.
So
let
us
know
how
it
goes.
B
Okay,
next
next
item,
so
I
had
an
action
item
last
week
to
to
start
looking
at.
Actually,
there
was
jason
neisha
and
myself
had
an
action
item
to
start
looking
at
the
proposals
and
start
requirements
gathering,
so
I've
placed
two
links
of
documents
that
I
reviewed
in
addition
to
the
initial
proposals,
and
I
wanted
to
just
give
some
feedback
on
how
I
was
thinking
about
this
and
start
a
discussion
about
how
we
could
start
to
break
this
set
of
challenges
down.
B
So
let
me
give
you
that
feedback
and
then
we
can
have
any
questions.
If
folks
have
questions
just
place
your
hand
up,
so
I
read
through
dan
dan
lawrence's
doc
on
the
review
between
the
two
proposals,
which
was
you
know
really
good.
I
encourage
everybody
to
go.
Take
a
look
at
that
and
I
also
read
nisha's
dock
as
well
and
when
you
know
when
I
finished
with
reading
all
those
docs
and
the
proposals
I
started.
B
Thinking
to
myself,
you
know
we're
all
talking
about
the
the
fields
and
the
versioning
and
garbage
collection,
but
nobody's
talking
about
what
the
ux
is
or
what
actually
the
experience
should
be
to
a
to
an
end
user
when
they're
interacting
with
these
types
of
you
know
s-bombs
or
signatures
and
sorry,
I
can
try
and
use
the
the
ice
cream
vernacular
soon.
So
I
think
I
was
very
interested
in
rather
than
working
on
fields
and
changes
to
api
specifications.
Would
it
not
be?
B
Would
it
not
serve
us
well
to
say
as
a
user?
I
can
do
this
this
and
this
these
would
be
my
expectations
and,
for
example,
I
was
thinking
about
you
know
in
the
context
of
those
documents.
If
I
was
to
they,
you
know
that
you
could
read
the
requirements,
but
they're
not
explicit.
B
As
a
user,
can
I
push
an
s-bomb
to
a
registry,
and
you
know
I
was
looking
back
at
the
the
mission
statement,
which
was
to
describe
and
query
those
references.
So
if
I
was
to
query
a
reference,
would
I
say
what
are
the
references
to
this
container
image
or
you
know
what
toppings
or
what
nutritional
labels
go
for
this
ice
cream?
Should
I
actually
say
you
know,
how
would
I
get
that
information
back
out
and
I
thought
that
would
be
really
interesting
to
try
and
nail
those
requirements
down,
because
everything
would
flow
from
that.
B
So
what
is
the
user
expectation
and
what
you
know?
What
are
we
designing
here
from
an
api
level
and
then
getting
into
the
you
know
different
weeds,
because
when
I
did
read
the
three
different
proposals
there,
you
know
it's.
You
know
when
new
manifest
I'll
manifest
with
version
describing
garbage
collection
not
describing
alex
collection.
B
There
wasn't
too
much
differences
down
in
the
weeds
of
how
it
could
be
done,
but
I
just
thought:
maybe
us
discussing
what
we
expect,
as
you
know,
either
as
registry
providers
or
end
users
of
the
behavior
that
we're
expecting
the
registry
to
fulfill
or
the
client
and
making
a
decision
as
to
how
to
do
that.
So
that's
what
I
kind
of
came
out
thinking
was.
I
can't
you
know
reason.
B
It
seemed
to
be
more
a
challenge
with
me
understanding
what
this
referrers
api
would
actually
be
responsible
for
filling
than
it
was
about.
You
know,
lines
in
json
fields
and
manifests
and
how
they
interact.
So
that
was
my
takeaway
is
to
start
with
requirements,
and
then
we
could
go
down
and
reason.
Pausing
jason
has
his
hand
up.
G
G
So
it's
hard
to
design
the
api
to
hopefully
never
be
seen,
but
I
think
it's
worthwhile,
like
you
were
saying
to
to
think
about
like
what
are
some
scenarios
we
want
people
to
be
able
to
do.
I
think
it's
even
I
mean
I'm
gonna
violate
the
rule.
We
already
we
just
put
in
place
and
talk
about
specifics
and
not
ice
cream,
but,
like
I
don't
even
think
users
want
to
say
give
me
images
that
have
s
bombs
right
like
they
want
to
say.
Oh
no,
there's
a
log
for
j
problem.
B
G
Which
isn't,
which
means
even
like
the
existence,
the
concept,
the
definition
of
s
bombs-
is
also
invisible
to
the
end
user.
They
don't
know
whether
it
was
in
format
a
or
b,
and
they
don't
know
how
it
was
attached
and
they
don't
know
how
it
was
stored
they
just
want
to
like
am
I
am
I
going
to
die
from
this
yeah?
Is
this
ice
cream
going
to
kill
me?
They
don't
want
to
know
how
that
information
is
there
and
who
came
up
with
it.
G
Anyway,
I
will
see
by
time
now.
A
So
I
had
started
this
summary
document
that
just
gathers
up
all
the
proposals
together,
but
what
I
was
hoping
to
get
this
time
around
is
that
particular
thing
that
you
mentioned
lucky,
which
is
requirements,
and
it
seems
like
our
first
requirement-
is
user
stories
to
be
able
to
apply
these
proposals
to,
and
since
we
have
now
a
framework
to
talk
about
these
user
stories,
thanks
to
josh
and
his
wonderful
ice
cream
story,
we
can
probably
move
on
from.
A
B
Thank
thanks,
nisha
yeah.
I
think
that's
that's
where
I'd
like
to
go.
That
would
be
my
suggestion
and
you
know
I
did
read
through
your
document.
The
thing
that
wasn't
clear
to
me-
and
you
know
I'm
as
thick
as
two
planks-
is
whether
you
were
suggesting
a
an
abstracted
model
of
the
first
two
proposals
or
an
entirely
different
proposal
that
was
more
generic,
so
I
was
like.
B
B
B
Presumably
so
that
would
be
my
suggestion,
is
you
know,
could
we
could
we
start
to
hash
out
user
stories?
Maybe
we
we
add
a
section
to
your
doc
nisha
and
come
back
next
week
and
start
to
work
through
the
user
stories,
because
I
think
what
what
it's
going
to
go
down
to
is
somebody
reads:
a
user
story
and
people
say
yes
or
no
or
yes,
but
or
no.
A
Yeah,
so
did
I
understand
correctly
that
our
action
is
to
write
down
a
bunch
of
user
stories
and
have
the
group
look
at
them
before
the
next
meeting.
B
Oh
sorry,
that
was
yeah
thanks
brandon.
That
was
my
suggestion.
Just
one
suggestion
in
reading
it
because
I
think
that's
actually
where
we
need
to
get
to
as
a
working
group
is
what
do
we
think
this
api
is
going
to
do?
Not
what
fields
need
to
change
is
secondary
to
that
and
in
what
manifests
and
how
we
version
things
and
what
happens
with
garbage
collection
or
you're?
B
Not
it
was
more
just
I
I
feel,
like
that's
a
great
starting
point,
and
I
feel
like
everybody
who
has
a
stake
in
this
and
is
interested
in
defining
what
that
referrer's
api
behavior
allows.
You
know
users
to
do
having
us
go
and
walk
through
them.
B
I
just
think
you
know
that's
going
to
end
service
better
in
the
long
term.
When
we
really
can
have
say
hey.
Are
we
meeting
the
needs
of
this
ux?
Otherwise
we
don't
need
to
discuss
it
or
this
scenario
and
that's
going
to
help
us
in
you
know
nickel
and
diming
over
every
implementation.
It's
just
that
is
the
agreed
on
requirements.
We
will
build
the
api
to
those
requirements
and
you
know
move
on.
B
D
D
B
B
Brandon
and
I
think
that's
valuable
and
I
think
there's
enough
in
the
proposals
there
that
you
could
synthesize
out
the
requirements.
So
if
that's
the
way
that
you
like
to
to
do
those
things,
I
suggest
you
so
how
about
you
know,
I'm
just
going
to
put
a
proposal
for
an
action
item
here.
Is
I'm
going
to
work
with
nishi
to
open
up
nisha's
dock
to
add
requirements
and
everybody
just
add
your
requirements
that
you
see
fit.
However,
you
like
to
get
them.
B
There
add
your
name
at
the
end
and
then
the
next
meeting
we're
going
to
start
to
walk
through
them
and
see.
If
we
can,
you
know,
see
relationships
between
them
and
whittle
them
down
and
reduce
them
into
a
set
that
we
all
agree
on
and
then
from
there
we
can
go
back
and
reevaluate
the
proposals
seeing
some
nodding
and
thumbs
up
in
agreement.
Are
there
any
other
ways
that
we
can
do
this?
Just
knowing
that
there's
a
lot
of
history
here,
there's
a
lot
of
you
know
great
proposals
out
there.
B
I
just
want
to
I'm
trying
to
understand
how
we
can
move
forward
here
and
that's
my
suggestion.
Okay,
I
see
a
couple
of
thumbs.
Are
we
done?
That's
the
action
item
sounds
good.
Any
anything
else
like
feel
free
to
suggest
other
ways
to
do
this,
because
I
know
you
know
we
could
all
be
at
a
ball
and
a
gate
and
go
start
coding,
but
I
really
think
doing
this
is
going
to
serve
us
well
in
the
wrong
long
run.
B
B
A
B
B
Okay,
the
next
agenda
item
is
I'm
out
next
week
who
would
like
to
run.
This
meeting
sounds
like
we
have
an
agenda
at
least
one
item,
so
can
somebody
run
and
and
that
that
agenda-
or
we
can
also
say,
let's
take
two
weeks
to
sort
this
out,
and
you
know
you
don't
have
to
cancel
the
meeting
on
a
part
of
me.
We
want
to
keep
going.
I
just
won't
be
here
next
week.
So
as
long
as
somebody's
can
can
show
up
and
run
the
meeting.
That's
really
all
I
need
to
make
sure
that
happens.
B
B
Sorry
sorry,
keyword,
okay,
thanks
jeff.
E
B
B
Cool
well,
I
got
marching
orders.
Thank
you
very
much
thanks
josh
for
putting
that
together.
I
know
it
does
take
a
lot
of
time,
so
I
really
appreciate
you
taking
the
time
to
put
that
together.
Thanks
folks
and
we'll
see
you
same
time
same
place
next
week
thanks,
everyone
see
ya,
bye,
bye.
Thank
you.
Bye.