►
From YouTube: OpenActive W3C Community Group Meeting / 2018-08-30
Description
A public hangout for members of the OpenActive W3C Community Group.
Agenda and summary: https://lists.w3.org/Archives/Public/public-openactive/2018Aug/0006.html
For more information visit: https://www.openactive.io/w3c-community/
A
B
B
So
in
terms
of
progress,
we've
got
a
number
of
activities
going
on
in
parallel
at
the
moment,
revisions
to
both
the
data
model,
spec,
the
booking,
the
draft
booking
spec
and
some
of
our
developer
tools
and
documentation.
So
where
are
we
with
all
that?
We
had
a
good
discussion
around
the
booking.
Spec
was
the
last
call
which
flags
a
few
issues
with
the
current
draft,
just
largely
with
how
the
json-ld
responses
were
structured.
B
B
Alongside
of
doing
the
changes
to
the
draft
spec
Chris
who's,
leading
that
piece
of
work
has
also
been
working
on
a
reference
implementation
and
he's
found
that
useful
to
highlight
a
few
error
conditions
that
also
needed
to
be
flagged
a
bit
more
clearly
in
the
spec
as
well.
So
that's
moving
on
with
perhaps
a
few
days
behind
and
where
it
had
to
be,
but
broadly
on
track.
It
had
positive
feedback
from
everyone.
B
So
far,
we've
also
been,
as
I
mentioned,
and
last
few
calls
working
on
a
data
validator,
which
is
you
can
see
a
version
of
that
validator
active.
Do
the
work
on
that
is
largely
done.
We
have
a
validator
that
covers
the
data
model,
at
least
a
draft
2.0
date,
and
also
a
validator
that
provides
feedback
on
implementation
of
the
PDE
feed
spec.
So
those
are
largely
done
pending
at
any
other
feedback
on
user
interface
from
the
community.
B
All
final
changes
to
the
2.0
specification,
so
some
of
the
things
I'm
going
to
talk
about
in
a
minute
the
the
new
types
of
event
aren't
yet
in
the
validator
but
I'm
hoping
those
will
garyun
fairly
shortly.
But
that's
that
validation
tools
already
proven
useful
in
order
to
help
explore
the
2.0
changes,
but
also
you
support
some
of
the
new
publishers
that
have
been
coming
on
stream.
B
We've
also
got
a
new
developer
site,
which
will
have
a
bit
more
bit
more
documentation
for
developers
who
are
not
just
publishing
data,
but
also
using
data
I've
we've
written
few
tutorials,
which
will
be
going
out
over
the
next
few
weeks
as
well
so
there'll,
be
a
whole
kind
of
drop
of
documentation
tools
and
updated.
Specs
I
mean.
B
Probably
the
bulk
of
the
work
has
been
the
changes
to
the
data
model.
The
the
main
focus
for
the
2.0
spec
was
was
intended
to
be
the
changes
to
improve
the
quality
of
published
data,
so
tightening
up
some
of
the
areas
inspect
that
talk
about
what
what
constitutes
valid
data
limit.
Some
of
the
options
around
how
data
is
published
in
order
to
add
more
consistency.
B
There
were
a
few
other
things
that
I'd
hope
to
try
and
get
into
the
2.0
spec,
including
the
that
roots
proposal
that
we
had
a
discussion
on
couple
of
calls
ago.
But
given
that
there
was
quite
a
bit
of
feedback
on
the
roots,
work
I'm
going
decided
to
push
that
out
from
the
t-point
overly.
So
it
will
be
probably
in
the
2.1
proposal,
depending
on
any
iteration.
It's
not
that
it's
particularly
complex
a
feedback
is
just
on
top
of
all
the
other
changes
that
are
going
to
be
in
the
2.0
release.
B
If
they're
like
a
bit
too
much
to
try
and
rush
that
through
as
well,
so
we're
gonna
be
leaving
discussion
and
feedback
open
on
that
for
a
few
more
weeks.
Yet
there
is
a
working
draft
of
the
2.0
spec
available,
there's
a
bit
if
you
want
to
jump
into
it
now,
but
I'll
be
circulating
a
link
to
that
to
the
list
later
today.
So
that's
just
a
separate
editors
draft
2.0,
which
has
the
majority
of
the
changes
in
it.
B
Those
schedules
can
be
processed
to
create
individual
kind
of
calendar
entries
effectively
for
each
of
the
events
that's
described
in
that
series,
but
the
bulk
of
the
changes
around
the
validation
rules
that
are
all
in
there
and
the
initial
content
from
what
I'm,
just
about
to
run
through
around
types
of
event,
is
also
there
as
well
once
I
get
that
updated
draft
done
published
this
afternoon.
I
want
to
give
everyone
two
weeks
for
feedback
on
that
draft,
so
that
we
can
formally
publish
to
point
o
on
on
all
around
the
13th
of
September.
B
So
we've
got
a
call
on
the
12th
of
September,
which
I'd
want
to
use
to
just
quickly
step
through
any
any
feedback.
We'd
get
any
proposed
changes
and
get
those
into
the
specification.
So
that's
two
weeks
for
today
to
support
publishers
in
upgrading,
because
there
are
a
number
of
changes,
we're
going
to
provide
some
upgrade
advice,
we're
going
to
use
the
validation
tool
to
do
that,
so
we'll
be
able
to
generate
validation
reports
and
make
people
to
do
those
so
that
they
can
see
where
their
feed
might
be
invalid.
B
B
I'm
going
to
take
that
person
no,
but
we
jump
in
at
any
point.
Okay,
so
one
of
the
main
proposals,
those
changes
in
2.0
outside
of
the
validation
rules
was
add
thing
to
add
some
new
types
of
event.
So
in
1.0,
1.1
we've
been
only
using
the
schema.org
event.
B
B
So
there
are
broadly
three
three
types
of
event
that
we've
kind
of
noticed
appearing
as
patterns
in
data
there's
the
kind
of
archetypal
kind
of
weekly
gym
class.
Where
you
have
you
know,
in
a
class
that
a
weekly
gym
class
we
do
class,
for
example,
that
will
run
every
Wednesday
and
then
there
will
be
specific
instances
of
that
class
specific
sessions
that
will
be
taking
place
so
today,
as
X
p.m.
next
freaking,
6:00
p.m.
etc.
B
So
where
you
want,
you
might
have
a
10-week
sailing
course,
and
then
there
will
be
ten
individual
events
that
people
will
be
expected
to
turn.
So
those
are
the
use
cases
so
broadly.
The
first
one
is
about
a
schedule
and
the
individual
sessions
that
are
part
of
that
schedule.
The
second
case
we've
got
the
headline
event
is
about
having
an
event
which
is
made
up
of
kind
of
what
we
could
think
of
as
component
parts,
so
individual
events
in
the
program
and
then
courses
and
the
individual
classes,
so
it
in
each
of
these
cases.
B
It
would
be
useful
to
be
able
to
distinguish
between
these
different
types
of
an
event
in
the
published
data
rather
than
using
the
generic
type,
because
that
means
that
a
th
consumer
might
choose
to
display
that
information
differently.
So,
if
you're
publishing
information
about,
say
a
mass
participation
of
an
all-day
event,
you
might
want
to
have
a
page
that
has
information
about
that
whole
event
and
then
detail
on
its
its
program
to
give
people
a
flavor
of
what's
happening
over
the
course
of
the
day,
whereas
with
a
gym
class.
B
B
There's
also
what
we've
noticed
is
taking
in
the
case
of
where
people
publishing
data
about
gym
classes
that
it's
often
useful
to
be
able
to
publish
an
event
with
a
schedule
which
has
all
of
the
key
information
about
the
event
so
who,
where
it
is,
what
who's
organizing
it,
how
much
it
costs
to
take
part
and
that
information
is
consistent
across
all
of
the
individual
instances.
You
know
the
only
thing
that
really
changes
in
the
instances
is
what
day
or
time
it's
running
on
everything
else
is
the
same.
B
B
So
how
does
a
child
event,
so
this
afternoon's
class
inherit
that
information
from
the
kind
of
broader
scheduled
event,
so
we
needed
to
make
sure
that
we've
got
some
clarity
around
how
that
might
work
in
the
specification
so
that
consumers
can
consistently
process
this
information
so
yeah
on
slide
in
the
same
example,
so
a
gym-class
is
going
to
share
almost
all
the
same
information
across
all
of
those
Thursday
6
p.m.
sessions,
but
a
race
in
a
multi-day
event
might
not
it
might
be
at
a
different
location.
B
A
Quick
question
and
it's
the
same
way
that
it
would
work
where
you,
for
example,
allow
center
with
multiple
sites.
So
no
sorry
letter
operated
with
multiple
sites
with
then
it
might
have
the
same
types
of
classes
running
across
multiple
sites
just
for
different
times
and
days,
or
is
this
sort
of
a
slightly
different
use
case?.
B
That's
a
good
question,
so
I
think
in
that
case,
I
would
think
of
those
as
a
different
sets
of
events.
But
there
is,
there
is
a
there
might
well
be.
There
might
be
grouped
in
some
way.
One
way:
we've
kind
of
defines
it
to
kind
of
group.
These
things
that
are
in
the
existing
spec
is
through
the
program
property.
So
if
they're
for
like
the
same
brand,
so
if
it's
a.
C
If
it's
more
important
to
you,
it's
Zumba,
rather
than
the
detail,
underneath
it
of
what
site
and
what
date
and
all
that
kind
of
stuff,
so
yeah.
We
we
talk
about
that
a
bit
later.
Actually,
it
really
is
all
about
the
other
stuff
first
and
then
we
come
and
suddenly
realize
that
actually,
at
slightly
higher
level,
there's
a
bit
of
a
like.
You
say:
sometimes
you
just
care
about
the
the
headline
headline
meals.
You
just
care
about
the
kind
of
what
is
it
rather
than
the
detail.
B
D
Sorry,
a
good
question
as
well
quickly
and
easily
be
a
limit
on
great
on
the
amount
of
events
or
sub
events
within
a
group
as
well,
because
I'm
just
thinking
in
terms
of
savory
we're
offering
walking
or
running
or
cycling
toe
paths
that
sort
of
thing.
Potentially,
we
cannot
for
that
day
of
the
year
now
we
can
break
it
down
by
geographically
so
into
regions,
and
things
like
that
which
would
work,
but
it's
still
going
to
be
a
hell
of
a
lot
of
potentially
in
data
that
goes
in
there.
C
D
So
so,
for
example,
you
can
go
running
any
day
on
the
towpath
or
cycling
or
walking.
If
you
wanted
to
so
they're
all
potential
event,
events
I've
got
some
quit
balls
around.
You
know
the
definition.
Maybe
if
they've
been
potentially,
they
could
all
be
listed
there
every
day.
So
we
can
also
generate
those
into
the
feed.
Oh
I.
C
See
so
one
of
the
I
guess,
one
of
the
principles
of
the
feeds
is
that
the
type
of
auto
generation
we're
talking
about
there.
Basically,
we
tend
to
dissuade
that
being
a
thing
mainly
because
if
we're
also
generating
information,
it's
usually
coming
from
a
kind
of
more
concise
source.
So
in
that
case
it
would
be.
You
know
you
can
walk
any
day
on
this
tow
path
and
I
mean
for
that
for
taking
more
general
example
and
when
there's
an
event
schedule
where
it
could
be.
C
You
know
every
other
hour
for
the
for
the
next
three
weeks
or
the
next
two
years
and
there's
a
recommendation
to
kind
of
use
the
schedule
itself
in
the
data
so
rather
than
saying
literally
Monday
Tuesday
Wednesday,
you
just
say
every
day
of
the
week
and
then
you've
published
that
once
because
almost
that's
the
level
of
information
that
you
have,
rather
than
generating
additional
data,
which
is
kind
of
you
know,
implied
by
it,
but
is
not
kind
of
concrete.
If
you
like,.
C
It's
to
present
it
to
the
user
exactly
in
a
way
that
would
make
it
like
it's
it's
regular
and
for
the
particular
example
of
walking
we've
kind
of
talked
about
roots
a
bit
before,
but
for
to
be
more
of
a
self-directed
activity
where
you
may
publish
the
route
and
say
it's
available
anytime,
or
these
are
the
opening
hours
of
the
space
if
there
were
any
hours
of
that.
So
rather
than
kind
of
this
is
where
kind
of
teasing
out
with
different
types
of
sessions
is
in
here.
Okay,.
B
B
You've
got
we've
got
facility
use
which
is
basing
in
an
opportunity
to
use
the
facility
at
specific
times.
It
may
be
that
the
facility
doesn't
actually
get
used
for
some
of
those
slots.
You
know,
so
there
is
a
kind
of
an
element
of
kind
of
on
demand
there,
but
there's
a
specific
time
and
place
you
can
use
that
facility
and
then
there's
the
kind
of
on-demand
use
case,
and
at
the
moment
there
isn't
really
anything
inspect
that
talks
about
on
demand
in
1.0,
actually
I
think
most
have
been
one.
B
There
was
this
kind
of
we
had
this
Vevey
definition
of
a
activity,
opportunity
which
was
kind
of
like
an
event
but
wasn't
really
taking
place
at
a
time
a
specific
time,
but
it
wasn't
me
well
defined
and
actually
all
of
the
examples
that
that
we
had
that
might
fit
into
that
use
case.
We're
things
like
walking
routes,
biking,
routes,
running
routes.
So
that's
why
we've
kind
of
morphed
that
bit
into
the
the
routes,
proposal
and
I,
think
that's
probably
that
the
first
example
of
the
kind
of
on-demand
activity.
B
The
other
example
that
is
kind
of
floating
around
in
discussion
is
this
idea
of
virtual
events,
of
which
there
are
I,
think
three
or
four
different
kind
of
categories
that
people
have
been
exploring
so
I
think
we're
going
to
get
more
into
these
kind
of
on-demand
things,
but
I
think
they're
slightly
different
to
their
kind
of
event.
Model.
B
Okay,
so
so
that
so
those
are
they're
kind
of
the
kind
of
requirements,
so
we've
seen
specific
patterns
in
the
data
we
want
to
make
sure
that
they,
those
patterns,
are
consistently
displayed
and
interpreted
by
when
consumers.
So
there
is
a
some
text
now
in
the
draft
specification
and
that
there's
a
spreadsheet
are
just
going
to
walk
us
through
with
a
minute
that
talks
about
what
those
different
type
different
event
types
are.
B
So
we're
going
to
be
basically
defining
three
new
types
and
recommending
use
of
a
appending
type
in
schema.org
to
cover
these
different
use
cases.
So
we're
good
ly
calling
the
scheduled
events
headline
events
and
courses,
I'm
gonna
switch
to
a
spreadsheet
now
which
this
one
that
will
hopefully
kind
of
provide
some
useful
overview.
This
can.
Can
you
read
this?
Okay
through
the
screen
share,
yeah,
okay,
so
I'm
going
to
step
through
these
kind
of
five
examples
just
going
to
show
where
that,
where
the
new
event
types
kind
of
come
in,
so
we've
got.
You
know.
B
B
B
B
B
What
I'll
come
back
to
the
inheritance,
so
the
next
example
is
mass
participation
event.
The
example
here
is
the
big
southeast.
It's
a
one-day
event.
There
are
a
number
of
races
that
take
place
within
that
event.
So
what
we're
proposing
is
here
for
the
kind
of
main
was
calling
a
headline.
There's
a
new
type,
so
the
big
safety
is
a
coupon
would
be
a
headline
event.
The
individual
races
over
the
day
would
be
just
described
as
events
just
a
joke
genetic
events
because
it
might
be
a
race,
it
might
be
a
talk
course.
B
It
might
could
be
a
number
of
different
things
that
appear
in
the
program
and
the
reason
why
we're
kind
of
defining
the
type
further.
That
kind
of
the
headline
event
is
because
that's
where
would
be
the
useful
differentiator
for
a
consumer
so
that
they
can
see
that?
Actually,
this
thing
is
that
it's
made
up
of
smaller
events,
which
are
part
of
a
program,
so
you
probably
want
to
bundle
those
together
and
displaying
them,
and
then
the
last
example
is
a
course
where
you
have
a
scheduled
event
that
you
signed
up
to
a
number
of
classes.
B
You
know
you
expected
that
you'll
attend
all
of
those
classes
to
complete
the
course
so
schema.org
already
has
a
pending
type,
called
course
instance.
So
that's
the
course
that
might
be
running
in
the
autumn.
For
example,
the
individual
classes
will
just
describe
those
as
events
as
before
so
again,
similar
to
a
headline
event.
It's
just
a
useful
way
to
say
this.
This
is
something
this
is
a
grouping
of
of
events,
grouping
of
things
that
you.
B
So
that
make
sense
so
far,
yeah,
okay,
so
the
way
that
the
session
series
in
the
schedule
event
or
a
headline
event
an
event
will
be
associated
together
is
using
a
property
that
people
are
already
using,
which
is
sub
events.
So
in
the
drug,
the
new
draft
spec
there's
a
section
there
that
talks
about
these
parent-child
relationships
between
event.
So
a
headline
event
in
this
example
will
have
a
sub
event
of
this
case.
Different
different
races
in
so.
B
What
we,
what
we
also
saying
is
where
we
have
a
spec
we've
defined
this
idea
of
property
inheritance
so
where
there
is
a
sub
event
relationship
any
for
any
any
properties
of
the
parent
and
will
also
apply
to
the
child
unless
the
child
say
something
different.
So
that's
very
useful
in
the
case
of
session
series
different
example.
So
this
is
the
Wednesday
yoga
example.
So
all
of
the
key
things
are
actually
on
the
the
main
event
and
the
only
thing
that's
that's
distinguishing.
B
The
reason
for
that
is
the
the
what
you,
the
price
that
you
might
pay
to
attend,
like
a
full-day
event,
is
going
to
be
very
different
to
the
price
that
you
would
pay
to
take
part
in
one
just
one
portion
of
it.
You
know
just
the
one
event
in
the
afternoon
and
what
we
don't
want
to
do
is
to
have
implementers
wrongly
suggested
to
people
that
they
can
things
like
attending
this.
B
You
know
the
price
for
a
yoga
session
is
for
the
entire
series,
rather
than
just
actually
one
session
every
day
so
with
with
taking
offers
outside
of
that
in
inheritance,
apart
from
in
the
case
of
these
regular
classes,
where
we've
said
in
the
definition
of
scheduled
session
that
inherits
all
the
information
of
its
parent,
including
the
offers,
but
for
thee
of
those
examples,
you
don't
conclude
the
offers.
I
mean
general
for
any
type
of
event.
If
it's
got
a
sub
event
relationship,
you
never
inherit
the
offers,
because
we
think
I
think
that
makes
it
safe.
B
B
A
Quick
question:
does
that
include
than
the
scenario
kind
of
the
opposite
scenario,
where
you
can
only
turn
up
to
the
event
if
you're
kind
of
site
so
really
not
a
cross
lon
scenario?
Perhaps
there
might
be
a
scenario
where
you
have
to
kind
of
sign
up
to
the
headline
event
before
you
can
take
part
in
the
sub
event,
yeah.
B
So
if
there's
no,
if
there's
no
booking
in
there's
no
offers
or
booking
information
associated
with
the
individual
events
in
the
program,
then
the
only
thing
that
you
could
be
sold
is
office
for
therefore
for
the
full
day,
so
in
these
cases
it
would
have.
You
would
have
to
explicitly
put
some
pricing
or
booking
information
for
these
things.
If
you
want
people
to
be
able
to
buy
it
kind
of
piecemeal,
the
assumption
is
that
you
attend
there
kind
of
the
parent
event.
The
this
is
the
only
difference.
The
regular
class.
The
scheduled
session
is
anything.
E
E
B
Do
have
that
there's
a
you
can
express
an
event
schedule,
so
there's
no
vent
racial
property
which
actually
draws
on
iCal
for
describing
rules
for
its.
It
doesn't
support
everything
I
can't
us,
but
you
can
define
start
and
end
date
for
schedule
how
often
it
repeats,
which,
day
month,
day
or
month
it
repeats
on
and
that
this
some
change
is
still
to
go
in
here
around
just
to
help
kind
of
generate
the
individual
instances,
but
the
kind
of
snow
you're
talking
about
is
covered.
There
I
think.
E
B
That
yeah,
so
you've
got
basically
two
ways
to
publish
schedules.
If
you
want
to
say
there
are
say
so
for
a
sailing
course.
You
want
to
say
there
are
ten
courses,
sorry,
ten
classes,
and
you
want
to
individually
give
the
time
and
date
for
those
classes.
Maybe
there
are
different
locations
or
slightly
different
times.
You
could
list
those
out
as
tense
of
events
in
an
array
if
they're
always
going
to
happen
at
the
same
time
same
place
same
location.
B
B
The
the
sub
event
is
also
useful.
If,
for
example,
you
have
two
cancel
an
individual
event
in
series,
or
maybe
the
time
gets
rearranged,
then
you
can
publish
a
sub
event
that
had
two
states
us
to
one
of
those
things
in
the
series
to
say
this
is
now
cancelled
or
it's
full
or
it's
going
to
be
a
slightly
different
time,
so
that
some
of
that
wording
is
the
thing
that
I
still
need
to
put
into
the
specs
afternoon.
B
So
I
think,
just
to
summarize,
it
I
think
it
reflects
the
current
usage
most
of
the
published
data
that
is
using
sub
events
is
actually
I.
Think
this.
What
we're
now
describing
is
scheduled
series
scheduled
session,
so
it
kind
of
makes
that
a
bit
a
bit
clearer
and
set
some
expectations
around
how
sub
event
will
be
used.
B
We've
tried
to
aim
for
a
kind
of
default
default,
set
of
behavior
and
safe
behavior
for
consumers
to
say
you
know
what
they
should
or
shouldn't
do
when
they're
encountering
sub
events
and
when
is
safe
to
apply
offers
in
different
scenarios,
it
gives
publishers
still
some
flexibility.
So
it's
not
a
rigid
structure.
B
We're
not
rigidly
defining
these
things,
we're
just
defining
some
useful
kind
of
conformance
criteria,
so
you
can
still,
as
as
we
were,
just
discussing,
choose
to
offer
kind
of
piecemeal
attendance
or
classes
or
attendance
to
bits
of
a
you
know,
a
festival
or
the
kind
of
headline
event.
If
you
so
choose,
so
we
don't.
We
chose
not
to
kind
of
start
to.
B
But
we
think
that
this
kit
kind
of
gives
us
model
to
extend,
so
people
could
start
to
define
their
own
if
they
choose
using
extension
mechanisms
in
the
in
the
spec
or
we
can
start
to
codify
some
of
the
useful
patterns.
The
main
one
I
could
see
coming
is
the
virtual
events,
but
that
because,
as
I
said
earlier,
there's
probably
like
three
or
four
different
scenarios
that
people
are
describing
with
virtual
events,
which
are
actually
actually
quite
different
use
cases.
B
There
are
events
where
you
just
turn
up
in
the
gym
and
somebody's
being
broadcast
to
you.
There
are
events
where
you
take
part
just
by
leaving
your
house
and
you're
part
of
a
virtual
event
that
might
be
running
all
around
the
country.
You
know
everyone
goes
for
a
run
on
the
same
day
or
you
know
and
there's
some
other
example
of
those
as
well.
B
So
you
know
things
where
you
know
you
you
take
part
in
a
virtual
event,
but
you
know
at
the
same
time
as
everyone
else
or
everyone
goes
and
participates
at
a
location,
but
at
different
times
you
know,
there's
a
bit
of
some
work
to
do
there
before
we
kind
of
make
some
clear
recommendations
around
that.
But
I
think
this
gives
us.
B
The
other
thing
that
we've
done
is
the
apart
from
course
instance.
The
the
new
types
we've
defined
them,
rather
than
putting
them
into
schema.org,
and
the
reason
for
doing
that
is
it
gives
us
control
over
the
definition
of
some
of
these
conformance
rules.
There's
quite
a
lot
of
debate
and
discussion
in
schema.org
around
adding
different
types
of
events
at
the
moment,
and
they
don't
seem
to
have
got
to
a
broad
consensus.
B
So
we
wanted
to
have
some
clarity
for
our
own
purposes,
so
we're
just
going
to
go
ahead
and
define
what's
useful
for
us,
but
as
I
say
the
caveat
there,
of
course
instance.
This
seems
ready-made
for
we
want
to
use
before,
but
the
the
main
issue.
The
only
issue
with
it
at
the
moment
is
that
it's
pending,
so
they
could
decide
to
throw
it
out
or
they
could
decide
to
change
the
definition
which
gives
us
a
little
risk
and
I've
added
a
note
to
that
in
the
draft
to
say
it
could
change.
B
The
same
is
true
for
what
Nick
mentioned
earlier,
which
is
this
event
series,
so
the
other
thing
that
they've
considering
doing
is
provide
providing
ways
to
group
together
events
to
say
these
are
all
part
of
their
kind
of
common
series,
but
there's
probably
nothing
really
common
about
them
other
than
you
know
that
they're
part
of
that
name
series.
So
the
example
that
they
need
we've
here
is
Olympic
Games,
so
that's
an
event
series
and
then
the
individual
event,
like
the
2012
London
Olympics,
is
an
event
in
that
series
confusingly.
B
B
C
C
What
this
is
trying
to
solve-
and
this
is
a
like
of
fresh
proposal,
there's
only
like
hours
old-
is
this
issue
in
the
data
which
I
didn't
know
how
many
of
you
guys
have
kind
of
looked
at,
for
example,
to
get
active,
London
activity,
finder
or
other
activity
finders
using
active
data,
but
they
have
this
curious
problem
where
there
currently
isn't
a
way
to
sensibly
group
things
that
are
basically
the
same
and
when
I
say
the
same,
you
can
see
here.
Thats
Winfred
alts
has
cleared
the
same
picture
description
title
everything
about
it's
the
same.
C
C
So
you
end
up
with
like
a
big
directory
of
repeated
stuff
and
you
have
to
wade
through
and
look
for
the
relevant
things
you're
you're
interested
in,
because
obviously,
if
you're
browsing
as
a
casual
consumer,
when
you
decide
you
don't
care
about
swim
adults,
you
keep
don't
think
going
through
the
list
to
see
what
else
is
there
rather
than
oh
I'm,
not
sure?
Maybe
I
want
to
go
to
Emily.
C
It
just
occurs
at
lots
of
different
places
and
lots
of
different
times,
which
is
our
kind
of
existing
session
series
that
we
just
been
talking
about
and
what
I'm
I'm
kind
of
proposing
here.
Isis
is
when,
when
we're
pushing
everyone
to
version
two,
if
we
can
simultaneously
be
pushing
them
to
try
and
group
their
events
like
this,
if
they
have
that
ability
so
I
know
that,
for
example,
in
the
Gladstone
system,
they
could
do
that.
C
A
A
You
can
do
that,
but
you
might
also
be
searching
by
location,
and
you
don't
want
to
then,
if
I'm
searching
by
Wembley
I
don't
want
to
see
the
one
coming
up
in
Thornton
Heath,
which
is
the
other
side
of
London,
so
I
think
it's
and
again
this
is
just
my
I.
Don't
know
how
this
kind
of
stuff
actually
works,
but
it's
making
sure
your
people
can
group
it
by
it
can
be
shown
to
the
user
in
a
way
that
it's
grouped,
that
makes
sense
for
them.
A
B
That
makes
sense,
and
that's
one
of
the
reasons
why
I
was
kind
of
a
little
bit,
hesitant
or
kind
of
flip-flopping
a
bit
will
be
more
accurate
reflection
of
whether
to
put
this
in
or
not,
and
because
we
already
have
a
number
of
ways
to
roll
up
events
based
on
things
like
events
that
are
taking
place
in
the
same
location,
events
that
are
organized
by
the
same
person
or
group.
You
know
even
events
that
are
happening
on
the
same
day.
B
Right,
there's
multiple
ways
and
we
don't
we've
just
kind
of
those
are
all
kind
of
attributes
of
the
event
and
as
a
consumer,
you
can
choose
to
kind
of
group
and
organize
based
on
any
of
those
things.
You
know
another
one
would
be
all
of
the
cycling
events,
there's
lots
of
different
ways
to
fold
things
up,
and
so
what
I
think
what
we're
discussing
is
is.
Is
there
something
else?
Is
there
another
group
thing
that's
otherwise
hard
to
do
without
introducing
something
like
event,
series.
C
B
B
C
Totally
right
and
in
in
fusion
or
GL
or
any
of
the
leisure
operators,
data
that
challenge
we
have
is
the
organizer
is
the
is
gll.
The
location
is
the
leisure
center.
The
activity
is
yoga,
but
if
you
want
to
talk
about
something
like
this,
which
is
a
specific
type
of
yoga
and
with
a
particular
description,
that's
common
and
some
may
be
pricing
or
other
things
that
are
common
between
them
and
some
images
that
are
common.
There's,
no
way
of
doing
that.
C
It's
almost
like
we've
got
activity
which
is
like
this
high-level
thing,
and
we've
got
the
granular,
which
is
like
lots
of
little
flow,
yoga's
I.
Suppose
we
don't
want
the
activity
list
to
become
every
possible
type
of
naming
of
activities
which
is
one
way
of
solving
it,
but
doesn't
really
solve
it.
Because,
then
you
can't
put
images
and
descriptions
and
things.
So
one
thing
was
interesting
to
look.
Look
at
I
mean
we
could
probably
browse
goes
for
its
website.
B
Yeah
yeah,
so
I
think
so
I
think
we
could
put
this
in
as
a
way
to
to
indicate
this.
The
fact
that
discussing
it
for
schema.org
suggests
that
there
are
use
cases
for
it
as
well.
I
think
what
we,
where
we
might
have
be
careful
about
setting
expectations
is
just
because
you
put
an
event
series
in
doesn't
mean
that
your
events
are
gonna
get
displayed
in
a
certain
way.
A
consumer
is
free
to
you,
know,
reorganize
things
based
on
them
with
their
particular
needs.
B
D
Seems
to
be
more
aware
of
the
packaging
of
data
in
a
nice
in
a
nice
way,
but
it's
kind
of
we
needed
to
keep
the
the
UI,
the
user
interface,
that
people
how
people
will
display
the
information
separate.
So
personally,
I
mean
in
terms
of
the
event
series
I'd,
probably
just
rip
out
each
of
the
single
sessions
and
I
could
do
a
lot
more
with
it.
There
were
whenever
we
we
choose
to
use
it.
It
is
handy
to
have
there
in
terms
of
saving
data
being
pushed
around.
B
Yeah,
okay,
okay,
that's
useful
feedback;
I'll
put
something
in
the
Indus
back
about
grouping
events.
Maybe
just
talk
about
some
of
the
the
different
ways
that
events
can
be
grouped
and
then
indicate
how
events
use
could
be
used
to
do.
We'd
use
cases
where
you've
got
particular
browning
or
the
information
that.
D
C
Back
to
the
event
series
a
sec
just
to
point
out
the
dynamic
event,
so
it's
subtle,
but
you
can't
really
see
it
from
this
view,
but
c-section
series,
it
says
Tuesday
at
10
o'clock,
so
that's
actually
a
recurring
event
that
occurs
every
Tuesday
at
10:00,
and
so
that
would
be
a
if
we
were
representing
this
screen
in
data.
That
would
be
a
session
series
with
a
event.
Schedule
and
Churchill
would
say.
Tuesday
at
10:00
starts
this
week
and
ends
whatever
whenever
ends
and
then
invisible
on
this.
C
C
D
B
B
So
if
you
have
chance,
it
would
be
great
to
to
pull
out
some
specific
section
of
the
spec
well
I'd
like
to
get
a
feedback
but
being
going
through
the
detailed
wording
and
just
giving
any
comments
you
have
would
be
really
useful
so
that
we've
got
confidence
that
people
are
happy
with
the
changes.
40-Point
knows
this
there's
quite
a
lot
and
we've
been
talking
about
them
on
on
these
calls.
B
So
yeah
so
be
looking
for
that
in
the
next
next
two
weeks,
so
we
can
actually
formally
publish
that
spec.
So
our
next
call
is
on
the
12th
of
September,
so
that
will
be
just
before,
hopefully
we'll
hit
publish
and
if
he's
anything
like
the
call
we
had
for
the
release,
it
will
just
be
rattling
through
a
list
of
kind
of
bug.
B
B
Yeah,
if
you're
not
happy
so,
if
you're
happy
finding
an
issue
on
github,
then
just
giving
just
giving
me
you
know.
Ideally
you
know
this
bit.
I,
don't
agree
with
those
or
section
headings,
so
I
can
make
changes
if
you're
not
happy
about
it
on
github
then
drop
me
an
email
that
that's
the
best
way,
because
it
just
gives
me
a
task
place
to
work
through
and
that's
other
people
pitch
into
the
discussion
as
well.
If.
C
C
That's
an
issue:
I,
don't
like
it
and
yeah
detail,
and
then
you
just
need
to
hit
the
submit
button
in
green
after
you
give
it
a
subject,
heading
and
go
and
to
do
all
of
what
you've
just
seen
there.
You
would
need
to
create
an
account
which
is
also
really
easy
to
do
in
the
top
right
of
the
screen,
and
you
can
click
create
account
creator
under
your
personal
name.
B
There's
quite
a
lot
of
issues
in
backlog.
Some
of
them
are
proposals
and
things
for
future
versions
of
the
speck
on
the
github
projects.
There's
a
projects,
tab
and
there's
a
project
board,
which
is
what
I'm
working
on
for
this
release.
So
there's
different
different
columns
here.
So
the
the
this
one
second
from
the
right
in
editors
draft
those
are
all
the
changes
I've
got
in
so
far.
The
changes
I
need
to
do
this
afternoon.
B
Summarize
this
proposal
we've
been
discussing,
there's
a
few
other
proposals
that
are
under
discussion,
which
a
couple
of
these
might
make
it
in
but
I
think
I'd
like,
for
example,
as
exhibit
routes
that
start
those
that
will
be
in
a
future
version
of
the
specification
so
I'm
using
that
just
to
call
out
things
where
we've
got
some
active
discussion
in
the
community
there's
a
backlog
here.
It's
currently
24
issues
with
other
things
that
may
go
into
the
specification
at
some
point
as
well.
B
C
Worth
saying
anything
you
put
in
issues
is
kind
of
there
for
triage,
so
if,
when
you,
when
you
put
them
in
the
top
of
the
issues,
will
be
able
to
or
ever
will
be
able
to
pull
them
into
this,
this
backlog
so
really
just
shoving
them
into
the
issues
list,
and
then
the
ones
specific
particularly
relating
to
feedback
for
this
will
probably
just
go
straight
to
the
front
of
the
queue
I.
Imagine
they
all
just
put
yep.