What should an unavailable live-data source tell me about what I can conclude?

Do not turn missing data into a score or event status

Live event state separates status detail, score, clock and the basis for a status. A missing scoreboard state can leave the detail unknown and the clock or score null. Those values are not equivalent to a zero score or a confirmed no-game state.

If a schedule or current in-play price supplies a limited status basis, that fact should be read as its own source. It does not manufacture a live scoreboard, score or running clock.

• Treat missing score or clock data as unknown, not zero.
• Do not infer final, suspended or no-game from a feed failure alone.
• Check which source basis, if any, supports the event state.

Use only the facts that the available source supports

A scheduled start can provide schedule context, and an in-play price can provide a limited started-state basis. The scoreboard supplies its own status detail. If that source is stale or unavailable, do not treat an alternate basis as proof of current score or play-by-play state.

A missing live source also does not identify why it failed or promise when it will return. Keep the event's unconfirmed facts unresolved rather than making up standings or outcomes.

Illustrative example: schedule information without a live score

Imagine a fictional event whose scheduled start is known while the scoreboard source is unavailable. The schedule may supply timing context, but the missing scoreboard does not establish a score of zero or confirm that play is underway. The reader leaves live score and clock unknown until a source supports them. No real event or status is represented.

Related questions

Sources and further reading

• BSD public features overview

Continue reading

• Explore BSD features