# W3C Community

## About the group

#### The OpenActive community are working together to improve how systems in the sport and physical activity ecosystem connect. <a href="#the-open-data-institute-and-the-openactive-community-are-working-together-to-improve-how-systems-in" id="the-open-data-institute-and-the-openactive-community-are-working-together-to-improve-how-systems-in"></a>

This discussion takes place in our [W3C Community Group](https://www.w3.org/community/openactive/), where we are developing the standards for opportunity data that will make it easier to publish, find and use. We are at the start of a long term change in the physical activity sector and work in this area is evolving. We welcome you to contribute and join the open conversation by joining our W3C Community Group.

> A W3C Community Group is an open forum, without fees, where Web developers and other stakeholders develop specifications, hold discussions, develop test suites, and connect with W3C’s international community of Web experts.

## How to join the group&#x20;

[**First click here**](https://www.w3.org/community/openactive/), then click "**JOIN OR LEAVE THIS GROUP**" halfway down the right hand side of the page.

Once you have done this be sure to attend our meetings and engage in our GitHub discussions:

{% content-ref url="/pages/-LJnKdNcgg9ZTYagmOvt" %}
[Upcoming Meetings](/meeting-calendar)
{% endcontent-ref %}

{% content-ref url="/pages/-LJVxstD4myS1bin8J8D" %}
[Key Discussions](/key-discussions)
{% endcontent-ref %}

## Our focus

Following conversations with a variety of sport and physical activity organisations, the ODI is currently recommending that the OpenActive W3C Community Group focuses on developing and refining standards for the following three aspects of opportunity data:

**Publishing** — the way that booking systems and websites can allow data about opportunities to be easily found on the internet in a consistent format that computers understand. A specification is currently in development for this area; to become an early adopter please click here.

**Activities** — the language used to label the different types of physical activities that are available with a short description of what they involve.

**Content fields** — specific details about the sessions including location, date and time, difficulty level, age range and cost.

Please join the W3C Community Group to join the discussion.

## Should I join the W3C community?

Please consider joining the W3C Community Group, whether you build technology in the physical activity sector, have a general interest in it, or have non-technical thoughts on how activities should be described (e.g. categorising activities, or defining what information should be provided to consumers about an activity).

Your contributions will help shape the future of technology that will be used by everyone. Note that the W3C Community Group is part of OpenActive - if you haven’t already please also join OpenActive by contacting us via the “join us” section of this site.

## What are standards and why do we need them?

Having data standards in place for physical activity opportunity data means that it can be used by developers and innovators to create new products and services that help get people active.

This just isn’t possible when opportunity data is described in different ways using different formats, for example, different providers might call a “location” a “meeting point”, or might refer to “football” or “soccer”. Once these descriptors have been standardised, and data is openly published, information across the sector can be compared and categorised, making it much more accessible and valuable to developers, and ultimately consumers.<br>


# Upcoming Meetings

## Meeting Calendar

All OpenActive events are publicly accessible via the [OpenActive Google Calendar](https://calendar.google.com/calendar/embed?src=openactive.io_645khi45bjhce06osqdls9u900%40group.calendar.google.com\&ctz=Europe%2FLondon).

## **Meetings Dial-in Details**

Join from PC, Mac, Linux, iOS or Android:

<https://zoom.us/j/3906833882>

Meeting ID: 3906833882

Or Telephone: Dial:

* +44 (0) 20 3051 2874 Meeting ID: 3906833882
* +44 (0) 20 3695 0088 Meeting ID: 3906833882<br>


# Key Discussions

## Discussions happen in the open

Our community documents all discussions on GitHub. Even if there's a conversation in person or on Slack, we post a summary on the GitHub issue tracker, and give the rest of the community time to respond before finalising the decision.

{% embed url="<https://opensource.com/open-organization/17/2/tracking-issues-publicly>" %}

## GitHub repositories worth watching

If you join GitHub, you can "Watch" the conversations happening in the following repositories:

* [Modelling Specification](https://github.com/openactive/modelling-opportunity-data/issues)
* [Open Booking API](https://github.com/openactive/open-booking-api/issues)
* [Data Model Validator](https://github.com/openactive/data-model-validator/issues)
* [Opportunity API](https://github.com/openactive/opportunity-api/issues)
* [Activity List](https://github.com/openactive/activity-list/issues)
* [Paging Specification](https://github.com/openactive/realtime-paged-data-exchange/issues)

You can easily keep track of these conversations following the #w3c-cg channel on [Slack](https://www.openactive.io/public-openactive-w3c/) or Gitter.

## Access to Slack

You can find out how to join our Slack channel at the link below:

{% embed url="<https://openactive.io/public-chat/>" %}


# 2025-02-19 Specification Development Plan

### Summary <a href="#summary" id="summary"></a>

We invite comments on the proposed priorities to end of June 2025:

* Interoperability with Open Referral UK to support social prescribing.
* Explore decoupling the OpenActive and OpenBooking specifications.&#x20;
* Evaluate requirements for improved OpenActive specifications / guidance / tools for describing routes, accessibility and safeguarding

Discussion then moves on to:

* Porism's earlier work mapping OpenActive to Open Referral UK formats.&#x20;
* London Sport's experience creating an ORUK feed from OA data.
* Supporting clubfinder capabilities for National Governing Bodies.

### Slides

{% embed url="<https://docs.google.com/presentation/d/1j9ShLSqphw7U8e3DJGihFE7ybuRaHaZOonWkHYGMGvU/edit?usp=sharing>" %}

### Video

{% embed url="<https://youtu.be/R1nIfpacnhk>" %}


# 2024-10-23 - Routes Update

## Summary

We had an interesting discussion on the state of play of the specifications and various initiatives around sharing route information.

Startig with a quick Intro to the OpenActive's route guidance specifications, which initially focused on guided activities but expanded to encompass self-directed activities due to increased demand (especially around COVID). Sport England's interest stems from the accessibility and health benefits of outdoor activities.

**National Trust's path inventory** ([starts 2:38](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=158)). The National Trust has mapped its paths using OpenStreetMap, including details like path type (public right of way, permissive, etc.) and barriers (gates, stiles). They have not implemented all the optional attributes in the Route Specification v1.0, but there is alignment with the core aspects.&#x20;

There's a lack of consensus amongst providers regarding grading and accessibility standards. The National Trust is working on a comprehensive list of path attributes (80-100) and exploring consistent terminology with other organisations (e.g. Natural England, National Landscape Partnership). The focus is on “describing the path rather than the person” to allow users to make informed choices and the initial scope is walking / running.

Challenges include data capture for thousands of kilometres of paths, defining and consistently representing accessibility for diverse needs (wheelchair users, visually impaired, etc.), and standardising data collection across various organisations.&#x20;

**Slow Ways** ([starts 17:15](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=1035)) are creating a network of walking routes that connect all of Britain’s towns, cities and national parks. They piloted an interesting alternative data approach, using Uber's H3 hexagons to describe landscape characteristics and accessibility at different scales.

**British Cycling** ([starts 23:24](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=1404)) is interested in creating accessible cycling routes but faces similar challenges in defining accessibility for non-standard cycles. They have routes, including the Let’s Ride platform which has an OpenActive feed of group rides (though there are a few data issues there), and they also have clubs, which may not have a fixed base or location.

**Paddle UK** ([starts 27:34](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=1654))  wants to incorporate open data for paddle trails, including what is along the way, which can vary depending on river conditions.&#x20;

The **Stream Initiative** ([starts 29:12](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=1752)) - a number of Water Authorities are also exploring sharing data on routes and related activities at sites like reservoirs.

The **ODI and our role in OpenActive** ([starts 32:39](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=1949)) The Open Data Institute (ODI) works with governments and organisations to build and promote better data ecosystems and data infrastructure. We have been funded by Sport England to steward the OpenActive standards and specifications, provide technical support, and facilitate community engagement. The standards aim to encourage wider adoption of open data to promote physical activity.&#x20;

**Discussion** ([starts 35:54](https://youtu.be/z2uBhDEmYOQ?feature=shared\&t=2154)) around various issues, barriers and challenges to sharing data and getting people more active, and next steps.

**Next Steps: Strategic direction and outreach**

With National Trust, the ODI is exploring if there is more we can do to promote the work at a senior level to ensure the right organisations are included in conversations.

**Next Steps: Agreeing path attributes and terminology**

We will support and facilitate further work to reach consensus on the path attributes and to reflect this in the Route Guidance specification and guidance for publishers and consumers. We recognise the need to find the appropriate level of flexibility within the specification to balance standardisation with the needs of different audiences.&#x20;

**Next Steps: Supporting data publishers**

We’re also keen to support those implementing open data. Please get in touch if you’d like to arrange a chat about mapping your data to the Route Guidance data model, creating a data feed, or to share any feedback on the specifications and documentation.

## Video

{% embed url="<https://youtu.be/z2uBhDEmYOQ>" %}


# 2024-05-22 W3C/AEF Show & Tell - Stabilising and improving OpenActive's infrastructure

## Summary

The ODI are collaborating with Imin to stablise the initiaitves core, infrastructure, fixing long term issues and improving the maintainability of the code base to ensure OpenActive can be maintained by any suitably skilled individuals. This Show and Tell demonstrated the work Imin have delivered during the first half of the contract.

## Video

{% embed url="<https://www.youtube.com/watch?v=ax6kvWqL7mA>" %}


# March and April 2024 meetings cancelled

The W3C meetings in March and April 2024 were cancelled due to very low attendance.


# 2024-02-21 Phase 5 Extension and Club Data

## Summary

At this meeting the ODI presented an summary of the extension to OpenActive Phase 5. There was then a discussion on club data, including proposals from London Sport and a demo of a prototype from the ODI.\
\
The subject of Club Data can be discussed at: <https://github.com/openactive/modelling-opportunity-data/issues/313#issuecomment-1829622120>.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1vmc2KFZg6mGxxkCy0_12AGQ7V7C19HTpMt83cwh8vjU/edit#slide=id.g2bb1b66970b_0_218>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=PWkPTnCLWzE>" %}


# 2023-10-18 OpenActive and Open Referral UK

**Summary**

At this months W3C Community Group we were joined by colleagues from London Sport and Open Referral UK to deep-dive into the relationship between the two standards. The session introduced Open Referral UK and set out work London Sport have been doing to build a ORUK feed usingOpenActive data held in Open Sessions data.

**Video**

{% embed url="<https://youtu.be/7nW8bPfYKMM>" %}


# 2023-06-21 Approaches to maintaining the OpenActive tech infrastructure

**Summary**

At this months W3C Community Group we discussed models for maintining open source software and how these may be applied to OpenActive. This discussion was to inform a forthcoming Steering Committee discussion.

**Video**

{% embed url="<https://www.youtube.com/video/ZItGGY-d0-g>" %}


# 2023-05-24 Data Quality Explorer Demo

**Summary**

At this months W3C Community Group the ODI team provided a demo of the updated Data Quality Explorer and led an open discussion session.

**Video**

Please note the video does not include the discussion session as a Zoom issue meant the recording failed after the first presentation - apologies!

{% embed url="<https://youtu.be/C6B9hGhiQyc>" %}


# 2023-04-26 Data Quality, Activities and Priorities

**Summary**

At this months W3C Community Group the ODI team presented work on the new data quality explorer and updates and improvements to the OpenActive Activity List.\
The Community Group then discussed the prioritisation of future work around the OpenActive specifications.

**Slides**

{% embed url="<https://docs.google.com/presentation/d/17mmYsHo5AEnyq-ANR3G3k0Oeb_ALhwpcgD0csAL99mI/edit?usp=share_link>" %}

**Video**

{% embed url="<https://www.youtube.com/watch?v=vCzCBwc7DB8>" %}


# 2023-03-29 Facilities and Activities

## Summary

Discussion of issues relating to the mapping of facilities to activities and a proposal to add a beta field to enable add-on items that are available at a facility (eg tennis rackets at a tennis court) to be described.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1m82FhuqlUBZDkRpFKZVuAhUbdzIYBSFKL6F5_8tICrQ/edit?usp=share_link>" %}

## Video

{% embed url="<https://youtu.be/FajHbmU2iQk>" %}


# 2023-03-01 Data Quality Update

## Summary

Discussion of the latest iteration of the data quality metrics and proposed next steps: convening data users to test and refine the metrics, alongside further automation of reporting.&#x20;

We moved on to the proposed principles and fast track criteria for the OpenActive Activity List. Discussion of challenges around the wider need for lists covering both physical and non-physical activities and services.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1BFERDX7Ht3bYlhXAJYq-DCnYfL_Z9iBdo7jAAy5A6O4>" %}

## Video

{% embed url="<https://youtu.be/gV_lcVQrybM>" %}


# 2023-02-15 Active Places

## Summary

Joined by colleagues from Active Places who share open data on sites and facilities, via an interactive mapping and reporting tool and by API. For more detail, see this [brochure](https://sportengland-production-files.s3.eu-west-2.amazonaws.com/s3fs-public/2022-06/Active%20Places%20Power%20brochure.pdf).&#x20;

We discussed areas where the two data initiatives could potentially better align to maximise value - including Facility Types and Active Places IDs. As an example, if Active Places place IDs are included in OA opportunity data, activity finders could pull in up-to-date accessibility information at the site and facility level.

We outlined the new process for managing the OpenActive Activity List. Regarding change control, additions and reordering of the list should cause no problems but deletions would require wider discussion.&#x20;

## Slides

{% embed url="<https://docs.google.com/presentation/d/1uMIYoZBVPBvYCa2sKc9etR5L16PRKUvk0zJqZoOWIK0/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/6l3jAU7uqZk>" %}


# 2023-01-18 Focus for year ahead

## Summary

After drawing attention to the draft [OpenActive Data Quality Reporting Framework](https://docs.google.com/document/d/1WCFR9Js_NShTJeN1-aCIcSJNsPHTUHJ3mokvnC6Lt54/edit?usp=sharing), we discussed a proposed timeline for updates to some of the OpenActive tooling and then explored potential topics and issues to focus on over coming months.

The following topics were suggested, in no particular order:

* Accessibility
* Management of the Activity List and Facility List
* Github issues (e.g. high frequency / ad-hoc sessions)
* Interactions between OpenActive and OpenReferral
* Routes
* Places and links to Active Places
* Courses
* Processes (e.g. adding feeds to the catalogs)

## Slides

{% embed url="<https://docs.google.com/presentation/d/10JyfwNJr1OW3l4gOV8FSnBQDd47qYppwmAWYkgJfw7Q/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/UZz8lIg2dmE>" %}


# 2022-12-07 Data Quality Reporting

## Summary

With an initial focus on the Discovery and Booking use cases, we discussed possible data quality metrics for the set of key data fields identified in previous calls. For example, reporting on the inclusion of either the activity location postcode or geographic coordinates to allow activity finder developers to search by location and to present opportunities on a map.&#x20;

We discussed briefly the OpenActive 'Activity List' and other lists in use across the sector. We discussed management of the list (separate to this W3C group); challenges in adding to and updating the list; and options to promote use of the list as reference data more widely.&#x20;

## Slides

{% embed url="<https://docs.google.com/presentation/d/1LPsq6koAs1HY1CuZeNKRVYz8Fs7pdOPhGPlQ2rEHw2g/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/f5t04SunqlQ>" %}

## Notes

Spreadsheet view of the Activity Lists discussed on the call

{% embed url="<https://docs.google.com/spreadsheets/d/1-HNiHVWCnv76w2YREDc64f6WEZQlRKfEtLJfDlHj8o8/edit?usp=sharing>" %}


# 2022-11-09 Reporting Data Quality

## Summary

Along the lines of the Data Quality Action Plan approach shared by the Office of National Statistic's Data Quality Hub, we discussed which aspects of the opportunity data feeds were critical to meeting the 'discovery' use case, and therefore potential candidates for regular measurement and reporting. The intention is to define a set of measures that will: help understand and promote quality across the initiative, and help assess suitability for different use cases.

## Slides

{% embed url="<https://docs.google.com/presentation/d/18zRFVEhUw1hI2egMMQRWyapfHbw-gxGz4-hAevWE2aw/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=U0yWTzl1CLQ>" %}


# 2022-10-26 High Frequency Sessions

## Summary

A discussion around the challenges of high frequency sessions, also known as fast tickets or density booking. After COVID-19, there is need to handle maximum occupancy and book individual timed slots for example for gym and swim sessions. This has resulted in a type of opportunity that falls somewhere between a session (usually low frequency) and a facility slot (usually high frequency).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1l3aGJG-vlkOPvWr0jPSceR8z-03kNdOIKVRiRNg_hEk/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/WLZ77SjH8EY>" %}


# 2022-10-12 Data Quality in OpenActive

## Summary

Discussion on perspectives of data quality in OpenActive feeds, with a demonstration of data variability impacting user experience and a presentation on data quality action planning from the Office of National Statistics Data Quality Hub.

In this phase of OpenActive, we will be exploring data quality in the context of different use cases (mainly discovery and booking), to inform work to refine the standards if appropriate and related tools and infrastructure.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1blQ6sMrdCZTu6oBE1eoQPrI4khAZOoYj1r85EqeS3IY/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/wQjuGsXBd-E>" %}

## Notes

Results from the slido poll in the call.

{% embed url="<https://drive.google.com/file/d/1rdOrQXuBVe07y35baah5XSxKa3gUJMVn/view?usp=sharing>" %}


# 2022-09-14 - Ways of working

## Summary

Largely for the benefit of the new chair, discussion focused on the W3C Community Group's ways of working and charter. Reaffirming the commitment to the guiding principles of due process, consensus, balance, transparency and openness.&#x20;

Documents discussed are linked in the slides below.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1t1ZaJpLaZuKk6AfVQ-PnIrd4__PTxtI5ApbafliO8x8/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/r_gX5WdWa3I>" %}


# 2022-06-08 - Accessibility

## Summary

A review of how to communicate accessibility information within the existing Opportunity specification, and discussion of the proposed [Accessibility data model](https://docs.google.com/presentation/d/15J1i_ZazOq31cnEDkFu-YWDMCKTvR3PIOEJ-nxjvGII/edit#slide=id.g1114d313682_0_2).

## Slides

{% embed url="<https://docs.google.com/presentation/d/15J1i_ZazOq31cnEDkFu-YWDMCKTvR3PIOEJ-nxjvGII/edit#slide=id.g1114d313682_0_2>" %}

## Video

{% embed url="<https://youtu.be/PIWkCux_8x0>" %}


# 2022-04-20 - LGBT+ Inclusion

## Summary

A discussion of modifications needed to the Opportunity specification and the groups who would need to be consulted to better support LGBT+ inclusion.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1cFebHoq_vmoOgCYY8G-qS7B8KK5v2e-mTtZO9ACsSUc/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/FU6IseX3Nzw>" %}


# 2022-03-02 - Safeguarding Requirements

## Summary

A landscape review of safeguarding practice and the extent to which data standards can and should address safeguarding requirements.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1HeDSCNWh2Q3i9DhwtL9-Ply1WyEraA8tx2edKgZmQmI/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/rtXeA9RsPBk>" %}


# 2022-02-02 - Block Bookings

## Summary

Review of the [block bookings](https://github.com/openactive/modelling-opportunity-data/issues/299) proposal.

## Slides

{% embed url="<https://docs.google.com/presentation/d/17ulligxHy7EaC-Qkc0msWg8rQQmsdpD-PJHE4zYRe-8/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/PcQpz5kJ358>" %}


# 2021-12-06 - Social Prescribing Attributes, Places, and Block Bookings

## Summary

Topics for this call include:

* Attributes proposed for better support of social prescribing use-cases, including:
  * &#x20;an attribute to indicate when an organisation or opportunity, or data about these, was last manually confirmed
  * intensity level
  * A Boolean to indicate whether an Opportunity or Organisation isSocialPrescribingReady
* Discussion of how to deal with `Place` information, particularly considered in isolation from `Opportunity` data.
* Block booking, and how this should best be implemented within the Open Booking API

## Slides

{% embed url="<https://docs.google.com/presentation/d/1kGxlkjVewTUfHhwHlWihJLnBVNhHg-05Ehtf0drrjKI/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/BdPCsVIizKo>" %}


# 2021-11-24 - Dependent Accounts

## Summary

The topic for this call is the handling of dependant accounts, particularly for minors.

A more detailed summary of the discussion can be found in the [Call Notes](https://docs.google.com/document/d/1Ojo-fvi6IKpG6BFoulSHMVMmIXMI4II-ZptwkV4OGN8/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1Ro40x-8JsF9dwjg1JxnViF5Vuvpd7yugzbPWK0YuA4w/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/xtyd8aWwtpc>" %}


# 2021-11-10 - Access Pass Requirements

## Summary

The topic of this call is the requirements surrounding access passes such as barcodes and QR codes for the [membership proposal](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit#).

A more detailed summary can be found in the [Call Notes](https://docs.google.com/document/d/1fhChtVu5BWvSggRIPBprnQ3SAXeebl23tPiet44jkNQ/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1_FXTnZJgeFKZETO7x2xZuQV87ORnkskgpioVOidsF4g/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/5XksKafRaBc>" %}


# 2021-10-27 - Terminology in the Membership Proposal

## Summary

The topic of the call is terminology in the [membership proposal](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit#).&#x20;

A more detailed summary of the conversation can be found in the [Call Notes](https://docs.google.com/document/d/17ZgcSk7iVNgioo6-wolKNMEJEPTQQbvTtVwFxJ-iyS8/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1HAtE4hsZ1u-KFtt5zMSZLL7U8IdZuR4_boFpIa64cNc/edit>" %}

## Video

{% embed url="<https://youtu.be/FieAlQ77Jdk>" %}


# 2021-10-13 - Membership Proposal Review

## Summary

This call finalised review of the Scope and Use Cases sections of the [membership proposal](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit?usp=sharing); completed intial review of the Design Principles, Example User Journey diagram, and the deprecated Federation Gateway Architecture sections of the document; and began investigation of Checking Whether a Customer Account Exists.

A summary of the discussion can be found in the [Call Notes](https://docs.google.com/document/d/1ZCzyqpbX_QfjnYgrLTd8CU3TNT49mGLhy8iR4wHNYQo/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1tLQ3eEWJ-Y-n8uL0LJfuClGmmh1MzxTtONzn7zHvDIs/edit>" %}

## Video

{% embed url="<https://youtu.be/xpkLglN3TTk>" %}


# 2021-09-29 - Requirements for the Membership Proposal

## Summary

The focus of the call was the proposal for dealing with memberships. As the proposal is complex and addresses multiple inter-related concerns (including account management, barcodes, and entitlement pricing), the purpose of the discussion was to ensure that requirements have been adequately specified.

Relevant documents are:

* the [Membership proposal](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit#) itself
* the revised [high-level requirements](https://docs.google.com/document/d/1pb6DTu6cdZDHK_4eSIIv3M3gyStD65Xg9irn8KTtBWo/edit#heading=h.mtanw1ypij6l) outline

## Slides

{% embed url="<https://docs.google.com/presentation/d/1i56SNJEiwKqXPizwhTeQiMisopdCfWUgKtUjLtsVz4g/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=qEfrnBFG-CA&ab_channel=OpenActive>" %}


# 2021-07-14 - Phase 4 Technical Communication Channels

## **Summary**

Discussion focused on phase 4 technical communication channels

* W3C Calls
* Implementers’ Forum
* Tech Drop-in

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1CKUjodz_SatgiXrcDtQPFUxFgem1wDOQSB41mkrpXHE/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/oqqELbIMKYs>" %}


# 2021-06-30 - Phase 3 Summary

## **Summary**

Phase 3 Summary

* Open booking API
* Virtual events
* Routes
* Accessibility
* Issues to be expedited
* Issues needing further exploration

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1Ms9qo5nlggtEtPDd9QaQZBJWzUFpYDCY_fPoWfmq_wA/edit#slide=id.p3>" %}

## **Video**

{% embed url="<https://youtu.be/XTZo_wcNDmQ>" %}


# 2021-06-02 - Facility Types, pt. 2

## Summary

Conclusion of the Facility Types conversation.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1snD8F7vbpXPXPjoNnAbL_a_2VdSTSsTKshzrUpdahGE/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/KNixpMGJnh0>" %}


# 2021-05-26 - Facility Types

## **Summary**

* Surface type
* Venue

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/10gLxVZqqrsQCcg9gf8s4dIDFxMM4pcHwPGTX9GDKUZ4/edit#slide=id.p3>" %}

## **Video**

{% embed url="<https://youtu.be/-BRHx6erq-g>" %}


# 2021-04-07 - Updates to the Opportunity specification

## Summary

Discussion focused on three proposed changes to the Opportunity specification:

* Describing difficulty and intensity
* Describing the surface of pitches and other sporting facilities
* Adding a `lastModified` or similar attribute to data items

A summary of the discussion can be found in the [Call Notes](https://docs.google.com/document/d/1do7wcPLRiFtLGxncAq5nXSo5HaibQ4HkoK1ZFkv3CNs/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1mo-A8-ztPKz7sivkfAaC81Kt6cW88R97D7tq0-0iYeA/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/fiZ7UJV56vU>" %}


# 2021-01-13 - Dataset Site Specification

## **Summary**

Dataset Site Specification

* Review of outstanding issues
* Matter arising
* Special opening hours specification

## Slides

{% embed url="<https://docs.google.com/presentation/d/1VCV_bgEYKZNfdCmcSZDw1vrcUCuRg-VFXuHbCoT2CNY/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/ntJgkvUZvdw>" %}


# 2022-07-07 - Final Review and Signoff

## Summary

A session to gather final feedback on the [draft specification](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit#heading=h.4p5pd0ki57uf) prior to its elevation to Candidate Recommendation status.

## Slides

Because this was a feedback session in which meeting participants were invited to share their own thoughts and comments on the draft specification prior to sign-off on completion of this draft, no slides or agenda was provided.

## Video

{% embed url="<https://youtu.be/uSL66eeC1nQ>" %}
v
{% endembed %}


# 2022-06-23 Spec Finalisation Scheduling

## Summary

A short process discussion about scheduling and future meetings for final sign-off of the draft specification.

## Slides

Because this was simply a logistics and coordination meeting, no agenda was supplied.

## Video

{% embed url="<https://youtu.be/aIj5DlEhkAk>" %}


# 2022-06-09 - Preliminary Review, pt. 2

## Summary

Summary overview and walkthrough of the [draft specification](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit), in particular for the benefit of Gladstone and GLL representatives.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1qK01uygaGWqeWYzlkBMBhdhXYvnV97PAdR52wRHhIvw/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/Qa7_K6A_Pi0>" %}


# 2022-05-26 - Preliminary Review, pt. 1

## Summary

Nick Evans leads a review of the draft proposal, having incorporated feedback from the previous Technical Working Group meetings.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1NSHHahP_01p_Sd307cxqjkJ93j9K-GZSpNb9dQrmLeg/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/G0NWB-8cq6w>" %}


# 2022-01-27 - Worked examples of dependent account handling

## Summary

As described in the page title above, this call works through examples of how to apply the dependent accounts proposal in concrete situations.

## Slides

{% embed url="<https://docs.google.com/presentation/d/16vkg1GWXbjqiHFcL9HfzNg5WR-txbbEPbWtJ_Nv83Nw/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/R1pl2zfStzU>" %}


# 2022-01-20 - Dependent Accounts, Updating Personal Data, and Late Cancellation Policies

## Summary

As noted above, the topics for this call were:

* A proposal for dealing with dependent accounts
* Making updates to personal customer data atomic
* A proposed `customerAccountBookingLateCancellationPolic`y attribute

## Slides

{% embed url="<https://docs.google.com/presentation/d/1P-9YjeQ3pQR4s9S6yPwA96lPYULb5PgbYFBXcg38H3s/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/C0WYWwP3v1M>" %}


# 2022-01-13 - Facility Booking, Customer Age, Sections 9 & 10, Appendices D & G

## Summary

On the agenda for this call:

* Requirements discussion re: per-participant facility bookings
* Minimum Customer Age&#x20;
* Section 9: Adding and removing dependant accounts
* Section 10: Booking on behalf of dependant accounts
* Appendix D10: RPDE Customer Account updates
* Appendix [G](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit?pli=1#heading=h.3engs7j3jvp0): OpenID Connect<br>

The status of dependant accounts was also discussed at length.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1uDPl57_U0WE6b1lYczhWsIsfnIwuOkwpnS4A0naKM3E/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/69fCcrhrZPc>" %}


# 2022-01-06 - Sections 7 & 8, Appendices E & F

## Summary

On the agenda for this call:

* Update: MCRActive responsible-adult details capture
* Section [7](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit#heading=h.3smfqssbpf1t): Display of entitlement pricing
* Section 8: Online booking through a customer account
* Appendix E: Describing Opportunities bookable via Customer Account
* Appendix [F](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit?pli=1#heading=h.iqxym9h7amql): Details of making bookings via a Customer Account

## Slides

{% embed url="<https://docs.google.com/presentation/d/1uDPl57_U0WE6b1lYczhWsIsfnIwuOkwpnS4A0naKM3E/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/69fCcrhrZPc>" %}


# 2021-12-09 - Appendices C6, C7, C9, D3, D4, continued

## Summary

A discussion of the membership proposal, appendices C6, C7, C9, D3, D4.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1_yuTb9jM4x-R1uvTX5EUrS5dRKMKmpwtgqomJdYPo0Y/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/BdPCsVIizKo>" %}


# 2021-12-02 - Appendices C6, C7, C9, D3, D4, D5; Sections 5 & 6

## Summary

This call covered Appendices C6, C7, C9, D3, and D4 in detail. Further summary can be found in the [Call Notes](https://docs.google.com/document/d/1rYPcmz2GFSNrqK0OO8KrSmYU4z719twgyAv4dToZYR8/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1kdb2_3Om4U3yv2iFS82LGLF2CvbY1n1vsjJCC8vscJA/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/a21Y3k--R1Y>" %}


# 2021-11-25 - Modelling Dependent Accounts

## Summary

The focus of the call was on dependent accounts and how to model these. Additional points of discussion were how to model access codes and the appropriate treatment of organisations as customers.

A more detail summary can be found in the [Call Notes](https://docs.google.com/document/d/1Yu9ZeF_6Bzgm6mqxaHlYglv0eJo1oa5vbmKfAESlB8s/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/18u_HUENksb5y0u_F-8RNoWj-eBh0DSrfR63ZKbzxckc/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/IAZBKN_V0Rk>" %}


# 2021-11-18 - Modelling Customer Accounts and Customers

## Summary

Topics covered in this call include:

* the registration flow wireframes in Appendix B
* the Customer and CustomerAccount models described in Appendix C
* mechanisms for unblocking customer accounts and bookings

A more detailed summary of the topics discussed can be found in the [Call Notes](https://docs.google.com/document/d/1yCUI577uB2ktdcUzLtwgTZz6fqWTvTMkNNaRAjyTg-k/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1ZC2DO2punUoo_ZpOgVnC1ci5WqPwxjDrQXwGkU5oTcQ/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/PpNft7LZDcc>" %}


# 2021-11-11 - Terminology; Sections 1 & 2; Appendices A\&B

## Summary

In this call:

* finalisation of the terminology conversation
* review of Section 1 ('Checking whether a Customer Account exists')
* review of Section 2 ('Creating a new Customer Account')
* review of the appendices relevant to the above sections

A more detailed summary of the call can be found in the [Call Notes](https://docs.google.com/document/d/1m0lTOl1QpPX9lXSUauY54QgmiK5-uDZrdagWIe-KfAw/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1HVooUm99AyRssjietaIpMRA1BjtFrzx8Uh775jLd-OY/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/E7q_BrirtPU>" %}


# 2021-11-04 - Terminology

## Summary

Following on from the [W3C call of 27 October](/meetings/2021-10-27-terminology-in-the-membership-proposal), the Technical Working Group discussed the terminology to be used in the [membership proposal ](https://docs.google.com/document/d/1mjmb-si95H_YK9qeNIhyTBfstGI-2NPAycz0y78GYGc/edit#)itself.

A more detailed summary of the discussion can be found in the [Call Notes](https://docs.google.com/document/d/1N1wUKuxR0bz3ldQ8I5TJeVjwc__qaC-s9I0cPjava3I/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/19GqBWUP4ryN_k0R_Vid46qvSU1qQGg24pxgFlYAcVlU/edit#slide=id.p3>" %}
&#x20;
{% endembed %}

## Video

{% embed url="<https://youtu.be/pfeur2qm1HU>" %}


# 2020-11-18 - Accessibility Specification

## **Summary**

Accessibility Specification

* Proposal
* Modelling

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1PUq2HBAbYqzHYa5tCfHOLwFkAUyENqDSfw4F352ZYwU/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/DmJ3dnPruZ0>" %}


# 2020-11-04 - Documentation Review

## **Summary**

Documentation Review

* Standards
* Developer.openactive.io
* GitHub repositories
* Open booking SDK

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1MeOn-CYMMGWZNDm8ALQbToTwtTsvNrA4kcguPxJm1Sw/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/ZKnSNpHKi2E>" %}


# 2020-10-07 - Schedules

## **Summary**

Schedules

* Directly on the event
* Partial schedule
* Event schedule

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1HLENzutkGrPvfDD9WOu58ML5lOPE7-WkTTeK_heGpIw/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/ytzm6IQ34i8>" %}


# 2020-09-23 - 1:1 Coaching Sessions

## **Summary**

1:1 coaching / private coaching

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/15ZxOBzP-N9rLdW1CXa4R5YngO0yApUgfkGbguaaaj8I/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/mBFNaYhSsqk>" %}


# 2020-09-09 - The Dataset Site Specification cont..

## **Summary**

Discussed in the W3C calls of 15th July and 26th August

* Resolved (?) issues
  * Different feed types
  * Data catalog specification
  * Spoof-proofing identifiers
* Open issues
  * Handling of base URI
  * Publisher/creator/maintainer
  * Feature assertion
  * Status codes

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1egCGs1uJFOBGgXeepwSESr1T4ETSUgEprn22vx9OZdM/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/P3aBr-FjY2M>" %}


# 2020-08-26 - Dataset Site Specification (cont.)

## Summary

The topic of this call was the completion of actions and discussion of new issues related to the Dataset Site Specification. A summary of the above can be found in the [Call Notes](https://docs.google.com/document/d/1ltSw1_NPYoyV3DgXFejDZBDuegWUUzLoIenSahMib3s/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1VCgv_4k-Gr4tf7xPq79sK0--z9q_lrSpbUMv3zlYTsM/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/7SOXhHfnGjU>" %}


# 2020-07-15 - Dataset Site Specification

## Summary

The topic of the call was the first draft of the Dataset Site Specification. Notes on the discussion and actions can be found in the [Call Notes](https://docs.google.com/document/d/1tRNhCC4OBu7oReDQ_OeoUd9HjVOxGPxRO5_kuyabdw0/edit?usp=sharing).\
\
Actions updating the specification are to be completed before 29 August, when review will take place.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1LtTgtIV-uMznuD8d3sYx8KIeClT5b4MYGhSUfacztNE/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/swuIW8H8sX8>" %}


# 2020-07-01 - Opportunity API

## **Summary**

* Opportunity API original proposal summary 2018
* Initial Implementation

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1i6lIsFHgo3mUNZFKEW6coh3r0sWpoo4D60efizQdt3s/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/ATRe11-EXrc>" %}


# 2020-06-17 - Improving the RPDE specification

## **Summary**

Improvements to RPDE

* The harvesting model has limitations
  * Difficult to gauge progress
  * Requirement to harvest from the beginning of time
  * Cannot query selectively
* Pagination data
* Parameterise the RPDE querystring
* Movable first page

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1U4jXNuxEg96FrD5x3dl4GPLlVE-EdGpkrNiS9SazJaA/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/LIEsqGF4zqE>" %}

<br>


# 2020-06-03 - Modelling Facilities

## Summary

* Individual Facility Use and Facility Use
* Multi-purpose facilities

## Slides

{% embed url="<https://docs.google.com/presentation/d/1CSbOCMQoYzQINQlYzMlZilsuN_8OIF9FcrI6XGlag7A/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/KFh6lUFaC7g>" %}


# 2020-05-06 - Revisiting Accessibility

## **Summary**

Revisiting Accessibility

* History
* Current proposal

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1UnZa3cf_MVQEmjugOY17kXAhKeQ-frber0bmbKtEcyY/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/J4drt0arfw0>" %}


# 2020-04-22 - Safeguarding

## **Summary**

Revisiting safeguarding

* Initial proposal
* Feedback so far
* Revisions

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1mG8g0clzPH6em3pjKNJfLsKbqYVNzbO1-GN0A18eSeo/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/8oQ6nyFHRCY>" %}


# 2020-04-08 - Wrapping Up Virtual Events

## **Summary**

* Refining earlier proposal
  * Guidance for virtual and on-demand events
  * Maximum virtual attendee capacity and remaining virtual attendee capacity
* New
  * Donation payment URL

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1M5VfU6WjsUML-Cdlr0vdbiir0wK89uWJaTKqX5h6f54/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://www.youtube.com/watch?v=3Riny8zSvAI>" %}


# 2020-03-25 - Virtual Events and other COVID-19 proposals

## Summary

Given the urgency of the topic in light of the UK-wide 'lockdown', we aimed to finalise approval on all topics on the agenda in the course of the call.

**Virtual Locations (**[#224](https://github.com/openactive/modelling-opportunity-data/issues/224)**)**

* After discussion about the merits of supporting multiple broadcast platforms, the consensus was to keep `beta:virtualLocation` as a singular not array, as multiple broadcast platforms are likely an edgecase in this sector. We agreed to re-evaluate this before moving the property out of beta.

**VideoObjects and/or OnDemandEvents** ([#228](https://github.com/openactive/modelling-opportunity-data/issues/228))

* Use `OnDemandEvent`, to easily make use of all the existing properties of Events.
* Use `workFeatured` to embed any video or other media (e.g. a `VideoObject`)

**Describing required equipment** ([#229](https://github.com/openactive/modelling-opportunity-data/issues/229))

* There was a proposal that this should be triple-valued (roughly `required`, `optional`, `none`) - to account for events where equipment is optional (an alternative is provided for those without). Consensus was that context would indicate the meaning of the attribute, with additional guidance being provided in `attendeeInstructions` if required.

**Describing participantInteraction** ([#230](https://github.com/openactive/modelling-opportunity-data/issues/230))

* Use `beta:isInteractivityPreferred` boolean for now, as interaction being strictly “Required” is probably an edge case
* Consider repurposing [`https://schema.org/interactivityType`](https://schema.org/interactivityType) for this in future
* `attendeeInstruction` should be used to provide further detail if required.

**eventAttendanceMode** ([#225](https://github.com/openactive/modelling-opportunity-data/issues/225))

* No changes

**maximumVirtualAttendeeCapacity and related properties** ([#226](https://github.com/openactive/modelling-opportunity-data/issues/226))

* This has the potential to create a large amount of complexity and confusion, especially given the `maximumAttendeeCapacity` property still exists and is used widely, and `remainingAttendeeCapacity` is used heavily by the [Open Booking API](https://www.openactive.io/open-booking-api/EditorsDraft/).
* For now just add `beta:maximumVirtualAttendeeCapacity` to `VirtualLocation`, so as not confuse any logic around booking (keeping booking separate for now, and readdressing this with any additions to Open Booking API to handle virtual classes in future)
* Note that this is the capacity of the specific `VirtualLocation` (e.g. that specific Zoom room), not the entire event.

**EventMovedOnline Event status** ([#227](https://github.com/openactive/modelling-opportunity-data/issues/227))

* Add a new property `beta:affiliatedLocation` was proposed for the original locations of an online-only event, to ensure that the existing data users’ implementations would be intentionally broken by the lack of a `location` field in all cases, and hence they would not misrepresent virtual classes as physical ones.
* This replaces the need for `EventMovedOnline`, which can therefore be removed.
* Hence, for virtual events where `eventAttendanceMode` is set to `https://schema.org/OnlineEventAttendanceMode`,  `location` MUST NOT be included.

**Guidance (**[#231](https://github.com/openactive/modelling-opportunity-data/issues/231)**)**

* Put `beta:maximumVirtualAttendeeCapacity` into `VirtualLocation` as a beta field, but keep this RECOMMENDED
* Offer is required either in `SessionSeries` or in `ScheduledSession` update to match current spec
* `beta:affiliatedLocation` is RECOMMENDED
* `workFeatured` is RECOMMENDED

**Levels (**[#82](https://github.com/openactive/modelling-opportunity-data/issues/82)**)**

* Standardise only the string “`Beginner`” for now, as a short term solution to save trying to solve the larger levels problem.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1srA7SyfDBqCHwFTT7oVxyu4-Hl_3NBkSlpCDMKqj4HE/edit>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=IR6EDwUvAsA>" %}


# 2020-03-11 - Customer authentication continued

## **Summary**

Customer authentication continued;

* Use case 1: User account is with broker only
* Use case 2: User account is with seller only
* User account has both broker and seller accounts

## **Slides**

{% embed url="<https://docs.google.com/presentation/d/1Hzy4nMOy8UcXIy9BJJHb_9eRHkYn-Tq2WTJMSKZ8p-Q/edit?usp=sharing>" %}

## **Video**

{% embed url="<https://youtu.be/7Kg4JRGnZuQ>" %}


# 2020-02-12 - Opportunity Specification Proposals

## Summary

A number of recently-proposed updates to the [Opportunity Specification ](https://www.openactive.io/modelling-opportunity-data/)were discussed, specifically:

* [dealing with](https://github.com/openactive/modelling-opportunity-data/issues/219) JSON-LD '@' prefixes
* ad-hoc [Event Locations](https://github.com/openactive/modelling-opportunity-data/issues/209)
* require [startDate and endDate to have a time component](https://github.com/openactive/modelling-opportunity-data/issues/208)
* [IndicativeOffers](https://github.com/openactive/modelling-opportunity-data/issues/207)
* [estimatedDuration](https://github.com/openactive/modelling-opportunity-data/issues/201)

&#x20;A summary of the call and follow-up actions can be found in the [Call Notes](https://docs.google.com/document/d/1-MKuP8asU35G0NXNLICu12q0mUwjTQCAWLilz50zY_M/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/119bVxjCEZfFvuLvQxEbcqqm-VNQQIhib2vE7AeOXKCI/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=gkw9tlI6EUg&feature=youtu.be>" %}


# 2020-01-29 - Customer Authentication continued

## Summary

Continuation of the discussion of Customer Authentication initiated on the [2019-11-20 call](/meetings-archive/2019-12-04-safeguarding-and-html-support), and in particular of the [overview of its conclusions ](https://github.com/openactive/open-booking-api/issues/120#issuecomment-556335643)given in the relevant [GitHub Issue](https://github.com/openactive/open-booking-api/issues/120).&#x20;

Notes and actions following on from the discussion can be found in the [call notes](https://docs.google.com/document/d/1RBrAJi6gwnbsr0l6PgJjmOiUwAUqe-IOMbOQ5fpQWEs/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1tZejMLmasdDr4s4mR6MzXY7RRcC3ry2KDsymRlYEZQQ/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/7KsrcTUkMsg>" %}


# 2019-12-04 - Safeguarding and HTML support

## Summary

Further discussion of Safeguarding, and development of the proposal to support HTML and/or markdown formatting in text fields.&#x20;

A summary of the proceedings can be found in the [call notes](https://docs.google.com/document/d/121MW-D10EERXzWccCHim4gbmGj0i1XcajBcOgObLkWc/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1QfqWXgWjk5jtzr_rBCjQthR38VFtGe591HqVsrFgVsE/edit#slide=id.p3>" %}

## Video

{% embed url="<https://youtu.be/XCdH_FsKHpE>" %}


# 2019-11-20 - Customer Authentication

## Summary

This was the first call where proposing community members discussed the Customer Authentication issue, prompted by discussions on the mailing list ([1](https://lists.w3.org/Archives/Public/public-openactive/2019Sep/0001.html), [2](https://lists.w3.org/Archives/Public/public-openactive/2019Oct/thread.html#msg5), [3](https://lists.w3.org/Archives/Public/public-openactive/2019Nov/thread.html#msg5)).

A summary of the discussion so far, including the key points covered on this call, can be found in [this GitHub issue](https://github.com/openactive/open-booking-api/issues/120#issuecomment-556335643) and the [call notes](https://docs.google.com/document/d/143d3hRiRxE_lzvpBVk-xdyZ_-rO9Hc-wXB9VMC1Y4nM/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/17iXfN_nXZmGySETGWn6ms0S4vE8gtx6OTfOBPce05G4/edit>" %}

## Video

{% embed url="<https://youtu.be/tFwc9LdlL8M>" %}


# 2019-11-06 - Finalising the Routes Specification

## Summary

The call reviewed several changes to the draft specification for RouteGuidance, preparatory to finalisation of this section of the Opportunity specification later in the month.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1VGiP0N4sqqQ2qIQQBRrDEE7fz2EumFdPiMsQ4Ynie8Q/edit>" %}

## Video

{% embed url="<https://youtu.be/t2E2YTwMe0M>" %}


# 2019-09-25 - References vs Objects

## Summary

The focus of the call was chiefly on URL references and the extent to which these should be permitted to replace fully-represented objects within the specifications. For more details see the [Call Notes](https://docs.google.com/document/d/1S_4xyqgyMkbtQ2jktGB-WddppVADXBch-jj3EOb9EnA/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1fit_iTV2m-txyrQA19We0Ya8l183q1FZZY8-2oqebDA/edit>" %}

## Video

{% embed url="<https://youtu.be/q1Wl4xQNk2c>" %}


# 2019-10-09 - Difficulty Level and Prerequisites

## Summary

The purpose of the call was to finalise discussion of standardising the terms used to capture `oa:level,` and to unpick how best to model prerequisites that needed to be satisfied in order to participate in certain kinds of activity or at certain levels. For more details see the [Call Notes](https://docs.google.com/document/d/14oUWudYpZCrSbRA_oKFor9nCOn2sYInHJyHwZvRqyLw/edit?usp=sharing).

## Slides

{% embed url="<https://docs.google.com/presentation/d/14whCFAndCPyfz0bSFKZrjdSKYQ8_AJatxyPz4-dJFkE/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/ee_8fet2emg>" %}


# 2019-09-11 - Safeguarding and the Opportunity Specification

## Summary

Discussion of the [Safeguarding and trust networks](https://github.com/openactive/modelling-opportunity-data/issues/217) proposal. Notes on the call can be found at <https://docs.google.com/document/d/1ht1nVzK9Yp6fBrK3y8pg-8e9JVRgGchBYL2OahpB2AM/edit?usp=sharing>.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1Ti499xyJ-DkMKTuP-bls1BLKHyg2V37U4M_Gxvtxd3E/edit>" %}

## Video

{% embed url="<https://youtu.be/2KVM1ksAvUo>" %}


# 2019-08-14 - Routes versioning and data publication

## Summary

Continuing topics from the previous call, discussion focused chiefly on questions of publication and specification versioning. Agenda and notes can be found at <https://docs.google.com/presentation/d/1CJVZyyB6Gx7_KYdN_9Ra4CGFTAZuZvDYK-dsTZrIqgk/edit?usp=sharing>

## Slides

{% embed url="<https://docs.google.com/presentation/d/1CJVZyyB6Gx7_KYdN_9Ra4CGFTAZuZvDYK-dsTZrIqgk/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=iNPskGNFjpQ&feature=youtu.be>" %}


# 2019-07-31 - Routes Initial Implementation

## Summary

With the publication of the first draft of the Routes specification, discussion was largely focused on paths to implementation and data-publishing. Call notes can be found at <https://docs.google.com/document/d/1SwDKt8NrnQeQeo3fA54kb52y9-dUMjDxBwj5OIHKKVc/edit?usp=sharing>

## Slides

{% embed url="<https://docs.google.com/presentation/d/1FeNCfUGMj_vG1KXcKIpNTLYF_096oNMUUlknO4UIQ9I/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=Cvvk8dRnTQY&feature=youtu.be>" %}


# 2019-07-17 - Routes Workshop Follow-up

## Summary

This call was focused on reviewing the outcomes of the Routes workshop that was held on 4 July 2019, with a particular focus on user-story prioritisation, Route segmentation, and assessments of safety/risk and difficulty level. Call notes can be found at <https://docs.google.com/document/d/1ICpeyn-H4t6sOCbWLSWy2b2NE_Yc1LsbwsrRdspiiBM/edit#>.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1eSJcDousnZpMQ1ZG4VGcSQBiXqVcOAb4qCrSxcOrkqs/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=EFIPxRG17Vg>" %}


# 2019-07-03 - Routes Workshop Preparation

## Summary

This call was dedicated to discussion of the Routes Use-Case Workshop scheduled for the following day (4 July 2019). Materials and outputs from the Workshop can be found at <https://drive.google.com/drive/u/0/folders/1mR_dov8w33tdWPdnRBiwW4eBxqyTmQQL>.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1zZjYpbq_w0-iRBXUU80_QyDSKxfrK1WwkbUyLToexqU/edit#slide=id.p3>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=Abdg4zmvJ0w&feature=youtu.be>" %}


# 2019-06-19 - Modelling Opportunities: Difficulty Level/Prerequisites

## Summary

This call continued the discussion about standardising Difficulty Level started in the previous meeting. The chair's proposal of hiving off 'prerequisites' as a separate concern (<https://github.com/openactive/modelling-opportunity-data/issues/210>) was also addressed.&#x20;

Call notes can be found at: <https://docs.google.com/document/d/15iHqTOaLWWaohWT4kyfk7_KLTmsCROEAEDxtucuEUeI/edit?usp=sharing>

## Slides

{% embed url="<https://docs.google.com/presentation/d/1ZxGyD05Whu8c0gqFpbSmZJg4mt0wlenmn6IbTMBxwaA/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/H9r93aPH-20>" %}


# 2019-06-05 - Modelling Opportunities: Difficulty Level

## Summary

Discussion on this call was focused on Difficulty Level in the Opportunity specification. The original GitHub issue can be found here: <https://github.com/openactive/modelling-opportunity-data/issues/82>, and a more detailed summary of the call is provided in the [Call Notes](https://docs.google.com/document/d/1gcG_LF1z89M-bdabJhLfUCnTGBnD4T1I-d_w_anBsno/edit#).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1a9N-64TGON2spxSCOtXtXcSDkkPVGe-CzBB9zg7Q0nU/edit>" %}

## Video

{% embed url="<https://youtu.be/VrIxgozYRwI>" %}


# 2019-05-22 - Routes Data Exploration

## Summary

The purpose of this call was to review Routes data 'in the wild', looking at and evaluation existing practices for publishing this kind of information. A summary of the discussion can be found in the [Call Notes](https://docs.google.com/document/d/1aFzed35cXOv4bTXJz9ca2rmFP90il_lly1_ZQbWj7n4/edit#).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1cNe3XGqhaOmGlrRRG5HrQxo6g18A1NSMAlGf1iMGErc/edit#slide=id.g48309f7275_0_222>" %}

## Video

{% embed url="<https://youtu.be/pR9YL6GAXWU>" %}

## <br>


# 2019-05-08 - Routes and Accessibility Planning

## Summary

The purpose of the call was initial high-level roadmapping for the specifications to be developed over the next year - in particular, the Routes and Accessibility specs. A summary of the discussion can be found here: <https://docs.google.com/document/d/15DzAXlqvIaZ58V1CC2DvzHW2jQrrV_wbpuF0Rhli-0k/edit#>

## Slides

{% embed url="<https://docs.google.com/presentation/d/1qFlnO967BJbrvjnfdbNMcHVcHq5ClhR0DU6CF1Phol4/edit#slide=id.p3>" %}

## Video&#x20;

{% embed url="<https://www.youtube.com/watch?v=TKT6aQknleE&t=2s>" %}


# 2019-04-10 - Booking: Workshop followup

## Summary

We discussed feedback received at the Open Booking Finalisation Workshop, and covered some of the common followup questions that we did not have time to address during the event:

* **Opportunity & Offer** - both an Opportunity ("Yoga Tuesday 14th 7pm") and an Offer ("Junior (8-18)") are required to start the booking flow. This explains how a booking system knows which price is applicable without attendee data such as date of birth.
* **Trust and Control** - The specification does not currently include fine-grain control of opportunity bookability e.g. it does not allow "bookability by broker" to be advertised or elegantly controlled. This is simply because of the scale of the controls required and the cost of these e.g. if a Seller partnered with 100 brokers, they would need to administer "Bookable via Broker 1" though to  "Bookable via Broker 100" on a per-activity basis, which would be an enormous administrative burden (and increased development cost for booking systems). Especially when we consider that it's likely that the constraints will be more nuanced than just per-activity. For example one might want "Bookable via Broker 1 only off-peak and on a Wednesday", and "Bookable via Broker 5 for junior Offers only". If we went down the route of constraining booking at an API level it would get extremely complicated and the cost of administration would likely not outweigh the risk of bad partners (keeping in mind that a Seller can instantly terminate their connection with any rogue partner Broker with zero notice if they wish, in the case that they violate the agreement). The trust relationship discussed at the workshop between Sellers and their partner Brokers is the key. A Seller's contract with each Broker will likely include restrictions on what they can and cannot book and under what circumstances,  which can then be audited during reconciliation if needed. So the Brokers that Sellers partner with will have the technical ability to book anything, but will have to follow the terms of any agreement with them. This has been added to the "out of scope" list in the specification for clarity.
* **Attendee detail capture** - We talked through the Attendee Details Capture [GitHub issue](https://github.com/openactive/open-booking-api/issues/107) (a.k.a. "date of birth") in detail. We are actively seeking feedback on this issue - which is fairly complex - and propose to delay this for a future version of the specification. Izy from Sport England was keen to point out that Sport England are supportive of minimal data capture during booking, and that any activity providers being pressured by Sport England to provide reporting of detailed demographics based on details captured during booking should contact her for assistance.

The [Open Booking specification](https://www.openactive.io/open-booking-api/EditorsDraft) release has been delayed until 17 April to allow for minor technical refinements to be made (such as REST conformance and model consistency), and is now scheduled for ratification on 1 May.

The [OpenActive model validator](http://validator.openactive.io) will be updated to include the models in the Open Booking specification as soon as it is published, to aid implementation work.

## Slides

{% embed url="<https://docs.google.com/presentation/d/14gm_ms8hZzbaHIYwjHE0Qa55JlY7fVcMlJ2wPdQMiVs/edit#slide=id.g3de11654c2_0_98>" %}

## Video

{% embed url="<https://youtu.be/tYFVM2TSb8Q>" %}


# 2019-04-02 - Booking Finalisation Workshop

## Summary

With the Open Booking Specification nearing finalisation this workshop offered a presentation of its features and limitations, the decisions that have been taken by the community to date, and provided a final opportunity for feedback.

Delegates attended both in person and via live stream, and included executive representation from major booking systems, brokers, leisure operators, and other activity providers.

The following changes will be made to the Open Booking specification as a result of the workshop:

* Change the language in the logical steps from "Register" to "Identify", to clarify that registration is not mandatory.
* Add a property that can be used by the Broker to clearly display free text restrictions such as "2:1 adult/child ratio", in addition to improved guidance for the Broker to prominently communicate existing age and gender restrictions in advance of the booking being confirmed.
* Add guidance for `attendeeInstructions` to be sent as part of the booking confirmation from the Broker to the Customer, so that information about how local car parking works, locker tokens, etc are guaranteed to be communicated.
* Clarify financial data / reconciliation requirements including cost centre.

Additionally we created the following GitHub issue for further discussion:

* [Attendee detail capture](https://github.com/openactive/open-booking-api/issues/107)

## Slides

{% embed url="<https://docs.google.com/presentation/d/1obGCA0BhYYzO92A2WU7fp0aH3qu3GUK0kxZIwdkVoTc/edit>" %}

## Video

### Part 1: Slides 1-36: **Introduction and OpenActive Overview**

{% embed url="<https://youtu.be/HHxNq5XR-6U>" %}

| **Slide** | Video | Section Title                             | Speaker                                                         |
| --------- | ----- | ----------------------------------------- | --------------------------------------------------------------- |
| 1         | 0:00  | **Introduction and Agenda**               | Nick Evans, Technical Engagement Lead, Open Data Institute      |
| 8         | 7:30  | **OpenActive Background**                 | Izy Champion, Data and Innovation Manager, Sport England        |
| 20        | 16:00 | **OpenActive and Open Data Introduction** | Richard Norris, Programme Manager, Open Data Institute          |
| 27        | 25:10 | **Open Data Q\&A**                        | Richard Norris and Nick Evans                                   |
| 28        | 41:30 | **Open Booking Introduction**             | Richard Norris                                                  |
| 35        | 46:20 | **Why now?**                              | Sean Maguire, Managing Director, Legend Club Management Systems |

### Part 2: Slides 37-68: **Booking Finalisation Part A**

{% embed url="<https://youtu.be/9JwXulzy4mM>" %}

| **Slide** | Video | Section Title                                   | Speaker                                                |
| --------- | ----- | ----------------------------------------------- | ------------------------------------------------------ |
| 37        | 0:00  | **Developing standards for OpenActive**         | Leigh Dodds, Director of Advisory, Open Data Institute |
| 42        | 9:00  | **Booking Finalisation Introduction and Scope** | Nick Evans                                             |
| 49        | 13:10 | **Key Actors**                                  | Nick Evans                                             |
| 50        | 17:48 | **Booking Flow and Leasing**                    | Nick Evans                                             |
| 57        | 35:25 | **Roles and Responsibilities**                  | Nick Evans                                             |
| 59        | 40:50 | **Receipts and Notifications**                  | Nick Evans                                             |
| 62        | 43:55 | **Types of Broker**                             | Nick Evans                                             |
| 65        | 50:30 | **Tax and Tax Exemption**                       | Nick Evans                                             |
| 68        | 56:00 | **Open Booking Q\&A 1**                         | Nick Evans and Richard Norris                          |

### Part 3: Slides 69-90: **Booking Finalisation Part B**

{% embed url="<https://youtu.be/jY-cm0YNlSc>" %}

| **Slide** | Video | Section Title             | Speaker                       |
| --------- | ----- | ------------------------- | ----------------------------- |
| 70        | 0:55  | **Guest Checkout**        | Nick Evans                    |
| 73        | 3:30  | **Marketing Preferences** | Nick Evans                    |
| 75        | 6:26  | **Access Control**        | Nick Evans                    |
| 77        | 8:28  | **Cancellation**          | Nick Evans                    |
| 79        | 12:48 | **Booking Approval**      | Nick Evans                    |
| 81        | 14:46 | **Dynamic Pricing**       | Nick Evans                    |
| 84        | 20:45 | **Open Booking Q\&A 2**   | Nick Evans and Richard Norris |
| 86        | 46:24 | **What's next?**          | Nick Evans                    |


# 2019-03-27 - Booking: Overview and feedback

## Summary

We ran through the following feedback points around the [booking specification](https://www.openactive.io/open-booking-api/EditorsDraft) in detail:

* Access control
* Reconciliation&#x20;
* Refund behaviour

## Slides

{% embed url="<https://docs.google.com/presentation/d/1wNKozyH9cWAU5WO-6Rmck6D2pvMY72SIt9ijd-db7jw/edit#slide=id.p3>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=oZaAkIshTGY>" %}


# 2019-03-13 - Booking: Overview and feedback

## Summary

We ran through the [booking specification](https://www.openactive.io/open-booking-api/EditorsDraft) 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 [version issue](https://github.com/openactive/open-booking-api/issues/105) open for comment to seek wider feedback.
* Clarified the cancellation of events after they have occurred in the specification.

Additionally Izy requested feedback [her work](https://docs.google.com/document/d/1-z3KkQYch-qY1OKbk-o9WTEabIr-JGcRd55fEtKjQJg/edit) following the [last accessibility call](/meetings-archive/2018-10-24-accessibility-requirements).

## Slides

{% embed url="<https://docs.google.com/presentation/d/1b6sbpd0wwGx_ezWEk_wmr-ZoRdC04tYexhedsa1viYA/edit?usp=sharing>" %}

## Video

{% embed url="<https://youtu.be/7Zg4iRWRRj8>" %}


# 2019-02-27 - Booking: Overview and direction check

## Summary

We ran through the [booking specification](https://www.openactive.io/open-booking-api/EditorsDraft) at a high level, including checking the direction taken on remaining issues. Everyone was broadly happy, with some comments to raise on GitHub and a suggestion to consolidate cancellations into a single PUT call for the Order (to allow for atomic cancellation, given the potential for additional cancellation constraints to exist).

As a result of the call we:

* Clarified the spec regarding the error raised when attempting to book a non-"bookable" opportunity.
* Amended the spec to make cancelling multiple items atomic, with an outstanding question regarding restrictions (<https://github.com/openactive/open-booking-api/issues/102>)
* Raised and linked an additional issue: <https://github.com/openactive/open-booking-api/issues/103>

## Video

{% embed url="<https://youtu.be/hz85pUuDgx8>" %}


# 2019-02-13 - Booking: Cancellations and Refunds

## Summary

Presentation of a more comprehensive solution to cancellations and refunds, which was broadly accepted on the call with some minor changes required.

## Slides

{% embed url="<https://drive.google.com/open?id=1bnsR_-B8r56Y2VTeGvuDdlfF6fHXCQx6vcVAZ2CrnoY>" %}

## Video

{% embed url="<https://youtu.be/OKyzFjRVVV4>" %}


# 2019-01-30 - Booking: Cancellations and Refunds

## Summary

Presentation of a solution for cancellations and refunds, which on examination through the call was deemed to be only a partial solution. More work is required to create a robust cancellation and refund process.

## Slides

{% embed url="<https://drive.google.com/open?id=1X-MVQFVhW803t9jJz66meJJVyzFrEOOlyymV38QVNgk>" %}

## Video

{% embed url="<https://youtu.be/hcut6wkJ1Bg>" %}


# 2019-01-16 - Booking: Walkthrough

## Summary

Walkthrough of the booking specification for final comments, which uncovered issues around cancellation and refunds.

## Slides

{% embed url="<https://drive.google.com/open?id=11mmONFyT67tct0rS7DNG56irz6yjI20HeYd8rVxWOS8>" %}

## Video

{% embed url="<https://youtu.be/6woJfHqzWdA>" %}


# 2018-12-05 - Booking: Tax

## Summary

More detailed discussion around tax, captured in this document: <https://docs.google.com/document/d/1QKqzkgCS0pijfdOkyZVfLwzeUeRAxDxiFKnxmmAzyE4/edit>

## Video

{% embed url="<https://youtu.be/VmJtJrv496U>" %}


# 2018-11-21 - Booking: Tax

## Summary

Revisited extra booking feedback, including the issues on tax.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1jA_JzBwEUBd2UH6vvH3onqZbt6Cqy1a4fjF3JoJBuu4/edit#slide=id.p3>" %}

## Video

{% embed url="<https://youtu.be/sbV8q_tPjMU>" %}


# 2018-11-16 - Activity List Tool

## Summary

A call to talk through the new Activity List management tool for collaborative editing of the OpenActive Activity List

## Slides

{% embed url="<https://drive.google.com/open?id=1uLhbRVNn-SJvP3jsuC9ehqFVS15T9PhUaOyeikM9Xx8>" %}

## Video


# 2018-11-07 - Booking Feedback

## Summary

We produced a short document that summarises that feedback and requirements. The call on the 7th November focussed on discussing this document:

<https://docs.google.com/document/d/1oylsEIFIlJUuZ1DL6Bv_fMdDAfvUR9vdha6bNp5QCSI/edit?usp=sharing>

## Slides

{% embed url="<https://docs.google.com/presentation/d/1JVi_5_RcPb2aULNMnnEcKL_A1h6N6qT2LgXJlEkvqw4/edit>" %}

## Video

{% embed url="<https://youtu.be/OZake5lZGTw>" %}


# 2018-10-24 - Accessibility requirements

Update on the accessibility requirements in the OpenActive spec and proposal to extend these in the next versions of the specifications

## **Summary**

### **OpenActive accessibility requirements approach so far**

In the past we looked at data being published by different activity providers and tried to find commonalities. This led to a list of AccesibilitySupport dropdown options + a free text field.

Some people in the group were concerned that data at this level isn’t currently collected/known by activity providers and that we should focus on getting this level of adoption. Following this we can see what other data we have, rather than creating gold plated standards that providers can’t give information against.

### New suggestions

There are two new suggestions (SpecialRequirements & IsWheelchairAccessible) but in the call we mainly focused on the ‘SpecialRequirements’

#### IsWheelchairAccessible

The group noted that there is difference between something being physically wheelchair accessible, and really being suitable or pleasant for wheelchair users - so user testing the definitions and guidelines is important.

#### SpecialRequirements&#x20;

There was some confusion as to what these tags actually meant: should the categorisation be taken to mean that those with the specified condition are welcome, or the activity has to be specifically targeted to that group? Are they based on conditions or people’s needs (e.g. ‘strokes’ have different severity levels)? Could a more general field of ‘disability aware or friendly’ be easier for an activity provider to tick?

Wording: ‘impairments’ may not be very accessible/relevant to people - but it was noted that this may not be what is displayed to a consumer anyway&#x20;

In general the group thought that it could be useful to be able to give this information if available but:

* It would be difficult for an activity provider to determine whether they were friendly to ‘strokes’. OpenActive has previously talked about making questionnaires & guidance to help activity providers standardise, but this hasn’t yet been done, and OpenActive may not be best placed as non-experts. This has led to a situation where some providers tick everything because they want to run an inclusive session and some providers don’t tick anything because they are nervous about making this judgement.
* By allowing activity providers to self identify, there are lots of data quality risks, whereas it is possible for someone independent say ‘there is disabled parking space or changing rooms suitable for wheelchair users’ (see disablego link in slides).
* There are a range of ‘strokes’ too, which lead to a range of cognitive + physical issues. In the options given in the list they seem a varied bag in terms of granularity and types of support someone might need.
* There’s a difference between events specifically targeted at someone specific (maybe for more severe cases) and events that are friendly towards people with conditions but aren’t aimed at them. It was felt important to be able to tag events if they’re specifically being run for rehabilitation rather than being termed ‘suitable’ for lots of conditions but aimed at the general public.
* If someone needs significant extra support they may be with a carer - so it could be most useful to understand whether the person leading the session is disability aware and friendly. This becomes a question customer experience too.

#### Queries about the scope of accessibility requirements

We discussed accessibility/suitability of a particular event vs the accessibility of the venue vs the accessibility of the activity type vs the provision of equipment: for example ‘is there a racing wheelchair or an adapted boat’ available. We felt that this could live in the free text field, as having the equipment available is not something people would necessarily expect to be able to filter results on, and this would stay in line with the rest of the spec which groups equipment in free text fields. We noted Active Places does has equipment fields based on location.

#### Queries about the process

It was asked whether the categories and wording been run past people with disabilities and/or there had been a formal consultation? The ODI hasn’t run a consultation, but have worked with organisations such as Activity Alliance who do, and have used wording suggested by them. Disabilities Rights can create focus groups (which don’t focus on sports, ideal for our aims of getting inactive people active) and recommend carrying out direct consultation, from the beginning. We think we have enough suggestions and data to be able to test with users. We want to understand whether these are the categories people want and also to understand how inaccurate data is going to affect people’s uptake of activities.

It would also be useful to do some testing/research with data providers - how do they react to the number of choices and is it information they are comfortable providing?

We asked what what other organisations are currently doing:

* the British Paralympic Association have tried to tackle this and find the Paralympic categorisations are too specific in some areas and don’t cover all the areas that consumers want. The existing categorisation looks to be like the level of detail required for their new website, and they are happy to feedback their experience of using the categorisation to support this project.
* Richmond Group of Charities support a wide range of conditions. Some of their work is around message testing - could we do this at the same time? They will follow up and see what the call to action could be. They need to think about whether they want to work at the level of detail existing in the spec, or test some of the new proposals.

**Next steps**

1. Izy & Cecilia (Sport England) to touch base with Kirsty (Disability Rights) & Michelle (Richmond Group of Charities) as well as Activity Alliance and work out what might be best re: user testing/consultation with disability groups - and then Izy to feedback to the group.
2. The next call for the subject will be to review the results of that.

## &#x20;**Slides**&#x20;

{% embed url="<https://docs.google.com/presentation/d/1zYyz3vS8xegMI9Tt_q9tCciqseRns4VYPHtw8vQNlu0/edit#slide=id.p3>" %}

## Video&#x20;

{% embed url="<https://www.youtube.com/watch?v=9H3nvgBcSxY>" %}


# 2018-10-10 - Booking API Update and Feedback

Update on the booking API work and discussion on some of the issues that have come up in recent feedback

## Summary

A quick progress update on new developments:

* We have published the [V2.0 data model specification](https://www.openactive.io/modelling-opportunity-data/EditorsDraft/)
* Our [Validator ](https://www.validator.openactive.io)is up to date and conforms with the specification&#x20;
  * Open source, to be updated by the community as we continue to update the specifications
* We've launched our [Developer ](http://developer.openactive.io)site
  * Acts as a reference point for people who are starting to publish and use data as part of OpenActive
  * Aimed at developers, people looking to build applications against existing data feeds (knowledge of JSON and data model)
* We've made progress on our Booking API ([Booking 1.0 draft](https://www.openactive.io/open-booking-api/EditorsDraft/)), and understand that the community needs more time to explore the specification.&#x20;
  * We would like to collate feedback from practical use

We had a discussion on how to structure and approach the booking API flow, exploring anonymous leases, 2-phase commit options, alternative 2-phase commits, and two-step payment options. The discussion centred around community feedback and thoughts on how to approach the booking API flow. More detailed notes on the call can be found [on this link](https://docs.google.com/document/d/1lhPdIK3tcn3dV27DMvAhYU_7p9FcErQhaO65hEmEYpY/edit?usp=sharing).

## &#x20;Slides

{% embed url="<https://docs.google.com/presentation/d/1nBBwhY0MhqCWVA_pcrimjo9iWfXFC_lBeKZapJYQCRg/edit#slide=id.p3>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=HaswQ6T2hio>" %}


# 2018-09-12 - Booking API 1.0

Initial draft of Booking API 1.0, moving to formal publication

## Summary

We've just published an initial editors draft of the Open Booking API 1.0. The updated document can be found here:

<https://www.openactive.io/open-booking-api/EditorsDraft/index.html>

Changes include:

* Orders now contain arrays of orderedItems and acceptedOffers
* A richer set of error conditions
* Revised modelling on Order, Payment, Error and around where properties

  such as privacyPolicy, termsAndConditions and potentialAction sit
* Improved modelling and documentation relating to cancellation of events
* Introduction of webhook subscription for *brokers* to be notified of

  events cancelled by *booking systems*
* Moved to use validFrom/validThrough for Offer as it expresses the

  intent more clearly than availabilityStarts/availabilityEnds
* Improved modelling of free offers which brings it into line with

  Modelling Specification 2.0
* Finalised new Booking models for Error and Payment

We are publishing this draft so that we can collect comments and feedback from the community as early as possible.

Please review the latest document and file your feedback on github:

<https://github.com/openactive/open-booking-api/issues>

We'd like to get this published as a formal community group deliverable in the next 2-3 weeks.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1ijrA2aCZOtNTGNIT5o4ZrPmgW0KOe_Sl9_JKzg8rNOk/edit>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=8wZ5LZZTO_M>" %}


# 2018-08-30 - Modelling Event Types

## Summary

We discussed the changes to add new Event types. Additionally, an editors draft of the Modelling Opportunity Data specification 2.0 is now available for review.

<https://www.openactive.io/modelling-opportunity-data/EditorsDraft/>

The specification includes a number of improvements and updates which we've discussed in our recent community group calls and via proposals on github.

The key changes are:

* stricter rules around required, recommended and optional fields for all

  areas of the model
* stricter conformance criteria that outline things that publishers and

  consumers MUST, MUST NOT, SHOULD and SHOULD NOT do when publishing and

  processing data
* clearer discussion of use of parent-child relationships between events

  (Section 5.5.7)
* a new set of Event types to help provide more context around different

  types of event (Section 5.5.8)
* better documentation for event schedules and how to apply these (Section

  5.5.9)
* expanded section on extending the model (Section 5.12)
* removal of Activity Opportunity ahead of adding support for Routes
* changes to the URLs used for the OpenActive context
* various minor text clarifications and improvements

Given the substantial number of changes in this revision, and the pending discussion around the data model for Routes, this will be deferred to a later release (2.x).

To help move this forward please provide feedback on the draft document by 13th September. Please submit feedback directly to Leigh or as github issues, indicating the change(s) you'd like to see at:

<https://github.com/openactive/modelling-opportunity-data/issues>

## Slides

{% embed url="<https://docs.google.com/presentation/d/18vtVRu-kvZDjIukv3j-zjI2bQVC8xRDVijsWGjzqZNE/edit?usp=sharing>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=6sSAYH49D-4>" %}


# 2018-08-15 - Booking

## Summary

We reviewed progress on the booking API specification and several recent additions, including:

* Support for exposing terms and conditions and privacy notices
* Support for cancellations and refunds

The key conclusions are that:

* we need to add support for privacy notices, in addition to terms and conditions
* we should consider how best to provide this, often service level information, in ways that minimises repetition of data
* we need to support marketing opt-in information
* we need to be careful around conformance language re: marketing opt-in, etc to ensure that we are inline with current GDPR and marketing email guidance
* that as not all platforms support refunds, we cannot mandate refund/cancellation support, but it will be recommended
* there is a need to include windows during which cancellations/refunds can be accepted, and whether cancellations are allowed, to improve user experience of bookings
* we also agreed to review how URL discovery is currently specified to ensure we're avoiding need to replicate data in feeds

## Slides

{% embed url="<https://docs.google.com/presentation/d/1VEsicULV18n2NOKKw-Vl7V8z9dKcTWfVdDsw9YrBJWI/edit>" %}

## Video

{% embed url="<https://youtu.be/rOoIPFNDgXw>" %}


# 2018-08-01 - Routes, Model V2

## Summary

The main focus for this call was the Routes proposal:

<https://github.com/openactive/modelling-opportunity-data/issues/108>

We're aiming to include this in the 2.0 release of the data model.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1b3uqM6eSt7FMawl6VftSU_tsuoJRznf8JHsoXXq5hgE/edit>" %}

## Video

{% embed url="<https://youtu.be/3m2_S8IFeZY>" %}




---

[Next Page](/llms-full.txt/1)