Skip to content

Meeting 2022 02 08

Jump to bottom
Martin Alvarez-Espinar edited this page Feb 8, 2022 · 3 revisions

Title: Virtual Meeting Open Athletics

When / Where

Agenda

  1. UCI API Overview - Eddy V.
  2. Evolution of the WA's draft - Martin + all
  3. AOB

Minutes

Intro and Housekeeping

  • Introduction of new members: Margus H (Sportity)

UCI API Presentation

[Eddy V. presented the UCI BWS API with real examples oriented to velodrome]

[Eddy explained the API in detail, focused on the unique UCI IDs (long integers) to identify riders]

  • Example of filtering of Tom Pidcock -> not found because his name is Thomas
  • But there is a unique UCIID for all riders -> long integer for the ID for UCI
  • The Swagger documentation very complete and easy to use.
  • Eddy showed some examples of mistakes in the data (e.g., wrong IDs or quotation marks in the name fields)
  • UCI-ID is the base for the centralized data
  • The registration of riders in competitions is based on their UCI-ID

[Discussion after the presentation]

  • The disciplines (types of events) are based on predefined plain texts in English.

  • There is a clear similarity of cycling and athletics. Perhaps the difference is the number of athletes

  • Service providers discover athletes from the UCI ID

  • Athletics is different, top level federations discover the data after registrations, not at the beginning of the season.

  • Could be feasible national federations to submit to WA the athletes to populate their federations?

  • It's difficult but it could be great if WA would provide an API for the member federations to submit their athletes beforehand. The API could return the list of WAID's so the national federations could identify their athletes with the "universal ID".

  • We could create a pilot with some federations to see if this could be feasible.

Evolution of the WA's model

[Martin introduced the latest changes in the specification] [Questions raised and discussion for the refinement of the model]

Proposals:

  • Competition Unit: to include a new field gender to define the category according to sex and age.

  • Competition Unit: to include a new field discipline

    • discipline (type of event): to define a taxonomy with the official (and most common) ones

  • To include a flag to indicate if competition is held outdoors or indoors -> We could use the existing discipline model.

  • Change term Race -> EventUnit (to include field events)

  • Change term RelayTeam -> Team (to include non-relay team events)

  • Change term RelayResult -> TeamResult (to include non-relay team events)

  • Change term number in Race -> order (more clear)

  • IndividualResults: to include a new array of strings with the features related to results (e.g., RC, >,...)

  • Round: To add new field order (integer), to indicate the index of the rounds in a competition.

  • Proposal to explore the possibility to define results in numeric format (for better processing).

AOB

Clone this wiki locally