← Catalogue
World Models · legacy example

Sport Games & Recreation

This meta-model describes the world of organized sport and informal recreation: the disciplines people play and the rules that codify them, the leagues and competitions that structure play into seasons, fixtures, results and records, and the participation of teams, athletes and casual players. It is its own model because competitive sport has a distinctive lifecycle (sanctioning, seasons, fixtures, results, standings, records) that no generic event or organization model captures, while recreation adds a non-competitive participation dimension of its own.

AI YAMLAGENTS.mdSource
IDworld.d5-sport-games-and-recreation
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domaincivilization
Tagssport, games, recreation
Data structure

Bundles and layers

Bundle

discipline

What sports exist and how play is codified

Layers

sportTaxonomy`: sports, disciplines and their family tree · `ruleset`: codified rules of play, formats, scoring systems

Bundle

competition

Organized competitive play and its outcomes

Layers

league`: leagues, divisions, seasons and sanctioning · `fixture`: scheduled competitions, matches and staging · `result`: results, standings, records and rankings

Bundle

participation

Who plays, competitively or for leisure

Layers

athleteAndTeam`: teams, rosters and competitor roles · `recreationalActivity`: casual, amateur and club-level activity

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.organization` (O1): federations, leagues, clubs and organizing bodies are organizations; this model holds only their sporting roles
  • REFERENCE `world.person` (H1): athletes, officials and recreational participants resolve to natural persons; no personal attributes are copied
  • REFERENCE `world.buildingAndFacility` (U): stadiums, halls and grounds are facilities of the built environment; fixtures hold facility references only
  • REFERENCE `world.tourismHospitality` (D7): major competitions appear as visitor experiences in the tourism model
  • imports: SportsML (ALIGN): event, fixture and result vocabulary for sports data exchange
  • imports: schema.org (ALIGN): SportsEvent, SportsTeam and SportsActivityLocation typing for public projections

Canon, patches & standards

  • REFERENCE `world.organization` (O1): federations, leagues, clubs and organizing bodies are organizations; this model holds only their sporting roles
  • REFERENCE `world.person` (H1): athletes, officials and recreational participants resolve to natural persons; no personal attributes are copied
  • REFERENCE `world.buildingAndFacility` (U): stadiums, halls and grounds are facilities of the built environment; fixtures hold facility references only
  • REFERENCE `world.tourismHospitality` (D7): major competitions appear as visitor experiences in the tourism model
  • imports: SportsML (ALIGN): event, fixture and result vocabulary for sports data exchange
  • imports: schema.org (ALIGN): SportsEvent, SportsTeam and SportsActivityLocation typing for public projections

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `resultsFeedContract`: licensed distribution of live and final results to media and data consumers
  • `historicalStatisticsAccess`: research and almanac access to standings, records and season archives
  • `fixtureSyndication`: redistribution of fixture calendars with staging and ticketing pointers

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

Organizing bodies (federations, leagues, clubs) steward the layers they sanction: rulesets, seasons, fixtures and verified results. Roster and participation data concerning a person is disclosed only under that person's grant, with access always issued by the respective owner through the catalogue's S1/S2 ownership and access models and audited via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `sport`: a recognized sport or discipline; key attributes: name, family, discipline codes, governing federation reference
  • `ruleset`: a codified body of rules for a sport; key attributes: version, format, scoring system, sanctioning body reference
  • `league`: a standing competitive structure; key attributes: name, sport, tier, divisions, organizer reference
  • `season`: a bounded competitive cycle of a league; key attributes: start, end, format, promotion and relegation rules
  • `competition`: a sanctioned competitive event, from a tournament down to a single race; key attributes: type, stage structure, sanctioning status
  • `fixture`: a scheduled contest between competitors; key attributes: date, venue reference, competitors, officials
  • `result`: the recorded outcome of a fixture or competition; key attributes: score, placements, records touched, verification status
  • `team`: a competing collective with a roster; key attributes: name, club or organization reference, roster window
  • `recreationalActivity`: a non-competitive practiced activity; key attributes: activity type, setting, regularity, facility reference

Relationships

  • `sport` -> codifiedBy -> `ruleset` (1..n): each sport is governed by one or more versioned rulesets
  • `league` -> runsSeason -> `season` (1..n): a league is realized as a sequence of seasons
  • `competition` -> partOf -> `season` (n..1): competitions and rounds sit inside a season's calendar
  • `fixture` -> producedResult -> `result` (1..0..1): a played fixture yields at most one verified result
  • `team` -> competedIn -> `fixture` (n..m): teams and individual competitors meet in fixtures
  • `team` -> rosters -> `person` (n..m): roster slots resolve to natural persons in H1; only the role linkage lives here
  • `fixture` -> stagedAt -> `facility` (n..1): staging resolves to a sports facility governed by the built-environment model (U)
  • `recreationalActivity` -> practicedBy -> `person` (n..m): leisure participation, held at the participant's discretion

Events

  • `competitionSanctioned`: an organizing body approved a competition under a ruleset
  • `seasonOpened`: a league season began and its fixture calendar became binding
  • `fixturePlayed`: a scheduled contest took place
  • `resultRecorded`: an outcome was verified and entered into standings
  • `recordSet`: a performance surpassed a recognized record for the discipline
  • `teamRegistered`: a team entered a league or competition with a declared roster
  • `seasonClosed`: final standings were fixed and promotions or relegations applied

Projections

  • `publicStandingsBoard`: current standings and results per league; omits roster personal data and officials' details
  • `fixtureCalendar`: upcoming fixtures with venues; omits results processing and verification state
  • `sportAlmanac`: historical records and season archives; omits in-progress seasons and unverified results