►
From YouTube: W3C WebPerformance WG design call February 14th 2019
A
A
A
C
B
E
C
D
A
F
A
A
A
G
F
A
Yeah
I'm!
Sorry
about
that.
A
A
Wednesday
is
oh,
no
I
can't
I
washed.
It
I
can't.
I
A
A
A
A
B
He's
saying
he
can
hear
so
maybehe
we
got
here
new
like
any
wage.
While
these
this
is
bidding
hey,
I
guess
I
can
provide
a
little
bit
of
context.
B
I
guess
feel
free
to
dive
in
I
was
just
gonna,
provide
a
tiny
bit
of
context,
which
is
I've
talked
about
scheduling
on
a
previous
wall
as
well
as
a
tea
bag,
and
well
we've
been
working
with
a
bunch
of
partners
who
are
have
scheduling,
systems
and
JavaScript,
and
so
the
proposals
that
chiffons
gonna
talk
about
today
are
basically
incrementally
help
them
with
their
problems.
So
you
have
to
take
it
away.
D
F
So
window
dot,
so
I
should
first
say
that
all
this
sort
of
naming
in
a
lot
of
the
shape
of
this
stuff
is
not
set
in
stone.
We
do
want
to
ship
these
behind
a
flag
and
chromium
soon
as
an
experiment
and
possibly
an
origin
trial,
to
to
see
how
people
feel
about
them,
but
were
probably
some
distance
from
a
formal
standards
process
for
any
of
this
stuff,
so
the
first
one
is
window
dot
time
until
next
frame.
F
So
it's
method
on
the
global
object,
I
think
the
best
reference
point
for
this
is
the
quest.
I
will
call
back
which
not
sure
how
commonly
known
this
is,
but
when
you
register
a
callback
with
request,
I
would
call
back
you
receive
an
argument
to
your
callback
function,
which
is
an
idle
deadline.
Object.
The
idle
deadline.
F
Object
has
a
method
time
remaining
and
every
time
you
call
it,
it
will
give
you
a
number
in
milliseconds,
which
is
the
implementations
best
guess
of
how
much
time
you
have
left
to
run
code
before
something
urgent
needs
to
be
serviced
without
going
into
the
details
too
much.
Basically,
if
there's
no,
there
are
no.
Pending
events,
input
events
or
any
things
with
that
urgency,
the
time
you
get
back
will
be
the
estimated
time
until
the
next
rendering
update
is
scheduled.
If
there
are
no
rendering
updates
scheduled
you'll
get
a
maximum
time
of
fifty.
F
So
what
we've
been
hearing
from
developers
and
I
should
say
that
people
we've
been
talking
to
most
our
react.
People
at
Facebook,
as
well
as
the
Maps
team
here
at
Google,
and
then
I
think
she's
talked
to
some
other
external
developers,
but
those
are
the
big
ones
that
have
been
it's
warming,
a
lot
of
what
we've
been
doing
just.
K
Real
quick,
I'll
interject
because
communicate
this
to
Schumi
I've
got
about
20.
Microsoft
teams
lined
up
over
the
next
two
or
three
weeks
to
gather
their
feedback
and
whether
or
not
they
can
immediately
gain
values
from
these
eight
guys.
So
in
about
a
month,
so
I'm
not
gonna
have
I'll
go
to
show
them.
Yeah
do.
K
They
have,
in
some
piece
of
their
systems,
attempted
to
segregate
some
work
in
it,
but
not
like
a
react
scheduler
or
the
map
schedule
they're,
not
that
sophisticated,
so
I'll
have
a
better
to
breakdown.
Like
I
said,
once
I've
gathered
all
this
information
and
cold
great
thanks
by
the
way
they
all
think
they
want
the
api's
I.
As
you
know,
I'm
I'm
always
been
questioning.
So
we'll
see.
How
many
will
you
benefit
sure
yeah.
So.
F
F
F
Apart
from
whether
they're
appending
input
events,
so
they
really
want
to
be
able
to
to
intelligently
schedule,
work
around
frame
deadlines,
which
is
why
they
don't
so
that
again
the
idle
deadline
object
that
will
return
you.
You
know
if
there's
a
pending
input.
Events
in
the
time
reigning
remaining
method
will
return
zero
on
deadline.
They
they,
the
developers
we
talked
to
wanted
to
not
have
that
behavior.
They
wanted
it
strictly
based
on
frame
three
budgets,
so
this
would
be
a
method
that
could
be
called
any
time,
not
just
in
request.
F
I
will
call
back
any
time
you
kinda
wanna,
you
can
imagine
if
you
are
a
sophisticated
developer
and
you're
writing
sort
of
an
event
loop
within
JavaScript
and
every
time
you
get
to
the
top
of
the
event
loop.
You
want
to
check
and
see.
If
you
have
enough
time
left
to
run
another
unit
of
work
or
whether
it's
time
to
yield
back
to
the
browser's
in
the
browser
can
update
them,
I
mean
that's
kind
of
what
this
is
geared
towards.
H
So
I
think
this
API
is
a
bit
problematic
for
us,
because
I
don't
think
we
will
know
this
time
necessary
because
we'll
rely
on
cz
or
seer
to
let
us
know
when
the
next
frame
is
but
like
to
do
that.
We
have
to
raise
the
call
back
to
do
that
so
like
in
order
to
know
the
next
time.
Rendering
opportunity
will
happen.
We
have
to
basically
render
sort
of.
F
H
Refresh
rate
would
dynamically
change
the
basin's
by
the
system
so
I
we
like
it,
for
example,
if
like
if
the
OS
detects
that
application
is
not
catching
up
with
the
frame
rate,
we
would
automatically
filter
back
to
60
Hertz
or
in
the
30
Hort.
So
the
system
like
itself
is
dynamically.
Changing
the
freshmen
of
hardware
to
save
the
battery
life
in
that
case,
so
does
the
so.
F
Theoretically,
chromium
can
work
the
same
way,
but
whenever
we
get
the
frame
signal,
we
get
an
extra
field,
which
is
the
current
refreshment
that
the
system
is
working
at
now,
the
hardware.
So
if
we,
if
we
were
to
apply
some
Intel,
there's
actually
a
discussion
of
this
applying
some
acknowledges
so
for
all
go
back
the
frame
we
would
still
be
communicating
to
the
rendering
stuff.
This
is
the
rate
that
will
run
out
right
now.
H
Okay,
that's
that's
assuming
we
did
render
like
worth
something
we
right,
ender
right
in
that
case
we
would
know,
but
in
EXO
like
this
with
this
API,
because
we
are
taking
about
the
future.
It's
a
bit
for
me
because
if
we'd
never
tell
to
the
system,
oh
I'm
I
need
to
render
then
system
will
never
tell
us
the
name.
So
just
as.
F
A
bit
of
analogy:
if
you
did
a
request,
I
will
call
back
and
your
callback
was
invoked
and
you
check
the
idle
deadline.
Object
and
you
check
time
remaining
and
it's
a
50
milliseconds.
Then
you
would
conclude
it
there.
No
there's
no
rendering
scheduled.
If
the
next
thing
you
did
was
update
style,
the
Dom
node.
Obviously
the
50
milliseconds
is
no
longer
the
right
number.
So
don't.
H
Probably
from
that
sure
I
mean,
but
I
saw
so,
I
have
suggested
this
multiple
times
in
the
past
feedback
in
various
forums,
but
I
think
the
better
API
is
for
alternative
to
requestanimationframe,
where
the
function
Kaaba
itself
will
tell
you
the
next
time
that
the
timing
on
which
the
frame
will
be
rendered
right
like
so
so
you
don't
objected
to
providing
this
information.
It's
just
that.
You
don't
like
me.
In
fact,
that's
exactly
what
happens
in
like
CCTV.
They
will
tell
you
exactly
when
the
next
frame
will
be
rendered
right.
H
So,
like
they'll
tell
us
the
time,
so
we
you
know
in
fact,
for
most
of
native
a
guys
like
structure
this
way
that
you
you,
you
know
you
ask
me
in
GP
or
whatever,
and
then
they'll
tell
you
like.
Okay,
this
is
the
frame
like
this
is
a
time
all
the
time
them
is
to
specify
the
frame
you
know
the
timing
of
which
next
time
should
be
rendered
to
the
system.
Those
are
usually
to
be
negative,
I'm,
not
sure.
F
Okay,
so
that
well
says
so,
is
that
basically,
the
equivalent
of
requestanimationframe,
basically
yeah,
listen,
and
so
that
would
be
after
the
rendering
system
has
already
received
a
signal
saying
we
would
like
you
to
produce
his
reign
of
contract
right
for
this
time.
Okay,
so
is
it
not
I
mean
presumably
the
system?
F
K
H
H
F
Would
be,
you
would
certainly
be
an
estimate,
but
it's
so
the
if
you
think
about
the
the
problems
that
developers
have
now.
They
may
have
a
pretty
good
idea
that
the
system
is
running
at
60
Hertz,
but
that
doesn't
tell
them
that
much
about
how
much
time
they
have
left,
they
might
have
Q
milliseconds
left
and
they
might
have
10
dollah
seconds
left.
They
just
don't
know
so.
They're
they're
flying
blind
now
this
would
be
sort
of
making
them
fly
a
little
less
blind.
H
Honey
act
like
use
kissies,
you
know
this
thing
that
I
mean
the
way
requestanimationframe
in
what
works
is
even
is,
as
currently
doesn't
want
to
fix
it,
but
the
fires
are
right.
After
the
bee
sting
cards
right,
I,
think
after
we
get
the
call
back,
we
call
them
back.
So
the
reason
we
did
that
is
that
way,
the
requestanimationframe
happens.
You
know,
but
a
fixed,
more
free.
You
know
uniform
minute
about
what
the
VC
happens
with
that,
like
you
should
be
able
to
prepare
the
frame
for
the
next
frame,
but
the
like.
F
H
H
If
there's
a
browser
work
that
to
update
the
layout
or
style
anything,
then
the
time
at
which
the
best
animation
frame
falls
is
no
happening.
Every
16
milliseconds,
it
could
be.
You
know
like
after
two
millions
or
like
in
interval,
could
be
like
a
team,
a
transitory,
mere
seconds
right,
depending
on
how
all
I
can
maybe
less
than
that,
depending
how
how
much
work
the
brows
did
or
didn't
do
so.
I
totally
agree
that
there
we
need
to
provide
this
information
like
that
use
case.
I
agree.
What
I'm
saying
is
the
API?
F
B
F
Okay,
so
a
couple
of
things,
one
is
so.
It
sounds
like
what
you're
suggesting
is
that
the
developer
the
web
developers
should
have
should
we
should
require
them
to
do
their
own
bookkeeping
like
we
shouldn't
provide
any
assistance
in
this.
They
should
be.
Ticket
am
checking
timestamps
and
looking
at
these
time,
signals
from
request,
animation,
I'm.
L
F
You
know
no
frame
of
reference,
so
I
it's
hard
to
understand
why
this
information
couldn't
be
it
I
would
other
times
of
why
it
shouldn't
be
denied
to
develop
other
times,
because
we
kind
of
wanted
this
information
this.
But
if
you
could
deliver
any
requestanimationframe.
H
Why
can't
you?
Because
that
would
mean
that
you
know
I'm
gonna
have
to
paint
in
our
main
thread
every
single
frame.
That's
the
latest
information
we
move
and
I
want
to
do
that
for
power
reasons,
I
don't
follow
you
maybe
eat.
Let's
say
the
only
time
to
see
you
know
the
the
system
will
tell
us
one
on
the
next
frame
is
when
we
have
like,
when
we
requested
to
paint
right
when
we
race
or
call
back
to
paint
okay.
B
K
I
had
one
quick
question,
which
is
this
is
until
the
beginning
of
the
rendering
steps
and
I
actually
liked
this
as
an
API,
but
there
is
also
an
amount
of
time
from
when
the
rendering
sub
start
to
when
we
would
like
to
snap
the
UI
thread
to
actually
be
able
to
render
in
time
for
the
ex
vsync,
and
that
time
is
currently
not
surfaced.
Through
this
time
have
we
considered
whether
that
can
be
surfaced?
And
yes,
Rios
ki,
understand
that
that
may
not
be
possible
certain
architectures
I'm
just
asking.
K
Actually
they
said
because
you
repeat
what
what
precise,
which
time
you're
talking
about
so
right
now.
This
time
is
the
time
until
the
rendering
steps
begin.
There
is
also
a
planned
vsync
time,
which
is
sometime
in
the
future.
After
the
rendering
steps
begin
and
I
guess
my
core
question:
is
there
also
be
a
budget
exposed
for
that,
so
that
the
render
is
ups
themselves
can
run
fast?.
F
Enough
or
be
right,
my
understanding
is
that
it's
not
actually
possible
to
observe
the
time
of
these.
Think
that
the
part
the
display
Hardware
samples,
the
buffers,
but
we
don't
actually
know
what
happens
that
we
we.
Basically
we
run
the
GPU
process
at
you
know
we
can
detect
what
the
refresh
rate
is,
but
we
don't
exactly
know
what
it
gets
samples.
So
we
simply
try
to
match
the
stride
of
the
hardware's
refresh
rate.
F
In
other
words,
I.
Don't
think
that
information
is
available,
we
can
so
there's
been
discussion
about
getting
more,
basically
giving
it
how
long
we
spend
in
the
rendering
pipeline
and
try
to
provide
a
timestamp
of
when
we
finished
all
of
the
hard
work
in
in
redmond
rasterizing,
so
that
we
have
a
an
estimate
of
how
long
it
took
to
for
rendering
to
run
and
like
when
we
actually
set
up
the
pixels
to
be
sampled
by
the
by
the
display.
B
K
F
A
A
F
F
There
are
good
arguments
on
both
sides
of
schedule,
request,
summation
frame,
one
way
or
the
other,
so
this
proposal
for
request,
post
animation
frame
is
basically
to
say
why
can't
we
have
both
so
requestanimationframe
expected
to
run
sort
of
synchronously
and
contiguously
immediately
before
the
rendering
pipeline,
without
any
opportunity
for
any
other
JavaScript
to
run
between
requestanimationframe
callbacks
and
in
the
rendering
pipeline?
And
what
we're
saying
is
we
would
like
to
also
have
a
slot
to
run
code
immediately
after
the
rendering
pipeline
is
finished,
without
the
opportunity
for
any
other
JavaScript
to
run
beforehand.
F
Use
cases
first
of
all,
the
one
that
your
ears
could
described,
which
is
have
the
maximum
possible
time
to
prepare
for
the
next
frame
and
then
there's
also
another
concern
that
we've
heard
from
developers,
which
is
they
they
really
want
to
avoid
forced
layouts.
They
really
want
to
avoid
call
in
doing
Reeboks.
I
may
have
information
of
a
long
time,
and
they
don't
know
how
they
don't
have
the
way
to
wait
to
guarantee
that
they
won't
do
that,
and
this
is
a
way
to
guarantee
that
you
won't
force
a
layout.
H
H
F
H
F
Economically
I'm
not
sure
that
that's
better
than
to
call
back
slots,
but
either
way
would
probably
be
okay.
My
one
reservation
is
a
requestanimationframe
has
high
usage
rate.
It's
not
clear
to
me.
Currently,
it
doesn't
accept
a
second
parameter.
It's
not
clear
to
me
whether
there'll
be
some
fallout
anticipated
fallout
from
changing
the
signature.
Yeah.
C
I'm
not
sure
if
you
can
hear
me
but
I
think
the
Vixens,
so
there's
also
a
bug
in
the
w3c
but
Zilla
from
2015
we're
all
you
find
a
very
similar
bug.
He
also
suggested
I
think
a
second
argument,
which
is
a
often
stationary
and
proposed
names,
were
in
sync
or
whats
rendering
but
I
can
get
to
that.
But
in
the
minutes
yeah
I
think
it
make
sense.
Oh
yeah,
so
a
brief
description
of
what
we
do
with
the
Firefox.
We
get
to
be
synched
as
soon
as
we
get
the
decent.
C
F
It
may
actually
be
the
case.
It's
have
to
check,
maybe
actually
be
the
case
that
we
are
doing
the
same
thing
and
in
the
sense
that
we
we
trigger
requestanimationframe
callbacks
immediately
when
we
get
the
vsync
signal.
The
difference
between
us
wicked
is
that
wicked
that
will
then
run
other
JavaScript
callbacks
after
requestanimationframe
and
before
running
the
rendering
pipeline.
You
know,
I
should
go
back
and
second-guess
a
lot
of
things.
F
C
A
H
B
H
Probably
I
think
I'll,
probably
the
option
dictionary
makes
Muslims
I.
Think
the
to
respond
to
your
audio
concern.
I
think
usually
illegal
I
experiment
to
function
doesn't
result
in
any
issues,
and
the
nice
thing
about
that
is.
You
can
also
check
feature
check
very
easily.
You
just
called
the
customization
frame
documents
and
it
will
tell
you
whether
function
and
supported
mean
global
you're,
not
adding
a
new
function.
H
It
is
okay,
but
I
think
if
we
added
that
you
know
just
42-mile,
namespace
and
I
think
the
onion
to
call
box
my
mixes
in
a
case
where
you
want
to
be
both,
but
then
I
think
there
are
cases
why
you
want
to
just
use
one
on
a
data
right
and
it's
just
a
bit
awkward
having
personal
one,
fine
or
whatever
to
data
callback.
So
I
think
mining
option
is
probably
the
cleanest
API.
For
my
mac
shading
standpoint.
B
F
It
doesn't
seem
to
be
controversial,
but
certainly
we've
we've
heard
this
again,
like
a
state
matter
of
people.
You
know
we've,
we
are
always
telling
developers,
don't
force
layout,
don't
force
layout
and
a
lot
of
them
complain
that
they
try
not
to,
and
they
can't
help
it
sometimes,
especially
when
you
have
third-party
libraries
that
are
doing
scheduling
their
own
work.
He
just
is
just
impossible
to
know
when
layouts
go
be
clean,
I
mean.
B
Mean
I
guess
we
can
find
on
that
main
thing
made
up
date.
I
wanted
to
get
there
is
that
these
are
the
three
specific
low-level
ideas
here
for
seeing
we
already
talked
about
is
input
pending
in
a
vast
role,
and
then
these
are
the
other
two
concrete
ones
that
are
in
the
pipeline
right
now.
The
second
thing
we
are
exploring
as
a
proof
of
concept
is
the
high
level
scheduling,
ABI
and
thought
who's
on.
The
call
isn't
actively
working
on
this,
and
maybe
in
a
few
weeks
or
in
the
next
design,
called
we
loved.
F
There's
also
thought
up
to
our
API,
where
developer
can
choose
a
maximum
refresh
rate
that
they
want
to
run
out
under
the
assumption
that,
for
example,
a
game
developer
might
decide
that
a
reliable
30
Hertz
is
a
better
experience
than
a
janky
60
Hertz.
So
we
should
talk
about
this
now,
but
I
just
want
to
see
the
country.
C
C
A
K
K
A
H
B
H
B
Implement
was
just
for
them
rather
effort,
if
you
don't
know
which
things
will
like
a
lot
of.
These
are
going
to
go
in
order
to
trial
and
then
change
drastically.
So
it
was
just
sort
of
the
you
know,
larger
effort,
and
if
it
includes
the
these
ideas,
but
also
includes
the
high
level
API,
but
it
will
also
have
its
own
intent.
H
Okay,
is
it
also
possible
to
this
to
move
this
till
I
know
some
ycz
group
or
exempt
some
like
The
Oprah
Show
WPC
place,
so
that
we
can
start
targeting
issues
and
stuff
like
questions
by
sure.
H
L
Mr.
time,
al3
was
I
think
presented
a
while
back,
that's
not
the
prettiest
effect
or
the
one
before
than
one
but
I
just
wanted
to
add.
Everyone
know
that
the
spec
changes
have
landed.
I
can
give
a
brief
recap
of
the
changes
for
both
mark
and
measure.
We
have
a
new
field
which
is
of
type
any
it's
basically
to
append
metadata.
It's
called
a
detail
in
addition
to
that,
we
can
now
mark
or
measure
using
arbitrary
timestamps,
so
we
can
now
set
the
start
time
to
any
done.
L
High
res
timestamp,
now,
based
on
feedback,
we
added
a
method
measure
with
options,
instead
of
just
putting
all
the
new
aki
capabilities
inside
the
old
measure
method,
because
they
would
become
way
too
complex,
because,
right
now
a
measure
already
receives
three
parameters:
the
measure
name,
the
start
mark
the
end
mark,
but
with
the
new
API,
we
want
to
allow
the
start
and
end
to
be
done.
Iris,
timestamps,
instead
of
strings,
so
if
it
can
be
one
or
the
other,
and
we
also
want
all
out
the
detail
or
we
can
have
a
duration.
L
L
All
three
is
that
now
these
met,
these
methods
are
no
longer
void,
so,
instead
of
being
void,
and
then
you
have
to
query
the
performance
marker
performance
measure
for
from
performance,
docket
entries,
you
can
now
just
use
the
return
value
of
the
method,
so
those
are
the
main
changes
out.
One
additional
change
is
that
we
allow
performance
mark
to
be
constructed.
This
is
to
be
able
to
support
a
use
case
from
I.
Think
some
service
worker
I
don't
know
if.
L
Yes,
when
Kelly's
service
worker
proposal-
and
so
basically
this
would
allow
you
to
create
the
object
without
it
being
added
to
the
timeline.
Thanks
for
that
use
case,
you
don't
really
add
once
to
add
it
to
the
timeline
if
they
want
to
use
a
mark
as
a
input
to
the
method,
they
they
just
want
a
mark
instructor
instead
of
performance
that
mark,
because
it
basically
with
that
unnecessary
memory.
L
H
L
Wait
I
mean
it's
not
a
necessity
is
it's.
We
got
feedback
that
it
would
be
clear
to
have
a
new
method,
because
if
we
do
not,
then
basically
the
method
would
become
measure
which
receives
measure
name.
Then
a
dumb
string
or
performance
measure
options,
which
is
the
name
of
the
dictionary
start,
start
mic
or
measure
options.
I
guess
that
would
would
have
to
rename
the
family
tree
and
then
so.
We.
H
L
We
actually
I
I,
asked
in
one
of
the
issues
and
I
think
was
Nick
or
Charles
who
were
actually
saying
that
they
thought
it
would
be
better
for
developers
if
it
was
this
way.
So
it's
not
like
we're
concerned
about
the
idea
of
complexities,
it's
more
about
what
is
more
economic
for
developers.
If
we
want
to.
N
Separate
Oh,
what
so
I
was
gonna
say
that
I
tend
to
agree
with
Rio
skate.
I
actually
saw
that
too,
a
few
days
after
it
had
been
discussed.
Those
will
delay
looking
at
it,
but
my
reaction
was
was
measured
with
options
seems
a
bit
awkward
and
presumably
future
it'll
be
the
more
common,
the
more
common
to
use
that
then
the
old
way
with
start
and
end
name,
and
so
it
feels
like
we
should
be
optimizing
for
that
being
the
standard
going
forward
and
make
it
a
simple
name.
N
I
I
agree:
I
guess.
My
point
is
I
think
if
even
if
it
is
a
complex
idea,
if
it
is
possible
to
disambiguate
the
cases
in
the
idea,
then
my
preference
would
be
that
just
keep
the
name
mark.
Orcs
are
key
to
name
measure
and
if
the
second
option
is
a
dictionary,
then
we
assume
it's
in
the
new
mode.
If
the
second
option
is
a
string,
we
fall
back
to
the
old
blood
Nicholas.
N
L
Then
honey
can't
we
shouldn't
just
ignore
the
feedback
from
the
other
people.
Would
you
like
been
out
of
the
car
right,
yeah
Charlie.
A
P
Q
A
Q
A
A
P
Yeah
but
my
comment:
if
I
can
just
have
a
second
here,
my
comment
was
probably
based
on
the
nightmares
that
we've
run
into
instrumenting,
add
eventlistener
and
how
that's
that
used
to
take.
You
know
different
number
of
parameters,
and
now
it's
been
normalized
and
you
know
there's
footnotes
and
mdn
articles
where
that's
what
I
want
to
avoid
is
like
Oh
long
ago.
It
could
have
been
used
this
way
and
we
do
instrument
edit
baluster
but
like
if,
for
example,
we
needed
an
instrument
marker
measure,
we
wouldn't
in
the
future
were
instrumenting
other
people's
code.
P
A
P
Saying
is
if
a
library
were
to
one
day
want
to
instrument
the
mark
method,
he
would
not
know
which
flavor
of
the
development,
which
version
the
developer
meant.
The
second
argue.
The
second
argument
was
an
object.
That's
like
incredibly
easy
right.
You
just
called
PI
Paul
will
tell
you
no,
but
if
you,
if
it
was
an
object,
you
it
gets
call
it.
You
get
to
strained.
H
A
G
Can
I
interject
so
philippe
suggested
also
publishing
first
draft:
should
we
publish
her
first
draft
of
level
three
and
full
of
questions
about
is
in
that
draft?
Should
we
maintain
the
curve
measure
with
options
or
should
be
reverted
back
to
measure
and
then
a
denotes
suggesting
measure
with
options
which
which
do
we
actually
want
to
publish
I.