►
From YouTube: IETF110-JSONPATH-20210310-1200
Description
JSONPATH meeting session at IETF110
2021/03/10 1200
https://datatracker.ietf.org/meeting/110/proceedings/
A
A
A
A
A
A
A
If
you
send
it
out
afterwards,
I'm
sure
we
can.
We
can
help
out
with
anything
that
you
miss.
Thank
you.
As
for
a
javascribe
I'll,
given
that
we're
we're
quite
a
small
group,
I'm
more
than
happy
to
do
that.
Is
there
any
agenda
bashing?
Is
there
anything
that
anybody
has
a
particular
subject,
they'd
like
to
bring
up
before
we
get
started.
A
Nope,
okay,
the
agenda's
fairly
minimal
today,
usually
I
would
expect
him
to
be
driving
this
he's,
unfortunately
not
here,
but
I
guess
maybe
is
a
good
starting
point.
If,
if
our
editors
and
those
who've
been
working
hard
on,
the
draft
could
perhaps
provide
some
sort
of
informal
update
about
where
things
are
when
you
you
recently
have
had
submitted
the
renaming
of
the
draft.
B
Okay
not
used
to
the
protocol.
I
can
just
summarize
where
we're
at
I
mean
a
while
back.
We
we
formed
the
working
group
and
got
a
emerged
draft
together
of
the
draft
that
I'd
been
editing
and
the
one
that
stefan
gerstner
and
carson
have
been
working
on,
and
so
we
got
that
merged
draft
and
there's
been
a
little
bit
of
editorial
work
on
it
and
that's
now.
B
The
current
base
zero
zero
version
in
the
documents
area
on
data
tracker,
but
more
recently,
there's
been
a
flurry
of
activity
on
the
mailing
list
and
in
issues
discussing
various
aspects
gradually
coming
to
conclusions
in
various
places,
but
a
lot
of
discussion
going
off
in
various
tangents.
So
I'm
not
sure
whether
we're
converging
or
diverging
at
the
moment,
but
there's
certainly
a
lot
of
discussion
going
on,
but
no
sign
of
any
pull
requests.
So
there's
no
writing
going
on.
B
A
D
D
A
Okay,
that,
that's
that's
very
that's
a
very
good
update.
Thank
you
for
that
carsten
in
terms
of
the
processing
model,
as
you
described
it
is
that,
to
me,
sort
of
sounds
like
an
effort
for
perhaps
is
that
something
that
we
could
discuss
in
in
this
time
slot
now
and
make
some
sort
of
meaningful
discussion
about,
or
is
that
something
you
think
we
should
take
to
the
mailing
list.
D
A
D
D
But
basically,
the
idea
is
that
you
have
ways
to
to
step
from
the
nodes
that
that
you
are
currently
sitting
on
and
that
you
have
ways
to
to
select
subsets
and
and
compute
values,
and
at
the
time
we
had
an
expression
language
that
was
based
on
this.
That
is
what
that
was
doing,
all
these
things,
that
that
got
turned
into
a
special
thing
for
xpath
and
and
xslt.
D
But
I
think
basically
the
idea
is
the
same,
but
the
the
important
part
to
make
this
whole
thing
work
is
that
you
need
to
know
where
you
are
and
and
what
actually,
the
the
how
the
sequence
of
steps
actually
are
connected
together.
So
what
are
the
intermediate
results
and
for
xpath?
That's
a
pretty
obvious
structure.
D
D
Okay
yeah,
so
just
judging
from
the
title,
I
think
27
is
one
of
them.
23
is
one
of
them.
21
is
one
of
them.
I
think
even
15
is
14
and
15
are
one,
so
these
are
just
different
ways
of
of
approaching
the
elephant
and
and
finding
trunks
and
legs
and
so
on
off
of
the
overall
question.
What's
the
processing
model.
A
D
A
A
A
Given
the
amount
of
participation
that
we
have
is
fairly
minimal,
the
and
thank
you
for
the
link
in
the
chat
christina,
given
the
amount
of
we've
got
fairly
a
small
community
here
in
this
working
group,
I
would
say
just
go
ahead
and
do
stuff,
obviously
in
a
considerate
manner.
So
if
people
need
access,
I
need
to
twiddle
things
to
help
you
get
this
work
done.
I
will
do
it.
That's
that's
that's
my
role.
D
A
A
D
B
Okay,
yeah
I'll
buy
it,
so
it
depends
on
the
type
of
reference
that
the
node
set
makes
into
the
into
the
json
document.
That's
input!
How
did
you
see
that
going?
Would
you
would
that
be
a?
Would
it
point
to
a
node?
Would
it
be
a
reference
to
a
node
in
some
sense
in
in
the
original
document
or
a
copy
or
what
or
a
value?
No,
it's
a
reference
reference.
Okay,.
B
B
You
know
the
components
of
the
selector
and
and
didn't
remove
duplicates,
and
I
just
had
in
mind
efficiency
really
and
sensitivity
to
the
current
implementations.
I
don't
think
there
are
many
if
any
implementations
that
remove
duplicates
so
that
that
was
my
goal,
but
certainly
having
a
maybe
not
a
node
set,
but
a
node
list.
You
know
an
ordered
collection
of
nodes
would
satisfy
that.
A
D
The
next
step
would
be
to
actually
go
through
these
issues
with
the
assumption
we
are
using
a
node
list
and
see
whether
the
examples
that
have
been
brought
up
in
these
issues
actually
bring
up
problems
with
that
or
advantages
of
of
doing
that.
That
may
be
a
bit
tedious
to
do
in
the
meeting.
So
I'm
wondering
how
to
do
this.
So
if
I
was
doing
this
in
a
classroom,
I
would
just
divide
the
students
into
small
groups.
D
A
Yep,
that
would
be
the
only
challenge
that
we
have
is
that
our
editors
aren't
about
so
which
I
met.
I
kind
of
ran
on
the
assumption
that
they
would
be
in
the
best
position
to
do
this,
but
this
is
certainly
something
that
that
I
can.
I
can
do,
and
I
guess
if
we
can
get
some
help
from
other
members
of
the
working
group
who
have
prepared
to
look
at
a
couple
of
issues.
D
Yeah,
I'm
afraid
mideco
doesn't
have
breakout
rooms
which
I
would
use
for
that,
so
it's
hard
to
to
duplicate.
We
have
done
this
in
this
new
thing
to
think
research
group,
occasionally
that
we
just
we
all,
went
into
one
of
the
four
corners
of
the
room
and
and
try
to
get
some
some
work
to
get
done
and
then
came
back
together
and
reported
on
on
what
the
four
corners
found.
But
you
cannot
do
this
in
mid
echo.
A
A
A
A
C
A
E
C
B
Can
I
just
interrupt,
I
mean
I
think
signing
and
one
of
these
issues
to
someone
at
this
point
is
probably
not
the
best
ploy,
because
we're
just
talking
about
doing
some
analysis
coming
back
and
discussing
it,
whereas
we
don't.
I
personally
don't
want
to
be
quite
lumbered
with
one
of
these
issues
after
the
meeting.
A
E
F
E
E
E
E
E
A
B
C
C
C
C
A
C
Sure
so
I
looked
at
15,
which
is
selector
definitions.
Basically,
an
attempt
to
start
a
processing
model
and
karsten
has
chimed
in
there
with
the
collections
idea
and
the
the
impact
of
of
defining
this
as
a
list
seems
to
be
that
that
nobody
is
doing
that
by
default.
All
of
the
discussion
is
talking
about
which
set
of
objects.
C
Particular
things
are
returning
and
not
what
order
they
are
and
in
javascript
objects,
kind,
only
kind
of
have
an
order.
I
looked
up
the
json
rfc
and
it
says
sometimes
they
they
make
the
ordering
of
object.
Members
visible,
so
we're
going
to
have
if,
if
we
keep
an
order
here,
we're
going
to
have
to
say
that
it's
we're
going
to
have
to
say
what
order
things
things
show
up
in
which
could
be
could
be
ambiguous
for
objects.
C
C
D
Yeah,
so
the
the
whatever
8259
says,
the
practical
matter
is
that
that
jsonpath
evaluator
will
sometimes
have
to
work
on
json
data
and
not
on
a
json
text,
and
the
json
data
may
not
be
presented
in
a
way
that
that
provides
any
ordering
to
the
map
entry.
So,
for
instance,
javascript
tends
to
to
put
numeric
map
keys
first
and
and
then
the
the
other
map
keys
and
so
on.
So
there
is
some
reordering
going
on
in
implementations
in
python.
D
That
reordering
is
actually
different
between
each
invocation,
which
can
be
a
lot
of
fun
with
it
when
you're
trying
to
debug
things
so
yeah
json
objects
do
not
have
order
and
any
selector
that
actually
relies
on
an
order
in
a
map
is
early.
Fine,
of
course,
arrays
do
have
order,
and
I
think
that
that
generally,
if
you
filter
an
array,
the
result
of
that
data
should
have
the
same
order
that
the
original
array
had.
B
Yeah
I
was
going
to
make
a
comment
about
the
ordering
of
objects.
I
think,
if
I
remember
correctly,
the
only
selector
component
selected
that
actually
would
that
would
impact
is
something
like
an
asterisk.
You
know
square
brackets
asterisk
to
pick
out
all
the
values
of
an
object,
and
in
that
case
yes,
the
output
would
be
the
order
will
be
non-deterministic,
but
I
think,
aside
from
that,
I
think
ordering
would
work.
B
But
suppose
someone
had
introduced
square
bracket
star
twice
over
somehow,
not
sure
exactly
how
that
would
work,
then
I
think
the
removal
of
the
duplicates
there
afterwards
still
work
we'd
end
up
with
the
original
non-deterministic
order.
Potentially,
so
I
think
think
it
could
be
made
to
work
together.
Don't
think
we
need
to
throw
out
ordering
just
because
of
the
behavior
of.
D
A
B
Let
me
just
express
an
opinion
while
we're
here.
I
don't
think
it
should
be
deterministic
in
this
case,
because
I
think
that
would
be
too
constraining
on
the
implementations
and
I
don't
think
it
actually
matters,
because
I
think
applying
star
to
a
an
object
is,
is
probably
a
pretty
rare
use
case.
I
don't
think
it
really
matters,
and
if
you
exclude
that
case,
then
it
becomes
deterministic
everywhere
else.
B
B
D
Yeah,
I'm
in
the
middle
of
typing
that
issue,
but
anyway,
so
the
the
processing
model
discussion,
our
algorithm
discussion
under
number
14
was
actually
pretty
far
along
when
it
kind
of
derailed
into
it's.
It's
funny
to
to
see
people
fixing
the
mark
down
there
when
it
derailed
into
a
discussion
about
what
we
can
do
about
recursive
or
nested
filters,
and
so
on.
I
think
that
that's
a
completely
different
issue,
so
it
doesn't
really
have
a
bearing
on
on
this.
D
D
D
We
just
return
the
current
note
list.
That
makes
a
lot
of
sense
to
me,
except
again
that
I
don't
know
what
append
and
distinct
are
meaning
exactly
so
there
are
several
options
not
taken
here.
So,
for
instance,
the
the
selector
does
not
get
the
whole
node
list.
The
selector
gets
each
entry
of
the
node
list
each
element
of
the
node
list
in
turn,
so
you
cannot
write
selectors.
That
order,
note
lists
or
do
something
interesting
like
build
an
average.
You
only
ever
get
selectors
that
work
on
on
a
single.
D
Note
and
yeah,
I
said
it's
not
clear
what
this
thing
means
and
I
think
we
just
already
discussed
about
selectors
that
that
take
objects
exclusively
take
items
out
of
an
unordered
map
or
json
object.
I
think
we
covered
that
already,
so
I
I
would
love
to
hear
what
people
think
about
this
append
and
distinct
operations.
B
For
me,
the
obvious
meaning
for
append
is
really
concatenate.
I
would
think
the
selector
brackets
item
would
return
a
node
list
and
append
would
concatenate
the
two,
but
I
admit
it's,
it's
ambiguous,
isn't
it
it
could
be.
You
know
something
else
distinct,
I
would
hope,
runs
through
the
node
list
in
linear
order
and
when
it
encounters
a
duplicate,
removes
the
later
occurrence
of
the
duplicate
and
then
keeps
going.
So
essentially,
if
you
get
the
same
node
multiple
times
over,
only
the
first
occurrence
survives.
F
D
So,
unless
there
is
more
discussion
that
calls
in
the
question
whether
these
decisions
are
right,
we
can
make
a
pull
request
out
of
that,
and
the
pull
request
should
should
be
specific
and
detailed
and
unambiguous
enough
that
we
really
can
discuss
it,
in
particular,
against
the
the
various
implementation
survey
pieces.
We
have
that
we
can
run
against
this.
A
Okay,
that
sounds
like
we've
made
some
good
progress
there.
That
pull
request
can
okay
sounds
like
we
can
put
a
summary
on
to
some
of
these
issues,
then
I'll
do
that
afterwards
after
I
speak
to
tim
and
make
sure
that
he's
he's
abreast
as
to
what
we're
doing
it
sounds
like
we've
made
a
fair
work
of
progress
today.
A
B
So
number
27
actually
was
a
one.
It's
just
a
single
comment
issue
and
it
referred
mainly
back
to
number
23
duplicates
in
selector
output,
and
there
was
a
bit
of
discussion
back
and
forth.
Wasn't
really
a
consensus
there,
but
the
the
last
proposal
seemed
to
be.
It
wasn't
immediately
counted,
so
it
was
tending
towards
removing
duplicate
nodes,
but
not
duplicate
values,
which
is
consistent.
I
think,
with
the
node
list
idea
we've
been
discussing
today.
B
A
B
There
isn't,
as
far
as
I
know,
so
that's
that's
fine,
so
yeah.
There
was
interesting
discussion
in
number
23
about
whether
removal
of
duplicates
would
affect
ordering
and
consequently
make
the
spec
non-deterministic,
but
I
don't
think
it
would.
I
think
if
we
defined
it
carefully
and
said
that
later
nodes
were
discarded
in
preference
to
earlier
nodes.
Sorry
in
favor
of
earlier
knows,
then
you'd
get
deterministic
ordering.
B
B
A
A
A
A
D
E
G
A
A
B
I
mean
it
seemed
to
me
that
the
next
step
here
was
for
someone
to
simply
make
a
choice
in
each
line
of
the
table
and
then
put
in
a
pull
request,
and
I
was
kind
of
holding
my
breath
opening
up
hoping
that
stefan
would
do
that,
but
he
hasn't
decided
to
so
far.
So
it
just
seemed
like
a
coin.
Tossing
exercise
really
to
pick
on
some
terms.
D
D
A
A
D
B
A
A
D
A
G
B
Just
in
passing,
I
mentioned
a
mathematical
alternative
for
the
name,
value
pair
or
key
value
pair
in
an
object
will
be
maplet
would
be
what
we
want.
Maplet
m-a-p-l-e-t,
oh
you
know.
If
we
wanted
to
something
that
was
completely
neutral
from
a
computing
point
of
view
and
a
you
know,
unique
term,
it's
got
a
well.
You
know
mathematical
history
behind
that
term.
If
we
wanted
to
use
it.
A
D
A
D
A
D
D
E
A
B
G
D
F
B
B
E
D
G
D
A
A
B
D
Yeah,
I
think
we
should
have
a
little
bit
of
introductory
text
that
that
explains,
I
mean
we
should
not
overdo
this,
but
we
should
really
explain
at
the
beginning
what
the
the
consideration
considerations
were
that
went
into
this
process,
and
so
I
think
this
this
is
good
material,
but
it's
mostly
just
editorial
writing
this
up.
I
don't
think
there
is
a
big
disagreement
on
the
principle
that,
of
course,
there
always
will
be
disagreements
on
what
the
principle
actually
means
in
a
specific
case,
so
so,
for
instance,
in
the
filter.
D
D
A
A
This
is
something
that
I
can
do
with
tim
in
terms
of
creating
the
new
issues
and
if
people
in
the
working
group
want
to
check
my
homework
to
make
sure
that
I
haven't
misrepresented
the
issues
or
or
said
anything
untoward.
That
would
be
very
much
appreciative
and
then
once
we've
got
those
issues
we
can
refer
back
to
54
and
then
close
them.
D
A
A
D
B
A
A
G
Sometimes,
between
this
itf
and
the
next
one,
and
it
would
be
good-
I
was
looking
at
some
of
the
people
who
are
active
in
the
in
the
github
issues
and
some
of
them
seem
to
be
in
a
different
time
zone.
So
it
might
be
good
to
have
like
a
doodle
poll
and
make
sure
that
editors-
and
at
least
these
people
can
be
present.
A
Yep
that
works
for
me.
I
would
thank
you
for
bringing
that
up.
I
was
going
to
do
it
eventually
would
just
just
a
straw
poll
of
people
would
would
something
say
the
approximately
the
first
week
or
two
of
may
be
appropriate,
given
that
the
next
atf
meeting
is
not
until
mid
july.
If
I
remember
correctly,.
A
I'll
be
honest
and
say
it
probably
favor
the
times
and
dates
for
a
lot
of
the
editors
that
are
editors
as
well
as
my
co-chair,
but
I'll
put
it
I'll
I'll,
create
it
as
an
action
to
take
it
to
the
mailing
list
and
come
up
with
some
times
and
dates,
and
we
can.
We
can
set
set
up
something
in
in
may
or
even
april.
D
But
I
think
it
would
be
good
to
to
read
this
issue
and
maybe
further
issues
we
we
get
from
from
other
people
who
who
want
to
use
this
work
and
think
about
what
what
our
response
should
be.
So
if
they
have
un
unfulfillable
expectations,
we
probably
should
say
that
or
if
there
are
activities
that
needs
need
to
be
split
off
and
and
are
not
currently
in
in
the
purview
of
this
group,
we
shall
try
to
to
detect
that.
A
A
D
A
B
A
B
D
D
So
it's
just
a
question
where
we
need
to
collect
information
and
then
make
a
decision.
These
should
always
be
converted
into
issues.
So
people
can
start
writing
pull
requests
because
pull
requests
really
should
be
closing
issues,
so
I
mean
we
may
occasionally
have
pull
requests
that
don't
have
an
issue,
but
the
normal
situation
would
be.
B
A
Through
okay
I'll
I'll,
take
that
silence
as
we're
good
to
go.
I'd
like
to
thank
all
of
you
for
your
time
today,
including
newcast
and
glenn,
and
jeffrey
for
helping
me
out
here
being
without
a
co-chair
I'll,
be
putting
out
a
poll
to
the
mailing
list
later
today
or
in
the
next
coming
days.
I'll.
I
better
make
a
promise.
I
can
actually
keep
and
we'll
see
you
on
the
mailing
list
and,
if
not
we'll
see
you
at
the
next
atf
in
july,.