Skip to content
Andrew Wanczowski edited this page Dec 20, 2022 · 12 revisions

Welcome to the sport-model wiki!

Here is where we are collecting our work towards "the next generation of SportsML", which may not even be called SportsML any more...

Scope

We are creating an RDF model that represents schedules, statistics and results for all levels of all sports, for both human and machine consumption.

Participants

Please add your name and/or fix your details here.

  • Paul Kelly - product consultant, lead of Sports Content Working Group
  • Silver Oliver - data architect at Data Language
  • Nathan Matten - XML Team
  • Jim Howard - product consultant
  • Paul Wilton - data architect at Data Language
  • Drew Wanczowski - Principal Solutions Engineer at MarkLogic
  • Brendan Quinn - Managing Director at IPTC

Background and motivation

We (mostly Jim Howard) have developed a document showing what could be done with a semantic sports model in the future:

Read it here: IPTC Sport Development

To help prioritise our development, we have developed some Use Cases - mostly sample questions that people would want to ask of sports data.

We are using these to define the scope and prioritise our work and to explore the complexity of different implementation options.

Requirements

  • plays well with other vocabularies
  • works on the web (i.e. schema.org)
  • can generalize and map other proprietary formats (IOC, OPTA, STATS, etc.)
  • plays well with current dev tech (i.e. GraphQL)
  • flexible regarding format (json, xml, ttl, etc.)

Modelling and Format

Initial attempts with RDF model using Turtle format

Turtle and SPARQL samples

Design Approaches

Generic versus Specific

Generic
Specific
  • brevity (data and query code)
  • data typing
  • IDs readymade