Table of content

Table of content 2

1   Introduction   3

1.1.. This document 3

1.2.. Objective. 3

1.3.. Main Audience. 3

1.4.. Glossary. 3

1.5.. Related Documents. 3

2   Overall Perspective  3

2.1.. Objective. 3

2.2.. End to End data flow. 3

3   Messages  3

3.1.. Applicable Messages. 3

3.2.. Messages. 3

3.2.1... List of participants by discipline / List of participants by discipline Update. 3

3.2.1.1    Description. 3

3.2.1.2    Header Values. 3

3.2.1.2.1     PiT Header 3

3.2.1.3    Trigger and Frequency. 3

3.2.1.3.1     PiT Triggers. 3

3.2.1.4    Message Structure. 3

3.2.1.5    Message Values. 3

3.2.1.6    Message Sort 3

3.2.2... List of teams / List of teams update. 3

3.2.2.1    Description. 3

3.2.2.2    Header Values. 3

3.2.2.2.1     PiT Header 3

3.2.2.3    Trigger and Frequency. 3

3.2.2.3.1     PiT Triggers. 3

3.2.2.4    Message Structure. 3

3.2.2.5    Message Values. 3

3.2.2.6    Message Sort 3

3.2.3... Historical records. 3

3.2.3.1    Description. 3

3.2.3.2    Header Values. 3

3.2.3.2.1     PiT Header 3

3.2.3.3    Trigger and Frequency. 3

3.2.3.3.1     PiT Triggers. 3

3.2.3.4    Message Structure. 3

3.2.3.5    Message Values. 3

3.2.3.6    Message Sort 3

3.2.4... Start List 3

3.2.4.1    Description. 3

3.2.4.2    Header Values. 3

3.2.4.2.1     PiT Header 3

3.2.4.3    Trigger and Frequency. 3

3.2.4.3.1     PiT Triggers. 3

3.2.4.4    Message Structure. 3

3.2.4.5    Message Values. 3

3.2.4.6    Message Sort 3

3.2.5... Event Unit Results. 3

3.2.5.1    Description. 3

3.2.5.2    Header Values. 3

3.2.5.2.1     PiT Header 3

3.2.5.2.2     RT Header 3

3.2.5.3    Trigger and Frequency. 3

3.2.5.3.1     PiT Triggers. 3

3.2.5.3.2     RT Triggers. 3

3.2.5.4    Message Structure. 3

3.2.5.5    Message Values. 3

3.2.5.6    Message Sort 3

3.2.6... Phase Results. 3

3.2.6.1    Description. 3

3.2.6.2    Header Values. 3

3.2.6.2.1     PiT Header 3

3.2.6.2.2     RT Header 3

3.2.6.3    Trigger and Frequency. 3

3.2.6.3.1     PiT Triggers. 3

3.2.6.3.2     RT Triggers. 3

3.2.6.4    Message Structure. 3

3.2.6.5    Message Values. 3

3.2.6.6    Message Sort 3

3.2.7... Cumulative Results. 3

3.2.7.1    Description. 3

3.2.7.2    Header Values. 3

3.2.7.2.1     PiT Header 3

3.2.7.2.2     RT Header 3

3.2.7.3    Trigger and Frequency. 3

3.2.7.3.1     PiT Triggers. 3

3.2.7.3.2     RT Triggers. 3

3.2.7.4    Message Structure. 3

3.2.7.5    Message Values. 3

3.2.7.6    Message Sort 3

3.2.8... Event Final Ranking. 3

3.2.8.1    Description. 3

3.2.8.2    Header Values. 3

3.2.8.2.1     PiT Header 3

3.2.8.3    Trigger and Frequency. 3

3.2.8.3.1     PiT Triggers. 3

3.2.8.4    Message Structure. 3

3.2.8.5    Message Values. 3

3.2.8.6    Message Sort 3

3.2.9... Event’s Medallists. 3

3.2.9.1    Description. 3

3.2.9.2    Header Values. 3

3.2.9.2.1     PiT Header 3

3.2.9.3    Trigger and Frequency. 3

3.2.9.3.1     PiT Triggers. 3

3.2.9.4    Message Structure. 3

3.2.9.5    Message Values. 3

3.2.9.6    Message Sort 3

3.2.10   Records. 3

3.2.10.1  Description. 3

3.2.10.2  Header Values. 3

3.2.10.2.1     PiT Header 3

3.2.10.3  Trigger and Frequency. 3

3.2.10.3.1     PiT Triggers. 3

3.2.10.4  Message Structure. 3

3.2.10.5  Message Values. 3

3.2.10.6  Message Sort 3

3.2.11   Brackets. 3

3.2.11.1  Description. 3

3.2.11.2  Header Values. 3

3.2.11.2.1     PiT Header 3

3.2.11.3  Trigger and Frequency. 3

3.2.11.3.1     PiT Triggers. 3

3.2.11.4  Message Structure. 3

3.2.11.5  Message Values. 3

3.2.11.6  Message Sort 3

3.2.12   Discipline Configuration. 3

3.2.12.1  Description. 3

3.2.12.2  Header Values. 3

3.2.12.2.1     PiT Header 3

3.2.12.3  Trigger and Frequency. 3

3.2.12.3.1     PiT Triggers. 3

3.2.12.4  Message Structure. 3

3.2.12.5  Message Values. 3

3.2.12.6  Message Sort 3

3.2.13   Event Unit Weather Conditions. 3

3.2.13.1  Description. 3

3.2.13.2  Header Values. 3

3.2.13.2.1     PiT Header 3

3.2.13.3  Trigger and Frequency. 3

3.2.13.3.1     PiT Triggers. 3

3.2.13.4  Message Structure. 3

3.2.13.5  Message Values. 3

3.2.13.6  Message Sort 3

4   Messages Sequence  3

5   Codes  3

5.1.. Global Codes. 3

5.2.. Speed Skating Codes. 3

6   General definitions  3

6.1.. ODF Message Structure. 3

6.1.1... ODF Declaration. 3

6.1.2... ODF Header 3

6.1.3... ODF Body. 3

6.2.. ODF Data Types and Formats. 3

6.2.1... Rules for rounding numbers. 3

6.2.2... Measures format 3

6.2.3... Rules for measures conversion. 3

6.3.. ODF Message Update. 3

7   DOCUMENT CONTROL   3

7.1.. File Reference. 3

7.2.. Version history. 3

7.3.. Change Log. 3

 

1   Introduction

1.1  This document

This document includes the ODF Speed Skating Data Dictionary. This document refines the messages described in the ODF General Messages Interface Document specifically for Speed Skating, as well as defines the codes used in these messages.

1.2  Objective

The objective of this document is to provide a complete and formal definition of the ODF Speed Skating Data Dictionary, with the intention that the information message producer and the message consumer can successfully interchange the information as the Speed Skating competition is run.

1.3  Main Audience

The main audience of this document is the IOC as the ODF promoter, ODF users such as the World News Press Agencies, Rights Holding Broadcasters and International Sports Federations.

1.4  Glossary

The following abbreviations are used in this document

Acronym

Description

IF or International Federation

The international governing body of an Olympic Sport as recognized by the IOC

IOC

International Olympic Committee

IPC

International Paralympic Committee

NOC

National Olympic Committee recognized as such by the IOC

NPC

National Paralympic Committee as recognized by the IPC

ODF

Olympic Data Feed

ODF Light

It is a type of ODF message that includes extensions to standard ODF messages in order to resolve references between messages and common codes. These extensions facilitate the message processing for ODF customers

ODF-PiT

Olympic Data Feed Point in Time, messages that are generated at certain point during competition

ODF-RT

Olympic Data Feed Real Time, messages that are generated when available

OPNS

Olympic and Paralympic News Service

RSC

Results System Codes, determine uniquely one unit of the competition, specifying the discipline, gender, event, phase and unit.

Sport

is administered by an international federation and can be composed of one or more disciplines

WNPA

World News Press Agencies

 

 

 


 

1.5  Related Documents

 

Document Reference

Document Title

Document Description

ODF/INT001

ODF Message Transmission Document

This document describes the technical standards to be used to transfer ODF messages between the message generators and the final ODF users

ODF/COD001

ODF Common Codes Document

This document describes the ODF codes used across the rest of the ODF documents

ODF/INT004

ODF General Messages Interface Document

This document describes the ODF general messages

 

 

2   Overall Perspective

2.1  Objective

The objective of this document is to focus on the formal definition of the ODF Speed Skating Data Dictionary.

2.2  End to End data flow

In the following chapters, for each ODF message the general description, header values, triggers and frequency, structure, values and sort of the message will be defined.


3   Messages

3.1  Applicable Messages

The following table is a full list of all ODF messages and describes the list of messages used in this sport.

 

   The column “Message type” indicates the DocumentType that identifies a message

 

   The column “Message name” is the message name identified by the message type

 

   The column “Feed” identifies the message feed (PiT for Point in Time messages, RT for Real Time messages and PDF for PDF messages)

 

   The column “Message extended in this document” indicates whether a particular message has extended definition in regards to those that are general for all sports. If one message has extended definition, it should be considered both, the extensions as well as the general rules for one message that is used in the case of the sport. However, if one particular message is not extended, then it should follow the general definition rules.

 

Message Type

Message Name

Feed

Message extended

DT_SCHEDULE

Competition schedule

PiT

 

DT_SCHEDULE_UPDATE

Competition schedule update

PiT

 

DT_PARTIC / DT_PARTIC_UPDATE

List of participants by discipline / List of participants by discipline Update

PiT

X

DT_PARTIC_TEAMS / DT_PARTIC_TEAMS_UPDATE

List of teams / List of teams update

PiT

X

DT_MEDALS

Medal standings

PiT

 

DT_MEDALLISTS_DAY

Medallists of the day

PiT

 

DT_HISTORIC_RECORD

Historical records

PiT

X

DT_GLOBAL_GM

Global good morning

PiT

 

DT_GLOBAL_GN

Global good night

PiT

 

DT_START_LIST

Start List

PiT

X

DT_RESULT

Event Unit Results

PiT/RT

X

DT_PHASE_RESULT

Phase Results

PiT/RT

X

DT_CUMULATIVE_RESULT

Cumulative Results

PiT/RT

X

DT_RANKING

Event Final Ranking

PiT

X

DT_MEDALLISTS

Event’s Medallists

PiT

X

DT_MEDALLISTS_DISCIPLINE

Medallists by discipline

PiT

 

DT_RECORD

Records

PiT

X

DT_COMMUNICATION

Official Communication

PiT

 

DT_BRACKETS

Brackets

PiT

X

DT_GM

Discipline/venue good morning

PiT

 

DT_GN

Discipline/venue good night

PiT

 

DT_CONFIG

Discipline Configuration

PiT

X

DT_WEATHER

Event Unit Weather Conditions

PiT

X

DT_SERIAL

List of Current PiT Serial

PiT

 

DT_RT_KA

RT Discipline/Venue keep alive

RT

 

DT_PDF

PDF Message

PDF

 

DT_PDF_GM

PDF Discipline/Venue good morning

PDF

 

DT_PDF_GN

PDF Discipline/Venue good night

PDF

 

DT_PDF_SERIAL

List of Current PDF Serial

PDF

 

DT_RT_GM

RT Discipline/venue good morning

RT

 

DT_RT_GN

RT Discipline/venue good night

RT

 

 

 

 

 


 

3.2  Messages

 

3.2.1    List of participants by discipline / List of participants by discipline Update

3.2.1.1  Description

A participant is considered as an individual competitor (type athlete, participating or not in the current games) or as an official in one or several disciplines or as a competitor being part of a team (team member).

 

Although the participant participates in more than one event or more than one discipline, this message just contains all the information for the discipline of the message, although listing the information of all the events for that discipline.

 

This message includes historical athletes that do not participate in the current competition. Historical athletes will not be registered to any event.

 

It is important to point out that all the sport messages that make references to athletes (start list, event unit results, etc.) will always match the athlete ID with the athlete ID as it is being sent in the List of athletes by discipline message. The historical athletes will be used to match historical athlete information as it is in the records message when sending the previous record information and this previous record was an historical record not being broken in the current competition.

 

This message also includes the historical team members of the historical teams’ messages. It could happen these historical athletes would appear in this message just for this reason (being part of historical teams).

 

List of participants by discipline (DT_PARTIC) is a bulk message, provided for each discipline. It is a complete participant information message for one particular discipline.  The arrival of this message resets all the previous participants’ information for one particular discipline. This message can include a list of current athletes, officials, coaches, guides, technical officials, Reserves and historical athletes.

 

List of participants by discipline update (DT_PARTIC_UPDATE) is an update message. It is not a complete list of participants’ information by discipline message, only the participant data being modified, i.e. if some data of one participant changes, the element Participant for it with all its children and attributes must mbe sent.

 

The key of the information updated consists of the following attribute: Participant @Code. Therefore, any new or updated Participant Discipline-Event will be identified by all these attributes.

 

 

3.2.1.2  Header Values

3.2.1.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD is defined according to CC @Discipline

DocumentType

DT_PARTIC / DT_PARTIC_UPDATE

List of participants  by discipline message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.1.3  Trigger and Frequency

3.2.1.3.1  PiT Triggers

The DT_PARTIC message is sent as a bulk message one month before the Games.

 

 It is sent several times up to the date from what only DT_PARTIC_UPDATE messages are sent.

 

 The DT_PARTIC_UPDATE message is triggered when there is a modification in a DT_PARTIC bulk message sent before.

 

 


3.2.1.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Participant (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Parent

 

 

 

 

 

Status

 

 

 

 

 

GivenName

 

 

 

 

 

FamilyName

 

 

 

 

 

PrintName

 

 

 

 

 

PrintInitialName

 

 

 

 

 

TVName

 

 

 

 

 

TVInitialName

 

 

 

 

 

Gender

 

 

 

 

 

Organisation

 

 

 

 

 

BirthDate

 

 

 

 

 

Height

 

 

 

 

 

Weight

 

 

 

 

 

PlaceofBirth

 

 

 

 

 

CountryofBirth

 

 

 

 

 

PlaceofResidence

 

 

 

 

 

CountryofResidence

 

 

 

 

 

Nationality

 

 

 

 

 

MainFunctionId

 

 

 

 

 

Current

 

 

 

 

 

OlympicSolidarity

 

 

 

 

 

ModificationIndicator

 

 

 

 

 

Discipline

 

 

 

 

 

 

Code

 

 

 

 

 

InternationalFederationId

 

 

 

 

 

RegisteredEvent (0,N)

 

 

 

 

 

 

Gender

 

 

 

 

 

Event

 

 

 

 

 

Bib

 

 

 

 

 

EventEntry (0,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

Pos

 

 

 

 

 

Value

 

 

OfficialFunction (0,N)

 

 

 

 

 

 

FunctionId

 

 

 


3.2.1.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Participant

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Participant’s ID.

 

It identifies an athlete or an official and the holding participant’s valid information for one particular period of time.

 

It is used to link other messages to the participant’s information.

 

Participant’s information (example @Organisation) will not be the latest for the athlete/official, unless the @Code attribute is the same as the @Parent attribute. However, this information could be the one being valid in the particular moment of a start list, event unit results, etc.

 

When the participant is an historical one, then this ID will start with “A” when it is an Athlete, “C” when Coach and “O” when Official.

Parent

M

S(20) with no leading zeroes

Participant’s parent ID, which is used to link to the latest valid information for one participant. @Parent attribute should be linked to the latest participant‘s information, by retrieving that Athlete/Official whose @Code attribute is the same as @Parent.

 

The participant containing @Code attribute being the same as the @Parent attribute will be the one with the latest information for the participant.

The @Parent attribute will only be different from @Code in the case that critial personal information has changed from previous competitions. The typical examples are Organisation (for change of country) or Name (particularly for women changing their name at marriage). Further to be clear, @Parent and @Code can only be different if Current = "false".

Status

O

CC @AccreditationStatus

Participant’s accreditation status this atribute is Mandatory in the case of @Current=”true” and it is optional in the case that @Current=”false”.

 

To delete a participant, a specific value of the Status attribute is used.

GivenName

O

S(25)

Given name in WNPA format (mixed case)

FamilyName

M

S(25)

Family name in WNPA format (mixed case)

PrintName

M

S(35)

Print name (family name in upper case + given name in mixed case)

PrintInitialName

M

S(18)

Print Initial name (for the given name it is sent just the initial, without dot)

TVName

M

S(35)

TV name

TVInitialName

M

S(18)

TV initial name

Gender

M

CC @PersonGender

Participant’s gender

Organisation

M

CC @Organisation

Organisation ID

BirthDate

O

YYYYMMDD

Date of birth. This information could be not known at the very beginning, but it will be completed for all participants after successive updates

Height

O

N(3)

999

Height in centimetres. It will be included if this information is available. This information is not needed in the case of officials/referees.

Weight

O

N(3)

999

Weight in kilograms. It will be included if this information is available.

This information is not needed in the case of officials/referees.

PlaceofBirth

O

S(75)

Place of Birth

CountryofBirth

O

CC @Country

Country ID of Birth

PlaceofResidence

O

S(75)

Place of Residence

CountryofResidence

O

CC @Country

Country ID of Residence

Nationality

O

CC @Country

Participant’s nationality.

 

Although this attribute is optional, in very exceptional situations it will not be known, and for this reason not ready to be sent.

Nationality

O

CC @Country

Participant’s nationality.

 

Although this attribute is optional, in very exceptional situations it will not be known, and for this reason not ready to be sent.

MainFunctionId

O

CC @Function

Main function

In the Case of Current=”true” this attribute is Mandatory.

Current

M

boolean

It defines if a participant is participating in the games (true) or is a Historical participant (false).

OlympicSolidarity

O

Y or N

Flag to indicating if the participant participates in the Olympic Movement program.

ModificationIndicator

M

N, U

Attribute is mandatory in the  DT_PARTIC_UPDATE message only

 

N-New participant (in the case that this information comes as a late entry)

U-Update participant

 

If ModificationIndicator=’N’, then include new participant to the previous bulk-loaded list of participants

 

If ModificationIndicator=’U’, then update the participant to the previous bulk-loaded list of participants

 

To delete a participant, a specific value of the Status attribute is used.

 

Participant /Discipline

Although any participating athlete will be assigned at least one discipline, it could be more. Any accredited official will be assigned at least one discipline, but it could be more. If an athlete or official is assigned to more than one discipline, it will be included in the participant message of both disciplines.

Attribute

M/O

Value

Comments

Code

M

CC @Discipline

It is the discipline code used to fill the OdfBody @DocumentCode attribute.

InternationalFederationId

O

S(16)

Competitor’s federation number for Speed Skating.

 

Participant /Discipline /RegisteredEvent

Any accredited athlete will be assigned to one or more events. There is one exception: in some sports, substitutes may be accredited without any associated event.

 

Historical athletes are not register to any event.

Attribute

M/O

Value

Comments

Gender

M

CC @DisciplineGender

Discipline Gender Code

Event

M

CC @Event

Event ID

Bib

M

N(3) 999

Skier bib number, to be sent mandatory in all the individual event units

 

Participant /Discipline /RegisteredEvent /EventEntry

Send if there are specific athlete’s event entries.

Type

Code

Pos

Value

Description

E_ENTRY

E_PB

 

MM:SS.hh

99:90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Skater’s personal best.

MM is minutes, SS is seconds, hh is hundredth of second

E_SB

 

MM:SS.hh

99:90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Skater’s season best.

MM is minutes, SS is seconds, hh is hundredth of second

E_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

ISU rank. It is by athlete in individual events.

E_SUBSTITUTE

 

Y, N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Y- For substitute

N- For not substitute

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

E_ENTRY/ E_PB

Skater’s personal best

Always, as soon as this information is known and this athlete has a personal best

E_ENTRY/ E_SB

Skater’s season best

Always, as soon as this information is known and this athlete has a season best

E_ENTRY/ E_RANK

ISU rank

Always, as soon as this information is known and this athlete has a ISU rank

E_ENTRY/ E_SUBSTITUTE

Substitute / not substitute

Always, as soon as this information is known.

 

 

 

Participant /OfficialFunction

Send if the official has optional functions. Do not send, otherwise.

Attribute

M/O

Value

Comments

FunctionId

M

CC @Function

Additional officials’ function code

 

 

3.2.1.6  Message Sort

The message is sorted by Participant @Code


 

 

3.2.2    List of teams / List of teams update

3.2.2.1  Description

DT_PARTIC_TEAMS contains the list of teams related to the current competition.

 

A team is a type of competitor, being a group of two or more individual athletes participating together in one event. Pairs (tennis, figure skating, etc.) are also defined as team of two competitors. One team participates in one event of one discipline. When one team participates in multiple events, there will be one team for each event for the same group. Also when the same organisation participates in the same event twice, there will different teams.

 

A historical team is defined as a group of athletes (team members) competing in the past in a competition event for an organisation. The historical team members appearing in this message will be listed in the list of historical athletes’ messages. The list of historical teams just associates historical team members with the corresponding historical teams. Historical teams will not be registered to any event.

 

For equestrian one athlete and one horse are not considered a team, the horse is an attribute of the athlete.

 

List of teams (DT_PARTIC_TEAMS) is a bulk message by discipline. The list is always complete. The arrival of this message resets all the previous participant teams’ information for that discipline. It is assumed that all teams appearing in this list are valid, in the meaning that they are participating or they could participate in one event.

 

List of teams update (DT_PARTIC_TEAMS_UPDATE) is an update message. It is not a complete list of teams’ information message. It only contains the team data being modified.

 

The key of the information updated consists of the following attribute: Team @Code. Therefore, any new or updated Team Discipline-Event will be identified by all these attributes.

 

 

3.2.2.2  Header Values

3.2.2.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD is defined according to CC @Discipline

DocumentType

DT_PARTIC_TEAMS_UPDATE / DT_PARTIC_TEAMS

List of participant teams message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.2.3  Trigger and Frequency

3.2.2.3.1  PiT Triggers

The DT_PARTIC_TEAMS message is sent as a bulk message one month before the Games.

 

It is sent several times up to the date from what only DT_PARTIC_TEAMS_UPDATE messages are sent.

 

The DT_PARTIC_TEAMS_UPDATE message is triggered when there is a modification in a DT_PARTIC_TEAMS bulk message sent before.

 

 


3.2.2.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Team (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Organisation

 

 

 

 

 

Number

 

 

 

 

 

Name

 

 

 

 

 

Gender

 

 

 

 

 

Current

 

 

 

 

 

ModificationIndicator

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 

 

 

Discipline (0,1)

 

 

 

 

 

 

Code

 

 

 

 

 

InternationalFederationId

 

 

 

 

 

RegisteredEvent (0,1)

 

 

 

 

 

 

Event

 

 

 

 

 

Gender

 

 

 

 

 

EventEntry (0,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

Pos

 

 

 

 

 

Value

 


3.2.2.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Team

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Team’s ID (example ATM001ESP01, 393553)

 

When the Team is an historical one, then this ID starts with “T”.

Organisation

M

CC @Organisation

Team organisation’s ID

Number

M

N(2)

Team’s number. In this sport, it will be always 1.

Name

M

S(73)

Team’s name.

Gender

M

CC @DisciplineGender

Discipline Gender Code of the Team

Current

M

boolean

It defines if a team is participating in the games (true) or it is a Historical team (false)

ModificationIndicator

M

N, U, D

Attribute is mandatory in the DT_PARTIC_TEAMS_UPDATE  message only

 

N-New team (in the case that this information comes as a late entry)

U-Update team

D-Delete team

 

If ModificationIndicator=’N’, then include new team to the previous bulk-loaded list of teams

 

If ModificationIndicator=’U’, then update the team to the previous bulk-loaded list of teams

 

If ModificationIndicator=’D’, then delete the team to the previous bulk-loaded list of teams

 

Team /Composition /Athlete

In the case of current teams the number of athletes is 2 or more.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID of the listed team’s member. 

 

Therefore, he/she makes part of the team’s composition.

Order

O

Numeric

Team member order

 

Team /Discipline

Each team is assigned just to one discipline.

Attribute

M/O

Value

Comments

Code

M

CC @Discipline

It must be the discipline code used to fill the OdfBody @DocumentCode attribute

InternationalFederationId

O

S(16)

Federation number for the corresponding discipline (include if the discipline assigns international federation codes to teams)

 

Team /Discipline /RegisteredEvent

Each team is assigned at least to one event, except for a historical team, which will not be registered to any event.

Attribute

M/O

Value

Comments

Event

M

CC @Event

Event ID

Gender

M

CC @DisciplineGender

Discipline Gender Code

 

Team /Discipline /RegisteredEvent /EventEntry

Send if there are specific team’s event entries.

Type

Code

Pos

Value

Description

E_ENTRY

E_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

ISU rank. It is by team in team events.

E_SUBSTITUTE

 

1, 2

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

First substitute

Second substitute

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

E_ENTRY/ E_RANK

ISU rank

Always, as soon as this information is known and this team has a ISU rank

E_ENTRY/ E_SUBSTITUTE

First or second substitute

Send for those teams acting as first substitute or second substitute

 

 

 

 

3.2.2.6  Message Sort

The message is sorted by Team @Code.


 

 

3.2.3    Historical records

3.2.3.1  Description

The “historical records” is a message that lists the records broken in previous Competitions.

 

 

3.2.3.2  Header Values

3.2.3.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD should be defined according to CC @Discipline

DocumentType

DT_HISTORIC_RECORD

Historical records message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.3.3  Trigger and Frequency

3.2.3.3.1  PiT Triggers

“Historical records” are sent only once with a bulk message when the information is available before the competition starts.  A new version of this message substitutes previous historical record information.

 

 


3.2.3.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Level 9

Competition

 

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

 

HistoricalRecords

 

 

 

 

 

 

 

 

 

Record (1,N)

 

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

 

RecordType (1,N)

 

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

 

Subcode

 

 

 

 

 

 

 

 

Equalled

 

 

 

 

 

 

 

 

RecordData

 

 

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

ExtRecords (0,1)

 

 

 

 

 

 

 

 

 

ExtRecord (1,N)

 

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

 

Value

 

 

 

 

 

 

Competitor (1,N)

 

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

 

RecordData (0,1)

 

 

 

 

 

 

 

 

 

Country

 

 

 

 

 

 

 

 

Place

 

 

 

 

 

 

 

 

Date

 

 

 

 

 

 

 

 

Confirmed

 

 

 

 

 

 

 

 

Event

 

 

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

 

RecordData (0,1)

 

 

 

 

 

 

 

 

 

Country

 

 

 

 

 

 

 

 

Place

 

 

 

 

 

 

 

 

Date

 

 

 

 

 

 

 

 

Confirmed

 

 

 

 

 

 

 

 

Event

 


3.2.3.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

HistoricalRecords /Record

Attribute

M/O

Value

Comments

Code

M

CC @RecordCode

Record code. Send several record codes in the case several record codes are available in the historical records message.

 

HistoricalRecords /Record /RecordType

Send several elements when several records were broken for the current event unit (specified in ODF header).

It is possible to have more than one element with the same type (as in the case of National Records.

Attribute

M/O

Value

Comments

Code

M

CC @RecordType

Record type.

Subcode

O

-  NOC if Code=”NR” or “NB”

-  Rank if Code=”BOP”, “ALL” or “SBP”

-  WRC order if Code=”WRC”

It will be mandatory in case of Code=”NR”, “NB”, “BOP”, “ALL, “SBP” or “WRC”

Equalled

M

Y, N

Y-There are more than one competitor sharing the record

 

 

N-There is just one competitor holding the record

 

HistoricalRecords /Record /RecordType /RecordData

Attribute

M/O

Value

Comments

ResultType

M

CC @ResultType

“TIME”

Indicate that the result type for the record is a time.

Result

M

SS.hh(h)

99.99(9)

 

 

Or

 

MM:SS.hh(h)

99:90.00(0)

The result of the competitor for the record.

 

Send just in the case @ResultType is Time (see codes section)

 

 

MM is minutes, SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

 

SS.hh is used in the 2x500 event.

 

 

MM:SS.hh format is used in Team Pursuit and all the Individual events except 500m.

 

HistoricalRecords /Record /RecordType /ExtRecords /ExtRecord

/ExtRecords /ExtRecord are optional elements according to competitors’ rules.

Type

Code

Pos

Value

Description

ER_SS

SS_LAP

Numeric

SS.hh(h)

99.99(9)

 

 

Or

 

MM:SS.hh(h)

99:90.00(0)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the intermediate lap, from 1 to the total number of laps.

In the case of the 500 and 2x500, the position 1 (the first 100 m) and 2 (the last 400 m) it will be used for the 500 m event and the 1, 2, 3 and 4 for the 2x500 event (1 and 2 for the first race and 3, 4 for the second race).

For @Value:

Cumulative time at the @Pos lap of the old record.

 

For the 500 m event, the cumulative time of the first lap from the second race will be the time of the lap (Pos 3 should contain the time of the lap, for example 10.00).

 

MM is minutes, SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

 

SS.hh is used in the 2x500 event.

 

 

MM:SS.hh format is used in Team Pursuit and all the Individual events except 500m.

SS_TIME_LAP

Numeric

SS.hh(h)

99.99(9)

 

 

Or

 

MM:SS.hh(h)

99:90.00(0)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the intermediate lap, from 1 to the total number of laps.

In the case of the 500 and 2x500, the position 1 (the first 100 m) and 2 (the last 400 m) it will be used for the 500 m event and the 1, 2, 3 and 4 for the 2x500 event (1 and 2 for the first race and 3, 4 for the second race).

For @Value:

Time for each lap of the old record.It is not a cumulate time.

 

MM is minutes, SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

 

SS.hh is used in the 2x500 event.

 

 

MM:SS.hh format is used in Team Pursuit and all the Individual events except 500m.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

ER_SS/ SS_LAP

Cumulative time at the @Pos lap of the old record.

Always

ER_SS/ SS_TIME_LAP

Time for each lap (@Pos) of the old  record.It is not a cumulate time.

Always.

 

 

 

HistoricalRecords /Record /RecordType /Competitor

Competitor to whom the record is assigned.

Athlete’s or team’s information should be in DT_PARTIC (@Current=”false”) if Competitor @Type=”A” or DT_PARTIC_TEAMS (@Current=”false”) if Competitor @Type=”T”.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Competitor’s ID

 

When the Competitor is an historical athlete, then this ID will start with “A” and when it is a Team it will start with “T”.

Type

M

T, A

T for team

A for athlete

 

HistoricalRecords /Record /RecordType /Competitor /RecordData

If Competitor @Type=”T”, always send.

If Competitor @Type=”A”, do not use.

Attribute

M/O

Value

Comments

Country

M

CC @Country

Country code where the record was broken

Place

M

S(40)

Place (town or city) where the record was broken (example: “Salt Lake City”).

Date

M

YYYYMMDD

Date when the record was broken.

Confirmed

O

Y,N

Send if it is being requested by the specific discipline, since some historical records / record types may not be confirmed

Event

O

S(40)

Send the text of the event name where the record was broken (example: “World Championships”, “Olympic Games”, etc.).

 

HistoricalRecords /Record /RecordType /Competitor /Composition /Athlete

Individual athlete / team member information should be in   DT_PARTIC (@Current=”false”).

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding to either a team member or an individual athlete

 

This ID will start with “A” as it is an historical Athlete.

Order

M

Numeric

Order attribute used to sort team members in a team if Competitor @Type=”T” or 1 if Competitor @Type=”A”.

 

HistoricalRecords /Record /RecordType /Competitor /Composition /Athlete /RecordData

Individual athlete’s record data, according to competitors’ rules.

 

If Competitor @Type=”A”, always send.

If Competitor @Type=”T”, do not use.

Attribute

M/O

Value

Comments

Country

M

CC @Country

Country code where the record was broken

Place

M

S(40)

Place (town or city) where the record was broken (example: “Salt Lake City”).

Date

M

YYYYMMDD

Date when the record was broken.

Confirmed

O

Y,N

Send if it is being requested by the specific discipline, since some historical records / record types may not be confirmed

Event

O

S(40)

Send the text of the event name where the record was broken (example: “World Championships”, “Olympic Games”, etc.).

 

 

3.2.3.6  Message Sort

Sort by Record @Code attribute and then by RecordType @Code attribute.


 

 

3.2.4    Start List

3.2.4.1  Description

The Start List is a message containing the list of competitors for one particular event unit (individual or team event unit).

 

The Start List is a mandatory message for all disciplines.

 

Each ODF Sport Data Dictionary will include the mandatory attributes /elements of this message and redefine the optional ones.

 

 

3.2.4.2  Header Values

3.2.4.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

The DocumentCode attribute in the ODF header will be sent according to the ODF Common Codes document (header values sheet).

DocumentType

DT_START_LIST

Start List message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.4.3  Trigger and Frequency

3.2.4.3.1  PiT Triggers

The general rule is that this message is sent as soon as some of the information arriving in this message and associated to the event unit (PhaseInfos, UnitInfos, and Officials) is known and also when all the competitors for one particular event unit are known.

 

For team event units this message should send as soon as the teams are available (maybe first teams, and after another message with team members).

 

The message is also expected in the case of re-skating for the individual events:

-  During the competition a new Start List is expected. This message contains the list of all the skating pairs including the ‘Reskate’ pair(s).

 

-  A DT_RT_RESULT message is expected with the Result status Live Mandatory.

- A DT_RT_CUMULATIVE_RESULT message is expected with the message status Live Mandatory only for the 500m race 2 event. 

-  After the result of the reskate is known, a new Start List is expected. This message contains all pairs except the reskate pair(s).

 

-  A DT_RT_RESULT message is expected with the Result status Live Mandatory. (The result of the re-skated athlete will be updated, if applies, in the initial row of the athlete)

- A DT_RT_CUMULATIVE_RESULT message is expected with the message status Live Mandatory only for the 500m race 2 event.

 

The message is also expected in the case of re-skating for the team events:

-  During the competition a new Start List is expected for the reskating heat.

 

Trigger also after any major change.

 

 


3.2.4.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Competition

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

Start (0,N)

 

 

 

 

 

 

 

StartOrder

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Type

 

 

 

 

 

 

EventUnitEntry (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Order

 

 

 

 

 

 

Bib

 

 

 

 

 

 

EventUnitEntry (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 


3.2.4.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

UnitInfos /UnitDateTime

Scheduled start date and time.

Attribute

M/O

Value

Comments

StartDate

M

DateTime

Actual start date and time. For multiday units, the start time is on the first day.

 

UnitInfos /UnitInfo

Unit info item associated to the event unit.

Type

Code

Pos

Value

Description

UI_SS

SS_BREAK_PAIR

Numeric

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

The number of the ‘Ice preparation’ event

For @Value:

The number of the last pair before the ice preparation’s break.

SS_HEAT_NUMBER

 

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

The heat number.

For the heats (including the heats of the semi-finals, quarter-finals) will be the number of the heat: 1, 2,…,5

In the finals, send Final A, Final B, Final C and Final D as appropriate.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

UI_SS/ SS_BREAK_PAIR

The number of the last pair before the ice preparation’s break.

Just for the individual events

UI_SS/ SS_HEAT_NUMBER

The heat number including the semi-finals and quarter-finals..

In the finals, send Final A, Final B, Final C and Final D as appropriate.

Just for the team events

 

 

 

Start

For any start list, competitors will be sent as soon as known.

 

First information regarding to UnitInfo, UnitActions, etc might be sent before competitors (either single athletes or teams) are known. For this reason, Start is optional (temporally not including any competitor information

Attribute

M/O

Value

Comments

StartOrder

M

Numeric

   For individual events:

Pair number in the start list. There will be two competitors with the same number.

 

For team events:

Use 1 for ‘Finishing straight’ and 2 for ‘Crossing straight’.

SortOrder

M

Numeric

   It should sort out competitors from its @StartOrder attribute, however

 

For individuals:

placing first the inner lane skater, and afterwards the outer lane skater

 

For teams:

Placing first the finishing straight starting team, and afterwards the crossing straight starting team

 

Start /Competitor

Competitor participating in the event unit

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Competitor’s ID

Type

M

T,A

T for team

A for athlete

 

Start /Competitor /EventUnitEntry

Type

Code

Pos

Value

Description

EU_ENTRY

SS_COLOUR

 

R,W

For @Type:

Send proposed type

For @Type:

Send proposed type

For @Value:

R – For the team wearing red armbands

W – For the team wearing white armbands

SS_RS

 

RS

For @Type:

Send proposed type

For @Type:

Send proposed type

For @Value:

Send ‘RS’ if the team is reskating

SS_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Type:

Send proposed type

For @Value:

Send ‘WD’ in the case of withdrawal (See codes section).

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

EU_ENTRY/ SS_COLOUR

The colour of the armband wearied by the team members.

For team pursuit event units

EU_ENTRY/ SS_RS

Send ‘RS’ if the team is reskating

For team pursuit event units

EU_ENTRY/ SS_IRM

Send ‘WD’ in the case of withdrawal

For team pursuit event units

 

 

 

Start /Competitor /Composition /Athlete

Athlete or team member’s extended information.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding to either a team member or an individual athlete

Order

M

Numeric

The order of the competitors in the team.

Bib

M

N(3) 999

Skier bib number, to be sent mandatory in all the individual event units

 

Start /Competitor /Composition /Athlete /EventUnitEntry

Team member or individual athlete’s event unit entry.

Type

Code

Pos

Value

Description

EU_ENTRY

SS_E_LANE

 

I, O

For @Type:

Send proposed type

For @Type:

Send proposed type

For @Value:

I – For Inner lane skater

O – For outer lane skater

SS_RS

 

RS

For @Type:

Send proposed type

For @Type:

Send proposed type

For @Value:

Send ‘RS’ if the athlete is in the ‘Reskate’ pair

SS_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Type:

Send proposed type

For @Value:

Send ‘WD’ in the case of withdrawal (See codes section).

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

EU_ENTRY/ SS_E_LANE

Inner lane or outer lane

For individual event units

EU_ENTRY/ SS_RS

Send ‘RS’ if the athlete is in the ‘Reskate’ pair

For individual event units

EU_ENTRY/ SS_IRM

Send ‘WD’ in the case of withdrawal (See codes section).

For individual event units

 

 

 

 

3.2.4.6  Message Sort

The message is sorted by the Start@SortOrder attribute.


 

 

3.2.5    Event Unit Results

3.2.5.1  Description

The Event Unit Results is a message containing the results of the competitors in one (individual or team) event unit.

 

The Event Unit Results is a mandatory message for all sports. The  definition includes as much generic information as possible due to the fact that each discipline and event has its own format for the results information (example: score of a match, time in a race, distance in a throw…).

 

 

3.2.5.2  Header Values

3.2.5.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

The DocumentCode attribute in the ODF header will be sent according to the ODF Common Codes document (header values sheet).

DocumentType

DT_RESULT

Event Unit Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or unofficial (or intermediate, interim, partial).

“OFFICIAL” /

“UNOFFICIAL” /

“INTERMEDIATE” /

“INTERIM”/

“PARTIAL”

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

DocumentSubtype

N/A

Not used for SS.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

3.2.5.2.2  RT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

UU according to CC @Unit

DocumentType

DT_RT_RESULT

Event Unit Real Time Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is live update or live full (or live Mandatory, Live Last).

“LIVE_UPDATE” /

“LIVE_FULL” /

“LIVE_MANDATORY” /

“LIVE_LAST

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

RTSerial

Numeric

Incremental and unique sequence number for ODF-RT messages.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.5.3  Trigger and Frequency

3.2.5.3.1  PiT Triggers

The general rule is that this message is sent when the event unit finishes and the results are still unofficial. Also, this message is expected when the results become official. The official/unofficial status is included  in the ODF headers (ResultStatus attribute).

 

Trigger also after any major change.

 

If there is any kind of sport specific rule, this can overwrite in the corresponding ODF Sport Data Dictionaries the general trigger rule: example to send interim results, partial results, etc.

 

There is a special case when the finish result is a tie-break with a lot of data (for example in GA). In this case the DT_RESULT message including DocumentSubtype is sent only with the data of the tie-break.

 

 

3.2.5.3.2  RT Triggers

For ResultStatus=LIVE_UPDATE:

o T1: Trigger when an athlete/team finishes a split

 

o T2: Trigger before a new pair starts to compete

 

o T3: Trigger when the current skating pair finishes

 

o T4: Trigger when an athlete/team finishes the race or gets a status

 

•  For ResultStatus=LIVE_FULL

Send as it will be defined for each RT transmission in the parameters of the DT_RT_GM message.

 

o T5Trigger when the result of the race became unofficial

 

•  For ResultStatus=LIVE_MANDATORY

It is sent when a correction in the previous messages has to be done.

Also is expected in the case of the re-skate.

 

•  For ResultStatus=LIVE_LAST

Send as the last message (that indicates that no new messages are expected for the given ODF unique key, unless something unexpected, that needs correction of previous messages data, happens while the transmission is still open (Good night message has not been sent)).

 

 


3.2.5.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Competition

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

 

 

EndDate

 

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

QualificationMark

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

RecordIndicators (0,1)

 

 

 

 

 

 

 

 

RecordIndicator (1,N)

 

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

RecordType

 

 

 

 

 

Competitor (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Composition

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 


3.2.5.5  Message Values

Competition

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

CC @Competition

Unique ID for competition

N

When available

 

UnitInfos /UnitDateTime

Actual start –and/or end- dates and times.

 

This element is just for PiT.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

StartDate

M

DateTime

Actual start date-time. For multi-day units, the start date-time is that on the first day.

N

When available

EndDate

O

DateTime

Actual end date-time (The attribute should be informed, when available, for ResultStatus UNOFFICIAL and OFFICIAL)

N

When available

 

UnitInfos /UnitInfo

Unit info item associated to the event unit.

Type

Code

Pos

Value

Description

UI_RESULTS

SS_CURRENT_LAP

Numeric

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Used to identify the lane of the competitor:

For the individual events: Send 1 for the ‘Inner lane’ and 2 for the ‘Outer lane’

For the team events: Send 1 for the start position ‘F’ and 2 for the start position ‘C’

For @Value:

Last split reached by the  competitor (0,1,2,3,..99).

Use  99 when finish line is reached.

 

For the DNF athlete, the last  split is considered the  split where he felt.

SS_CURRENT_PAIR

Numeric

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The competitor’s lane.

Send 1 for ‘I’ and 2 for ‘O’.

For @Value:

The code of the current competitor. Please send 'RS'+ athlete code for the reskating athlete.

 

To be sent empty when the last athlete from the race receives its result (T5)

SS_NEXT_PAIR

Numeric

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The competitor’s lane.

Send 1 for ‘I’ and 2 for ‘O’.

For @Value:

The code of the next competitor. Please send 'RS'+ athlete code for the reskating athlete.

SS_LAST_PAIR

Numeric

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The competitor’s lane.

Send 1 for ‘I’ and 2 for ‘O’.

For @Value:

The code of the last competitor. Please send 'RS'+ athlete code for the reskating athlete.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

RT Only

RT Trigger

UI_RESULTS/ SS_CURRENT_LAP

Event unit’s last split reached by the competitors from the current pair.

Always

Y

T1

UI_RESULTS/ SS_CURRENT_PAIR

The code of the athletes from the  current skating pair.

Just for the individual events.

Y

T2,T5

UI_RESULTS/ SS_NEXT_PAIR

The code of the athletes from the  next skating pair.

Just for the individual events.

Y

T2

UI_RESULTS/ SS_LAST_PAIR

The code of the athletes from the  last skating pair.

Just for the individual events.

Y

T2

 

 

 

Result

For each Event Unit Results message, there must be at least one competitor being awarded with a result in the event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Rank

O

Numeric

Rank value in the course

N

T4

RankEqual

O

Y or N

It identifies if a rank has been equalled.

For Pit just include this attribute in case of equalled ranks with value "Y"

N

When available

Result

O

SS.hh(h)

99.99(9)

 

 

Or

 

MM:SS.hh(h)

99:90.00(0)

Result for the particular event unit.

 

Send just in the case @ResultType is Time (see codes section)

 

 

MM is minutes, SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

 

Result format for 2x500m event (sprint event is (S)SS.hh(h)

Result format for other events is MM:SS:hh(h)

N

T4

IRM

O

CC @IRM

IRM for the particular event unit

 

Send just in the case @ResultType is the code including Invalid Rank Mark (see codes section)

N

T4

QualificationMark

O

CC @QualificationMark

It just applies to team pursuit events:

 

Send just in the case the team qualified, according to the codes.

N

T4

SortOrder

M

Numeric

This attribute is a sequential number with the order of the results for the particular event unit, if they were to be presented. It is mostly based on the rank, but it should be used to sort out rank ties as well as results without rank.

 

Also for Real Time,  any sort order change from the initial start list order for any competitor will be provided in this attribute regardless the competitor is ranked or not (this includes ranked, none-ranked and IRM athletes/team).

N

When available

ResultType

M

CC @ResultType

Result type, either Time or IRM for the corresponding event unit

N

T4

 

Result /RecordIndicators /RecordIndicator

Result’s record indicator.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Order

M

Numeric

Order is always ‘1’for records broken/equalled in this Event Unit.

N

T4

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

N

T4

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

N

T4

 

Result /Competitor

Competitor related to the result of one event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Competitor’s ID. Only for the individual events, please send 'RS'+ athlete code for the reskating athlete.

N

When available

Type

M

T,A

T for team

A for athlete

N

When available

 

Result /Competitor /ExtendedResults /ExtendedResult

Type and extension Type

Code

Extension Code

Pos or extension Pos

Value or extension Value

Description

ER_SS

SS_LAP

 

Numeric

MM:SS.hh(h)

99:90.00(0)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the lap, from 1 to the total number of laps

For @Value:

Cumulative time at the @Pos lap for the team

 

MM is minutes, SS is seconds, hh is hundredth of second

SS_DIFF

 

+S.hh

+9.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Team time behind at lap.

 

S is seconds, hh is hundredth of second

 

For the competitor with the first rank send 0.00.

 

Empty if no lap time available for the lap leader.

SS_TIME_LAP

 

SS.hh(h)

90.00(0)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time for each split .It is not a cumulate time.

 

SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

SS_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank at the @Pos lap for the team

SS_ERANK

 

S(1)

(Y, N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

It identifies if the rank at this point has been equalled, send “Y” in this case.

SS_IDK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the Rank to sort the teams

SS_RESKATE

 

 

Y,N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Indicates if the team is repeating the race (reskating).

SS_FF

 

 

Y,P

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

To know if the competitor’s final result was decided by photo.

Send Y for Evaluated Status

Send P for Pending Status.

SS_RESULT_STATUS

 

 

‘OFFICIAL’

OR

‘UNOFFICIAL’

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

The status of the result (official, unofficial)

 

For the table above, we have the following additional/summary information:

 

Type/Code/Extension Code

Description

Expected

RT Only

RT Trigger

ER_SS/ SS_LAP

Cumulative time at the lap

Only for team pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_DIFF

Team time behind at lap.

Only for team pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_TIME_LAP

Time for each lap. It is not a cumulate time.

Only for team pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_RANK

Rank at the @Pos lap for the team

Only for team pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_ERANK

It identifies if the rank at this point has been equalled, send “Y” in this case.

Only for team pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_IDK

Index based on the Rank to sort the teams

Only for team pursuit.

N

T1,T4

ER_SS/ SS_RESKATE

Indicates if the team is repeating the race (reskating).

Only for team pursuit.

N

T3,T4

ER_SS/ SS_FF

Photo Finish Flag

Only for team pursuit.

N

T3,T4

ER_SS/ SS_RESULT_STATUS

The status of the sent result (official, unofficial)

Only for team pursuit.

Y

T4

 

 

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding to either a team member or a single athlete.

Send ‘RS’+ ‘athlete code’ for those athletes with re-skate result.

N

When available

Order

M

Numeric

Order attribute used to sort team members in a team (if Competitor @Type=”T”) or 1 if Competitor @Type=”A”.

N

Only if necessary

Bib

M

N(3) 999

Athlete’s bib number

N

When available

 

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

Team member or individual athlete’s extended result.

Type and extension Type

Code

Extension Code

Pos or extension Pos

Value or extension Value

Description

ER_SS

SS_DIFF

 

 

+S.hh

+9.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time behind leader.

 

S is seconds, hh is hundredth of second

 

For the competitor with the first rank send 0.00.

SS_LAP

 

Numeric

SS.hh(h)

99.99(9)

 

 

Or

 

MM:SS.hh(h)

99:90.00(0)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the intermediate lap, from 1 to the total number of laps.

For @Value:

Cumulative time at the @Pos lap for the single athlete.

 

MM is minutes, SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

 

Result format for 2x500m event (sprint event is (S)SS.hh(h)

Result format for other events is MM:SS:hh(h)

SS_TIME_LAP

 

SS.hh(h)

99.99(9)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time for each lap .It is not a cumulate time.

 

SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

SS_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank at the intermediate lap for the single athlete

 

Send empty for all the laps if the ResultType=’IRM’.

SS_ERANK

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

It identifies if the rank at this point has been equalled, send “Y” in this case.

SS_IDK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the Rank to sort the single athletes

SS_DIFF

 

+SS.hh +99.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

 

Time difference to the first on this split for the single athlete (send “0.00” if the intermediate result rank for that point is 1)

 

S is seconds, hh is hundredth of seconds.

SS_TB_LEADER

 

+SS.hh +99.99

Or

-SS.hh -99.99

Or

0.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

 

Time difference at this split to the leader at the finish line for the single athlete.

 

Empty if no lap time available for the lap leader.

 

S is seconds, hh is hundredth of seconds.

SS_RESKATE

 

 

Y,N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Indicates if the original result of the athlete is updated  by the reskate race result.

 

Send ‘Y’ in this case.

SS_RESULT_STATUS

 

 

‘OFFICIAL’

OR

‘UNOFFICIAL’

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

The status of the result (official, unofficial)

SS_TIME_MS

 

 

SS.hhh

90.000

or

SS.hh

90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

The result of the athlete in SS.hh(90.00), or SS.hhh(90.000) if tie is produced

SS_RS_CODE

 

 

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

Athlete’s ID, corresponding to a single athlete in the re-skate race

SS_LAST_RESULT

 

 

S(1)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

“Y” when athlete gets the final result

“N” when one athlete of next pair gets final result

 

For the table above, we have the following additional/summary information:

 

Type/Code/Extension Code

Description

Expected

RT Only

RT Trigger

ER_SS/ SS_DIFF

Time behind leader.

Always, except for pursuit.

N

T4

ER_SS/ SS_LAP

Cumulative time at the lap for the single athlete.

Always, except for pursuit.

N

T4

ER_SS/ SS_LAP/ SS_TIME_LAP

Time for a particular lap (not cumulative).

Always, except for pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_RANK

Rank at the intermediate lap for the single athlete

 

Send empty for all the laps if the ResultType=’IRM’.

Always, except for pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_ERANK

It identifies if the rank at this point has been equalled, send “Y” in this case.

Always, except for pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_IDK

Index based on the Rank to sort the single athletes

Always, except for pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_DIFF

Time difference to the first on this split (skater who is rank 1 at this split)

Always, except for pursuit.

N

T1,T4

ER_SS/ SS_LAP/ SS_TB_LEADER

Time difference at the split to the leader at the finish line.

Always, except for pursuit.

Y

T1,T4

ER_SS/ SS_RESKATE

Indicates if the original result of the athlete was updated  by the reskate race result.

Only send for  affected competitors

N

T4

ER_SS/ SS_RESULT_STATUS

The status of the sent result (official, unofficial)

Always, except for pursuit.

Y

T4

ER_SS/ SS_TIME_MS

The result of the athlete in SS.hh(90.00), or SS.hhh(90.000) if tie is produced.

Only for the 2x500 event

N

T4

ER_SS/ SS_RS_CODE

Athlete’s ID, corresponding to a single athlete in the re-skate race

Always, except for pursuit.

Y

T1,T2,T3,T4

ER_SS/ SS_LAST_RESULT

Flag to indicate that athlete has gets his final result.

“Y” when athlete gets the final result

“N” when one athlete of next pair gets final result

Always, for individual events.

Y

T4

 

 

 

 

3.2.5.6  Message Sort

Sort by Result @SortOrder


 

 

3.2.6    Phase Results

3.2.6.1  Description

The Phase Results is a message containing the results for the list of competitors in a particular phase (example: Alpine Skiing Super Combined, Downhill). The “Unit” attributes (in the ODF header or the message body) will be informed with zeroes. Then, the Phase Results will be understood for the phase as a whole (not including cumulative information from previous phases), if there are rules for the particular sport in regards to it.

 

The Phase results message is a generic message for all sports, including as much generic information as possible, considering results may have substantial differences between different disciplines and events (example: score of a match, time in a race, distance in a throw, etc.).

 

The mandatory attributes and mandatory elements defined in this message will have to be used by all the sports. This ODF Sport Data Dictionary will also explain with further detail the optional attributes or optional elements of the message.

 

 

3.2.6.2  Header Values

3.2.6.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEP00

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

DocumentType

DT_PHASE_RESULT

Phase Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or unofficial.

“OFFICIAL” /

“UNOFFICIAL”

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

3.2.6.2.2  RT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEP00

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

DocumentType

DT_RT_PHASE_RESULT

Real Time Phase Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is live update or live full (or live Mandatory, Live Last).

“LIVE_UPDATE” /

“LIVE_FULL” /

“LIVE_MANDATORY” /

“LIVE_LAST”

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

RTSerial

Numeric

Incremental and unique sequence number for ODF-RT messages.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.6.3  Trigger and Frequency

3.2.6.3.1  PiT Triggers

The message is expected only for the Team Pursuit events.

 

The general rule is that this message is sent as soon as the last event unit for the corresponding phase finishes and the message becomes unofficial just at the end of the event unit, and afterwards when the message becomes official (when the last event unit of the phase becomes official). The official/unofficial status can be seen in ODF header (ResultStatus attribute).

 

Trigger also after any major change.

 

 

3.2.6.3.2  RT Triggers

The message is expected only for the Team Pursuit events.

 

•  For ResultStatus=LIVE_UPDATE:

 

o T4: Trigger when a team finishes the race or gets a status

 

•  For ResultStatus=LIVE_FULL:

 

o Send as it will be defined for each RT transmission in the parameters of the DT_RT_GM message

 

•  For ResultStatus=LIVE_MANDATORY

It is sending when a correction in the previous messages has been done.

 

•  For ResultStatus=LIVE_LAST

Send as the last message (that indicates that no new messages are expected for the given ODF unique key, unless something unexpected, that needs correction of previous messages data, happens while the transmission is still open (Good night message has not been sent)).

 

 


3.2.6.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

Rank

 

 

 

 

 

RankEqual

 

 

 

 

 

ResultType

 

 

 

 

 

Result

 

 

 

 

 

IRM

 

 

 

 

 

QualificationMark

 

 

 

 

 

SortOrder

 

 

 

 

 

RecordIndicators (0,1)

 

 

 

 

 

 

RecordIndicator (1,N)

 

 

 

 

 

 

Order

 

 

 

 

 

Code

 

 

 

 

 

RecordType

 

 

 

Competitor

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

Type

 

 

 

 

 

Code

 

 

 

 

 

Pos

 

 

 

 

 

Value

 

 

 

Composition (0,1)

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 

 

 

 

 

Bib

 


3.2.6.5  Message Values

Competition

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

CC @Competition

Unique ID for competition

N

When available

 

Result

For any Phase Results message, there should be at least one competitor being awarded a result for the phase.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Rank

O

Numeric

In Team Pursuit event it will be the Rank at the end of the phase

N

T4

RankEqual

O

Y or N

Indicates if the rank at the end of the phase is equalled

For PiT just include this attribute in case equaled ranks wiyh value “Y”

N

T4

ResultType

M

CC @ResultType

Result type, either Time or IRM for the corresponding phase.

N

T4

Result

O

MM:SS.hh(h)

99:90.00(0)

In Team Pursuit event it will be the result at the end of the phase.

 

Send just in the case @ResultType is Time

 

MM is minutes, SS is seconds, hh is hundredth of second or hhh in the case of tie it will be thousand of a second

 

Result format for the event is MM:SS:hh(h)

N

T4

IRM

O

CC @IRM

In Team Pursuit event it will be the IRM at the end of the phase.

 

Send just in the case @ResultType is the code including Invalid Rank Mark (see codes section)

N

T4

QualificationMark

O

CC @QualificationMark

Qualificiation Mark.

N

T4

SortOrder

M

Numeric

This attribute is a sequential number with the order of the results for the particular event unit, if they were to be presented. It is mostly based on the rank, but it should be used to sort out rank ties as well as results without rank.

N

T4

 

Result /RecordIndicators /RecordIndicator

Phase result’s record indicator.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Order

M

Numeric

Deprecated: currently, Order is always ‘1’ for the latest (best) record of each type broken/equalled up to the current phase.

N

T4

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

N

T4