1 of 18

OpenActive Community Group Hangout

​

Facilities, Booking API,

Data validation

​

2018-02-28

2 of 18

Agenda

  • Roadmap review
  • Facilities
  • Booking API progress update
  • Data validation
  • AOB
  • Next Calls

​

3 of 18

Facilities

updated proposal

4 of 18

Facility Availability use cases

  • What facilities are available at a location?
  • What activities can be carried out in this facility?
  • How do I find this specific squash court?
  • What dates and times can I book this squash court?
  • Is this squash court still available at a given time?

5 of 18

Facility requirements (updated)

  1. Publish data about opportunities to book facilities in an RDPE feed
  2. Describe the product being offered to user
    • associate the Product with activities
    • associate the Product with events (slots)
      • individual, or schedule
    • describe availability of an Event (slot)
  3. Check if an Event (slot) is still available

6 of 18

Facility requirements (updated)

  • BookableFacility (a schema:Product)
    • name, description, images, etc
    • activity -> the activities the facility supports
    • location -> Place
      • describes the facility, can be tagged (e.g. “indoor”)
    • offers -> Offer
      • the price, etc as normal
    • events -> Event
      • describes the slots and availability

7 of 18

Thoughts and comments?

  • Please provide comments on github
  • Plan to revise and publish draft of 1.1 specification by Friday to provide more technical detail

8 of 18

Booking API

progress update

9 of 18

Current Working Documents

​

10 of 18

Open issues

  • bookableItemId vs zero Offers
  • Shopping basket vs. collection of leases
  • Anonymous leases
  • Persistent “Order” vs transient “Reservation”

​

11 of 18

Data validation

​

improving data quality

use cases for tools

12 of 18

Data validation use cases

  • Does this RDPE feed conform to the specification?
  • Does this JSON data conform to the opportunity data model?
  • Does this JSON data include all recommended information from the opportunity model?
  • Is this feed and its contents valid?
  • Is this live feed still responding?

​

13 of 18

Defining what it means to be valid

  • The RPDE specification is fairly prescriptive, easy to define what is valid
  • The opportunity model is very flexible, which was intentional, but adds some potential overheads
    • less directive in advice to publishers
    • requires clients to be more flexible
  • Some items will always need to be optional, flexibility is important

​

14 of 18

Providing useful guidance

  • Validation tools should enforce the specification
    • Are all REQUIRED fields present?
    • Strong suggestion to add RECOMMENDED fields, with a clear reason
    • Highlight missing OPTIONAL fields
  • Validation tools should encourage consistency
    • Recommend specific use of JSON-LD syntax

​

15 of 18

Tasks

  • We need to review status of all fields in specification
    • REQUIRED, RECOMMENDED, OPTIONAL
    • Can check published data
    • Would like feedback from community
  • Provide specific guidance on:
    • location
    • activities
    • events and dates

​

16 of 18

AOB

​

Next meetings

17 of 18

Next Calls

  • 14th March
    • Booking API issues and implementation feedback
  • 28th March
    • Activity list

​

​

​

18 of 18

Please share our work

  • Who else should be attending these meetings?
  • Videos of our calls
  • OpenActive blog
  • @openactive

​

​