►
From YouTube: CALEXT WG Interim Meeting, 2019-05-14
Description
CALEXT WG Interim Meeting, 2019-05-14
A
So,
as
I
was
saying
it
recently,
discussed
in
session
is
covered
and
about
well
domain
things
yeah
other
things
discussed
here
are
public
and
your
name
will
get
added
to
the
list
of
attendees.
Here
you
can
choose
not
to
be
covered
under
that
and
and
not
to
be
covered
under
the
IPR
rules
of
the
idea.
But
then
you
don't
get
speaking.
You
don't
get
to
influence
the
direction
of
any
standards
that
the
agent
works.
A
So
basically
the
rules
are
designed
in
such
a
way
that
if
you
propose
something,
then
you're
required
to
disclose
IPR
that
you're,
aware
of
that,
your
organization
ions
and
the
influences
the
standards,
the
submarine
things
in
ties
here.
So
it's
all
quite
reasonable.
There's
heaps
of
stuff
there
in
that
document,
if
you
interested
in
reading
it,
this
is
the
agenda
that
we've
put
together,
I've
added
a
venn
company
in
progress
documents
and
expected.
A
It
would
already
be
through
last
call,
but
some
issues
have
been
raised
so
there's
still
some
to
discuss
there
and
in
progress
documents
always
get
priority
in
patient
meetings
before
you
propose
work
because
we
want
to
progress
them.
We
then
have
the
drafts
that
we
have
proposed
to
work
on
soon,
scheduling
for
Jazz
calendar
could
potentially
be
put
into
future
work,
rather
than
propose
next
drafts,
we're
not
really
ready
for
yet
and
then
moving
through
there.
A
D
Calendar
Robert,
you
wanted
yeah,
so
J's
calendar.
We
we
had
last
call
which
ended
last
week.
We
didn't
receive
substantial
feedback
on
the
mailing
list
on
that
we
did,
however,
get
substantial
feedback
in
the
course
of
this
meeting.
So
by
understanding
there's,
there
is
still
room
for
this
specific
items,
namely
in
the
time
model.
D
This
is
the
one
input
that
we
got.
The
other
input
that
we
got
is
that
there
is
that
came
up
again.
The
discussion
on,
if
allowing
or
if
allowing
to
go,
meet
zero
time
stamps
on
all
the
events
would
allow
for
better
usability
or
and
probably
even
to
disambiguate
between
date
and
date/time
properties.
We
really
come
up
with
proposal
for
this,
so
in
summary,
we
will
have
to
update
or
we
will
update
the
draft,
so
we
will
have
to
take
at
least
one
more
round
before
we
can
finalize
last
court
yeah.
D
D
E
D
A
D
A
Means
it's
traded
as
a
floating
time
event,
with
a
length
of
one
day
or
have
many
days.
It's
it's
set
out
us,
but
yeah
B
is
type
date.
It
becomes
a
floating
event
automatically
and
you
can't
set
a
time
zone
which
causes
frustration.
We
discuss
some
things.
Cases
where
you
say:
I,
don't
want
an
appointment
to
be
made
on
my
birthday
and
you're
doing
things
across
multiple
time
zones.
Where
is
your
birthday
kind
of
considered?
You
know
I,
don't
want
to
take
a
call
on
my
birthday.
A
F
C
A
G
D
A
F
Think
that
would
be
better
to
propose
that
on
the
mailing
list
and
then
yeah,
because
I
I
don't
think
it's
also
necessary
to
keep
compatibility
with
in
between
GS
calendar
and
I
calendar
I
mean
I'm,
not
I
mean
if
one
is
getting
more
used,
we
should
not
I
mean
make
things
heavier
with
compatibility,
I
mean
not
necessarily,
sir.
It
was
just
a
question
like
that.
The
other
question
I
had
regarding
the
to
draft
is
just
them.
F
A
All
right
so
move
on,
yes,
cool
chuckling
controls
is
made
it's
a
very
simple
spec.
That
just
adds
a
couple
of
headers
to
the
house
of
commands
that
allow
you
to
say,
I
want
to
be
treated
as
this
user,
when
I'm
scheduling
and
I
want
shillings
to
not
happen
in
some
cases,
so
on
the
server
not
send
any
messages.
I
want
to
just
be
able
to
edit
my
copy
of
the
event.
The
interesting
part
is
the
I
want
to
be
considered
to
be
this
user.
A
There's
a
signal
user
address
set
which
I
have
not
yet
done
all
the
tests
on,
but
I've
suddenly
plan
through
what
clients
do
if
you
say
that
more
than
one
address
it's
a
set
and
I
should
be
able
to
be
a
list
of
potential
addresses,
but
I
mentioned
most
clients
just
use
one
of
them,
but
you
say
my
I'm
brunette
fast-melting
common
brunette
brunette,
and
you
know
secretary
and
organization,
and
if
I
receive
email
to
any
of
these
with
an
attached
event.
That
invites
me.
A
I
may
want
to
store
that
on
my
calendar,
so
I
need
some
way
to
know
who
I
am
when
dealing
with
them,
and
this
additional
header
allows
you
to
tell
the
server
I.
Am
this
person?
That's
I'm,
interacting
with
this
this
event,
so
that
it
can
do
the
great
changeling,
because
it
needs
to
say
whether
you
updating
it
caldera
in
general,
didn't
handle
aliases
and
that
concept
at
all?
Well,
and
so
this
is
an
attempt
to
to
allow
you
to
override
what
the
server
would
do
automatically.
A
A
C
C
C
C
C
A
G
G
F
G
G
My
story,
I
could
remember
exactly
why
I
proposing
the
idea
of
Vani
was
text.
So
that
seems
like
a
good
reason
for
dropping
I.
Think
the
reason
was
the
the
possible
needs
to
representation
of
a
because
in
the
property
value,
but
that
could
be
done
with
the
data
URI.
So
it
doesn't
really
need
to
be
redefined,
so
I
I
think
I
was
they
did
the
I
need
to
expend
mr.
participant
I
think
an
S
could
be
backwards
compatible
and
then
they
seem
a
lot
of
discussion
around
the.
G
It's
a
move
away
from
the
traditional
idea
that
it's
all
about
meetings,
it's
not
all
about
meetings
anymore,
it's
about
attending
public
events
and
eventually
moving
into
a
world
where
you
might
have
meetings
or
gatherings
without
any
any
explicit
organizer.
At
the
moment,
it's
all
centered
around
the
idea
of
an
organizer
with
attendees
a
lot
of
social
things
take
place
where
it's
just
participants
in
something
that's
happening
at
a
certain
time,
and
this
isn't
someone
moved
in
that
direction.
G
G
A
A
G
A
Certainly
the
idea
of
just
adding
another
part,
the
most
part
alternative
with
application
jazz
telling
the
Plus
JSON,
which
is
pretty
unwieldy,
but
there
you
go,
ask
the
DJs
calendar
version
of
the
event
for
client
seems
easy
enough
and
sensible
enough
to
do,
and
then
the
preference
order
is
the
later
one
is
more
preferred,
so
you
would
fall
back
to
using
the
text
calendar
part.
If
that's
all
of
your
system
supports
that
should
just
magically
work
everywhere.
Obviously,
they've
been
some
testing
play
with
that
as
part
of
my
testing.
A
That
would
also
fall
into
this,
creating
a
relationship
with
with
your
participants
per
event,
rather
than
trying
to
create
a
trust
relationship
between
entities
that
convention
to
with
each
other
would
allow
you
to
do
things
like
move
to
another
calendar
system
and
just
have
all
your
new
events
happen
there.
But.
A
Hopefully
the
fact
that
you
can
of
multiple
ways
in
which
to
reply
to
an
event,
even
Jay
s
calendar
as
a
way
I'm
offering
either
here's
the
email
address
to
send
your
only
response
to-
or
here
is
a
better
way
when
you
consider
that
Google
send
out
invitations
that
have
a
link
in
the
HTML
that
you
can
click
on
to
directly
say
yes,
I'm
attending
without
meeting
a
calendar,
client
there's
already
a
permanent
secret
in
there.
That
is
used
to
do
that.
A
Doesn't
require
you
to
have
the
count
on
this
system
because
as
a
per
event
secret
and
if
you,
if
we
were
to
take
that
concept
of
her
event
secrets
and
bring
it
into
a
more
general
scheduling,
I
think
that
would
be
good,
any
other
suggestions
he
or
any
feedback.
We
should
take
to
designing
this
thing.
A
C
Yeah
I
think
there
what-whatever
had
taken
from
the
initial
apple
drafts
looks
good
it.
It's
probably
95
percent
of
what
people
have
implemented
right
now,
anyways
the
only
thing
only
spot
I
think
we
need
to
beef
it
up.
A
little
bit
is
how
you
handle
scheduling
with
shared
calendars,
which
I
think
we'd
better
session
on
that
tomorrow.
Correct.
A
C
C
Anybody
and
I
think
they
also
would
leave
an
alarm
in
there
with
a
date
that
was
far
in
the
past,
so
that
it
would
that
the
server
would
see
the
alarm
not
add
one,
but
I
would
never
trigger,
because
we've
already
surpassed
that
time.
That
was
that's
the
only
thing
that
I
think
was
kind
of
kind
of
funky
and
I
draft
everything
else.
I
think
we've
determined
is
pretty
straightforward
in
terms
of
alarm
acknowledgement
and
that
kind
of
stuff.
A
This
was
the
idea
that
you
could
manage
a
server
and
tell
it
that
it
was
actually
copying
from
another
server,
so
set
some
properties
on
that
the
username
and
password
or
token
it
allows
it's
been
synchronized
to
a
different
LDAP
server
to
actually
and
there's
just
proxy
in
the
data
through
yeah
I.
Don't
have
anything
ready,
I,
don't
think
anyone.
F
C
C
C
A
C
Vol
arm
extensions
is
pretty
simple:
the
calendar
sharing
is
basically
three
layered
documents.
One
has
generic
WebDAV
notifications,
one
is
generic
web
dev
sharing
and
then
the
calendar
sharing
piece
is
fairly
small.
On
top
of
it,
as
I
said
before,
I
think
the
only
place
we
need
to
beef
up.
The
text
is
how
to
handle
this
on
public
calendars.
So
I'm
going
to
work
on
on
these
I
just
need
to
know
if
I
need
to
resend
them
as
working
group
drafts
before
he
starts
out
of
it.
Well,.
A
A
A
C
C
C
A
E
Yes,
so
the
current
status
is
that
there
is
a
draft
which
is
expired,
which
expired
couple
years
ago
already
and
on
recent.
Well,
not
so
recent
call
and
we
decided
to
split
it
into
two
documents:
first,
one
to
specify
the
generic
model
and
pushed
protocol
and
the
other
one
to
specify
the
specific
depth
implementation
of
the
model
and
yeah
that
still
needs
to
be
done.
E
F
F
And
is
that
inish
people,
or
is
it
one
or
two
or
probably
five
ish
I,
would
say?
Okay,
so
maybe
before
going
to
dispatch,
it
might
be
good
that
we
we
had
a
chat
with
the
VAD
Barry
yeah,
so
I
mean
because
II
yeah,
it
might
be
I
mean
I,
don't
know
what
he's
gonna
say,
but
I'm
I
would
like
to
avoid
that.
A
A
F
Yeah
I
think
I
have
no
concern
about.
If
we're
changing
something
in
HTTP
or
adding
some
of
the
stuff,
they
would
be.
I
expect
Martin
Nottingham
to
be
pretty
reactive
yeah
and
it
might
be
the
only
tricky
part
we
have
to
to
address
not
to
fall
down
into
the
the
case
we
were.
We
have
a
needed
agreement
with
the
HTTP
community
and
then
we
don't
know
how
to
move
that
things
forward.
So
no
real
trouble
I
mean
no
concern
about
how
mean
I
think
they're
willing
to
provide
some
feedbacks.