This group's mission is to discuss and prepare data and API specifications which facilitate the use of open and shared data relating to sport and physical activity. We have so far used http://www.openactive.io (along with https://github.com/openactive and Google Docs) to facilitate our work, supported by the Open Data Institute, and created an initial set of specifications within our open group of organisations. We would now like to progress our group to become a W3C CG, sharing our work with the wider community. The group will base its work on existing standards as much as possible, and re-use existing terms wherever appropriate. The group will seek consensus around, and support for, these specifications which may then be brought to an appropriate Working Group to advance a specification from draft to standard. The group will seek to coordinate as appropriate with the Web Schemas Task Force of the Semantic Web Interest Group and other relevant groups within the W3C.
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Over the coming weeks we’ll continue to hold our regular community hangouts. These have all been recorded and available on YouTube. By working in the open in this way we help to keep a record of our discussions and progress, while allowing as many people as possible to be involved in the group’s activities. Here’s a summary of our discussion of yesterday’s meeting.
Over the coming weeks we’ll be doing more work in some specific areas, including:
How to standardise activity lists within the sector, to simplify data integration
Extending the specification to include details on support for disabilities at events. This is an important area and we’re going to take the time to focus on this and ensure its done correctly
Starting to capture requirements around event attendance, availability and booking
Producing more guidance around how to publish opportunity data
Welcome to the OpenActive Community Group! This post provides a short introduction to the group, covering its scope, initial roadmap and some notes on how to get involved.
Supported by Sport England, the Open Data Institute is collaborating with the sports sector to help activity providers produce openly available data on what, where and when physical activity sessions are happening. This data, which won’t include any personal information, will be open for anyone to access, use and share.
By making more data available, in consistent easy to use formats, we can support the creation of a new range of products and services. Ultimately we want more people to be more active.
To achieve this we need to create open specifications that describe how to publish and share data for reuse in the sector. We will be using this community group to co-ordinate that activity.
Why use a W3C community group?
Community groups are designed to promote innovation and allow anyone to contribute to the development of community specifications.
A W3C community group is the ideal place to co-ordinate this type of activity which benefits from an open, neutral environment that can bring together people from across a sector.
We also plan to hold regular community hangouts to facilitate discussion and feedback. These will be advertised on the list and will also be open to everyone. We’ll also post status updates and news on the technical work on this blog.
What is the scope of the group’s activities?
In order to publish and share physical activity data we need to:
Specify how to describe activities by agreeing on a basic model for events and how to describe them
Define how to publish data for others to reuse, e.g. via APIs, standard data formats and mark-up embedded in web pages
And, eventually, how to book activities so that people can sign-up to the events they’re interested in
The sports activity sector is very diverse. Data is held in large scale leisure management systems and also shared via individual websites, meetup groups, etc. We need to be working towards supporting the breadth of that community.
The specifications we create will build as far as possible on existing standards and technologies, e.g. Schema.org, etc.