Candidate Specification of Modelling Opportunity Data 2.0 - please comment by 13th September

Hi,

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. At this point we will formally publish this as the new
version of the specification.

Please submit feedback as github issues, indicating the change(s) you'd
like to see at:

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

(If you're uncomfortable using github then send feedback directly to me).

Please be as clear as possible with your feedback, ideally providing
revised wording and/or identifying how you'd recommend changing the
specification.

As a reminder, if you have no specific comments on the specification an
email or note to say you're happy with the changes will also help us
demonstrate support for the proposed changes.

Our community group call on 12th September will be used to resolve any
outstanding issues.

In our call today we discussed the changes to add new Event types. There's
a summary of that in the slides here. The feedback from today's call has
already been included in the draft specification:

https://docs.google.com/presentation/d/18vtVRu-kvZDjIukv3j-zjI2bQVC8xRDVijsWGjzqZNE/edit?usp=sharing

Thank for you all of you who have provided input so far. This is a
substantial piece of work that along with the validator will greatly
improve the quality and consistently of the open data.

Cheers,

L.

-- 
Leigh Dodds, Data Infrastructure Programme Lead, theodi.org
@ldodds
The ODI, 65 Clifton Street, London EC2A 4JE