activity
, location
and startDate
specified: so a Yoga class in Downtown Leisure Centre, at 7pm, on a Tuesday. See here for further clarification of the types available. EventSeries
, SessionSeries
, and ScheduledSession
, linked via the superEvent
and subEvent
properties. These are described by example in the diagram below:ScheduledSession
will inherit the properties of the SessionSeries
, and the SessionSeries
will inherit the properties of the EventSeries
.EventSeries
is not supplied, its details must be included on the SessionSeries
.EventSeries
, SessionSeries
, and ScheduledSession
. These are described by example in the diagram below:SessionSeries
must always be supplied, including details that would otherwise be present in an EventSeries
if no EventSeries
is supplied.ScheduledSession
must be supplied, either embedded, within a separate feed, or generated through a Schedule
.EventSeries
should be used to group these together. This avoids seemingly duplicate search results from a single provider. ScheduledSession
may be embedded in the SessionSeries
or visa versa.ScheduledSession
is highly recommended to be provided in a separate feed to the SessionSeries
. This will reduce data transfer volumes significantly.EventSeries
is unlikely to change frequently enough compared with the SessionSeries
to warrant its own feed, and so can usually be embedded in the SessionSeries
.@id
and superEvent
for split feeds@id
must be used.@id
is a globally unique identifier which must be in URL format for the purposes of namespacing. The @id
does not need to resolve to a functional endpoint, but must use a domain name controlled by the organization or system publishing the data. See here for more information.@id
, such as:"https://id.ourparks.org.uk/api/session-series/1234
"
SessionSeries
feed, the SessionSeries
@id
is defined for each data item:ScheduledSession
feed, that SessionSeries
@id
is referenced by the superEvent
property:EventSeries
and Event
, linked via the superEvent
and subEvent
properties. These are described by example in the diagram below:EventSeries
.EventSeries
is not supplied, its details must be included on the Event
.EventSeries
if no EventSeries
is supplied.EventSeries
should be used to group these together. This avoids seemingly duplicate search results from a single provider.Event
s in stand-alone feeds separate from ScheduledSessions
and SessionSeries
.EventSeries
is unlikely to change frequently enough compared with the Event
to warrant its own feed, and so can usually be embedded in the Event
.activity
andlocation
specified, where the activity can be booked in slots: so a Tennis at Downtown Leisure Centre with slots available hourly from 8am until 8pm.FacilityUse
represents "Badminton at Downtown Leisure Centre", where as IndividualFacilityUse
is "Court 2 in Sports Hall 3 for Badminton at Towntown Leisure Centre".FacilityUse
/IndividualFacilityUse
and Slot
, linked via the facilityUse
and event
properties.http://www.example.org/feeds/facility-uses
http://www.example.org/feeds/individual-facility-use-slots
Slot
availability at the IndividualFacilityUse
level, which is now recommended for all new feeds.@id
and facilityUse
for split feeds@id
must be used.@id
is a globally unique identifier which must be in URL format for the purposes of namespacing. The @id
does not need to resolve to a functional endpoint, but must use a domain name controlled by the organization or system publishing the data. See here for more information.@id
, such as:"https://id.bookingsystem.com/api/facility-uses/1402CBP20150217/individual-facility-uses/1
"
FacilityUse
feed, the FacilityUse
@id
is defined for each data item, and IndividualFacilityUse
@id
values are defined within these:Slot
feed, that IndividualFacilityUse
@id
is referenced by the facilityUse
property:HeadlineEvent
can be used to represent whole day or multi-day events, such as mass participation events, family fun days, etc.HeadlineEvent
(for the overall event) and Event
(for small events within the overall event) linked via the superEvent
and subEvent
properties.CourseInstance
(for the whole course) and Event
(for the individual occurrences) linked via the superEvent
and subEvent
properties.superEvent
and subEvent
properties, with the exception of:FacilityUse
/IndividualFacilityUse
and Slot
, which are linked via the facilityUse
and event
properties FacilityUse
and IndividualFacilityUse
, which are linked via the aggregateFacilityUse
and individualFacilityUse
properties.EventSeries
, SessionSeries
, ScheduledSession
, HeadlineEvent
, CourseInstance
, and Slot
all sub-class Event
.