OpenActive W3C Community Group
Developer ReferenceData ValidatorDataset Dashboard
  • W3C Community
  • Join the group
  • Upcoming Meetings
  • Key Discussions
  • Community Group Meetings (2021-24)
    • 2025-02-19 Specification Development Plan
    • 2024-10-23 - Routes Update
    • 2024-05-22 W3C/AEF Show & Tell - Stabilising and improving OpenActive's infrastructure
    • March and April 2024 meetings cancelled
    • 2024-02-21 Phase 5 Extension and Club Data
    • 2023-10-18 OpenActive and Open Referral UK
    • 2023-06-21 Approaches to maintaining the OpenActive tech infrastructure
    • 2023-05-24 Data Quality Explorer Demo
    • 2023-04-26 Data Quality, Activities and Priorities
    • 2023-03-29 Facilities and Activities
    • 2023-03-01 Data Quality Update
    • 2023-02-15 Active Places
    • 2023-01-18 Focus for year ahead
    • 2022-12-07 Data Quality Reporting
    • 2022-11-09 Reporting Data Quality
    • 2022-10-26 High Frequency Sessions
    • 2022-10-12 Data Quality in OpenActive
    • 2022-09-14 - Ways of working
    • 2022-06-08 - Accessibility
    • 2022-04-20 - LGBT+ Inclusion
    • 2022-03-02 - Safeguarding Requirements
    • 2022-02-02 - Block Bookings
    • 2021-12-06 - Social Prescribing Attributes, Places, and Block Bookings
    • 2021-11-24 - Dependent Accounts
    • 2021-11-10 - Access Pass Requirements
    • 2021-10-27 - Terminology in the Membership Proposal
    • 2021-10-13 - Membership Proposal Review
    • 2021-09-29 - Requirements for the Membership Proposal
    • 2021-07-14 - Phase 4 Technical Communication Channels
    • 2021-06-30 - Phase 3 Summary
    • 2021-06-02 - Facility Types, pt. 2
    • 2021-05-26 - Facility Types
    • 2021-04-07 - Updates to the Opportunity specification
  • 2021-01-13 - Dataset Site Specification
  • Meetings - Technical Working Group
    • 2022-07-07 - Final Review and Signoff
    • 2022-06-23 Spec Finalisation Scheduling
    • 2022-06-09 - Preliminary Review, pt. 2
    • 2022-05-26 - Preliminary Review, pt. 1
    • 2022-01-27 - Worked examples of dependent account handling
    • 2022-01-20 - Dependent Accounts, Updating Personal Data, and Late Cancellation Policies
    • 2022-01-13 - Facility Booking, Customer Age, Sections 9 & 10, Appendices D & G
    • 2022-01-06 - Sections 7 & 8, Appendices E & F
    • 2021-12-09 - Appendices C6, C7, C9, D3, D4, continued
    • 2021-12-02 - Appendices C6, C7, C9, D3, D4, D5; Sections 5 & 6
    • 2021-11-25 - Modelling Dependent Accounts
    • 2021-11-18 - Modelling Customer Accounts and Customers
    • 2021-11-11 - Terminology; Sections 1 & 2; Appendices A&B
    • 2021-11-04 - Terminology
  • Meetings Archive
    • 2020-11-18 - Accessibility Specification
    • 2020-11-04 - Documentation Review
    • 2020-10-07 - Schedules
    • 2020-09-23 - 1:1 Coaching Sessions
    • 2020-09-09 - The Dataset Site Specification cont..
    • 2020-08-26 - Dataset Site Specification (cont.)
    • 2020-07-15 - Dataset Site Specification
    • 2020-07-01 - Opportunity API
    • 2020-06-17 - Improving the RPDE specification
    • 2020-06-03 - Modelling Facilities
    • 2020-05-06 - Revisiting Accessibility
    • 2020-04-22 - Safeguarding
    • 2020-04-08 - Wrapping Up Virtual Events
    • 2020-03-25 - Virtual Events and other COVID-19 proposals
    • 2020-03-11 - Customer authentication continued
    • 2020-02-12 - Opportunity Specification Proposals
    • 2020-01-29 - Customer Authentication continued
    • 2019-12-04 - Safeguarding and HTML support
    • 2019-11-20 - Customer Authentication
    • 2019-11-06 - Finalising the Routes Specification
    • 2019-09-25 - References vs Objects
      • 2019-10-09 - Difficulty Level and Prerequisites
    • 2019-09-11 - Safeguarding and the Opportunity Specification
    • 2019-08-14 - Routes versioning and data publication
    • 2019-07-31 - Routes Initial Implementation
    • 2019-07-17 - Routes Workshop Follow-up
    • 2019-07-03 - Routes Workshop Preparation
    • 2019-06-19 - Modelling Opportunities: Difficulty Level/Prerequisites
    • 2019-06-05 - Modelling Opportunities: Difficulty Level
    • 2019-05-22 - Routes Data Exploration
    • 2019-05-08 - Routes and Accessibility Planning
    • 2019-04-10 - Booking: Workshop followup
    • 2019-04-02 - Booking Finalisation Workshop
    • 2019-03-27 - Booking: Overview and feedback
    • 2019-03-13 - Booking: Overview and feedback
    • 2019-02-27 - Booking: Overview and direction check
    • 2019-02-13 - Booking: Cancellations and Refunds
    • 2019-01-30 - Booking: Cancellations and Refunds
    • 2019-01-16 - Booking: Walkthrough
    • 2018-12-05 - Booking: Tax
    • 2018-11-21 - Booking: Tax
    • 2018-11-16 - Activity List Tool
    • 2018-11-07 - Booking Feedback
    • 2018-10-24 - Accessibility requirements
    • 2018-10-10 - Booking API Update and Feedback
    • 2018-09-12 - Booking API 1.0
    • 2018-08-30 - Modelling Event Types
    • 2018-08-15 - Booking
    • 2018-08-01 - Routes, Model V2
    • 2018-07-18 - Validator
    • 2018-07-04 - Roadmap
    • 2018-06-20 - Facilities
    • 2018-06-06 - Facilities
    • 2018-04-25 - Opportunity Model, Booking
    • 2018-04-11 - Virtual Events, Booking, Governance
    • 2018-03-28 - GetTheData, ageRange, genderRestriction, amenities
    • 2018-03-14 - "Amenity Use", Booking, RDPE 1.1
    • 2018-02-28 - Facilities, Booking, Validation
    • 2018-02-14 - Booking
    • 2018-01-31 - Booking
    • 2018-01-17 - Facilities
    • 2017-12-13 - Booking
    • 2017-11-29 - Activity List
    • 2017-11-15 - Audit of Published Data
    • 2017-11-02 - Data Usability
    • 2017-06-21 - Activity List
    • 2017-05-24 - Modelling Events
    • 2017-05-10 - Accessibility, Activity List
    • 2017-04-26 - Event attendance, Booking
    • 2017-04-12 - Modelling Events, Activities
    • 2017-03-29 - Modelling Events, Activities
    • 2017-03-13 - Modelling Events, Activities
    • 2017-02-22 - Modelling Events, Activities
    • 2017-01-25 - Initial draft model
    • 2016-12-07 - Introductions
Powered by GitBook
On this page
  • Summary
  • Slides
  • Video
  1. Meetings Archive

2019-03-13 - Booking: Overview and feedback

Previous2019-03-27 - Booking: Overview and feedbackNext2019-02-27 - Booking: Overview and direction check

Last updated 6 years ago

Summary

We ran through the in more detail, including checking the direction taken on issues raised since the previous call. Everyone was broadly happy, with notable points raised which did not require updates to the spec:

  • MLP emphasising for the importance of flexibility of payment provider, including decoupling of payment method from reconciliation.

  • After a discussion on the value of having telephone number as a required field it was concluded that it would be best for this not be required at the API level, and for any such constraints to be applied on a contract level if required for specific scenarios.

  • The usefulness of Offer overrides for flexibility of business models.

  • The spec covers cancellations and refunds before the event has occurred, however it does not explicitly cover cancellations after the event has occurred (e.g. partial refunds are useful if for example floodlights shut out halfway through the event). These can be completed out-of-band, as they were considered an edge-case for this version of the specification.

As a result of the call we:

  • Have left the open for comment to seek wider feedback.

  • Clarified the cancellation of events after they have occurred in the specification.

Additionally Izy requested feedback following the .

Slides

Video

booking specification
version issue
her work
last accessibility call