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... List of teams / List of teams update. 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... Start List 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.3    Trigger and Frequency. 2

3.2.3.3.1     PiT 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... Event Unit 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... Discipline Configuration. 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... Event Unit Weather Conditions. 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

4   Messages Sequence  2

5   Codes  2

5.1.. Global Codes. 2

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

Photofinish

PiT

 

DT_PRESSPHOTOFINISH_LK

Press Photo finish

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

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

 

 

 

 

Class

 

 

 

 

Guide

 

 

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. However, it will be listed the discipline of the message

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)

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

 

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

For team members:

N(3)-N(1) 990-9

 

Or

 

For single athletes:

N(3) 999

Bib number.

 

Bib number is in fact a special Event Entry. However, since it is very meaningful in the sports that make use of this attribute, it has been considered as an attribute, although it was part of EventEntry in the previous versions.

Send only in the Case of Current=”true”.

Class

O

CC @SportClass

Not used for Olympics

Guide

O

S(20) with no leading zeroes

Not used for Olympics

 

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

Competition

 

 

 

 

 

Code

 

 

 

 

Team (1,N)

 

 

 

 

 

Code

 

 

 

 

Organisation

 

 

 

 

Number

 

 

 

 

Name

 

 

 

 

Gender

 

 

 

 

Current

 

 

 

 

ModificationIndicator

 

 

 

 

Composition (0,1)

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

Code

 

 

 

 

Order

 

 

Discipline (0,1)

 

 

 

 

 

Code

 

 

 

 

RegisteredEvent (0,1)

 

 

 

 

 

Event

 

 

 

 

Gender

 

 

 

 

Bib

 


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)

Organisation

M

CC @Organisation

Team organisation’s ID

Number

M

N(2)

Team’s number. In the case there is not more than one team for one organisation participating in one event, it will be 1.

 

For BT it will be 1

Name

M

S(73)

Team’s name.

 

It will apply to some of the disciplines. If there is not any special rule for that discipline, send the Description of the code CC@Organisation. It is Optional in the case of  List of Team Update when the @ ModificationIndicator=D

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

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

 

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

Bib

M

N(3)

990

Bib number mandatory for relay event

 

 

3.2.2.6  Message Sort

The message is sorted by Team @Code.


 

 

3.2.3     Start List

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

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

 

Trigger also after any major change.

 

Please, follow the general definition above, taking also into account the following:

- For Individual/Sprint events - after the draw.

 

- For Relay event – after de entry deadline.

 

- For Pursuit event - after the Sprint results.

 

- For Mass Start - before the start of competition.

 

 


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

Competition

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

 

 

Competitor (0,N)

 

 

 

 

 

 

 

Organisation

 

 

 

 

 

 

Order

 

 

 

Officials (0,1)

 

 

 

 

 

 

 

Official (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Function

 

 

 

 

 

 

Order

 

 

 

 

Start (0,N)

 

 

 

 

 

 

 

StartOrder

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Type

 

 

 

 

 

 

Bib

 

 

 

 

 

 

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.3.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_BT

BT_ST_PROVISIONAL

 

N(1)

0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos :

Do not send anything

For @Value:

In case of Relay send 0

In case of Mass Start: send the number of competitions that are complete

BT_ZEROING_ALLOCATION

N(2)

90

“P” or “S”

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send the lane number (1..30)

For @Value:

Send proposed value,

P for Prone and S for Standing

BT_RANGE_ALLOCATION

N(2)

90

“P” or “S”

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send the lane number (1..30)

For @Value:

Send proposed value,

P for Prone and S for Standing

BT_P_CONFIRM

 

DateTime

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Date time when ahtlete must confirm the participation

BT_BIB_DIST

 

DateTime

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Bib numbers distribution

 

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

 

Type/Code

Description

Expected

UI_BT/ BT_ST_PROVISIONAL

Provisional Start List

Send in the case of provisional Start List only

UI_BT/ BT_ZEROING_ALLOCATION

Allocation of lanes for zeroing of rifles

Send always, except for Official Training and provisional start list (mass start)

UI_BT/ BT_RANGE_ALLOCATION

Range Allocation

In the case of official training only

UI_BT/ BT_P_CONFIRM

Participation confirmation by athletes

Send in the case of mass start list (also provisional start list)

UI_BT/ BT_BIB_DIST

Bib number distribution

Send in the case of mass start list (also provisional start list)

 

 

 

UnitInfos /UnitInfo /Competitor

UnitInfo /Competitor /Composition is optional, because sometimes it is known the teams related to a UnitInfo, but not the team members related to this UnitInfo.

Attribute

M/O

Value

Comments

Organisation

M

CC @Organisation

Organisation ID

Order

O

N(3)

Order of the organisation associated to the UnitInfo, if more than one organisation associated. Do not send otherwise

 

Officials /Official

Official associated to the event unit.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Official’s code

Function

M

CC @Function

Send the function code for:

IBU Technical Delegate - Chairman

IBU Assistant Technical Delegate

International Referee for Course

Member

Order

M

Numeric

Official’s order following the Sport Rules

 

Start

This element is optional (due to the information availability, the information related to the event unit can be sent before the competitors information).

Attribute

M/O

Value

Comments

StartOrder

O

Numeric

Start order of the competitor in the start list (do not send for mass start lists or relay).

SortOrder

M

Numeric

Same as @Bib.

 

However, in the case of provisional mass start lists, the sort order should also consider

 

In the case of provisional start list (mass start), the order would be according to:

 

For medal winners:

1 – Number of gold medals 2 – Number of silver medals 3 – Number of bronze medals 4 –Family name 5 – Given name

 

For top 15 athletes qualified by world cup total score:

1 – World cup rank 2 - Family name 3 – Given name

 

For athletes qualified in these Games:

1 – Olympic Games Points 2 - Family name 3 – Given name

 

For reserve athletes::

1 – Olympic Games points 2 - Family name 3 – Given name

 

Start /Competitor

Competitor participating in the event unit

 

Start /Competitor /Composition is optional for a similar reason: knowing the teams participating in one event unit, it is not known yet the team members participating.

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

Bib

O

Numeric

Team’s bib number, to be sent mandatory just in the case of relay event units

 

Start /Competitor /EventUnitEntry

Type

Code

Pos

Value

Description

EU_BT

BT_START_ROW

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Start row

 

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

 

Type/Code

Description

Expected

EU_BT/ BT_START_ROW

Start row

Always, for relay 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

In the case of relay, it will be: 1 – r(ed), 2 – g(reen), 3 – y(ellow), 4 – b(lue).

Bib

M

For team members:

N(3)-N(1) 990-9

 

Or

 

For single athletes:

N(3) 999

Skier bib number. If the bib is not known that field should be empty (Attribute = "").

 

Start /Competitor /Composition /Athlete /EventUnitEntry

Team member or individual athlete’s event unit entry.

Type

Code

Pos

Value

Description

EU_ENTRY

BT_START_ROW

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Start row

BT_LEG_NUMBER

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Leg number of the team member

BT_COLOUR

 

S(1)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Bib colour (“b”, “g”, “r” or “y”)

BT_START_TIME

 

HH:MM:SS

00:00:00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Start time for the competitor

BT_START_GROUP

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Start group for the competitor

BT_START_BEHIND

 

MM:SS

90:00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Start behind for the competitor, where MM=minutes and SS=seconds

BT_LANE

 

N(3)

990

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Lane number

BT_PROVISIONAL_BIB

 

N(3)

990

 

Or

 

‘***’

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Provisional bib number for mass start provisional start list.

Send ‘***’ if competitor out of NOC quota.

Send an empty value if reserve athletes qualified by Olympic Games Points.

BT_MS_GROUP

 

CC @MassGroup

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Group for provisional mass start list according to one of the codes

BT_WC_RANK

 

N(3)

990

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send world cup rank, if information available

BT_OG_POINTS

 

N(3)

990

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send Olympic games points, if information available

 

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

 

Type/Code

Description

Expected

EU_ENTRY/ BT_START_ROW

Start row

Always, for mass event units except for the provisional start list (mass start)

EU_ENTRY/ BT_LEG_NUMBER

Leg number of the team member

Always, for relay

EU_ENTRY/ BT_COLOUR

Bib colour

Bib colour (“b”, “g”, “r” or “y”), for relay

EU_ENTRY/ BT_START_TIME

Start time

Always, for individual and sprint

EU_ENTRY/ BT_START_GROUP

Start group

Always, for individual and sprint

EU_ENTRY/ BT_START_BEHIND

Start behind time

Always, for pursuit

EU_ENTRY/ BT_LANE

Lane number

Always, for pursuit

EU_ENTRY/ BT_PROVISIONAL_BIB

Provisional bib number

Send always in the case of mass start list (for provisional start list).

Once the official start list for mass start is known, send also with the last provisional bib number used.

EU_ENTRY/ BT_MS_GROUP

Group for provisional mass start list

Send in the case of mass start list (also provisional start list)

EU_ENTRY/ BT_WC_RANK

World cup rank

Send in the case of mass start list (also provisional start list)

EU_ENTRY/ BT_OG_POINTS

Olympic games points

Send in the case of mass start list (also provisional start list)

 

 

 

 

3.2.3.6  Message Sort

The message is sorted by the Start@SortOrder attribute.


 

 

3.2.4     Event Unit Results

3.2.4.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.4.2  Header Values

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

 

Each ODF Sport Data Dictionary will have to complete the explanation regarding to this attribute

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

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType for some messages.

Optional attribute only for special cases in result messages (for example TIE BREAK in GA,… ) because there are a lot of data.

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

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

 

Each ODF Sport Data Dictionary will have to update the definition of this attribute

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

3.2.4.3.1  PiT Triggers

Every 5 minutes during competition, the message will be sent with intermediate results.

o  ResultStatus in the headers will have the value “INTERIM” for Sprint and Individual Events and “INTERMEDIATE” for the rest.

 

Once the first competitors arrive, the message will be sent with partial results.

o  ResultStatus in the headers will have the value “PARTIAL”.

 

o  The message will be resent with partial results every 10 minutes until the last competitor completes the race (mass start and relay). For team sprint, after the 5 top teams finish (semifinals), or after the 3 top teams finish (final).

 

Then proceed with unofficial and official results, as expected.

 

 

3.2.4.3.2  RT Triggers

The following is the trigger for this message in ODF-RT:

•  ResultStatus=”LIVE_UPDATE”

o  T1: Trigger at the beginning of the day.

 

o  T2: Trigger when a competitor passes through an intermediate point.

 

o  T3: Trigger when the leader crosses a timing point.

 

o  T4: Trigger after each shot of a competitor.

 

o  T5 : Trigger when a competitor leaves a shooting range. This trigger is not currently used. For the moment T4 (a much harder trigger than T5) should be tested in order to test stress performance. However, T5 would be enough in the case of BT if T4 was problematic ).

 

o  T6: Trigger when a competitor arrives to finish.

 

o  T7: Trigger when a competitor finishes a loop.

 

o  T8: Trigger when a competitor crosses a pre-timing point for Sprint and Individual events only.

 

o  T9: Trigger when an athlete finishes a leg for Relay only.

 

o  T10: Trigger when an athlete arrives to the end of a sector.

 

o T11: Trigger at the beginning of the competition with initial values.

 

oT12: keep the Y for 30 sec and send N then but only for the interval starts events.

 

For the other ResultStatus we should follow the general definition.

 

 


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

 

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

 

 

EndDate

 

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

Competitor (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

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

 

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

 

UnitInfos /UnitInfo

Unit info item associated to the event unit.

Type

Code

Pos

Value

Description

UI_RESULTS

BT_CURRENT_INTERMEDIATE

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Last intermediate point reached by the first competitor (1,2,3,..).

Finish line is considered as an intermediate point.

BT_CURRENT_LEG

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Current Leg

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

UI_RESULTS/ BT_CURRENT_INTERMEDIATE

Event unit’s last intermediate point reached by the first competitor

Always, for all event units

N

T2,T11

UI_RESULTS/ BT_CURRENT_LEG

Current leg reached by the first competitor

Always, just for Relay event

N

T3, T11

 

 

 

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 of the competitor in the corresponding event unit. This attribute is optional because the competitor could get an invalid rank mark.

The Rank attribute will be filled with empty rank "" in case the competitor is pending of a Photo Finish decision

N

T2, T5

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

Only if necessary

Result

O

HH:MM:SS.t

99:99:90.0

Result for the particular event unit.

 

Send just in the case @ResultType is Time or both Time and IRM (see codes section)

 

HH is hours MM is minutes, SS is seconds, t is tenth of second

N

T2, T5

IRM

O

CC @IRM

IRM for the particular event unit

 

Send just in the case @ResultType is IRM, or both time and IRM (see codes section)

N

T2, T5

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 the attribute regardless the competitor is ranked or not (this includes ranked, none-ranked and IRM athletes/team).

N

T2, T5

ResultType

O

CC @ResultType

Result type, either time, IRM or IRM+time for the corresponding event unit

N

Only if necessary

 

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

N

When available

Type

M

T,A

T for team

A for athlete

N

When available

Bib

O

Numeric

Team’s bib number, to be sent mandatory just in the case of team event units

N

When available

 

Result /Competitor /ExtendedResults /ExtendedResult

Type and extension Type

Code

Extension Code

Pos or extension Pos

Value or extension Value

Description

ER_BT

BT_DIFF

 

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Event unit’s time difference for the whole team (for Result @Rank=1, send “0.0”, however)

 

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_SHOOTING

 

 

N/A

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Do not send anything

BT_TOT_PENALTIES

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total penalties so far of all shooting sessions for the whole team

BT_TOT_SPARE

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total spare round so far of all shooting sessions for the whole team.

BT_TOT_PENALTY_PRONE

 

N(2)

90

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Total prone penalties for team (Relay)

BT_TOT_PENALTY_STANDING

 

N(2)

90

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Total standing penalties for team (Relay)

BT_TOT_SPARE_PRONE

 

N(2)

90

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Prone spare rounds for team (Relay)

BT_TOT_SPARE_STANDING

 

N(2)

90

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Standing spare rounds for team (Realy)

BT_TOT_SHOOTINGTIME

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Shooting time for this shooting session

BT_TIME_ADJUSTMENT

 

Numeric

(+)HH:MM:SS.t

(+)99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed extension code

For @Pos:

Send intermediate Number in which time was adjusted

For @Value:

Time adjustment, sent only from the shooting range

BT_POT_DSQ

 

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y when it is a Potential DSQ.

Send N when decision is made.

BT_RULE

 

 

String

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

IBU rule number

BT_FF

 

 

S(1)

(Y,P,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send Y for Evaluated Status and P for Pending Status for the Photo finish.

Send N if Pending and no photo decision is needed.

BT_TOT_PENALTIES

 

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total cumulative penalties of all shooting sessions for the whole team regardless of the shooting position.

In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

BT_TOT_SPARE

 

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total cumulative spare rounds of all shooting sessions for the whole team regardless of the shooting position.

In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

 

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

 

Type/Code/Extension Code

Description

Expected

RT Only

RT Trigger

ER_BT/ BT_DIFF

Event unit’s result time difference (whole team)

Always, just for relay event units

N

T2, T5

ER_BT/ BT_SHOOTING

Cumulative information for the whole team after the shooting

Always, just for relay event units

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_TOT_PENALTIES

Total penalties so far of all shooting sessions for the whole team

Always, just for relay event units

N

N/A

ER_BT/ BT_SHOOTING/ BT_TOT_SPARE

Total spare round so far of all shooting sessions for the whole team

Always, just for relay event units

N

N/A

ER_BT/ BT_SHOOTING/ BT_TOT_PENALTY_PRONE

Total prone penalties for team (Relay)

Always, just for relay event units

N

N/A

ER_BT/ BT_SHOOTING/ BT_TOT_PENALTY_STANDING

Total standing penalties for team (Relay)

Always, just for relay event units

N

N/A

ER_BT/ BT_SHOOTING/ BT_TOT_SPARE_PRONE

Prone spare rounds for team (Relay)

Always, just for relay event units

N

N/A

ER_BT/ BT_SHOOTING/ BT_TOT_SPARE_STANDING

Standing spare rounds for team (Realy)

Always, just for relay event units

N

N/A

ER_BT/ BT_SHOOTING/ BT_TOT_SHOOTINGTIME

Shooting time for this shooting session

Always, just for relay event units

N

N/A

ER_BT/ BT_TIME_ADJUSTMENT

An addition or subtraction of time from a competitor's or a team

competition time as decided by the Jury

N/A

N

Only if necessary

ER_BT/ BT_POT_DSQ

Potential team disqualification, time adjustment or protest

For relay event units, send just if potential DSQ

N

T2, T5

ER_BT/ BT_RULE

IBU rule number, only for Jury decisions

Only if it is available

N

T2, T5

ER_BT/ BT_FF

Photo finish status

Just if applies

N

T2, T5

ER_BT/ BT_TOT_PENALTIES

Total cumulative penalties of all shooting sessions for the whole team regardless of the shooting position.

In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

Always, just for relay event units

N

Only if necessary

ER_BT/ BT_TOT_SPARE

Total cumulative spare rounds of all shooting sessions for the whole team regardless of the shooting position.

In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

Always, just for relay event units

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. Can belong to a team member or an individual athlete.

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

When available

Bib

M

For team members:

N(3)-N(1) 990-9

 

Or

 

For single athletes:

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_BT

BT_DIFF

 

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Event unit’s time difference for the single athlete (for Result @Rank=1, send “0.0”, however)

 

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_SHOOTING

 

N(2)

90

N/A

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Send the current shooting session number

For @Value:

Do not send anything

BT_RECENT_DEPARTURE

 

S(1)

Y,N

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Send ‘Y’ in the case of most recent time departure after shooting.

otherwise send N. Just for RT.

BT_CURRENT_SHOOT

 

S(1)

(Y,N)

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send ‘Y’ if the competitor is currently in the range.

otherwise send N

BT_LAST_SHOOT

 

S(1)

(Y,N)

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send ‘Y’ if case of the most recent time (The athlete has completed shooting). Otherwise send N

BT_PENALTY

 

N(1)

0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Number of shooting penalties for this shooting session (0..5)

BT_SPARE

 

N(1)

0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Number of shooting spare rounds for this shooting session (0..5).

It applies just to relay event units.

BT_SHOOTINGTIME

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Shooting time for this shooting session

BT_TOT_PENALTIES

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total penalties so far of all shooting sessions

BT_TOT_SPARE

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total spare round so far of all shooting sessions. It applies just to relay event units.

BT_TOT_SHOOTINGTIME

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total cumulative shooting times of all shooting sessions

BT_DEPARTURE_TIME

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Range departure time for current shoot (after the penalty loop)

BT_DEPARTURE_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Range departure time behind leader (current shoot)

BT_ARRIVING_TIME

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Competitors arriving time at the range area

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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.otherwise send N

BT_CUM_PENALTIES

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

The cumulative team penalties so far for this shooting position. It applies just to relay event units.

BT_CUM_SPARE

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

The cumulative team spare rounds so far for this shooting position. It applies just to relay event units.

BT_INTERMEDIATE

 

N(2)

90

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the intermediate result point, from 1 to the total number of intermediate result points

For @Value:

Cumulative time at the @Pos intermediate result point for the single athlete.

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_RECENT_TIME

 

S(1)

Y,N

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Send ‘Y’ in the case of most recent time. Otherwise send N

For interval starts send BT_RECENT_TIME=Y for the most recent time of each athlete, send BT_RECENT_TIME=N after 30 seconds. For mass starts send BT_RECENT_TIME=Y for the most recent time of each split.

Just for RT.

BT_PENALTY

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Penalties (not cumulative) at this intermediate result point

BT_TOT_PENALTIES

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Cumulative Penalties after this intermediate result point

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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. Otherwise send N

BT_IDX

 

N(3)

990

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on rank for each intermediate point.

BT_IDX_POS

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the athletes order of arrival to the intermediate point.

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the intermediate

BT_LEG

 

Numeric

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

The number that identifies the leg or round, from 1 to 4

For @Value:

Cumulative time after the @Pos leg or round for the athletes

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_PENALTY

 

N(2)

90

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Number of shooting penalties at this leg

BT_SPARE

 

N(2)

90

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Number of shooting spare rounds at this leg

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader at the end of the leg

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete when arriving at the end of the leg according to the cumulative time at the end of the leg

BT_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. otherwise send N

BT_IDX

 

N(3)

990

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort the team member on the leg

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the leg or round

BT_LOOP

 

N(2)

90

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the loop, from 1 to the total number of loops

For @Value:

Time for the Pos loop. It is not cumulative. It will be for single athlete, or team member in the case of relay

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index to sort according to BT_RANK

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the loop

BT_COURSE

 

Numeric

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the loop, starting from 1.

For @Value:

Course time (not cumulative) for the referred intermediate. It is the skiing time only without shooting range time.

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader.

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete when arriving at the end of the loop according to the cumulative time at the end of the loop.

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort the athlete

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the loop.

BT_SECTOR

 

Numeric

90

 

90

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the sector or loop, starting from 1.

For @Value:

Time for the Pos sector or loop. It is not cumulative. It will be for single athlete, or team member in the case of relay

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader at the sector or loop.

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank at the sector or loop.

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort the athlete

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the sector or loop.

BT_LEG_SECTOR

 

Numeric

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the sector or loop, from 1 to the total number of sectors or loops

For @Value:

Sector time in the @Pos leg or round for the team member in the leg (relay) or round (team sprint). It is not cumulative.

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank at the leg or round for the team member in the leg (relay) or round (team sprint), according to  BT_LEG_SECTOR time.

BT_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. otherwise send N

BT_IDX

 

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 team member in the leg (relay) or round (team sprint).

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference after the leg or round for the team member in the leg (relay) or round (team sprint). Send “0.0” if the rank for that leg/round is 1.

 

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the leg or round

BT_TOT_COURSE

 

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Total time on course (skiing only without shooting range time)

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader at the end of the leg

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete when arriving at the end of the leg according to the cumulative time at the end of the leg

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Sort order of the athlete according to BT_RANK

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the total course

BT_TOT_RANGE

 

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Total range time.

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the total range

BT_ISOLATED_PURSUIT

 

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Isolated pursuit time. It applies just to pursuit event units, and it is the difference of the event unit result, and the start behind time

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the course (pursuit)

BT_SKI_TIME

 

 

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Ski time regardless of the penalties. It applies just to Indidivual event.

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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.  otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the course

BT_PRETIMING

 

Numeric

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the pre-timing point, from 1 to the total number of intermediate result points

For @Value:

Cumulative time at the @Pos pre-timing point for the single athlete

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank at the  pre-timing point for the single athlete, according to BT_INTERMEDIATE_RESULT_TIME

BT_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. otherwise send N

BT_IDX

 

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

BT_IDX_POS

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the athletes order of arrival to the pre-timing point.

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference at the pre-timing point for the single athlete (send “0.0” if the pre-timing rank for that point is 1)

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

IRM at the @Pos intermediate

BT_POT_DSQ

 

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y when it is a Potential DSQ.

Send N when decision is made.

BT_RULE

 

 

String

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

IBU rule number

BT_TIME_ADJUSTMENT

 

Numeric

(+)HH:MM:SS.t

(+)99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Send intermediate Number in which time was adjusted

For @Value:

Time adjustment, sent only from the shooting range

BT_FF

 

 

S(1)

(P,Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y for Evaluated Status and P for Pending Status for the Photo finish.

Send N if Pending and no photo decision is needed.

BT_PENALTY_TIME

 

Numeric

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the intermediate, starting from 1.

For @Value:

Penalty time (not cumulative).

HH is hours MM is minutes, SS is seconds, t is tenth of second

In case of no penalties send 0.0

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort the athlete

BT_RANGE

 

Numeric

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the intermediate, starting from 1.

For @Value:

Range time (not cumulative). Time of staying in shooting range area number @Pos (range time + course time = total time). Send just in the intermediate with shooting. For the other intermediates, do not include this extension

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank of the athlete

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort the athlete

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the range.

BT_TOT_PENALTIES

 

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Total cumulative penalties of all shooting sessions regardless of the shooting position

In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

BT_TOT_SPARE

 

 

Numeric

For @Type: Send proposed type (that is, the same @Code as the parent ExtendedResult element ) For @Code: Send proposed extension code For @Pos: Do not send anything For @Value: Total cumulative spare of all shooting sessions regardless of the shooting position In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

BT_CUM_PENALTIES

 

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

The cumulative team penalties so far for this athlete regardless his shooting position. It applies just to relay event units

BT_CUM_SPARE

 

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

The cumulative team spare rounds so far for this athlete regardless his shooting position. It applies just to relay event units.

BT_SHOOTING_SECTOR

 

Numeric

90

HH:MM:SS.t

99:99:90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

The number that identifies the shooting position 1…8.

For @Value:

Time for the Pos. It is not cumulative. It will be for team member.

HH is hours MM is minutes, SS is seconds, t is tenth of second

BT_DIFF

 

+HH:MM:SS.t

+99:99:90.0

 

Or

 

“0.0”

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Time difference to the leader at the sector for the current shoot.

BT_RANK

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Rank at the sector for the current shoot.

BT_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. otherwise send N

BT_IDX

 

Numeric

For @Type:

Send proposed type (that is, the same @Code as the parent ExtendedResult element )

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Index based on the rank to sort the athlete

BT_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

IRM at the sector for the current range.

 

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

 

Type/Code/Extension Code

Description

Expected

RT Only

RT Trigger

ER_BT/ BT_DIFF

Event unit’s result time difference

Always, except relay event units

N

T2, T5

ER_BT/ BT_SHOOTING

Information of current shooting session

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_RECENT_DEPARTURE

Send ‘Y’ in the case of most recent time departure after shooting.

Always

Y

Only if necessary, T12

ER_BT/ BT_SHOOTING/ BT_CURRENT_SHOOT

Send ‘Y’ if the competitor is currently in the range.

otherwise send N

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_LAST_SHOOT

Send ‘Y’ if case of the most recent time (The athlete has completed shooting).

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_PENALTY

Number of shooting penalties for this shooting session (0..5)

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_SPARE

Number of shooting spare rounds for this shooting session (0..5).

It applies just to relay event units.

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_SHOOTINGTIME

Shooting time for this shooting session

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_TOT_PENALTIES

Total penalties so far of all shooting sessions

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_TOT_SPARE

Total spare round so far of all shooting sessions. It applies just to relay event units.

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_TOT_SHOOTINGTIME

Total cumulative shooting times of all shooting sessions

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_DEPARTURE_TIME

Range departure time for current shoot (after the penalty loop)

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_DEPARTURE_DIFF

Range departure time behind leader (current shoot)

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_ARRIVING_TIME

Competitors arriving time at the range area

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_RANK

Rank of the athlete

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_ERANK

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

Always

N

Only if necessary

ER_BT/ BT_SHOOTING/ BT_CUM_PENALTIES

The cumulative team penalties so far for this shooting position.

Only for relay events

N

T4

ER_BT/ BT_SHOOTING/ BT_CUM_SPARE

The cumulative team spare rounds so far for this shooting position.

Only for relay events

N

T4

ER_BT/ BT_INTERMEDIATE

Cumulative time, rank, time difference, penalties, cumulative penalties at the intermediate result point

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_RECENT_TIME

Send ‘Y’ in the case of most recent time.

For interval starts send BT_RECENT_TIME=Y for the most recent time of each athlete, send BT_RECENT_TIME=N after 30 seconds. For mass starts send BT_RECENT_TIME=Y for the most recent time of each split.

Just for RT.

Always, for all event units

Y

T2, T5, T12

ER_BT/ BT_INTERMEDIATE/ BT_PENALTY

Penalties (not cumulative) at this intermediate result point

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_TOT_PENALTIES

Cumulative Penalties after this intermediate result point

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_DIFF

Time difference to the leader

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_RANK

Rank of the athlete

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_ERANK

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

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_IDX

Index based on rank for each intermediate point.

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_IDX_POS

Index based on the athletes order of arrival to the intermediate point.

Always, for all event units

N

T2, T5

ER_BT/ BT_INTERMEDIATE/ BT_IRM

IRM at the intermediate

Always, for all event units

N

T2, T5

ER_BT/ BT_LEG

Total time, rank, time difference, penalties, spare rounds, etc. of the team member (leg)

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_PENALTY

Number of shooting penalties at this leg

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_SPARE

Number of shooting spare rounds at this leg

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_DIFF

Time difference to the leader at the end of the leg

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_RANK

Rank of the athlete when arriving at the end of the leg according to the cumulative time at the end of the leg

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_ERANK

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

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_IDX

Index based on the rank to sort the team member on the leg

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LEG/ BT_IRM

IRM at the leg or round

Always, just in the case of relay event units

N

T2, T5

ER_BT/ BT_LOOP

Time (not cumulative), rank, sort order at the @Pos loop (according to loop time) and time difference in a particular loop. For single athlete if not relay, or team member if relay.

Always

N

T2, T5

ER_BT/ BT_LOOP/ BT_DIFF

Time difference to the leader

Always

N

T2, T5

ER_BT/ BT_LOOP/ BT_RANK

Rank of the athlete

Always

N

T2, T5

ER_BT/ BT_LOOP/ BT_ERANK

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

Always

N

T2, T5

ER_BT/ BT_LOOP/ BT_IDX

Index to sort according to BT_RANK

Always

N

T2, T5

ER_BT/ BT_LOOP/ BT_IRM

IRM at the loop

Always

N

T2, T5

ER_BT/ BT_COURSE

Course time

Always

N

When available

ER_BT/ BT_COURSE/ BT_DIFF

Time difference to the leader

Always

N

When available

ER_BT/ BT_COURSE/ BT_RANK

Rank of the athlete when arriving at the end of the loop according to the cumulative time at the end of the loop.

Always

N

When available

ER_BT/ BT_COURSE/ BT_ERANK

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

Always

N

When available

ER_BT/ BT_COURSE/ BT_IDX

Index based on the rank to sort the athlete

Always

N

When available

ER_BT/ BT_COURSE/ BT_IRM

IRM at the loop

Always

N

When available

ER_BT/ BT_SECTOR

Sector time

Always, except Relay event units

N

When available

ER_BT/ BT_SECTOR/ BT_DIFF

Time difference to the leader at the sector or loop.

Always, except Relay event units

N

When available

ER_BT/ BT_SECTOR/ BT_RANK

Rank at the sector or loop.

Always, except Relay event units

N

When available

ER_BT/ BT_SECTOR/ BT_ERANK

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

Always, except Relay event units

N

When available

ER_BT/ BT_SECTOR/ BT_IDX

Index based on the rank to sort the athlete

Always, except Relay event units

N

When available

ER_BT/ BT_SECTOR/ BT_IRM

IRM at the sector or loop.

Always, except Relay event units

N

When available

ER_BT/ BT_LEG_SECTOR

Time for a particular leg  (not cumulative) after the @Pos leg  for the team member in the leg (relay)

Always just in the case of relay event units (legs)

N

T2

ER_BT/ BT_LEG_SECTOR/ BT_RANK

Rank at the leg or round for the team member in the leg (relay) or round (team sprint), according to  BT_LEG_SECTOR time

Always just in the case of relay event units (legs)

N

T2

ER_BT/ BT_LEG_SECTOR/ BT_ERANK

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

Always just in the case of relay event units (legs)

N

T2

ER_BT/ BT_LEG_SECTOR/ BT_IDX

Index based on the Rank to sort the team member in the leg (relay) or round (team sprint).

Always just in the case of relay event units (legs)

N

T2

ER_BT/ BT_LEG_SECTOR/ BT_DIFF

Time difference after the leg or round for the team member in the leg (relay) or round (team sprint). Send “0.0” if the rank for that leg/round is 1.

 

HH is hours MM is minutes, SS is seconds, t is tenth of second

Always just in the case of relay event units (legs)

N

T2

ER_BT/ BT_LEG_SECTOR/ BT_IRM

IRM at the leg or round

Always just in the case of relay event units (legs)

N

T2

ER_BT/ BT_TOT_COURSE

Total time on course

Always

N

T2, T5

ER_BT/ BT_TOT_COURSE/ BT_DIFF

Time difference to the leader at the end of the leg

Always

N

T2, T5

ER_BT/ BT_TOT_COURSE/ BT_RANK

Rank of the athlete when arriving at the end of the leg according to the cumulative time at the end of the leg

Always

N

T2, T5

ER_BT/ BT_TOT_COURSE/ BT_ERANK

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

Always

N

T2, T5

ER_BT/ BT_TOT_COURSE/ BT_IDX

Sort order of the athlete according to BT_RANK

Always

N

T2, T5

ER_BT/ BT_TOT_COURSE/ BT_IRM

IRM at the total course

Always

N

T2, T5

ER_BT/ BT_TOT_RANGE

Total range time

Always

N

T2, T5

ER_BT/ BT_TOT_RANGE/ BT_DIFF

Time difference to the leader

Always

N

T2, T5

ER_BT/ BT_TOT_RANGE/ BT_RANK

Rank of the athlete

Always

N

T2, T5

ER_BT/ BT_TOT_RANGE/ BT_ERANK

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

Always

N

T2, T5

ER_BT/ BT_TOT_RANGE/ BT_IDX

Index based on the rank to sort

Always

N

T2, T5

ER_BT/ BT_TOT_RANGE/ BT_IRM

IRM at the total range

Always

N

T2, T5

ER_BT/ BT_ISOLATED_PURSUIT

Isolated pursuit time, rank (according to the isolated pursuit time) and time difference.

Send just in pursuit event units

N

T6

ER_BT/ BT_ISOLATED_PURSUIT/ BT_DIFF

Time difference to the leader

Send just in pursuit event units

N

T6

ER_BT/ BT_ISOLATED_PURSUIT/ BT_RANK

Rank of the athlete

Send just in pursuit event units

N

T6

ER_BT/ BT_ISOLATED_PURSUIT/ BT_ERANK

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

Send just in pursuit event units

N

T6

ER_BT/ BT_ISOLATED_PURSUIT/ BT_IDX

Index based on the rank to sort

Send just in pursuit event units

N

T6

ER_BT/ BT_ISOLATED_PURSUIT/ BT_IRM

IRM at the course (pursuit)

Send just in pursuit event units

N

T6

ER_BT/ BT_SKI_TIME

Ski time regardless of the penalties time, rank, time difference and sort order

Send just in Individual event

N

T6

ER_BT/ BT_SKI_TIME/ BT_DIFF

Time difference to the leader

Send just in Individual event

N

T6

ER_BT/ BT_SKI_TIME/ BT_RANK

Rank of the athlete

Send just in Individual event

N

T6

ER_BT/ BT_SKI_TIME/ BT_ERANK

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

Send just in Individual event

N

T6

ER_BT/ BT_SKI_TIME/ BT_IDX

Index based on the rank to sort

Send just in Individual event

N

T6

ER_BT/ BT_SKI_TIME/ BT_IRM

IRM at the course

Send just in Individual event

N

T6

ER_BT/ BT_PRETIMING

Cumulative time at the pre-timing  point

For Individual and Sprint events

N

T1

ER_BT/ BT_PRETIMING/ BT_RANK

Rank at the  pre-timing point for the single athlete, according to BT_INTERMEDIATE_RESULT_TIME

For Individual and Sprint events

N

T1

ER_BT/ BT_PRETIMING/ BT_ERANK

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

For Individual and Sprint events

N

T1

ER_BT/ BT_PRETIMING/ BT_IDX

Index based on the Rank to sort the single athletes

For Individual and Sprint events

N

T1

ER_BT/ BT_PRETIMING/ BT_IDX_POS

Index based on the athletes order of arrival to the pre-timing point.

For Individual and Sprint events

N

T1

ER_BT/ BT_PRETIMING/ BT_DIFF

Time difference at the pre-timing point for the single athlete (send “0.0” if the pre-timing rank for that point is 1)

HH is hours MM is minutes, SS is seconds, t is tenth of second

For Individual and Sprint events

N

T1

ER_BT/ BT_PRETIMING/ BT_IRM

IRM at the @Pos intermediate

For Individual and Sprint events

N

T1

ER_BT/ BT_POT_DSQ

Potential disqualification, time adjustment or protest

For all event units except for relay units, send just if potential DSQ

N

When available

ER_BT/ BT_RULE

IBU rule number, only for Jury decisions

Only if it is available

N

When available

ER_BT/ BT_TIME_ADJUSTMENT

Time adjustment

Just if applies

N

When available

ER_BT/ BT_FF

Photo finish status

Just if applies

N

When available

ER_BT/ BT_PENALTY_TIME

Penalty Time

Always

N

When available

ER_BT/ BT_PENALTY_TIME/ BT_IDX

Index based on the rank to sort the athlete

Always

N

When available

ER_BT/ BT_RANGE

Range Time

Always

N

T2, T5

ER_BT/ BT_RANGE/ BT_DIFF

Time difference to the leader

Always

N

T2, T5

ER_BT/ BT_RANGE/ BT_RANK

Rank of the athlete

Always

N

T2, T5

ER_BT/ BT_RANGE/ BT_ERANK

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

Always

N

T2, T5

ER_BT/ BT_RANGE/ BT_IDX

Index based on the rank to sort the athlete

Always

N

T2, T5

ER_BT/ BT_RANGE/ BT_IRM

IRM at the range.

Always

N

T2, T5

ER_BT/ BT_TOT_PENALTIES

Total cumulative penalties of all shooting sessions regardless of the shooting position

In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

Always

N

Only if necessary

ER_BT/ BT_TOT_SPARE

Total cumulative spare of all shooting sessions regardless of the shooting position In case of DNF, and not all shooting sessions are completed, send blank (Value=“”) to clean any value

Always

N

Only if necessary

ER_BT/ BT_CUM_PENALTIES

The cumulative team penalties so far for this athlete regardless his shooting position.

Only for relay events

N

T4

ER_BT/ BT_CUM_SPARE

The cumulative team spare rounds so far for this athlete regardless his shooting position

Only for relay events

N

T4

ER_BT/ BT_SHOOTING_SECTOR

Sector Time for the current shoot

Only for relay events

N

When available

ER_BT/ BT_SHOOTING_SECTOR/ BT_DIFF

Sector Time difference to the leader for the current shoot

Only for relay events

N

When available

ER_BT/ BT_SHOOTING_SECTOR/ BT_RANK

Sector Rank of the athlete for the current shoot

Only for relay events

N

When available

ER_BT/ BT_SHOOTING_SECTOR/ BT_ERANK

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

Only for relay events

N

When available

ER_BT/ BT_SHOOTING_SECTOR/ BT_IDX

Index based on the rank to sort the athlete

Only for relay events

N

When available

ER_BT/ BT_SHOOTING_SECTOR/ BT_IRM

Sector IRM for the current shoot.

Only for relay events

N

When available

 

 

 

 

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

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

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

The general rule is that this message is sent just at the end of the last event unit of one particular event.

 

Trigger also after any major change.

 

If there is any kind of sport specific rule, override it in each of the ODF Sport Data Dictionaries

 

 


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

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Composition

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos