Updated OpenActive Modelling Opportunity Data Specification

Dear OpenActive community,

We are pleased to announce a revised Editors Draft (version 2.1)
<https://openactive.io/modelling-opportunity-data/EditorsDraft/> of the
OpenActive Modelling Opportunity Data specification.

The editors draft includes non-breaking changes that will have no impact on
existing data feeds and applications. The full implementation of OpenActive
enables a seamless end-to-end discovery and booking of opportunities - and
this is very much still the prime focus of the specification.

Summary of changes:

1) Enabling organiser (or club) level data feeds

Over the last few years, we have discussed the lack of a standard means to
share information about organisations that provide opportunities for sport
and physical activity.

Over the last 12 months, we have explored how the OpenActive opportunity
data specification can support this. For more background, see the
discussion under the issue ‘Proposal: Enabling Club Finder capability’
<https://github.com/openactive/modelling-opportunity-data/issues/313>.

The changes to reflect organiser level feeds are non-breaking changes. They
mainly consist of edits to reflect the idea that a club providing
activities can be considered an 'opportunity' even if the details of
specific dated and timed events are not published, or not yet published.
Some introductory text in the abstract explains this.

2) Earlier work in the Editors Draft to incorporate the Route Guide
specification has been amended to point to the standalone specification
<https://openactive.io/route-guide/EditorsDraft/> and to indicate for
example how a route guide could be attached to a 'guided walk' event. This
has been done to reduce the size and complexity of the opportunity
specification and to allow the Route Guide specification to evolve at its
own pace.

3) The data model image has been updated to reflect events linked to route
guides and organisers linked to activities.

4) To avoid confusion and simplify editing, in the specification we use
Organizers and Organization throughout (rather than mixing in Organisers
and Organisations). This aligns with schema.org, the basis of the
OpenActive specification.

As per our usual process, we will now pilot these changes and seek feedback
from the community before convening a W3C Community Group session to
approve an update to the published Final Community Group Report.

Regards,
Howard

*Howard Askew (he/him), Senior Data Technologist *@ theODI.org
<http://theodi.org/>
ODI, 4th Floor, Kings Place, 90 York Way, London, N1 9AG
<https://www.google.co.uk/maps/place/Kings+Place+Box+Office/@51.5349572,-0.1238635,17z/data=!3m1!4b1!4m5!3m4!1s0x48761b3e69e594f5:0x7075953fb01bfd7c!8m2!3d51.5349539!4d-0.1216748>