►
From YouTube: OpenActive W3C Community Group Meeting / 2019-04-10
Description
A public hangout for members of the OpenActive W3C Community Group.
https://w3c.openactive.io/meetings/2019-04-10-booking-workshop-followup
A
A
So
I
gotta
say
to
you
guys
and
to
anyone
else
watching
us.
Thank
you
so
much
for
persevering.
This
is
like
the
very
end
of
a
very
long
journey
and
I
think
we
all
just
want
this
done
now,
so
I'm
quite
happy
that
we're
nearly
there
and
that
nearly
there
has
a
timescale
on
it.
So
yeah
great.
So
one
of
the
things
that
came
up
in
this
booking
workshop
is
this:
both
open
data
and
open
booking
is
kind
of
needed
to
make
booking
happen.
A
So
you
need
to
have
the
open
data
feeds
you
need
to
have
loads
and
booking
working
the
finalization
workshop.
If
you
guys
you
guys
have.
Obviously
we
were
all
there.
Anyone
who
wasn't
you
can
go
back
and
watch
it
on
the
on
the
w3c
sub-site,
a
very
active
all
the
videos
are
up
so
just
to
kind
of
summarize
the
changes
we've
made
off
the
back
of
that
in
the
workshop,
those
that
were
there
will
remember,
Shawn
shouting
out
that
he
disagreed
with
the
wording
of
the
logical
steps.
A
This
was
previously
register,
so
we're
changing
this
to
be
identify
which
I
think
everyone
thought
was
reasonable
at
the
time
and
the
other
couple
changes
were
making
following
the
workshop,
our
free
text
restrictions.
So
basically,
this
means
that
you
can
now
you
can
specify
as
part
of
an
event
the
restrictions
that
are
related
to
it.
B
A
Then
the
bookings
back
references
that
it
must
be
displayed
as
part
of
the
process
and
then
the
attendee
instructions
which
are
already
there
in
the
bot
in
the
model,
as
you
say,
is
II.
That's
there's
just
a
note
in
the
booking
spec
that
they
should
be
included
as
part
of
a
confirmation,
email
that
gets
sent
out.
A
This
was
to
Chris
Phelps
his
point
that
actually,
in
some
situations
you
might
want
to
send
a
follow-up
note
to
the
the
customer
saying
you
know
you
know
there
are
lockers
available
or
you
know
there
is
whatever
that
information.
Is
that
there's
something
you
might
want
to
tell
them
about
the
venue
and
you
can
put
that
in
the
attendee
instructions
and
send
that
so
eternity
instructions
is
already
used
for
this
anyway.
A
So
think
people
can
write
exactly
this
kind
of
information
and
don't
forget
to
bring
your
trainers,
and
so
that
will
just
make
sure
that
they'll
get
the
information
it's
sent
to
them
and
then
finally
I'm
trying
to
arrange
a
conversation
about
reconciliation
following
our
previous
call
about
reconciliation,
I
think
a
couple
of
weeks
ago,
and
it
was
raised
as
well
at
the
booking
workshop
as
a
question.
So
we
still
don't
know
I
think
in
a
couple
weeks,
I
took
an
action
to
try
and
find
out
from
people
what
they
needed
in
terms
of
reconciliation
data.
A
We
said.
Maybe
an
idea
was
good
enough.
Maybe
we
need
some
more
information,
so
I've
pinged,
three
people
in
particular,
who
I
know,
have
strong
views
on
this
I'm,
going
to
try
and
get
information
out
of
them
next
week
and
build
that
into
the
spec.
As
far
as
I'm
aware,
that's
the
only
thing.
That's
not
yet
well
defined.
I
think
we've
talked
about
it
in
enough
detail
last
time
that
we've
got
a
way
forward
which
has
kind
of
allows
generic
reconciliation.
It
sounded
like
the
last
question
there
was.
A
Is
it
needed
I
think
that
was
the
last
call
we
had
before
the
booking
workshop?
We
kind
of
came
to
that
conclusion.
We've
got
our
mechanism,
it
looks
like
we're
happy
with
it.
Is
it
needed,
and
so
whether
that
reconciliation
mechanism
will
be
in
the
actual
final
spec
or
not,
will
depend
on
this
conversation
with
these
people
to
see
if
there's
a
way
we
can
get
around
in
their
use
cases
where
the
people
have
said.
This
is
what
we
need,
if
there's
an
alternative
that
doesn't
require
that
additional
property.
A
So,
if
that's
all
good
and
nothing
nothing
unexpected,
then
the
other
thing
I
thought
we
quickly
just
go
through
is
just
this.
The
way
that
bookings
happen,
probably
just
just
really
emphasize.
In
some
cases,
it
was
unclear
the
steps
that
you
would
take
to
make
a
booking
if
there
was
a
child
or
an
adult
involved,
and
there
was
conversations
about
date
of
birth
afterwards
and
whether
you'd
ask
for
date
of
birth
up
front.
A
We
should
have
probably
kept
it
in
and-
and
this
is
just
to
show
you
that
you
select
the
ticket
type
ie
the
offer
type
of
adult
before
you
confirm
the
opportunity,
and
what
this
means
is
that
there
are
two
things
you
need
before
you
start.
The
booking
flow
need
the
opportunity,
which
is
this
case.
It's
it's
Monday
first
of
April
badminton
that's
opportunity,
and
then
you
also
need
the
offer
and
that's
adult.
So
when
you
have
those
two
things,
then
you
proceed
to
booking
and
that
kind
of
advances,
people's
questions
about.
A
How
is
it
that
you
know
if
it's
a
child,
if
I,
don't
know
the
date
of
birth?
Well,
it's
because
you've
chosen
the
offer
of
the
junior
offer
and
so
Opportunity
Plus
offer.
Is
then
what
you're
booking
against
you
can't
book
an
opportunity
without
an
offer
you
have
to
have
both,
and
so
that's,
then,
how
you
get
to
the
page
we
did
show
on
the
day,
which
was
this
kind
of
final
booking
step.
You
do
have
to
choose
the
off
first
and
I.
Think
that
was
that's
an
important
step
that
we
missed.
A
That
logically,
then
means
that
we'll
ask
ratan,
know
and
opportunity
loss
opera's,
also
how
you
you
deal
with
on-peak
off
peak
because
again
the
opportunity.
This
is
an
example
of
Malkovich's
grid.
The
opportunity
changes
in
price,
depending
on
the
time,
as
you
can
see
here
what
I'm
talking
laughter
means
48
pounds.
7
o'clock
in
the
afternoon
is
60
pounds
and
that's
part
the
opportunity.
So
your
opportunity,
which
includes
on
peak
of
peak
combined
with
the
offer
which
is
at
all
junior,
that's
what
gives
you
there.
The
thing
you
can
bug
does
that
make
sense.
C
D
A
Excellent
great
thanks
guys.
So
then
the
next
little
thing
was
about
trust
in
control.
I
met.
You
got
a
slide
on
this,
but
just
to
explain
what
what
this
means
there
aren't
any
controls,
at
least
in
the
specification
that
allow
at
least
that
you
could
do
it,
but
there's
nothing
that
suggests
you
should
or
shouldn't
do
it.
That
meant
make
means
that
booking
system
should
apply
any
kind
of
control
to
what
the
broker
can
and
can't
do.
So.
A
Some
of
the
questions
that
we
had
following
the
workshop
with
things
like
in
in
Gladstone
or
in
legend,
how
do
I
make
it
so
that
that
broker
a
can
book,
X
and
broker
B
can
look
why,
but
not
the
other
way
around.
Well,
how
do
I
make
sure
that
yes,
I
broke
a?
Can
only
book,
off-peak
stuff
or
broke
a
be,
can
only
book
certain
types
activities,
maybe
broker
beacon
any
book,
Zumba
and,
and
maybe
only
maybe
broke
a
see,
can
use,
offer
overrides
that
may
be
broken.
A
You
can't
use
L
for
overrides,
and
this
kind
of
thing
so
the
way
that
the
kind
of
one
of
the
principles
of
respect
and
I
think
we've
talked
about
this
in
previous
calls,
but
just
kind
of
reiterate
it
is
a
bit
like
with
most
api's
you
can.
Access
to
you
can
do
a
lot
of
stuff
with
them.
Currently
a
lot
of
the
booking
api's
works
like
this
anyway,
when
you
get
access
to
booking,
you
can
make
bookings
across
all
things
using
all
of
the
you
know
everything
you
can
book
whatever
you
want.
Obviously,
what
controls?
A
What
you
book
is
the
contract,
the
agreement,
the
arrangement
that
the
broker
has
with
the
seller.
So
if
the
seller,
for
example,
GLL
has
an
arrangement
with,
for
example,
my
local
pitch-
that's
only
off-peak
bookings,
then
they
should
expect
my
local
pitch
to
only
make
off-peak
bookings
if
they
do
something
if
they
make
a
non
peak
booking.
That
would
be
against
their
agreement
and,
of
course,
they
have
the
power
to
terminate
that
agreement.
A
A
If
someone
changes
their
mind
and
all
those
kind
of
things
that'd
be
a
lot
of
administrative
overhead,
but
it
also
be
a
lot
of
complexity
in
the
system,
because
you
would
need
to
build
in
those
controls
against
each
of
the
brokers
and
the
administration
panels
would
be
crazy,
complicated.
So
the
costs
for
administration
and
the
cost
build
goes
up
a
lot
and
I.
Suppose
the
question
is
what
what
purpose
we
know.
A
There's
no
GDP
our
concerns
here,
it's
all
just
about
whether
they
do
what
they're
supposed
to
or
not
and
so
yeah,
so
just
to
say.
Currently
the
way
this
is
all
working
is
that
it's
about
trust
so
that
you
have
that
contract
in
place
and
that
contract
should
be
respected.
Obviously
that
within
the
system
they
can
look
at
what
bookings
were
made
running
a
report
of
whatever
booking
system
to
check
against
a
particular
broker.
What
they've
been
what
they've
been
booking
and
if
they
find
in
that
report
that
things
haven't
been
done
properly,
then?
A
Obviously,
it's
up
to
them
to
terminate
the
agreement.
Ask
for
the
money
back
whatever
it
is,
and-
and
this
is
where
obviously
you
go
into
business
with
people,
you
trust
and
and
if,
if
there
was
concerns
about
that
level
of
trust,
then
you
would
also
have
concerns
about.
You
know
whether
they
would
take
the
correct
payments
and
all
the
other
things
that
they
could
do
wrong,
whether
the
people
would
be
real.
Would
they
submit
correct
personal
data?
A
You
could
go
in
to
the
enth
degree
of
checking
this
stuff,
so
it
also
when
it
comes
down
to
making
sure
partners
are
accredited
and
and
trustworthy
and
that
sellers
only
work
with
those
partners
that
they're
happy
to
work
with,
and
obviously,
if
you
get
kind
of
a
black
mark
against
you,
it's
a
small
sector.
So
I
imagined
that
you,
wouldn't
it
wouldn't.
Do
you
too
well
to
try
and
circumvent
the
system?
A
There
was
a
big
kind
of
discussion
that
lasted
about
15
minutes
about
date
of
birth
and
things
like
that,
and
so
just
to
kind
of
show
you
what
what
we've
done
about
that
there's
a
github
issue
which
is
called
attendee,
detail
capture
this
kind
of
summarizes
what
was
discussed
in
the
in
the
room.
It's
three
main
points
that
basically
I
think
that
the
kind
of
requirements
seemed
to
be
around
safeguarding
reporting
and
registration,
which
basically
safeguarding
is
the
kids
allowed
to
go
to
the
activity
at
the
underage?
A
Is
there
a
danger
to
that
being
the
case
and
the
same
with
two
to
one
ratio?
You
know
if
there's
too
many
kids
for
an
adult,
are
they
allowed
through
reporting
people
were
saying
you
know
we
want
to
demonstrate
the
sport
England
that
we've
got
enough
people
active
who
are
they
and
looking
into
this
in
detail,
there's
all
kinds
of
questions.
People
are
asking
for
reporting
an
ethnicity,
religion,
all
sorts
of
stuff,
that
people
need
to
know
to
show
diversity.
A
You've
got
a
bit
of
a
bigger
list
here:
medical
conditions,
disabilities,
a
bunch
of
personal
questions,
they're
asking
to
try
and
understand
the
kind
of
people
who
are
coming
in
so
there's
a
question
about
reporting,
and
then
there
was
a
question.
My
registration-
and
this
is
things
like
the
next-of-kin
or
the
parents,
details
things
like
that,
and
so
these
are
the
main
three
reasons
that
we've
seen
to
boil
it
down
to
what
want
additional
information
and
a
few
people
after
the
workshop
said
well
wait.
A
Maybe
we
can
just
ask
for
days
as
an
additional
field
with
the
customer
and
actually
turned
out
to
be
problematic,
because
the
customer
is
actually
with
Booker,
not
the
attendee,
and
so
the
person
booking
might
be
the
parent.
The
attendee
might
be
the
child.
It's
the
attendees
information.
You
want
for
a
boarding,
the
attendees
information
you
want
for
safeguarding
and
the
attendee
that
you
want
in
terms
of
registration.
A
You
don't
need
the
book
of
details,
so
actually
what
we're
talking
about
capturing
attendee
detail,
which
is
a
lot
different
to
what
we
currently
have
in
the
spec,
which
is
only
booking
the
Booker
details,
and
so
basically,
what
this
comes
down
to
is
or
for
safeguarding
there's
two
options.
One
is
that
you
capture
a
date
of
birth,
of
each
attendee,
for
example,
to
make
sure
they're
a
right
age
and
two
is
what
we
were
talking
about
in
the
room.
A
Is
you
just
clear,
clearly
describe
each
opportunity
to
make
sure
it's
clear
what
the
constraint
restrictions
are.
So
if
the
restriction
is
age,
eight
to
ten
that
that
is
written
on
the
activity
itself,
so
you
can't
get
that
wrong
when
you,
when
you
book
it,
you
can't
accidentally
but
wrong
ticket,
and
so
at
the
moment
the
currents
tech
supports
the
description.
A
You
can
put
those
details
in
we're,
adding
that
free
text
restriction
to
allow
for
all
types
of
descriptions
of
restrictions
to
be
to
be
in
there,
but
it
doesn't
currently
allow
for
kind
of
a
check
based
constraint
is
the
date
of
birth
right
currently
can't
do
that
at
the
moment.
But
that's
what
you
would
need
to
do.
You
would
need
to
calculate
a
birth
and
check
it
against
what
you'd
expect
and
the
same
registration
reporting
there's
no
way
of
capturing
any
attempted
details
at
the
moment
in
the
spec.
A
So
you
would
need
to
capture
all
of
this
information
as
a
new
thing
and
you
would
need
to
do
it
per
order
item,
which
is
because
each
order
item
could
be
a
different
attendee.
So
you
could
book
with
two
friends
and
that
would
be
three
different
items
and
so
yeah,
if
you
booked
with
for
three
of
you,
that
would
be
three
items.
You
would
need
three
different
attendee
details.
A
So
do
we,
then
that
need
to
say
well,
you
know:
is
this
person
one
like
you,
do
with
cinema
tickets
and
drag
drag
and
drop
them
onto
your
ticket
to
say
that's
intended,
one,
that's
attendee,
two
and,
and
the
suggestion
here
is
for
the
simplicity.
Actually,
we
could
just
ask
you
for
the
information,
because
we're
just
storing
it
for
reporting
the
registration
purposes
if
it's
the
same
person
in
both
it's
a
guest
checkout.
Ultimately,
so
you
were
just
you
could
capture
this
information
both
they
could
just
as
easily
make
a
follow
up
booking
and
capture.
A
You
know,
let's
say
that
I
have
a
friend
and
is
he
as
a
friend
and
we
both
go
I
go
to
Zumba
with
this
friend
on
Monday
and
Izzy
goes
to
yoga
on
Tuesday
with
the
same
person.
Now
we
both
would
enter
their
attendee
details
on
from
both
of
our
respective
booking,
but
obviously
it's
Booker's
we're
different
and
any
account
stuff
is
totally
different,
so
that
person
isn't
really
the
same
person
as
far
as
there's
nothing
to
really
connect
them
together.
A
That
said,
you
know,
I
want
to
book
me
and
my
friend
on
I,
don't
really
want
to
ask,
but
their
date
of
birth,
an
email
address,
I
just
want
to
book
my
friend
on,
because
and
if
I
have
to
ask
them
for
all
this
information.
That's
a
barrier
I!
Don't
really
want
to
go
through
that,
if
I
don't
know
their
exact
date
of
birth,
for
example,
or
I'm,
a
parent
looking
for
my
child
and
my
my
child's
friend
two
children
do
I
know
my
child's
friends
dates
at
birth.
A
So
why
do
I
need
the
date
of
birth,
but
I
know
they're
definitely
over
8,
because
they're,
both
11,
I
just
don't-
know
exactly
hold
the
eleven-year-old
is
so
it's
you
know
it's
these
kind
of
things
so
yeah
and
then
GDP
are
basically
says
that
we
want
to
minimize
the
amount
of
data
captured
by
default
if,
unless
it's
absolutely
necessary
and
there's
a
good
question
about,
is
reporting
necessary.
Is
that
good
enough
reason
to
catch
all
this
additional
data
from
people
and
their
friends?
A
Maybe
they
are
so
all
of
that
being
said,
the
suggested
flow
is
basically
to
kind
of
jump
straight
to
the
model.
Is
we
treat
attendees
as
repeat
repeat,
attendees
as
different
people?
So
we
don't
try
anything
clever
about
you
know.
Alex
is
booking
onto
two
things:
it's
the
same
person,
just
duplicate
that
information
and-
and
you
can
still
apply
automatic
constraints
to
that,
because
you
can
check
you've
got
a
child
order
from
particular
order
item
you
can
check
the
date
of
birth.
Put
against
that
order.
A
Item
is
a
child
date
of
birth
and
fits
within
that
constraint
same
with
you
booked
a
female
ticket
for
something
you
can
check
the
female.
They
are
female
and
they
booked.
So
you
can,
you
can
add
those
two
constraints
easily
enough.
Other
constraints
are
more
difficult
to
do
around
things
like
ethnicity,
but
you
probably
wouldn't
want
to
do
that.
So
this
is
where,
at
the
moment,
it's
those
two,
the
main
things
people
seem
to
be
saying
are:
the
constraints
is
gender
and
date
of
birth
and
the
way
it
would
work
is
that
you
would.
A
You
would
have
a
when
the
order
item
is
returned.
When
you
do
the
initial
quote,
it
gives
you
back.
It
says
these
are
the
required
fields,
I
need
for
each
attendee,
I
need
email,
address,
I,
need
name
an
agenda
and
also
specifies
custom
fields
in
the
form
of
books.
That's
order,
item
intake
form,
so
you've
got
short
answer.
Multiple
choice,
answers
I
mean
arguably
a
multiple
choice.
Question
to
get
the
age
is
much
better
than
the
date
of
birth.
A
Asking
buckets
of
not
to
18
18
to
30
will
hit
your
reporting
requirements
without
needing
to
capture
that
really
specific
personal
data
of
date
of
birth.
So
you
could
ask
a
multiple
choice.
Question
like
that
you
can
choose
whether
it's
required
or
not
required,
and
then
that
information
is
then
captured
and
if-
and
the
other
thing
is
at
the
quote
stage,
if
you,
if
you
get,
you
can
get
an
error
message
saying
that
you
don't
have
complete
data,
it
basically
just
asks
you
to
keep
resubmitting
the
quote.
A
Until
you
have
all
the
data,
at
which
point
you
won't
have
any
errors
coming
back
and
then
you
can
go
forward
and
submit
the
final
order,
and
this
is
an
example
of
the
kind
of
thing
you
would
submit.
You
submit
your
attendee
one
per
order
item.
As
we
said
it
would
just
be
duplicated
if
that
same
person,
booked
or
lots
of
things,
so
you've
got
email
address
number
all
that
registration
detail.
A
If
you
need
it
date
of
birth,
gender
address
so
they're
all
the
standard
fields
that
seem
to
be
what
most
people
are
using
a
standard
fields.
If
you
wanted
to
add
additional
fields
as
we
venture,
if
you
want
to
capture
religion
because
that's
something
they
need
to
enter
as
a
required
field
to
book
onto
the
squash
court.
Apparently
this
is
actually
happening
in
some
places.
A
So
if
you
need
to
do
that,
then
you
can
you
can
do
that.
You
can
have
a
custom
field
and
you
can
you
can
even
put
a
multiple-choice
drop
down
with
a
list
of
religions
that
you
recognize
and
they
can
they
can
choose
from
there,
and
this
specifies
that
so
obviously,
my
I
think
my
personal
view
here
is
that
this
is
very
excessive
for
allowing
someone
to
access
certain
facility.
However,
because
people
in
India
have
requested
this
and
we're
very
keen
to
make
sure
this
works,
and
hopefully
as
a
as
advice
as
possible.
A
That
we
would
leave,
leave
this
for
now
and
put
this
in
a
kind
of
version
1.1
or
later
version,
but
but
leave
it
as
an
open
issue
that
people
can
kind
of
contribute
to
as
they
look
at
the
spec
and
go
well.
This
doesn't
meet
my
needs
if
it's.
For
this
reason,
they
can
contribute
to
this
and
check
it
and
see
if
this
is
what
they're
looking
for
before
we
kind
of
bake
this
into
the
spec
in
case
it's
too
complicated.
Maybe
this
is
maybe
this
does
too
much.
A
Maybe
there's
a
half
way
version,
although
from
the
sound
of
things
people
needing
ethnicity,
things
like
that
require
you
to
have
custom
fields,
and
so
it
sounds
like
we
can
get
away
with
just
the
registration
information,
because
often,
if
you're
asking
for
date
of
birth,
you're
asking
for
it
for
a
lot
of
other
reasons,
so
yeah
and
oh
yeah
and
there's
IDs
associated.
So
if
you
do
have
religion
or
age
or
something
stored,
you
can.
You
can
use
an
ID
to
make
sure
that
let's
say
that
you're
storing
a
particular
attribute
about
person.
A
Let's
say
that
the
home
phone
number
because
you've
got
their
mobile,
but
you
also
need
the
home
phone
number
you
could
you
could
use
an
ID
for
home
for
the
number
there,
and
that
means
that
you
ever
ask
for
information
again.
The
broker
could
remember
that
and
resupply
a
second
time
and
if
it
wants
to
save
you
trying
to
fill
it
in
so
obviously
the
broker
then
has
the
ability
to
remove
these
barriers
as
much
as
possible
if
they
are
being
presented
by
the
provider
for
legitimate
reasons,
the
broker
can
then
use
the
standard
fields.
A
It's
aware
of
here
to
try
and
prefilled
address
and
date
of
birth,
they're
known,
they
might
already
be
known.
The
brokers
captured
that
before
and
remember
the
multiple
choice,
answers
for
the
second
and
third
time
they're
entered,
so
they
don't
need
to
go
through
the
whole
journey
again,
if
they're
repeat
Booker's
for
some
reason.
So
that's
that's.
B
Yeah
definitely
some
thoughts
from
me,
so
I
think
I
would
definitely
support.
Moving
this
to
a
later
version
and
I
think
from
mine
and
Allison
Savitch
is
going
to
be
kind
of
led
on
open
active
before
I
was
here,
and
we
kind
of
had
a
chat
about
this
and
I
completely
agree.
I
think
this
is
where
actually
someone
booking
something
doesn't
actually
mean.
They
turned
up
also
so
I
wouldn't
even
say
that
it
works
for
reporting
in
some
ways,
yeah
and
obviously
is
supporting
them.
B
Supporting
them
wants
us
to
report
on
this
I'm
I'm,
more
than
happy
for
you
to
put
them
in
touch
with
me,
and
we
can
figure
out
where
that
pressure
is
coming
from
as
well
to
make
sure
that,
where
I
joined
out
that
there
are
people
within
supporting
them
to
you
on
participation
data-
and
you
know
that's
what
we
all
want
I
guess
the
end
of
the
day
to
prove
that
any
of
this
is
happening
and
working,
but
yeah
I,
just
think
there's
different
places.
We
can.
B
A
A
Please
do
comment
and
we'll
watch
and
as
it
develops
that
discussion,
I
I
sense
that,
especially
as
the
saying
is
you
there
that
there's
probably
a
lot
more
to
this,
then
then,
maybe
that
workshop
even
surface
on
the
motivations
here
around
systems
that
operate
in
a
certain
way,
because
they
have
previously
always
operated
that
certain
way
or
things
being
captured
because
they've
always
been
captured
and
so
I
guess.
This
is
a
really
good
opportunity
for
a
bunch
of
challenging
and
check
the
current
status
quo
and
see
if
that
still
what
we
need.
A
Maybe
it
is
yes,
that's
yeah
great
brocro,
so
so
cool
okay.
So
that's
what
that
is,
and
then
just
to
kind
of
point
us
out
again
briefly.
So
this
is
the
the
the
minimum
required
I
think
sure
I've
kind
of
early,
but
there's
a
few
end
points
that
you
need
to
implement,
and
that
is
one
two
three
four
end
points
we
need
to
implement.
A
It
all
makes
sense
nothing
massive
like
it
all
fits
within
everything.
We've
read
and
talked
about
in
detail.
It's
just
going
to
really
circle
semantics
and
making
sure
the
naming
zorkin
system
and
plurals
and
singular
terms
and
what's
kind
of
detailed
stuff
that
I'm
good
to
get
right
an
hour
at
the
point
where
you
can
look
at
that
because
before
we
were
at
the
point
where
some
of
this
stuff
was
going
to
be
cut
completely
or
changed,
so
luckily
a
detailed
stage.
So
yes,
so
these
are
the
kind
of
different
end
points
required.
A
We
try
to
keep
this
as
small
as
possible.
So
there's
you
know
as
few
as
possible
end
point
center
and
the
implementation
can
be
as
simple
as
possible,
but
a
sure
points
that
before
it
still-
and
these
are
small
but
mighty
end
points-
sometimes
they
require
a
few
different
things
now
behind-the-scenes
to
do
that,
depending
on
the
complexity
of
the
booking
system.
So
it's
not
to
say
that
they're
very
simple.
Sometimes
they
are
slightly
complicated
because
of
the
number
of
business
rules
in
place
in
the
booking
system,
but
hopefully
in
simple
booking
systems.
A
They
should
be
fairly
simple
to
implement
because
the
complexity
really
arises
with
the
translation
of
what
could
be
a
simple
request
of
placing
an
order
through
the
amount
of
business
logic
that
my
existing
system
and
mapping
it
to
the
internal
representation
of
that
in
the
system,
and
so
just
yeah.
It
was
worth
just
re
restating
these.
These
are
the
kind
of
this
is
the
minimum
and
then
there's
the
optional
that
you
can.
A
D
Not
really
I
think
it
makes
sense.
As
you
said,
this
is
quite
a
lot
of
work.
I
was
kind
of
hoping
that
cancellation
probably
would
be
in
phase
two,
but
there
so
we'll
have
to
do
it
because
I
think
cancellation
part
is
probably
1/4
of
the
work
for
us,
at
least
in
this
whole
thing,
so
yeah
we'll
go
through
it
and
we'll
dress
concerns
as
we
find.
A
Them
fantastic,
thank
you
and
it's
probably
worth
saying
yeah
we
were
hoping
to
do
it
without
cancellation
as
well.
I
think
it
was
gol
Circle
and
a
few
others,
and
everyone
acted.
Who
said
that
cancellation
was
crucial
for
them,
so
that's
mainly
because
they
get
a
lot
of
cancellations
apparently
and
they
didn't
want
to
handle
them
manually.
A
Yeah
great,
so
the
next
steps,
then
on
the
booking,
spec
we.
Finally,
so
the
idea
is
on
Wednesday
next
week,
which
is
delayed.
This
was
supposed
to
be
Friday
this
week,
but
we've
we
need
a
little
bit
more
time
to
finish
all
these
bits
off
so
Wednesday
next
week,
which
still
allows
us
to
hit
the
end
of
the
month
deadline
for
the
ratification,
which
is
now
moving
from
the
27th
of
April
to
the
1st
of
May,
and
so
that's
about
that
date
there.
A
A
The
idea
is
that
we
will
have
this
final
tweaks
done
and
submitted
on
the
17th
I'll,
give
it
to
weekly
a
window
for
anyone
who
has
any
objections
to
raise
them
as
part
of
the
formal
process
and
assuming
that
there's
none
then
we'll
have
the
spec
we
ratified
on
the
1st
of
May,
which
is
great,
and
then
we
can
do
something
else
that
isn't
booking,
which
will
be
amazing
for
everybody.
Who's
been
part
of
this.
A
For
so
long,
so
current
conversations
are
maybe
we
should
bring
up
roots
and
talk
about
that
on
the
24th
of
April.
So
that's
what's
penciled
in
at
the
moment
as
the
next
topic.
If
we
can
remember
what
it
was
like
before
we
looking,
there
was
a
time
before
working
and
I
think
there
will
be
a
time
after
as
well.
D
A
A
great
question:
yes,
we
are
absolutely
intending
to
build
one.
The
question
is
timescales
at
that
and
how
quickly
we
can
do
that
compared
to
your
bill
and
we'll
see
if
we
can
do
that
in
parallel.
So
so,
actually
your
neck
on
the
next
call
Tim
will
be
joining
us
and
Tim
is
joining
the
area.
My
team,
too,
to
help
with
this-
not
just
this
but
to
take
on
this
work
stream
of
the
standards
as
part
of
an
active
initiative
within
the
ODI
and
so
he'll
be
looking
at
that.
A
D
It's
basically
more
stood
on
the
object
metadata,
just
like
you
have,
let's
say,
God,
but
something
like
person
definition
of
person
in
currently
in
the
spec
for
for
the
feet
over
there
on
your
website.
So
similarly,
less
therefore
order
you
got
a
validator,
so
we
whatever
we
develop,
we
just
your
Python,
not
it
passed
through
that
thing
and
and
then
just
get
the
feedback
brilliant.
D
A
Former
third
set,
so
this
is
this-
is
easy.
Actually
we
can
read
this
validates,
who
has
actually
built
based
on
a
data
model
that
is
configurable,
so
we
can.
We
can
very
quickly
get
the
the
new
data
model
from
the
new
spec
into
this
validation,
so
it
works
with
the
order
order
items
those
things
so
we'll
do
that
as
step
one.
Is
that
something
that
is
that
enough?
Do
you
think,
would
you
need
more
than
that
or.
D
I
think
that
would
be
enough.
Actually,
if,
in
your
samples,
you've
got
the
minimum
list
of
properties
with
every
object
at
at
least
the
minimum,
then
we
can
simply
copy
and
paste.
You
know
work
projects
and
start
playing
with
them
and
see
what
we
are
missing.
So
it
will
actually
be
helpful
because
sometimes
I
think
in
the
samples
you've
got
more
than
minimum.
Yes,
so
if
you
start
with
the
minimum,
because
there
is
quite
a
lot
over
there,
I
was
looking
at
here.
A
Sounds
perfect
here
absolutely
it
should
say
that
some
of
the
minimum,
its
minimum
is
sometimes
case
dependent.
So,
for
example,
I
know
that
legends
were
really
concerned
with
tax
tax
is
optional,
because
tax
is
not
in
every
system
and
xn.
Don't
have
the
legend.
Do
so
I
mean
you
would
you
would
you
like
to
us
to
include
things
like
Max
in
man?
Oh.
A
D
I
think
tax
on
tag
on
the
subject
of
tax.
We
currently
got
one
price
which
include
tax.
So,
if
you
got
an
organization
which
is
tax-exempt
like
a
like,
a
person
wants
a
organization
that
want
to
make
a
booking.
Do
we
need
to
identify
and
legend
and
give
then
price
that
ring
back
doesn't
include
tax.
Is
that
what
is
your
expectation.
A
A
So
you
would
need
to
include
let's
go
to
an
example
mentioned
the
creation,
so
the
order
quote
comes
back.
The
order
quote
would
include
so
there's
a
unit
tax
specification
which
basically
says
how
much
of
each
price
is
tax
and
if
it's
tax
exempt,
this
could
just
be
not
included
because
there's
no
tax
or
it
could
be
zero.
It's
up
to
you.
D
Needed
I
mean
detect
who's
asking
for
the
court,
because
I
thought
it's
part
of
it
is
anonymous
like
anybody
can
go
and
ask
for
a
coat
at
that
time.
Ii
don't
know
who
that
person
is,
and
even
after
he's
registered
I
mean,
as
you
said,
the
minimum
you
need
to
create
a
account
in
booking
systems,
just
email
address
and
couple
of
other
fields.
So
it
doesn't
mean
that
we
need
some
extra
information
with
every
account
holder
that
tell
us
whether
he's
exempt
or
not.
Well,.
A
So
he's
exempt,
if
he's
a
person
and
not,
if
he's
an
organization,
so
when
the
when
the
seller
and
so
away
that
when
that
where's,
the
customer
should
the
Indian
its
previous
in
the
customer.
If
the
customer
is
a
type
person,
then
he
is
exempt
from
tax
if
the
activity
qualifies
for
it,
because
not
all
your
activities
qualify
for
tax
exemption
and
not
all
organizations
do
so.
Some
Legend
customers
will
not
have
tax
exemption.
Some
legend
custom
as
well
I.
A
A
D
A
D
A
Sounds
kids
well
great,
thank
you
very
much.
So
we
will
make
that
validator
happen.
Show
that
that
sounds
like
a
thing
we
can.
We
can
definitely
do
so
we'll
make
sure
we
release
that
as
soon
as
we
carry
out
the
spec
and
let
everyone
know
Tom
scales,
and
that
will
be
good
because
I
thought
you
were
innocent,
we
need
more
validation
stuff.
But
if
that's
enough
then
perfect,
we
will
do
that
minimum.
B
I
had
just
a
quick
question
about
moving
onto
routes
next,
which
you
know
I,
think
we're
all
excited
to
do
non-working
stuff
as
much
as
I
love
talking
about
booking
I.
Just
wonder
whether
and
open
to
other
people's
input,
obviously
in
this,
but
whether
it's
worth
going
back
to
the
accessibility
stuff
for
a
bit
or
not
or
whether
we
kind
of
start
with
my
roots
and
then
go
back
to
accessibility
or
how
we
handle
the.
Maybe
it's
a
question
or
so
for
him
once
he
started,
but
just
wanted
to
flag
it.
Now
as
a
thing.
A
B
Had
many
comments,
I
think
that
which
I
you
know
send
outs
people,
but
not
everyone
really
commented
on
it,
so
yeah
I
mean
maybe
you
and
I
can
catch
up
separately
on
this
and
just
think
about
I.
Just
wonder
whether
having
a
call
is
kind
of
a
focus
point
to
like
bring
everyone
back
onto
that.
Maybe
it
only
needs
to
be
one
that
then
we
move
on
to
roots
for
a
bit
and
just
kind
of
have
a
regular
check-in
point
on
the
accessibility
stuff
as
a
good
thing.
B
A
B
Of
the
answer,
I
think
I
sort
of
said:
yeah
I
can
do
that
and
then
was
like
what
do
I
actually
need
to
do
you
and
I
you
and
I
can
pick
it
up,
maybe
separately,
and
then
we
can
figure
out
if
it
makes
sense
and
again,
I
didn't
have
to
be
that
24th
of
April
cool
could
be.
You
know
a
few
weeks
after
that
that
we
pick
it
up
as
a
as
a
kind
of
little
special
special
call
or
something
but
yeah.
We
can
figure
it
out.
Okay,.
A
Yeah,
that
sounds
great.
Let's
definitely
do
that.
Yeah
Jim
will
be
picking
this
stuff
up,
but
we
want
to
make
sure
that
we
don't
dump
in
with
a
load
of
stuff
from
day
one.
So
if
it
it
might
be
a
nice
transition
to
have
the
accessibility
calls
and
ice
in,
but
let's
still
be
perfect.
Thank
you
cool,
no
problem
at
all
great
and
well.
A
Thank
you
guys
so
much
for
coming
and
thank
you
for
anyone
who's
watching
that
you've
made
it
through
to
the
end
of
the
ends
of
the
booking
stuff,
because,
oh
my
goodness,
this
is
taken
a
long
time.
But
thank
you
I'm
thinking
you
guys
here
for
for
supporting
this
and
so
so
yeah
with
any
luck,
I'm
crossing
my
fingers,
we'll
be
able
to
next
time.
We
talked
well
have
the
bookings
back
in
the
form
that
everyone's
happy
with
and
it's
it's
out,
and
it's
done
so
yeah
great.
It's
been
a
journey.