Skip to content

Decide whether canonical schema should carry team logos and goal-scorer events #10

Description

@paulyhedral

The bundesliga-reference-plugin change (FullTime-Plugin-Bundesliga) ran a side-by-side
live-network validation of this plugin's output against openligadb's direct client output,
both mapped through the canonical schema
(openspec/changes/bundesliga-reference-plugin/design.md, "Fields openligadb Provides
That the Canonical Schema Doesn't Carry"). Every canonical field matched; the following
upstream fields have no canonical-schema home and are dropped:

  • Team/TableTeam::icon_url (team logo URL)
  • Team::group (upstream team grouping label, distinct from match/round grouping)
  • League::sport
  • Match's league-identifying fields (league_id, league_name, league_season,
    league_shortcut, time_zone) — redundant for a single-league plugin, but would matter
    for a multi-league consumer
  • Match::last_update
  • Match::results's non-final entries (halftime, etc.)
  • Match::goals (individual goal events: scorer, minute, penalty/own-goal flags)
  • Location::city

None of these block the Bundesliga reference plugin — every field the canonical schema
currently defines is fully populated and verified. This issue is to decide whether any of
these should be added to the canonical league-data-schema, most plausibly team logos and
goal-scorer events for UI needs. No urgency; closing without action (schema stays as-is) is
a valid outcome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions