Table of content

Table of content 2

1   Introduction   2

1.1.. This document 2

1.2.. Objective. 2

1.3.. Main Audience. 2

1.4.. Glossary. 2

1.5.. Related Documents. 2

2   Overall Perspective  2

2.1.. Objective. 2

2.2.. End to End data flow. 2

3   Messages  2

3.1.. Applicable Messages. 2

3.2.. Messages. 2

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

3.2.1.1    Description. 2

3.2.1.2    Header Values. 2

3.2.1.2.1     PiT Header 2

3.2.1.3    Trigger and Frequency. 2

3.2.1.3.1     PiT Triggers. 2

3.2.1.4    Message Structure. 2

3.2.1.5    Message Values. 2

3.2.1.6    Message Sort 2

3.2.2... Start List 2

3.2.2.1    Description. 2

3.2.2.2    Header Values. 2

3.2.2.2.1     PiT Header 2

3.2.2.3    Trigger and Frequency. 2

3.2.2.3.1     PiT Triggers. 2

3.2.2.4    Message Structure. 2

3.2.2.5    Message Values. 2

3.2.2.6    Message Sort 2

3.2.3... Event Unit Results. 2

3.2.3.1    Description. 2

3.2.3.2    Header Values. 2

3.2.3.2.1     PiT Header 2

3.2.3.2.2     RT Header 2

3.2.3.3    Trigger and Frequency. 2

3.2.3.3.1     PiT Triggers. 2

3.2.3.3.2     RT Triggers. 2

3.2.3.4    Message Structure. 2

3.2.3.5    Message Values. 2

3.2.3.6    Message Sort 2

3.2.4... Phase Results. 2

3.2.4.1    Description. 2

3.2.4.2    Header Values. 2

3.2.4.2.1     PiT Header 2

3.2.4.2.2     RT Header 2

3.2.4.3    Trigger and Frequency. 2

3.2.4.3.1     PiT Triggers. 2

3.2.4.3.2     RT Triggers. 2

3.2.4.4    Message Structure. 2

3.2.4.5    Message Values. 2

3.2.4.6    Message Sort 2

3.2.5... Event Final Ranking. 2

3.2.5.1    Description. 2

3.2.5.2    Header Values. 2

3.2.5.2.1     PiT Header 2

3.2.5.3    Trigger and Frequency. 2

3.2.5.3.1     PiT Triggers. 2

3.2.5.4    Message Structure. 2

3.2.5.5    Message Values. 2

3.2.5.6    Message Sort 2

3.2.6... Event’s Medallists. 2

3.2.6.1    Description. 2

3.2.6.2    Header Values. 2

3.2.6.2.1     PiT Header 2

3.2.6.3    Trigger and Frequency. 2

3.2.6.3.1     PiT Triggers. 2

3.2.6.4    Message Structure. 2

3.2.6.5    Message Values. 2

3.2.6.6    Message Sort 2

3.2.7... Brackets. 2

3.2.7.1    Description. 2

3.2.7.2    Header Values. 2

3.2.7.2.1     PiT Header 2

3.2.7.3    Trigger and Frequency. 2

3.2.7.3.1     PiT Triggers. 2

3.2.7.4    Message Structure. 2

3.2.7.5    Message Values. 2

3.2.7.6    Message Sort 2

3.2.8... Discipline Configuration. 2

3.2.8.1    Description. 2

3.2.8.2    Header Values. 2

3.2.8.2.1     PiT Header 2

3.2.8.3    Trigger and Frequency. 2

3.2.8.3.1     PiT Triggers. 2

3.2.8.4    Message Structure. 2

3.2.8.5    Message Values. 2

3.2.8.6    Message Sort 2

3.2.9... Event Unit Weather Conditions. 2

3.2.9.1    Description. 2

3.2.9.2    Header Values. 2

3.2.9.2.1     PiT Header 2

3.2.9.3    Trigger and Frequency. 2

3.2.9.3.1     PiT Triggers. 2

3.2.9.4    Message Structure. 2

3.2.9.5    Message Values. 2

3.2.9.6    Message Sort 2

4   Messages Sequence  2

5   Codes  2

5.1.. Global Codes. 2

5.2.. Snowboard Codes. 2

6   General definitions  2

6.1.. ODF Message Structure. 2

6.1.1... ODF Declaration. 2

6.1.2... ODF Header 2

6.1.3... ODF Body. 2

6.2.. ODF Data Types and Formats. 2

6.2.1... Rules for rounding numbers. 2

6.2.2... Measures format 2

6.2.3... Rules for measures conversion. 2

6.3.. ODF Message Update. 2

7   DOCUMENT CONTROL   2

7.1.. File Reference. 2

7.2.. Version history. 2

7.3.. Change Log. 2

 

1   Introduction

1.1  This document

This document includes the ODF Snowboard Data Dictionary. This document refines the messages described in the ODF General Messages Interface Document specifically for Snowboard, 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 Snowboard Data Dictionary, with the intention that the information message producer and the message consumer can successfully interchange the information as the Snowboard 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 Snowboard 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_MEDALS

Medal standings

PiT

 

DT_MEDALLISTS_DAY

Medallists of the day

PiT

 

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_RANKING

Event Final Ranking

PiT

X

DT_MEDALLISTS

Event’s Medallists

PiT

X

DT_MEDALLISTS_DISCIPLINE

Medallists by discipline

PiT

 

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 may not be 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.

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 Scholarship 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)

FIS code of athlete for Snowboard

 

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

O

N(4)

9990

Bib numbers are specified in start lists elements.

 

Send it again when value known.

 

When sending start list elements also send this element with this attribute filled with the value.

 

Participant /Discipline /RegisteredEvent /EventEntry

Send if there are specific athlete’s event entries.

Type

Code

Pos

Value

Description

E_ENTRY

E_RANK

 

N(3)

990

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

FIS Rank.

E_POINTS

 

N(4).N(2)

9990.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

FIS Points

E_STANCE

 

S(1)

G or R

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send G for Goofy (right foot forward on the board) or R for Regular (left foot forward on the board).

 

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

 

Type/Code

Description

Expected

E_ENTRY/ E_RANK

FIS rank

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

E_ENTRY/ E_POINTS

FIS points

Always, as soon as this information is known and this athlete has FIS points

E_ENTRY/ E_STANCE

The position of the competitor on the board. Goofy (right foot forward) or Regular (left foot forward).

Always.

 

 

 

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    Start List

3.2.2.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.

 

 

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

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.2.3  Trigger and Frequency

3.2.2.3.1  PiT Triggers

As general rule, the message is sent as soon as the expected information is available:

-  event unit related information (PhaseInfos, UnitInfos, and Officials)

-  event unit related competitors.

 

Trigger also after any major change.

 

A major change in SBX is if the Jury change the starting order (when snowing, etc.) and the Snowseed assigned changes the StartOrder and SortOrder.

 

 


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

Level 7

Competition

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

PhaseInfos (0,1)

 

 

 

 

 

 

 

PhaseInfo (1,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

 

 

Competitor (0,N)

 

 

 

 

 

 

 

Organisation

 

 

 

 

 

 

Order

 

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

FamilyName

 

 

 

 

 

 

GivenName

 

Officials (0,1)

 

 

 

 

 

 

 

Official (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Function

 

 

 

 

 

 

Order

 

 

 

 

Start (0,N)

 

 

 

 

 

 

 

StartOrder

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Type

 

 

 

 

 

 

Bib

 

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Order

 

 

 

 

 

 

Bib

 

 

 

 

 

 

EventUnitEntry (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 


3.2.2.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

PhaseInfos /PhaseInfo

Phase info item associated to the event unit.

Type

Code

Pos

Value

Description

PI_SB

SB_PENALTY_TIME

 

MM:SS.hh

99:90.00

MM=minutes

SS=seconds

hh=hundredth

of second

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Penalty time applied according to sport rules.

 

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

 

Type/Code

Description

Expected

PI_SB/ SB_PENALTY_TIME

Penalty time applied according to sport rules.

Always in the case of Finals for PGS and PSL.

 

 

 

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_SB

SB_ALTITUDE_START

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Start Altitude in meters

SB_ALTITUDE_FINISH

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Finish Altitude in meters

SB_ALTITUDE_DROP

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Vertical Drop in meters

SB_LENGTH

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Length of course in meters

SB_COURSE_NAME

 

S(50)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Name of the Course.

SB_WIDTH_WALLS

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

HP Width wall to wall in meters

SB_INCLINATION

 

N(2).N(1)

90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

HP degrees of inclination

SB_HEIGHT_WALLS

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

HP inner height of walls in meters

SB_VERT_INCLINATION

 

N(2).N(2)

90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

HP degrees of vertical inclination

SB_HOMOLOGATION_NUM

 

S(40)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Course Homologation Number PSL, PGS

SB_GATES_NUM

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Number of gates PSL, PGS

SB_JUMPS_NUM

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Number of jump features

SB_JIBBING_NUM

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Number of jibbing features

SB_FEATURES_NUM

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Number of features

SB_FORERUNNERS

 

Do not send anything

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Do not send anything

 

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

 

Type/Code

Description

Expected

UI_SB/ SB_ALTITUDE_START

Start altitude in meters

Always, except for HP

UI_SB/ SB_ALTITUDE_FINISH

Finish altitude in meters

Always, except for HP

UI_SB/ SB_ALTITUDE_DROP

Vertical drop in meters

Always, except for HP

UI_SB/ SB_LENGTH

Course length in meters

Always

UI_SB/ SB_COURSE_NAME

Course Name

Always

UI_SB/ SB_WIDTH_WALLS

Halfpipe width from wall to wall

Always. Only for HP

UI_SB/ SB_INCLINATION

Halfipipe degrees of inclination

Always. Only for HP

UI_SB/ SB_HEIGHT_WALLS

Halfipipe inner height of walls in meters

Always. Only for HP

UI_SB/ SB_VERT_INCLINATION

Halfipipe degrees of vert inclination

Always. Only for HP

UI_SB/ SB_HOMOLOGATION_NUM

Course homologation number

Always. Only for PSL and PGS

UI_SB/ SB_GATES_NUM

Number of gates

Always. Only for PSL and PGS

UI_SB/ SB_JUMPS_NUM

SBS Number of jump features

Always. Only for SBS

UI_SB/ SB_JIBBING_NUM

SBS Number of jibbing features

Always. Only for SBS

UI_SB/ SB_FEATURES_NUM

SBX Number of features

Always. Only for SBX

UI_SB/ SB_FORERUNNERS

Code used for Forerunners information

 Always

 

 

 

UnitInfos /UnitInfo /Competitor

Just in the case of forerunners

Attribute

M/O

Value

Comments

Organisation

M

CC @Organisation

Organisation ID of the forerunner associated to the UnitInfo/Competitor forerunner unit information

Order

O

N(3)

Order of the forerunner in the unit.

 

UnitInfos /UnitInfo /Competitor /Composition /Athlete

Just for the forerunners

Attribute

M/O

Value

Comments

FamilyName

O

S(25)

Family name of the forerunner associated to the UnitInfo /Competitor forerunner unit information.

GivenName

O

S(25)

Given name of the forerunner associated to the UnitInfo /Competitor forerunner unit information.

 

Officials /Official

Official associated to the event unit.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Key of the official, to uniquely identify this element

Function

M

CC @Function

Send according to the codes.

Use one of the following list:

 

For Jury:

FIS Technical Delegate

Head Judge

Chief of Competition

FIS Race Director

FIS Race Director/Referee

Start Referee

Finish Referee

Chief of Finish

 

For Officials:

FIS Assistant Race Director

Chief of Halfpipe

Halfpipe Technical Adviser

Assistant Head Judge

Judge 1

Judge 2

Judge 3

Judge 4

Judge 5

Judge 6

 

Chief of Parallel Giant Slalom

Chief of Parallel Slalom

Course Setter

Video Controller

 

Chief of Slopestyle

Course Designer

 

Chief of Course

Course Builder

Start Referee

Finish Referee

Order

M

Numeric

According to the Sport Rules

 

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

O

Numeric

Start order of the competitor in the start list.

For PGS, PSL Qualification and Elimination runs two athletes may have the same start order (as they run in parallel at the same time, one in each course, see @SortOrder).

SortOrder

M

Numeric

In most cases, same as @StartOrder. However, in the case of the units of finals for PGS, PSL and SBX, it should be the sort order according to the brackets rules.

In the case of PGS and PSL

qualification and elimination, it should alternate red course / blue course with consecutive numbering (no repeating) according to the

@StartOrder attribute (StartOrder 1: SortOrder is 1 and 2; StartOrder 2: SortOrder is 3 and 4 and so on).

 

Start /Competitor

Competitor participating in the event unit

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes,

TBD, Code

Competitor’s ID, TBD in case that the competitor is not known.

Type

M

A

A for athlete

Bib

O

N(4)

9990

Competitor’s bib number.

 

Start /Competitor /Composition /Athlete

Athlete extended information

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID

Order

M

Numeric

For individual events it will be 1

Bib

M

N(4)

9990

Bib number.

 

Start /Competitor /Composition /Athlete /EventUnitEntry

Individual athlete’s event unit entry.

Type

Code

Pos

Value

Description

EUE_SB

SB_BIB_COLOR

 

CC @BibColor

For @Type:

Send proposed type. Only for PGS, PSL and SBX

For @Code:

Send proposed Code

For @Pos:

Don’t send anything.

For @Value:

Send one of CC @BibColor

SB_IRM

 

CC @IRM

For @Type:

Send proposed type. Only for PGS/PSL Qualification and Elimination Runs.

For @Code:

Send proposed Code

For @Pos:

Don’t send anything.

For @Value:

IRM for the particular event unit.

SB_HEAT

 

N(1)

9

For @Type:

Send proposed type.

For @Code:

Send proposed Code

For @Pos:

Don’t send anything.

For @Value:

Consecutive number of heat/pair. For HP/SBS (in case of Heats format) and PGS/PSL(Pair)/ SBX(Heat) Finals

SB_SNOWSEED

 

S(1)

Y or N

For @Type:

Send proposed type.

For @Code:

Send proposed Code

For @Pos:

Don’t send anything.

For @Value:

If athlete is assigned a Snowseed send Y, otherwise send N

 

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

 

Type/Code

Description

Expected

EUE_SB/ SB_BIB_COLOR

Bib Color

Always in the case of PGS and PSL (for red and blue); for SBX, not for Qualification phase but for all final phases.

EUE_SB/ SB_IRM

IRM

PGS/PSL Qualification and Elimination Runs.

EUE_SB/ SB_HEAT

Heat or Pair Number

For HP/SBS (in case of Heats format) it is the Heat number 1 or 2; for PGS/PSL(Pair)/ SBX(Heat) Finals is the consecutive number of the pairs/heats: in 1/8 Finals from 1 to 8, in Quarterfinals from 9 to 12, etc.

EUE_SB/ SB_SNOWSEED

Snowseed: In extraordinary conditions, the Jury may change the starting order (when snowing, etc.). A group of at least six competitors, nominated in advance, start before start number one. These six competitors are drawn from among the last 20% of the start list. They will start in reverse order of their start numbers.

Just for SBX.

 

 

 

 

3.2.2.6  Message Sort

The message is sort by the Start@SortOrder attribute.


 

 

3.2.3    Event Unit Results

3.2.3.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.3.2  Header Values

3.2.3.2.1  PiT 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_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 in SB

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.3.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.3.3  Trigger and Frequency

3.2.3.3.1  PiT Triggers

Follow the general rule.

o Only there is an exception for Halfpipe Qualification, the message will be sent also as “PARTIAL” after Heat 1 in men.

 

Then proceed with unofficial and official results, as expected.

 

 

3.2.3.3.2  RT Triggers

For ResultStatus=LIVE_UPDATE:

o T1: Trigger at the beginning of the unit.

 

o T2: Trigger as soon as athlete starts (is on course).

 

o T3: Trigger as soon as the time or points is available for an athlete or there is change in athlete’s rank (crosses an intermediate point or finish line).

 

•  For ResultStatus=LIVE_FULL

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 sent when a correction in the previous messages has to be 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.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

Competition

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

 

 

EndDate

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

QualificationMark

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

Competitor (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

Composition

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 


3.2.3.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

O

DateTime

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

 

Not needed for Real Time.

N

When available

EndDate

O

DateTime

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

 

Not needed for Real Time.

N

When available

 

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

Text

Rank of the competitor in the result.

It should be noticed that in the case of the PGS, PSL – Qualification Run, ranks are assigned independently for red course / blue course, and for this reason, two competitors could have the same rank despite of having different times, according to their participation in either the red course or the blue course.

N

T1, T3

RankEqual

O

Y or N

It identifies if a rank has been equalled.

 

For Pit, send just ‘Y’ for equalled ranks.

N

Only if necessary

Result

O

MM:SS.hh

99:90.00

Or

N(3).N(2)

900.90

Result for the particular event unit.

Send just in the case @ResultType is TIME in the case of PGS, PSL and SBX (for just applies for Qualification hase if proceed) or POINTS in the case of HP and SBS (see codes section).

Don’t send this attribute if the @ResultType is RANK.

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

N

T3

IRM

O

CC @IRM

IRM for the particular event unit. Send just in the case @ResultType is IRM (see codes section).

N

T3

QualificationMark

O

CC @QualificationMark

Not used for Snowboard in this message.

N

Only if necessary

SortOrder

M

Numeric

Used to sort all results in an event unit. For Real Time attribute is optional, because it should not be informed if ResultType is empty, as defined for the ResultType attribute.

In the case of the PGS,PSL – Qualification Run, for the same rank, it will be listed first the participant in the red course, and then the participant in the blue course.

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

Always

ResultType

O

CC @ResultType

Result type, either TIME (SBX Seeding runs, PGS and PSL Qualification and Elimination runs), POINTS

(HP and SBS), RANK (PG, PSL and SBX Finals), or IRM for the corresponding event unit.

For Real Time, when the message arrives (to include some extended results for a particular kind of competitor), no attributes at Result element level will be included if ResultType attribute is empty. In this case, it means it is not being sent data for the Result element. On the contrary, if ResultType is informed, and the other attributes are blank, it is assumed these attributes are being reset.

N

T3

 

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 or TBD

Competitor’s ID or TBD in case that the competitor is unknown

N

Only if necessary

Type

M

A

A for athlete

N

Only if necessary

Bib

M

N(4)

9990

Competitor’s bib number.

N

Only if necessary

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Athlete’s ID

N

Only if necessary

Order

M

Numeric

For individual events it will be 1

N

Only if necessary

Bib

M

N(4)

9990

Bib number

N

Only if necessary

 

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

Individual athlete’s extended result.

Type

Code

Pos

Value

Description

ER_SB

SB_DIFF

N(1)

9

MM:SS.hh

99:90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Run Number in the heat (1 or

2) only for Qualification (PGS and PSL)

For @Value:

Time difference (do not send

for Result @Rank=1)

In case of tie, send 0.00 for

both competitors.

- in qualification: time difference between the time of the rider and the best rider on the same course.

- in finals: time difference between the time of the rider and the rider from the same pair, but on the other course.

MM=minutes SS=seconds

hh=hundredth of second

SB_JUDGE

N(1)

9

N(3)

900

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Send judge number, from 1 to

6

For @Value:

Send points from the judge

identified by @Pos

SB_SPLIT_RESULT_TIME

N(1)

9

MM:SS.hh

99:90.00

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Send the intermediate point (1,2,3…)

For @Value:

Time at the split position

MM=minutes

SS=seconds

hh=hundredth of second

SB_SPLIT_RESULT_RANK

N(1)

9

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Send the intermediate point (1,2,3…)

For @Value:

Rank of the competitor in the split (if SB_SPLIT_RESULT_TIME exists)

SB_ADVANCED

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

"Y" to indicate the competitor

who is advanced to the next

phase as a result of a tie-break

or otherwise.

SB_CURRENT

N(1)

9

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Send current order, from 1 to 4. Only for SBX.

Do not send anything for PSL & PGS, HP & SBS

For @Value:

Send Y for the current athlete (see further description below)

SB_LAST_SCORED

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y for the most recent score

SB_NEXT

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y for the next athlete

SB_JUDGE_DISCARD

N(1)

9

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Send judge number, from 1 to 6

For @Value:

Send Y if points from the judge identified by @Pos are discarded (highest or lowest).

SB_TIEBRK_PTS

 

N(3).N(2)

990.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Should be the tie-break points of the run which breaks the tie, or the total score of worst run depending on the criteria which breaks the tie.

SB_DQP

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

Send Y if the athlete is potentially disqualified. Only RT

SB_PFR

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

Send Y if Photo has been evaluated.

Send P if Photo is under evaluation.

Send N if no Photo is required.

Only RT

SB_TIEBRKNG_FOR

 

MM:SS.hh

99:90.00

(PGS, PSL)

MM=minutes

SS=seconds

hh=hundredth

of second

 

Or

 

N(2)

90

(HP, SBS, SBX)

For @Type:

Send proposed Type

For @Code:

Send proposed Code

For @Pos:

Do not send anything

For @Value:

Tied time (PGS, PSL) or tied rank (HP, SBS, SBX) to break

SB_RE_RUN

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

Send Y if Re-Run has been given to athlete.

Only RT

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

ER_SB/ SB_DIFF

Time difference (difference in regards to the total time for PGS and PSL).

Always in the case of PGS or PSL, except for rank=1

N

T3

ER_SB/ SB_JUDGE

Points from a particular judge

Always just in the case of HP and SBS

N

T3

ER_SB/ SB_SPLIT_RESULT_TIME

Result at the split position

In SBX, just for Seeding phase.

Optional for PGS/PSL Qualification, Elimination and Final phases.

N

T3

ER_SB/ SB_SPLIT_RESULT_RANK

Rank at the split position

In SBX, just for Seeding phase.

Optional for PGS/PSL Qualification, Elimination and Final phases.

N

T3

ER_SB/ SB_ADVANCED

Competitor who is advance to the next Phase

For PGS and PSL Finals (phases 4,3,2,1) in case of tie-break.

N

T3

ER_SB/ SB_CURRENT

Current competitor on course. During Run should be set to Y when the competitor (who has SB_NEXT to Y) enters in the course. Should be set to N when the competitor is not on course (this will happen when the competitor gets his/her result) and sets his/her SB_LAST_SCORED value to Y

Always

Y

T2, T3

ER_SB/ SB_LAST_SCORED

Most recent score. During Run should be set to Y when the competitor gets the Result. Should be set to N when another competitor sets his/her SB_LAST_SCORED value to Y.

Always

Y

T3

ER_SB/ SB_NEXT

Next Competitor. Before the start of the Unit should set to Y for the first competitor to start when is presented. During Run should be set to Y when previous competitor becomes current. Should be set to N when another competitor sets his/her SB_NEXT value to Y (this will happen when a competitor becomes current).

Always

Y

T2, T3

ER_SB/ SB_JUDGE_DISCARD

HP,SBS: points from judge discarded (Y,N)

Always just in case of HP and SBS.

N

T3

ER_SB/ SB_TIEBRK_PTS

Tie-break points of the run according to rules

Only HP and SBS all phases for athletes in a tie

N

T3

ER_SB/ SB_DQP

Athlete is potentially disqualified (Y,N)

Always

Y

T3

ER_SB/ SB_PFR

Photo Finish is Required (Y,P,N)

Always for SBX

Y

T3

ER_SB/ SB_TIEBRKNG_FOR

Affected tie-breaking for,

PGS & PSL: Time

HP, SBS & SBX: Rank

Only for athlete in a tie

N

T3

ER_SB/ SB_RE_RUN

Athlete has a Re-run option (Y/N)

Affected SBX (Qualification), PGS/PSL (All Phases)

Y

T3

 

 

 

 

3.2.3.6  Message Sort

Sort by Result @SortOrder


 

 

3.2.4    Phase Results

3.2.4.1  Description

The Phase Results is a message containing the results for the list of competitors in a particular phase.

 

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.).

 

 

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

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 interim, partial, official or unofficial.

"INTERIM" /

“PARTIAL” /

“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.4.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.4.3  Trigger and Frequency

3.2.4.3.1  PiT Triggers

This message is sent like follows:

ResultStatus "INTERIM": HP and SS for unit that are not the last unit of the phase.

ResultStatus "PARTIAL": Rest of events for unit that are not the last unit of the phase.

ResultStatus "UNOFFICIAL"/"OFFICIALS" just at the end of the last unit of the phase.

 

Trigger also after any major change.

 

 

3.2.4.3.2  RT Triggers

For ResultStatus=LIVE_UPDATE:

 

o T1: Trigger at the beginning of the unit.

 

o T2: Trigger as soon as athlete starts (is on course).

 

o T3: Trigger as soon as the time or points is available for an athlete or there is change in athlete’s rank (crosses an intermediate point or finish line).

 

•  For ResultStatus=LIVE_FULL:

 

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

 

•  For ResultStatus=LIVE_MANDATORY

Send 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.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

Level 8

Competition

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

QualificationMark

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 


3.2.4.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

Rank of the competitor in the phase. In case of HP/SBS with two heats format and PGS/PSL/SBX Final phases, it is the rank of competitor within his/her heat/pair (two competitors will have same rank in phase). In case of PGS/PSL and SBX Finals it is the rank of competitor

This attribute is optional because the skier may have got an invalid rank mark.

N

T3

RankEqual

O

Y or N

It identifies if a rank has been equalled.

N

Only if necessary

ResultType

O

CC @ResultType

Result type, either TIME (SBX Seeding runs, PGS and PSL Qualification and Elimination runs), POINTS (HP and SBS), RANK (PGS and PSL Finals), or IRM for the corresponding event unit. Send this attribute if there is Result or IRM.

N

T3

Result

O

MM:SS.hh

99:90.00

Or

N(3).N(2)

900.90

The result of the competitor in the phase.

It is the total time for PGS and PSL, best score for HP and SBS and best time for SBX.

Send just in the case @ResultType is Time in the case of PGS, PSL and SBX or Points in the case of HP and SBS (see codes section).

MM is minutes, SS is seconds, hh is hundreds of second.

N

T3

IRM

O

CC @IRM

The invalid rank mark, in case it is assigned. Send just in the case @ResultType is IRM (see codes section).

N

T3

QualificationMark

O

CC @QualificationMark

Send just in the case the competitor qualified according to the codes. It will be basically used after second runs (SBX, HP and SBS), as well as in the Elimination run in PGS and PSL.

N

Send when information is known and it is not going to change, for example, if there are 20 athletes competing and 6 are qualifying, when the 15th competitor finishes there is one competitor that is going to qualify for sure.

SortOrder

M

Numeric

Used to sort all results in a phase, based on rank, but to break rank ties, etc. It is mainly used for display purposes. In case of HP/SBS with two heats format and PGS/PSL/SBX Final phases, where two competitors will have same rank in phase, it will be listed (sorted) by heat/pair (first lower heat/pair).

N

Always

 

Result /Competitor

Competitor related to one phase result.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Competitor’s ID

N

Only if necessary

Type

M

A

A for athlete

N

Only if necessary

Bib

M

N(4)

9990

Competitor’s bib number.

N

Only if necessary

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Athlete’s ID

N

Only is necessary

Order

M

Numeric

Always 1

N

Only is necessary

Bib

M

N(4)

9990

Competitor’s bib number.

N

Only if necessary

 

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

Individual athlete’s extended result when Competitor @Type=”A” according to competitors’ rules.

Type

Code

Pos

Value

Description

ER_SB

SB_DIFF

 

MM:SS.hh

99:90.00

MM=minutes

SS=seconds

hh=hundredth

of second

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference (do not send for Result @Rank=1) It is the time difference in regards to the total time for PGS, PSL (Qualification phase) and best time for SBX (Seeding phase).

SB_BEST_RUN

 

N(1)

0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send “0” to set undefined (in case of IRM for both runs) the best run

Send “1” to set run 1 as best

Send “2” to set run 2 as best

SB_COURSE_RANK

N(1)

9

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

1 Blue, 2 Red

For @Value:

Rank within course given by @Pos

SB_COURSE_ERANK

N(1)

9

S(1)

Y,N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

1 Blue, 2 Red

For @Value:

Equalled Rank for SB_COURSE_RANK given by @Pos.

SB_COURSE_IDX

N(1)

9

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

1 Blue, 2 Red

For @Value:

Order of the athlete within course related to the SB_COURSE_RANK given by @Pos

SB_TIEBRK_PTS

 

N(3).N(2)

990.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Tie break points (HP and SBS). Should be the tie-break points of the run which breaks the tie, or the total score of worst run depending on the criteria which breaks the tie.

SB_LAST_QUALIFIED

 

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send to Y when competitor is the last competitor qualified according to sport rules. (See table below for more information)

SB_SORT_HEAT

N(1)

9

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send the heat number

For @Value:

Send the sort order within the heat given by @Pos

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

ER_SB/ SB_DIFF

Time difference (difference in regards to the total time for PGS and PSL and best time for SBX).

Always in the case of SBX Seeding, PGS Qualification or PSL Qualification, except for rank=1

N

T3

ER_SB/ SB_BEST_RUN

Best Run Result

Just in the case of HP, SBX Seeding and SBS. (Two runs format)

N

T3

ER_SB/ SB_COURSE_RANK

Rank within a course

Just for PGS/PSL Qualification phase

N

T3

ER_SB/ SB_COURSE_ERANK

Equalled Rank within a course

Just for PGS/PSL Qualification phase

N

T3

ER_SB/ SB_COURSE_IDX

Order for SB_COURSE_RANK

Just for PGS/PSL Qualification phase

N

T3

ER_SB/ SB_TIEBRK_PTS

Tie break points according to rules. Should be the tie-break points of the run which breaks the tie.

Just for HP and SBS. All phases, only for athletes in a tie.

N

T3

ER_SB/ SB_LAST_QUALIFIED

Y if the competitor is the last one to qualify according to rules. It is the virtual last qualified position in the current moment.

All phases when there is a qualification criteria.

N

T3

ER_SB/ SB_SORT_HEAT

Sort order within the heat

Just for HP and SBS. All phases with heats.

N

T3

 

 

 

 

3.2.4.6  Message Sort

Sort by Result @SortOrder


 

 

3.2.5    Event Final Ranking

3.2.5.1  Description

The event final ranking is a message containing the final results and ranking at the completion of one particular event, either for individual athletes or for aggregated athletes.

 

The final ranking message is a generic message for all sports, including the full event final result for all competitors who were either ranked, got an Invalid Rank Mark (disqualified, etc.), or both.

 

 

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

DDGEEE000

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

DocumentType

DT_RANKING

Event Final ranking message

ResultStatus

CC @ResultStatus

Result status

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.

 

 

3.2.5.3  Trigger and Frequency

3.2.5.3.1  PiT Triggers

This message is sent at the end of each phase for all events.

 

 


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

 

 

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Composition

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 


3.2.5.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Result

For any event final ranking message, there should be at least one competitor being awarded a result for the event.

Attribute

M/O

Value

Comments

Rank

O

Numeric

Final rank of the competitor in the corresponding event. This attribute is optional because the skier may have got an invalid rank mark.

RankEqual

O

Y

It identifies if a rank has been equalled.

ResultType

M

CC @ResultType

Result type, either CODE or IRM for the corresponding event.

Result

O

CC @ResultPhase

Phase to which the competitor arrived

IRM

O

CC @IRM

IRM for the particular event.

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

SortOrder

M

Numeric

Unique sort order for all results based on rank to break rank ties.

 

Result /Competitor

Competitor related to one final event result.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Competitor’s ID

Type

M

A

A for athlete

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID

Order

M

Numeric

Always 1 (for Athlete)

 

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

 Individual athlete’s extended result when Competitor @Type=”A” according to competitors’ rules.

Type

Code

Pos

Value

Description

ER_SB

SB_RCE_PTS

 

N(4).N(2)

9990.99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Race Points.

SB_HEAT_RANK

 

N(3)

990

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank in the heat where athlete finished the competition. Applies for SBX Finals.

 

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

 

Type/Code

Description

Expected

ER_SB/ SB_RCE_PTS

Race Points

Always

ER_SB/ SB_HEAT_RANK

Rank in the heat where athlete finished the competition

Always for SBX Finals

 

 

 

 

3.2.5.6  Message Sort

Sort by Result @SortOrder


 

 

3.2.6    Event’s Medallists

3.2.6.1  Description

The “Event’s Medallists” is a message containing the list of medallists awarded in one particular event.

 

 

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

DDGEEE000

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

DocumentType

DT_MEDALLISTS

Event’s Medallists message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or partial.

“OFFICIAL” /

“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.

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 sent with ResultStatus=PARTIAL when the information of the medallist is known but the final event Unit is not yet finished.

 

The message is sent with ResultStatus=OFFICIAL when the medallists are official known.

 

For some sports, bronze medals are known before the end of the final event unit. In this case the message is sent the first time with the bronze medallists, and the second time with all the medallists.

 

Trigger also after any major change.

 

 


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

 

 

 

 

 

Medal (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Phase

 

 

 

 

 

Unit

 

 

 

 

 

Competitor

 

 

 

 

 

 

Type

 

 

 

 

 

Code

 

 

 

 

 

Order

 

 

 

 

 

Composition

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 


3.2.6.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Medal

Attribute

M/O

Value

Comments

Code

M

CC @MedalType

Medal type.

 

All the Competitors with the same CC@MedalType are not grouped in the same element.

Phase

M

CC @Phase

Phase code in which a medal was awarded.

 

It is used in case of disciplines like Ice Hockey or Basketball, with the bronze medal and the gold medal awarded in different event units.

Unit

M

CC @Unit

Unit code in which a medal was awarded.

 

It is used in case of disciplines like Ice Hockey or Basketball, with the bronze medal and the gold medal awarded in different event units.

 

Medal /Competitor

Attribute

M/O

Value

Comments

Type

M

A

Individual events:

A for athlete

Code

M

S(20) with no leading zeroes

Competitor’s ID

Order

M

Numeric

Competitor order (Send 1 by default). In the case of tie the order is defined for the sport rules.

 

Medal /Competitor /Composition /Athlete

(Include all members that won the medal according to sport rules if Competitor @Type=”T”)

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Competitor’s ID

Order

M

Numeric

Competitor order (Send 1 by default).

In the case of tie, order defined like sport rules.

 

 

3.2.6.6  Message Sort

The message is sorted according to the medal type. Moreover, in case of tie the order is according to the Competitor@Order (given by the sport rule). Team members are sorted according to the Athlete@Order.


 

 

3.2.7    Brackets

3.2.7.1  Description

The brackets message contains the brackets information for one particular event. It is used in events where there is a necessity to know in advance how successive event units will be filled as the competition progresses. In the early stages of the competition, it indicates how each of the event units will be built from the winners/losers, or other competition rules of the previous event units.

 

The message has to be sent just for finals on PGS, PSL and SBX events.

 

 

3.2.7.2  Header Values

3.2.7.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEE000

DD should be according to CC @Discipline

G should be according to CC @DisciplineGender

EEE should be according to CC @Event

DocumentType

DT_BRACKETS

Brackets message

ResultStatus

CC @ResultStatus

Status of the 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.7.3  Trigger and Frequency

3.2.7.3.1  PiT Triggers

This message should be sent at the very beginning of a competition, as soon as a brackets graph can be established.

 

Send when a match/event unit is completed, for Unofficial and Official status. Therefore it is triggered twice (with both status) for each event unit. The message should be updated including information oneach competitor in the different bracket items.

 

The @ResultStatus attribute will vary depending on the competition status.

 

•  Send with ResultStatus = "INTERMEDIATE" until the last event unit (GM Match) is Unofficial (i.e. for all event units up until the Gold Medal match is completed for an event)

 

•  Send with ResultStatus = "UNOFFICIAL" when the last event unit for an event (GM match) has Unofficial status.

 

•  Send with ResultStatus = "OFFICIAL" when the last event unit for an event (GM match) has Official status.

 

Trigger also after any major change.

 

 


3.2.7.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

 

 

 

 

 

 

Bracket

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

BracketItems (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

BracketItem (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Order

 

 

 

 

 

 

Unit (0,1)

 

 

 

 

 

 

 

Phase

 

 

 

 

 

 

Unit

 

 

 

 

 

ExtBracketItems (0,1)

 

 

 

 

 

 

 

ExtBracketItem (1,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

NextUnit (0,1)

 

 

 

 

 

 

 

Phase

 

 

 

 

 

 

Unit

 

 

 

 

 

NextUnitLoser (0,1)

 

 

 

 

 

 

 

Phase

 

 

 

 

 

 

Unit

 

 

 

 

 

CompetitorPlace (1,N)

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

PreviousUnit (0,1)

 

 

 

 

 

 

 

Phase

 

 

 

 

 

 

Unit

 

 

 

 

 

Competitor (0,1)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Type

 


3.2.7.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Bracket

Attribute

M/O

Value

Comments

Code

M

CC @Bracket

Bracket code to identify a bracket item.

 

Bracket /BracketItems

Attribute

M/O

Value

Comments

Code

M

CC @BracketItems

Each BracketItems should include all BracketItem grouped by their CC @BracketItems

 

Bracket /BracketItems /BracketItem

Attribute

M/O

Value

Comments

Code

M

CC @BracketItems

Code that categorizes each bracket item

Order

M

N(2)

90

Sequential number inside of BracketItems to indicate the order, always start by 1

 

Bracket /BracketItems /BracketItem /Unit

Unit related to the BracketItem.

Attribute

M/O

Value

Comments

Phase

M

CC @Phase

Phase code for the bracket item

Unit

O

CC @Unit

Unit code for the bracket item

 

Bracket /BracketItems /BracketItem /ExtBracketItems /ExtBracketItem

ExtBracketItems /ExtBracketItem are optional elements according to competitors’ rules.

Type

Code

Pos

Value

Description

EB_SB

SB_BI_ID

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

BracketItem sequential number (to sort BracketItem @Code) whenever it is heat, quarterfinal or semifinal.