►
From YouTube: OpenActive W3C Community Group Meeting / 2017-11-02
Description
A public hangout for members of the OpenActive W3C Community Group.
Agenda: https://lists.w3.org/Archives/Public/public-openactive/2017Nov/0000.html
For more information visit: https://www.openactive.io/w3c-community-group.html
A
Thank
you
all
for
joining
us.
They
and
apologies.
If
there
was
confusion
over
the
start
time,
that
was
entirely
my
fault
mixture
of
given
slightly
different
time
in
the
calendar
email.
So
I
apologize
for
that.
But
it's
nice
to
see
so
many
of
you
here
and
looking
through
the
faces
first
time
on
this
call
through
a
lot
of
you,
which
is
fantastic
because
one
of
the
things
that
were
aim
to
do
in
the
next
phase
of
this
project
work
is
to
get
more
people
involved,
so
we're
off
to
a
flying
start.
A
So
she's
gonna
give
it
update
on
some
of
the
work
that
she's
been
doing.
We're
gonna,
try
and
keep
the
time
and
also
make
sure
that
we
give
them
a
bit
of
time
for
discussion,
so
feel
free
to
ask
questions
as
we
go.
But
I
was
also
a
bit
of
time
at
the
end
for
anything
else
that
you
wanna
raise
or
any
any
questions,
and
you
haven't
had
a
chance
to
ask
so
I'm.
Just
gonna
share
my
screen.
A
Okay,
so
so
this
is
the
first
of
what
I've
been
joking
eco-link
season,
two
of
the
open
activestandards
work.
This
is
a
in
this
first
call
I
wanted
to
discuss
some
of
the
the
plans
and
priorities
for
phase
due
to
promise
perspective
of
the
standards
and
tools
and
technology
aspects
of
the
program.
We're
going
to
talk
a
bit
a
bit
about
some
of
the
research
that
we
start
to
get
underway
around
improving,
discoverability
and
usability.
A
A
A
But
one
of
the
key
things
that
we
need
to
focus
on
is
how
do
we
go
about
improving
the
discoverability
and
usability
of
both
the
data
and
the
standards,
and
that's
a
piece
of
work
that
we've
actually
already
got
underway
and
I
was
going
to
share
some
of
her
initial
thinking.
There
I
would
like
to
get
some
more
input
from
the
group,
and
the
other
thing
that
we
will
be
doing
is
trying
to
move
forward
with
the
activity
list.
A
We
made
some
progress
on
that
in
phase
1,
but
it's
still
a
long
way
from
being
complete
being
completed
and
so
wanted
to
share
some
thoughts
about
how
we
might
be
able
to
kind
of
get
that
back
on
track
and
be
really.
The
kind
of
new
area
that
we'll
be
focusing
on
in
terms
of
developing
guidance
and
standards
is
I'm
looking
at
booking.
A
So
how
do
we
build
on
the
open
data
to
support
booking
workflows
and
let
people
actually
be
more
than
just
discover
opportunities
to
be
active
but
actually
participate
and
take
part
in
those
events?
So
what
what
we've
been
thinking
about
at
the
ODI
is
is
about
the
the
broader
network,
the
ecosystem
that
we're
building
as
part
of
open
active
and
how
the
standards,
tools
and
technologies
that
we're
creating
in
this
group
can
help
move
that
forward.
A
So
we
have
publishers
like
fusion,
which
is
cycling,
who
are
providing
data,
that's
being
used
by
by
I
mean
in
their
role
as
an
intermediary,
and
we
also
have
interest
from
people
like
the
BBC
in
starting
to
incorporate
that
data
to
create
activity.
Finders
active
London
have
been
using
the
data
via
I'm
in
to
power
their
activity
finder.
So
we're
already
starting
to
see
some
benefits
to
end-users
in
terms
of
being
able
to
more
easily
discover
opportunities
to
be
active,
so
we
have
data
flowing
through
the
system
already.
A
So
we
want
to
kind
of
enable
kind
of
a
rich,
diverse
ecosystem
that
is
as
open
as
possible
for
as
many
people
to
get
involved,
but
the
the
emphasis
on
phase
one
was
on
the
really
about
publishing
data,
but
now
that
we
have
this
broader
ecosystem,
we
know
to
start
to
think
about
users
of
the
data
as
well
and
how
we
can
best
support
them
and
that's
going
to
be
a
key
theme.
I.
A
Think
of
what
we're
going
to
be
doing
in
Phase
two,
so
we've
been
looking
a
bit
this
idea
of
developer
relations,
so
how
you
start
to
support
developers
using
an
API
or
a
platform
or
participating
in
the
kind
of
ecosystem
that
we're
building
in
open
active.
This
is
quite
quite
nice.
Hierarchy
of
developer
needs
that
I
came
across
recently,
which
I
think
usefully
typed
this
together.
A
On
top
of,
that
is
a
variety
of
different
types
of
support,
so
a
community
support
through
the
forums
that
we've
been
creating
on
slack,
twitter
and
elsewhere,
but
also
educational
resources,
so
tutorials
document
and
other
forms
of
documentation.
So
it's
time
to
think
about
how
we
start
to
build
these
areas
across
the
program
so
I'm
going
to
pass
over
to
Sally.
A
B
Okay,
so
if
you
do
jumps
next
slide,
is
that
very
nicely
introduces?
We
have
been
looking
at
discoverability
and
usability,
but
I
just
wanted
to
really
quickly
summarize
that
so
this
sort
of
funnel
that
you
can
see
on
the
screen
is
very
much
what
we're
looking
at
in
terms
of
people's
kind
of
relationship
journey
with
open
active.
So
there
are
people
completely
unaware
and
don't
have
a
clue
that
it
exists
or
that
they
might
even
find
it
relevant.
There
are
people
who
are
starting
to
become
aware,
but
aren't
really
doing
anything.
B
Then
there
are
people
who
are
taking
action
in
various
different
forms,
and
then
there
are
the
people
who
have
already
done
stuff,
but
they
have.
This
is
essentially
ongoing
relationships.
So
what
we
want
to
do
is
we
want
to
kind
of
it
sounds
really
horrible
and
like
conversion
II,
and
that
we
want
people
to
kind
of
obviously
go
through
that
funnel
and
bring
other
people
along
the
way
as
well.
B
So
if
you
just
want
to
jump
to
the
next
one,
but
a
little
summary
I'm
going
to
fly
through
the
rest
of
this
because
I
don't
want
it
to
be
about
me
talking
at
you
the
whole
time
and
but
what
we
want
to
think
about
are
these
kind
of
different
areas.
So
how
do
people
find
the
data,
those
kind
of
questions,
so
where
should
we
be
this
fall
and
YouTube,
and
then
also?
B
How
can
we
support
people
better
using
the
data
so
to
do
that,
we've
been
posing
all
these
kind
of
questions
about
what
the
problems
are,
what
the
gaps
are,
what
we
could
be
doing
better
at
trying
to
think
in
a
little
bit
more
detail
about?
What's
actually
happening
so
if
you
go
through
again,
this
happily
ties
into
the
fact
that
we
are
reading
the
websites.
So
there's
a
couple
of
blog
posts
there,
one
being
talking
a
little
bit
about
the
website,
discovery
work
that
we've
done
and
one
being
the
fact
the
tender
is
open.
B
So
the
cons,
for
instance,
is
a
big
piece
of
it
and
but
in
the
middle,
we've
got
a
really
nice
little
bit
of
overlap.
So
if
you
want
to
jump
ahead
again,
we've
done
is
kind
of
merge
the
two
a
little
bit.
So
we've
done
all
of
these
things,
which
spans
from
looking
at
website
analytics
and
the
current
site
and
three
to
kind
of
holies
workshops
where
we'd
be
mapping
out
some
end-to-end
processes
that
people's
touch
points
all
along
their
way,
both
online
and
offline,
and
we've
been
doing
a
lot
of
things
like
interviewing
people.
B
So
if
anybody
anybody
out
there
wants
to
the
interviews,
it's
not
painful
at
all,
I
promise,
it's
just
really
informal
chat,
and
so
that's
either.
People
on
the
call
or
anybody
listening
afterwards
you're
very
welcome
to
get
in
touch
and
we've
also
been
doing
alone.
Surveys
so
outs
like
that
in
doing
later,
desk,
research
and
stuff
as
well,
which
you
can
read
this
at
your.
B
We
jump
ahead
again.
I've
got
a
few
examples,
so
desk
research,
wise
we've,
been
looking
at
a
load
of
developer
documentation.
So
this
is
just
the
face
book
developer
site
as
an
example,
but
looking
at
things
like
information
architecture,
so
how
they're
structuring
their
sites,
how
things
being
categorize
the
kind
of
terminology
that's
being
used,
basically
to
look
at
what
we
should
be
doing
better
and
on
the
next
slide,
you'll
see
that
we've
also
been
looking
at
UI
examples.
So
what
really
nice
examples
of
things?
Do
we
have
that
again?
B
We
learned
from
so
on
the
Left
I,
really
liked
the
fact
that
we've
got
this
kind
of
setup,
your
integration,
three
simple
steps
and
code
snippets
different
languages,
one
we've
got
at
the
top.
The
building
experiences
with
applets
example
gives
so
many
nice
use
cases
and
can
help
people
relate
to
it
quickly.
At
the
bottom,
we've
got
really
good
signposting,
which
I
think
it's
lacking
a
little
bit
at
the
moment,
and
then
there's
also
one
that
I
can't
see
very
well
do
spaces
in
the
way.
B
But
it's
something
it's
basically
like
a
three-step
process
of
making
it
very
clear.
What
actually
has
to
happen
so
there's
a
lot
of
things,
I
think
we
can
learn
from
and
on
the
next
slide,
we've
also
been
looking
at
content
as
well,
so
we
have
the
spec,
which
is
brilliant
and
Lee's
worked
incredibly
hard
on
that
and
this
unless
you're
the
kind
of
person
who
enjoys
reading
the
expect
dogs,
then
that
might
not
be
the
most
appealing
thing
to
you.
B
This
is
a
github
example,
but
there
are
lots
of
things
that
we
could
potentially
be
doing
better
on
that
front
and
there
are
some
important
points
which
I
think
we're
going
to
come
back
to
in
a
second
in
terms
of
responsibilities
and
division
and
actually
how
much
we
can
actually
do
in
terms
of
resources
and
timing
and
all
of
that.
But
just
in
terms
of
the
content
that
we're
looking
at
and
on
the
next
slide,
you'll
see.
B
A
Sure
so
this
this
was
a
breakdown
of
the
different
types
of
documentation
that
is
often
useful
to
help
developers,
but
also
people
more
broadly.
We
get
up
to
speed
with
new
subjects,
so
there
are
tutorials
how
to
go
in
those
discussions
and
reference,
so
reference
material.
So
to
put
that,
in
the
context
for
open
active,
what
we've
created
so
far
in
terms
of
the
specifications
is
really
just
reference
material.
A
It's
the
kind
of
detailed
guidance
which
you
need
to
kind
of
underpin
all
of
the
others,
but
he's
not
necessarily
the
most
accessible
way
for
somebody
to
get
to
grips
with
being
able
to
quickly
work
out
how
to
publish
their
data
according
to
the
standards
or
to
map
their
internal
data
model
to
standard
that
we've
described.
So
we
need
to
supplement
that
with
tutorials,
so
you
know
being
able
to
quickly
take
through
somebody
in
a
step
of
publishing
their
first
opportunity,
data
or.
A
Reading
from
the
paging
paging
API
to
collect
and
index
data
that,
from
elsewhere
terms
of
how
to
guidance,
this
is
more
goal
oriented.
So
it's
more
kind
of
problems,
so
problem
solving
I
think
a
good
content.
Ceo
is
think
about
Stack
Overflow
I
have
got
a
specific
problem.
How
do
I
address
that
again?
That's
something
we
need
to
fill
the
kind
of
discussion.
A
Material
is
much
more
general,
so
it
would
be
more
just
kind
of
background
to
why
we've
approached
designing
the
standards
in
a
particular
way,
what
we
hope
to
achieve
by
standardizing
particular
aspects
of
the
yueqin
system,
so
we're
planning
to
put
together
this
some
of
these
guidance.
So
we
will
have
some
resources
at
the
ODI
to
do
that,
and
we
have
to
start
releasing
some
Lao
for
the
coming
months
and
it
would
be
great
to
get
your
feedback
on
this.
A
So
if
you
have,
if
you
have
previously
struggled
to
get
started,
we'd
like
to
hear
about
what
problems
you've
faced,
so
that
we
can
think
about
whether
we're
creating
the
right
kind
of
documentation,
but
also
as
we
produce
some
of
these
tutorials
and
how-to
guidance
it'd
be
useful
to
get
some
feedback
from
you
wonder
how
well
you
think,
do
you
think
it
works?
So
we
can
make
sure
that
we're
supporting
their
community
in
the
right
ways.
A
Karam
a
little
bit
about
the
developer
tools,
just
to
kind
of
build
on
what
salary
was
just
saying
and
there's
a
variety
of
different
types
of
tools
that
are
useful
for
developers
at
one
end,
I
think
you
have
what
I've
been
thinking
of
in
terms
of
onboarding
and
discovery
tools.
So
how
do
you
find
the
data?
How
do
you
know
what
is
included
in
a
an
opportunity,
data
feed
from
a
particular
publisher?
So
how
do
you
know
what
activities
are
in
there?
A
So
if
you
go
to
the
open
banking
website,
you
can
see
on
one
page
all
of
the
api's
that
have
been
published
by
UK
banks.
You
can
see
whether
they've
implemented
we
take
api's
have
implemented,
which
version
of
the
API
conformal
move,
etc.
So
what
we
want
to
do
is
to
start
to
put
this
in
place
for
open
active,
so
we
can
highlight
how
do
you
get
to
the
endpoint
for
specific
publishers?
Is
that
endpoint
performant
with
paging
suspect?
Is
it
following
the
data
model?
What
types
of
activities
are
in
there?
A
B
And
again,
this
is
where
you
or
anybody
you
know
who
comes
in
in
terms
of
we're.
Gonna
get
started
on
that
because,
with
all
of
this,
we're
very
keen
not
to
turn
into
these
massive
kind
of
things
that
never
actually
get
finished.
So
we're
very
much.
The
mindset
that
we'll
put
stuff
out
and
we'll
iterate
on
it
so
that'll
carry
on
anyway
and
the
stuff
that
I'm
doing
in
terms
of
interviewing
people
and
doing
research
will
feed
into
that.
B
Tunics
them
and
the
bottom
of
that,
because
medium
is
so
beautiful
and
streamlines
that
it
doesn't.
Let
you
shout
about
things
very
easily.
We
have
a
survey,
and
so
that
is
the
survey,
and
that
is
a
blog
post.
So
if
you'd
be
so
kind
as
to
share
those
two,
please
send
us
your
thoughts.
That
kind
of
covers
a
whole
range
of
things
but,
as
we
said
say,
if
you
just
find
it
easier
to
jump
on
the
phone,
it
will
send
us
an
email.
B
D
A
Right,
so
that's
the
discovering
usability
where
the
in
terms
of
revising
the
opportunity
data
model
the
way
I
want
to
kind
of
drive
that
in
future
is
to
do
it
based
on
feedback
from
people
who
actually
start
to
use
the
data.
So
we
know
that
there
is
there's
quite
a
deal
of
flexibility
in
the
model.
A
We
may
need
to
start
tightening
that
up
to
make
it
easier
for
consumers.
There
are
other
refinements
that
we
could
make
to
the
model.
There
might
be
other
detail
that
we
need
to
add
to
make
it
useful
for
people
the
so,
rather
than
just
kind
of
forge
ahead
on
kind
of
guessing
what
might
be
useful,
what
what
we
should
prioritize
I'm,
really
keen
to
hear
from
people
who
are
actually
starting
to
use
the
data.
So
if
you
are
building
things
against
the
opportunity
data,
then
let
us
know
what's
working
on:
what's
not
working.
A
If
you
know
people
who
are,
then
please
ask
them
to
share
with
this
group
as
well,
so
thinking
about
the
the
other
areas
of
activity,
so,
firstly,
the
the
activity
list.
So
the
we
made
some
progress
on
that
last
year.
We've
got
it
was
really
encouraging
that
so
many
different
organizations
started
to
share
their
lists
with
the
group
so
that
we
could
start
to
look
for
commonalities
and
we
managed
to
make
some
progress
in
merging
together
some
lists
from
Sport
England
from
sports
wheat
and
from
dance
but
I
whoa
I.
A
Don't
think
anyone
has
totally
bought
into
the
structure
of
the
list
as
it
stands,
I
think
there's
some
there's
been
some
differing
opinions
about
how
we,
how
we
structure
the
list
in
terms
of
how
a
hierarchical
it
should
be
different
opinions
about
how
we
go
about
making
the
lists
be
useful.
So
should
we
aiming
for
it
to
cover
as
much
as
possible,
or
should
we
just
be
focusing
on
some
kind
of
subset
of
activities?
A
So
I,
don't
really
feel
like.
We've
got
to
a
good
set
of
agreement
on
that
early
draft.
So
while
it's
there
and
people
have
started
to
link
their
activities
back
their
own
activity
lists
against
it,
it
still
need
an
awful
lot
of
work
to
move
it
forward.
So
I
think
one
of
the
things
that
we've
been
struggling
with
is
just
to
get.
A
That
is
to
get
agreement
by
only
doing
it
largely
with
through
these
calls
so
I'm
thinking
that
we
might
need
to
actually
run
some
face-to-face
workshops
for
those
people
who
are
particularly
keen
on
moving
this
aspects
of
work
forward.
I
think
I
think
that
there's
a
lot
of
Merit
in
getting
us
getting
all
of
us
together
in
a
room
to
hash
out
what
that
structure.
A
Look
like
there's
some
considerations
that
we've
not
really
dug
into
yet,
which
is
about
how
the
list
is
owned
and
maintained
moving
forward,
because
it's
changing
quite
rapidly
could
be
changing
quite
rapidly.
We
need
to
work
out
what's
the
mechanism
for
taking
on
suggestions
and
incorporating
those
into
the
list
and
also
doing
some
user
testing.
So
is
the
list
actually
useful?
Is
it
fit
for
purpose?
A
So,
while
I
don't
think
the
the
lack
of
a
common
list
is
stopping
anybody
from
publishing
opportunity,
data
we're
not
yet
at
a
stage
where
list
is
that
we
could
strongly
recommend
at
the
moment
it
feels
like
something
that
people
that
could
be
testing
and
evaluating,
but
it's
not
really
where
we
want
it
to
be
so.
I
want
to
focus
one
of
our
next
calls
around
the
the
list
and
looking
at
some
of
the
structure,
but
I
will
also
be
trying
to
organize
some
workshops,
so
I'd
be
interested
to
know.
E
Know
we'd
be
interested
as
well
great,
okay,
so
I
think.
F
A
face-to-face
workshop,
you
know,
sounds
good
for
us
to
move
it
forward,
because
I
am
not
sure
how
much
time
I
would
be
able
to
spend
on
it
over
a
long
period
of
time,
but
certainly
face
to
face
workshops
you
know
would
be
would
be
something
that
could
be
scheduled
and
you
know
handled.
Is
that
way.
A
Yeah
I
think
sounds
good
I
think
if
we
can
get
to
a
point
of
having
some
common
agreement
around
the
the
structure
of
the
list
and
how
we
go
about
governing
the
contents,
then
that
will
give
us
a
framework
that
we
can
then
use
to
move
you
forward
if
you
have
to
continue
in
a
more
kind
distributed
way.
So
I'll
follow
up
with
the
with
send
an
email
to
the
list
to
start
to
find
a
good
time
for
the
workshop
and
see
who
else
was
to
be
involved.
Yeah
mindful.
D
I
think
there's
a
few
people
who
actually
using
this
list
at
the
moment,
planning
planning
issues
with
it
they're
having
trouble
spending
time
engaging
with
it,
so
I
yeah
keen
to
try
and
figure
out
a
way
that
we
can
engage
them
and
bring
them
into
this
conversation,
even
if
it's
only
they
can
only
spend
time
for
summary
thoughts.
Yeah.
A
Okay,
I'm
also
mindful
that
them
that
face-to-face
workshop
can
be
difficult
for
everyone
to
attend
just
for
location
reasons.
So
I
will
do
my
best
to
give
plenty
of
notice,
so
people
can
share
it
in
time,
but
if
we
have
several
that
we
try
and
use
that
use
different
locations
so
that
we
can
get
a
different
mix
of
people
involved,
and
the
intention
is
to
for
this
to
be
kind
of
productive
time.
It's
not
to
exclude
anyone.
A
So
we
kind
of
want
to
try
and
approach
this
quite
methodically.
So
what
we're
planning
to
do
to
start
with
is
to
try
and
take
stock
of
the
existing
landscape
of
booking
api's
in
the
sector.
So
we
get,
we
can
develop
a
shared
understanding
of
what
the
current
state
to
play
is
across
different
platforms,
different
applications
and
the
variety
of
business
models
and
approaches
that
are
being
used
so
far.
And
then
we
can
use
that
as
a
basis
for
working
out.
A
What's
the
most
useful
next
steps
in
terms
of
standardization,
I
think
there's
likely
to
be
a
different
mix
of
organizations
and
platforms
who
are
very
keen
to
to
get
involved
at
this
stage.
It
may
not
have
been
involved
in
some
of
the
early
work
on
open,
active,
so
I'm
keen
to
reach
out
to
to
those
people
and
make
sure
that
we
can
get
them
involved.
So
after
Sally
and
I
have
done
some
of
this
ground
work
around
discovery,
probability
and
usability
we'll
be
moving
on
to
booking.
A
G
Yeah
hi,
this
is
Dom,
for
my
men
might
be
here,
yeah
I
think,
as
some
of
you
aware,
booking
is
particularly
our
bag,
and
we're
really
excited
about
this
and
just
picking
up
on
something
you
said
their
room
Lee,
which
is
interesting.
There
are
a
variety
of
business
models
in
the
sector
and
loads
of
different
security
requirements,
but
if
we
think
back
to
when
this
all
started
and
we're
focusing
on
publishing
the
open
data,
it
did
at
that
point
seem
you
know
a
difficult
objective
and
something
that
was
like
this
can't
be
done.
G
And
now
we're,
like.
You
know
how
many
20
days
sets
open,
and
now
it's
like
more
coming
and
it's
great
so
I
think
we
should
be
looking
at
this
is
really
exciting,
as
you
alluding
to
a
really
exciting
opportunity,
if
I
could
just
spend
a
couple
of
minutes
and
explain
a
little
bit
about
where
our
logic
is
coming
from.
G
This
amazing
thing
when
they
turn
around
and
say
you
know,
where's
the
commercial
return
for
me
and
I
was
speaking
to
an
operator
yesterday
at
the
you
character
summit,
and
you
know,
within
about
20
seconds
of
explaining
the
whole
thing.
The
question
was
yeah,
but
what's
in
it
for
me,
where's
the
commercial
term,
what
do
I
get
back
and
the
way
we
see
this
is
whilst
open
data
is
obviously
all
built
on
open
data
than
you
know.
You
know
as
well
as
anyone
that
I
mean
really
applicative
datum.
G
We
need
evangelists,
but
we
think
it
really
centers
around
booking
the
next
step
and
we
just
kind
of
maybe
sometimes
a
lack
of
momentum.
In
terms
of
you
know
this
unresolved
github
issues
here
and
there
and
some
data
feeds
down,
and
we
need
to
really
build
a
strong
business
case
for
this.
We
need
to
get
data
open
and
make
it
book
a
book.
So
that
importantly-
and
this
is
coming
in
directly
from
the
word
nish
is
doing
so-
we
can
bring
on
board
high-profile
data
consumers
that
can
drive
traffic
towards
these
activity.
G
The
reason
that
this
is
comes
up
so
much
is
because
that
this
is
finding
that
no
big
brand
investing
in
a
digital
or
web
presence
once
people
leaving
a
web
app.
So
they
didn't
want
people
finding
an
activity
and
then
being
signed
posted
away.
Initially,
that
was
good.
That's
we
can
do
that
with
open
data.
Now
we
need
to.
We
need
to
kind
of
drive
the
booking
actually
within
the
the
experience
and
I
think.
G
Secondly,
initially
saying
that,
if,
if
booking
happens
with
a
brand
or
with
the
organization,
the
big
organization
with
a
lot
of
users
using
it,
then
they
own
the
customer,
they
can
learn
about
them.
They
can
reward
them,
they
can
support
them,
they
can
incentivize
them
going
forwards
and
they
can
better
serve
that
customers
needs
so
I,
guess
kind
of
picking
up
on
making
this
a
little
bit
more
tangible.
G
Some
of
the
examples
that
he's
coming
back
with
that
lucozade
sport
have
said
they
must
have
booking
to
prove
that
1
million
people
can
be
more
active,
reward
gateway
who
impro
involved
in
employee,
HR
and
wellness.
They
must
have
booking
vitality
and
the
rewards
in
insurance
company,
but
also
said
they
must
have
booking
and
importantly,
we're
now
getting
tech
companies
competing
for
contracts
and
being
asked
about
open
book
ability.
I
only
she's
been
speaking
to
badminton
england.
G
Recent
about
this
and
his
work
currently
extends
to
a
lot
of
organizations
within
open,
active,
so
he's
reached
out
to
a
few
who
he
hoped
would
make
it
to
the
core
today
and
so
he's
actually
got
something
on
their
behalf,
which
I'm
now
reading
on
his
behalf,
so
make
sweat.
So
Nick
from
make
sweat
has
said.
G
So
there's
real
emphasis
there
on
wanting
to
contribute
to
this
in
the
same
way
that
WT
sis
has
done
so
well
in
doing
the
activity
lesson
that
this
standard
and
one
more
and
I
apologize,
I,
know
I'm
speaking
quite
a
lot
here
on
Missy's
behalf.
So
do
blame
him
not
me,
but
hula
hub
have
also
said
that
and
they're
all
about
sports
and
leisure
activity
bookings
having
a
common
API
standard
for
bookings
will
allow
us
to
add
new
activity
providers
more
quickly
and
easily
from
the
overall
sectors
perspective.
G
It
will
also
help
widen
access
and
participation,
which
really
echo
is
the
message
we're
getting
back
from
these
big
brands,
which
is
that
we
can
help
get
people
more
physically
active,
but
we
just
need
to
be
able
to
offer
this
this
book
ability
and
then
finally,
ng
bees
are
also
happy
to
get
involved.
Antonis
is
working
helping
to
shape
their
the
standards
and
add
influence
at
badminton.
England
is
really
driving
this
and
really
at
the
forefront
of
wanting
this
book
ability
so
yeah.
G
That
was
a
lot
for
me,
but
that's
basically
kind
of
I
guess
an
overview
of
the
work
that
I'm
in
and
particularly
initial
in
the
field
has
been
doing
with
the
gospel
book
ability
and
how
important
we
see.
This
is
for
the
sector
and
building
on
something
that
it's
just
this
whole
movement,
I'd
only
tell
you
is,
is
amazing.
It's
done
so
many
great
things
and
to
take
it
to
the
next
level
and
engage
the
right
organizations
in
order
to
achieve
what
we
all
want
to
achieve,
which
is
a
more
active
nation.
G
C
B
A
D
Okay,
so
that's.
D
A
A
So
I
think
I
think
we're
all.
On
the
same.
The
same
page,
I
think
I
think
everybody
agrees
that
the
booking
is
a
vital
part
of
the
kind
of
ecosystem
that
we're
building-
and
it's
great
it's
great
to
know
that
that
there's
so
much
extra
momentum
that
we
can
unlock
by
making
some
progress
around
booking,
so
I
mean
I,
hope,
I
didn't
give
you
the
impression
that
booking
was
in
some
way
low
priority
or
wasn't
gonna
happen,
because
that
was
my
intent.
A
It
was
jobs
just
setting
out
a
proposal
for
how
we
were
going
to
start
to
move
that
new
thread
of
activity
forward.
Rather
than
just
assuming
a
blank
slate.
It
seems
reasonable
to
get
everybody
who
is
doing
some
work
around
looking
to
share
what
they've
learnt
so
far,
what
the
way
they
approach
building
those
api's.
So
we
can't
benefit
from
that
learning
and
and
move
forward
as
quickly
as
we
have
with
the
with
the
open
data.
I
mean
so
I
go
ahead.
G
Yes,
sir
I
just
accept
it
and
I
hope
you
didn't
come
across
as
a
diatribe
there.
They
I
wasn't
in
any
way
trying
to
like
cross
anything
you'd
said
before
it
was
really
kind
of
really
seizing
the
opportunity
with
you
know,
a
forum
and
if
you
kind
of
given
a
soapbox,
one
would
hope
they
try
and
get
up
there
and
preach
what
they
want
to
preach.
But
I
think
I'm
in
would
love
to
be
a
part
of
that
and
I'm
sure.
G
If
nish
was
here,
he'd
be
he'd,
be
saying,
you'd
be
happy
to
share
the
kind
of
data
he's
getting
back
and
the
information
and
what
people
want,
because,
ultimately
they
I
think
it's
going
to
be
these.
The
data
consumers
they're
going
to
be
driving
driving
this
agenda,
so
we'd
be
more
than
happy
to
kind
of
on
his
behalf,
offer
his
help.
So,
yes,
again,
I
think
as
the
the
chat
is
illustrating
like
people
are
keen
to
be
involved.
So,
let's
just.
G
A
I'm
just
skipping
over
this
slide
now,
so
we
have
got,
isn't
a
member.
Now
we've
got
a
bunch
of
work,
that's
currently
underway,
and
so.
A
We
also
have
developer
who's,
gonna
start
building
a
API
dashboard
he
starting
in
a
week
or
so
so
we
expensive
made
rapid
progress
through
that.
So
my
December,
we
hope
to
have
the
situation
of
that
dashboard
bailable.
We
hope
to
have
published
the
findings
around
discovery,
usability
and
get
some
the
documentation.
I
also
have
that
booking
research.
A
The
way
that
we
can
start
to
make
progress,
I've
been
thinking
about
doing
the
activity
list
workshop
in
January,
just
to
make
sure
that
we've
given
as
much
as
possible
in
the
I'll
come
back
to
the
on
booking
that
we
need
kind
of
I.
Suppose
the
approach
I
was
outlining
is
I.
Think
you
very
similar
to
what
we
did
at
the
start,
with
the
opportunity
and
I
asked
people
to
share
example,
data
so
that
we
could
start
to
compare
across
different
platforms,
and
then
we
we
start
to
draw
out
the
common
elements.
A
So
what
I
want
to
do
is
encourage
everybody
to
do
the
same
thing
looking
so
if
you've
got
existing
api's
where
you're
happy
to
share
imitation,
if
it's
not
already
open,
then
I
think
doing
them
would
be
useful.
Useful
input
into
that
research,
I
think
sharing
business
models
and
approaches
that
you're
you're
taking
around
implementing
looking
will
help
us.
A
G
D
General
activity
find
a
question
specifically
for
the
booking
research,
and
you
were
just
asked
you
about
people.
Spending
in
city
inspects.
I
can
see
sorry,
so
quote
you
there
Ravens,
for
the
sake
of
the
audience,
for
the
clarity
local
perspective,
we're
just
in
the
process
of
completing
in
rest-based
wrappers
around
some
of
our
booking
functionality,
he's
gonna
desiccate,
whether
you
can
share
those,
and
so
that
sounds
great
I'm
sure
there's
a
few
other
communities
I.
D
Can
the
important
bucking
bug
is
one
whether
you
have
to
share
the
existing
looking
API
ways
and
see
it's
time
to
do
the
same
for
those
that
don't
have
booking
a
PMO's.
Yet
it
was
this
or
are
you
able
to
create
some
kind
of
template
or
something
that
I'm
just
thinking
what
what
format
would
be
most
like
to
capture
alignments
and
from
the
making
people
that
might
want
to
create
an
API
in
the
future
and
yet
done
so.
A
A
What
I
was
thinking
was
that
if
we
can
understand
what
commonalities
there
are
between
the
api's,
then
we
might
be
able
to
kind
of
riff
off
in
terms
of
debate.
So
you
know
would
if
we
can
identify
the
commonalities.
Does
that
work
for
people
so
use
that
as
a
provocation,
rather
than
just
a
kind
of
general.
F
Li
one
of
the
other
things
which
we'll
also
need
to
sort
out
quite
quickly
is
we
all
need
to
will
need
to
know
that
what
the
scope
of
this
work
is
going
to
be
in
terms
of
will
it
stop
at
the
point
of
making
the
booking
or
will
this
also
have
some?
You
know
some
parts
to
it
for
after
service,
sorry,
after
booking
service
notifications
or
service
related
activities,
I
mean
one
of
the
biggest
things
that
we
get
is
after
a
booking
has
been
made.
F
There
is
all
the
normal
stuff
for
you
needing
to
send.
You
know,
send
email
confirmations
whatever
the
case
is,
but
then
more
and
more
people
are
wanting
push
notifications
six
hours
before
the
event,
so
that
they
have
a
have
a
little
reminder
on
their
phone
to
say
that
that
they
have
this
booking
or
whatever
the
cases
will
need
to
will
need
to
have
some
sort
of
guidance
in
all
this
as
to
what
happens
after
the
booking
has
been
taken,
accepted
and
processed
in
terms
of
service
communications,
and
things
like
that.
A
So
we
can
start
moving
forward,
don't
mean
there's
various
kind
of
a
use
case
templates
that
are
floating
around,
but
you
know
just
trying
to
identify
what
does
ability
mean
for
everyone
and
to
understand
what
they're,
where
those
kind
of
limits
are
where
we
can
most
usefully
focus.
Our
initial
focus
I
think
we
will
need
some
very
clear
use
cases
here
to
guide
the
work,
otherwise
we're
going
to
take
on
quite
a
lot
of
such
a
broad
space
that
we
can.
D
D
What
would
be
really
great
to
do
is
to
demonstrate
some
of
the
big
organizations
when
they
get
involved
and
I
wrote
that
when
they
need
to
engage
them,
what
they
would
need
to
provide-
and
that's
easy
to
do
but
I'm
just
thinking,
because
if,
if
we
can
do
that,
it's
much
easier
for
them
to
commit
to
joining
these
kind
of
calls,
but
they
can
see
where
the
outcome
is
going
to
be,
or
at
least
where
we're
going
with
it
and
by
a
certain
day.
I
know.
D
Last
time,
one
of
the
reasons
I
had
an
issue
just
in
terms
of
engaging
them
to
carry
on
coming
back
to
the
call
was
that
coming
back
to
the
cause
was
that
it
was.
We
had
quite
a
few
calls,
and
obviously
there
wasn't,
because
we
didn't
have
like
overarching
kind
of
this
is
when
we're
aiming
to
you
know
it
was
I,
guess
it
was
less
clear
to
them
when
you
was
going
to
finish
all
the
key
points
to
input
were
so.
If
we've
got
time
scales
around
this,
it
might
be
really
good
to
say.
D
D
You
might
be
interested
in
to
this
booking,
whatever
it
is,
and
then
my
we
can
really
focus
on
trying
to
get
those
people
engaged
in
the
conversation,
and
even
if
that
results
in
like
a
second
set
of
conversations,
another
focused
period
of
time,
which
they
can
decide
whether
to
commit
to
or
not
at
least
it's
kind
of
a
you
know,
almost
chapters
of
push
that
doesn't
kind
of
go
on
without
a
kind
of
next
chapter
being
defined.
It's
just
just
a
kind
of
idea.
Yeah.
A
Yeah,
well,
you
want
to
get
to
a
clear
road
map
and
have
some
target
dates
for
versions
of
specifications
and
outputs.
I,
don't
think
we're
in
a
state
where
we
start
to
do
that.
Yet
because
there's
just
need
to
get
the
groundwork
in
place
in
terms
of
scoping
use
cases
and
understand
the
existing
work,
so
I
think
a
little
way
off
from
get
in
there.
But
that's
certainly
what
we
need
to
be
aiming
for
and
I'm
mindful
of
time,
there's
a
because
one
ought
to
do
other
things
that
don't
stop
any
from
commenting.
A
But
there's
one
or
two
other
things
just
wanted
to
briefly
touch
on
I
will
share
these
slides
afterwards,
and
you
really
would
be
really
good
to
get
a
wider
mix
of
people
attending
these
meetings
so
that
we
can
get
developers
product
owners
who
were
starting
to
build
things
with
the
opportunity
data.
So
we
can
get
some
feedback
on
how
well
the
data
is
supporting
their
needs
and
as
a
vegetable
ready
around
Camp
broadening
input
around
booking.
A
It
would
be
great
for
all
of
you
to
kind
of
share
the
work
that
we
do
here,
that
we
start
to
communicate
through
the
blog
to
try
and
raise
some
of
the
visibility
of
it
more
generally
across
the
program.
So
there's
some
links
in
here
that
you
can
that'd
be
great.
If
you
could,
you
could
share
out
widely
in
terms
of
our
next
calls.
This
was
what
I
was
planning
to
do
between
now
and
Christmas,
so
I
in
the
corn.
A
In
two
weeks
time,
I
wanted
to
take
stock
of
where
we're
at
with
the
opportunity
data
so
I
starts,
do
look
ways.
We
can
do
some
analysis
of
the
data
that's
published,
so
we
can
get
a
sense
of
what
the
quality
variation
is
amongst.
Some
of
the
existing
data
feeds.
A
That's
something
that
we
need
to
be
doing
anyway.
The
ODI
is
part
of
some
of
the
platform
that
so
the
dashboard
build
out
that
we
are
doing
so
wants
to
share
that
with
the
group
and
have
a
check-in
and
discussion
in
in
November
later
in
November
around
the
activity
lists
where
I
think
we
can
firm.
What
we
were
trying
to
achieve
in
a
workshop
in
January
then
did
the
call
in
December.
A
Hopefully,
by
that
point
we
will
have
had
some
good
input
from
the
community
and
I'll
be
putting
some
calls
out
on
the
mailing
list
and
elsewhere
to
help
us
start
to
understand
what
the
landscape
looks
like
around
booking.
So
we
can
start
to
focus
in
on
some
of
those
use
cases,
some
of
the
other,
the
other
things
that
we
haven't
really
had
time
to
discuss
today
around
just
broader
requirements,
around
security,
privacy,
payment
handling
and
a
whole
bunch
of
issues
that
be
important
in
the
area.
B
Quickly,
the
video
reference
Jamie
before
he
left
he
such
drop-off
said,
and
he
has
drop-off,
will
be
able
to
lend
my
local
purchase
experience
in
consuming
breaking
a
POS
and
pain
points
and
particular
payments,
otherwise
haven't
had
too
much
drama
in
integrating
the
booking.
Api
is
often
more
straightforward
and
availabilities
saying
just
once
that
catchy.
A
Okay,
so
any
any
other
questions
or
feedback
from
the
group
today,
yeah.
H
Bring
up
one
thing
about
data
quality,
so
it
would
be
fantastic
to
be
able
to
offer
booking
through
getting
active,
for
example,
but
that's
only
going
to
be
effective
if
the
dates
is
good
enough
to
be
useful.
I
notice,
a
mule
made
a
comment
on
that
earlier.
What
we're
finding
is
that
there's
a
whole
range
of
data,
some
of
its
useful
and
some
of
its
doesn't
really
say
much
about
the
session,
so
we're
starting
to
look
at
how
we
can
rate
data
as
per
its
usefulness
to
an
end
user.
A
Yes,
yeah,
absolutely
and
and
that's
some
of
the
discussion
that
wants
to
have
it.
The
next
call
I'm,
because
I'm
looking
at
is
in
terms
of
which
fields
each
providers
using
how
they're
actually
filling
them
in
so
that
we
can
start
to
tighten
up
the
kind
of
conformance
criteria,
because
what
we've
done
so
far
is
really
just
sort
of
to
remove
any
blockers
to
publishing
have
just
said.
A
A
Yes,
yeah
absolutely
yeah
yeah
and
one
of
the
reasons
I
want
to
so
we
can.
We
can.
We
could
just
build
a
validator
for
the
model
as
it
stands,
but
I
kind
of
want
to
take
stock
of
what
that.
What
the
variance
is
in
the
data
so
that
we
can
focus
on
the
things
that
we
need
people
to
improve,
so
that
might
be
making
sure
that
things
are
geo-located.
For
example,
there's
a
core
set
of
fields
that
would
allow
looking
to
be
done
on
the
third
party
platform.