Add FitTrybe dataset site

[franschezco]

Publishing Checklist

I confirm the following:

• My open data feeds conform to one of the permissable combinations specified in https://developer.openactive.io/publishing-data/data-feeds/types-of-feed
• My open data feeds all pass the OpenActive Validator's model validation (https://validator.openactive.io/)
• My open data feeds all pass the OpenActive Validator's RPDE feed validation (https://validator.openactive.io/rpde)
• My open data feeds all pass the OpenActive Test Suite's deep validation (https://developer.openactive.io/publishing-data/data-feeds/testing-feeds#openactive-test-suite)
• My open data feeds include activity list references as specified in https://developer.openactive.io/publishing-data/activity-list-references
• My dataset site(s) each reference a GitHub Issues Board
• I have checked that the times in the feed startDate and endDate match the times on the website referenced by the url, and can confirm that there are no timezone issues

Maintenance Checklist

Our organisation is committed to:

• Ensuring activity providers are aware of the OpenActive initiative on an ongoing basis
• Providing high quality opportunity data that meets user needs, as specified in OpenActive's Data Quality reporting framework
• Resolving issues that are raised on the GitHub Issues Board(s)

[franschezco]

checked

[hkir-dev]

Thank you for your interest in Open Active. There are a few points to address before we can merge this:

1- superEvent and subEvent references point at the wrong records

In the ScheduledSession feed, superEvent is built from the ScheduledSession's own UUID:

"@id":        ".../openactive-scheduled-sessions?id=082029a1-3d96-43cc-aa13-c7b3739dc2b0"
"superEvent": ".../openactive-session-series?id=082029a1-3d96-43cc-aa13-c7b3739dc2b0"   ← same UUID

superEvent must be the @id of the parent SessionSeries, not a session-series URL constructed from the child's ID. This issue also exists in the SessionSeries subEvent references.

2- Please remove subEvent from the SessionSeries feed
Split feeds are the recommended configuration, and the combined patterns are no longer recommended for new implementations.

The expected shape would be:

// SessionSeries feed — no subEvent
{ "@type": "SessionSeries", "@id": "https://.../session-series/b8fd16d2-...", ... }

// ScheduledSession feed
{ "@type": "ScheduledSession",
  "@id": "https://.../scheduled-sessions/082029a1-...",
  "superEvent": "https://.../session-series/b8fd16d2-...", ... }

3- Suggestion: use PostalAddress for the address
Rather than putting the address in description, it could be represented as a structured PostalAddress:

"address": {
  "@type": "PostalAddress",
  "streetAddress": "East St",
  "addressLocality": "Epsom",
  "addressRegion": "Surrey",
  "postalCode": "KT17 1BN",
  "addressCountry": "GB"
}

4- Please also check the startDate/endDate values
The subEvents currently included in the SesssionSeries feed (which we aim to remove) are dated 2026-06-27, while the corresponding ScheduledSessionss are dated 2026-02-21. Could you please confirm whether these dates are correct?

Thanks again for the contribution!