Message Type	Message Name	Feed	Message extended
DT_SCHEDULE	Competition schedule	PiT
DT_SCHEDULE_UPDATE	Competition schedule update	PiT
DT_PARTIC / DT_PARTIC_UPDATE	List of participants by discipline / List of participants by discipline Update	PiT	X
DT_MEDALS	Medal standings	PiT
DT_MEDALLISTS_DAY	Medallists of the day	PiT
DT_GLOBAL_GM	Global good morning	PiT
DT_GLOBAL_GN	Global good night	PiT
DT_START_LIST	Start List	PiT	X
DT_RESULT	Event Unit Results	PiT/RT	X
DT_PHASE_RESULT	Phase Results	PiT/RT	X
DT_RANKING	Event Final Ranking	PiT	X
DT_MEDALLISTS	Event’s Medallists	PiT	X
DT_MEDALLISTS_DISCIPLINE	Medallists by discipline	PiT
DT_COMMUNICATION	Official Communication	PiT
DT_BRACKETS	Brackets	PiT	X
DT_GM	Discipline/venue good morning	PiT
DT_GN	Discipline/venue good night	PiT
DT_CONFIG	Discipline Configuration	PiT	X
DT_WEATHER	Event Unit Weather Conditions	PiT	X
DT_SERIAL	List of Current PiT Serial	PiT
DT_RT_KA	RT Discipline/Venue keep alive	RT
DT_PDF	PDF Message	PDF
DT_PDF_GM	PDF Discipline/Venue good morning	PDF
DT_PDF_GN	PDF Discipline/Venue good night	PDF
DT_PDF_SERIAL	List of Current PDF Serial	PDF
DT_RT_GM	RT Discipline/venue good morning	RT
DT_RT_GN	RT Discipline/venue good night	RT

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.5 Message Values

Competition

Attribute	M/O	Value	Comments
Code	M	CC @Competition	Unique ID for competition

Participant

Attribute	M/O	Value	Comments
Code	M	S(20) with no leading zeroes	Participant’s ID. It identifies an athlete or an official and the holding participant’s valid information for one particular period of time. It is used to link other messages to the participant’s information. Participant’s information (example @Organisation) will not be the latest for the athlete/official, unless the @Code attribute is the same as the @Parent attribute. However, this information could be the one being valid in the particular moment of a start list, event unit results, etc. When the participant is an historical one, then this ID will start with “A” when it is an Athlete, “C” when Coach and “O” when Official.
Parent	M	S(20) with no leading zeroes	Participant’s parent ID, which is used to link to the latest valid information for one participant. @Parent attribute should be linked to the latest participant‘s information, by retrieving that Athlete/Official whose @Code attribute is the same as @Parent. The participant containing @Code attribute being the same as the @Parent attribute will be the one with the latest information for the participant. The @Parent attribute will only be different from @Code in the case that critial personal information has changed from previous competitions. The typical examples are Organisation (for change of country) or Name (particularly for women changing their name at marriage). Further to be clear, @Parent and @Code can only be different if Current = "false".
Status	O	CC @AccreditationStatus	Participant’s accreditation status this atribute is Mandatory in the case of @Current=”true” and it is optional in the case that @Current=”false”. To delete a participant, a specific value of the Status attribute is used.
GivenName	O	S(25)	Given name in WNPA format (mixed case)
FamilyName	M	S(25)	Family name in WNPA format (mixed case)
PrintName	M	S(35)	Print name (family name in upper case + given name in mixed case)
PrintInitialName	M	S(18)	Print Initial name (for the given name it is sent just the initial, without dot)
TVName	M	S(35)	TV name
TVInitialName	M	S(18)	TV initial name
Gender	M	CC @PersonGender	Participant’s gender
Organisation	M	CC @Organisation	Organisation ID
BirthDate	O	YYYYMMDD	Date of birth. This information may not be known at the very beginning, but it will be completed for all participants after successive updates
Height	O	N(3) 999	Height in centimetres. It will be included if this information is available. This information is not needed in the case of officials/referees.
Weight	O	N(3) 999	Weight in kilograms. It will be included if this information is available. This information is not needed in the case of officials/referees.
PlaceofBirth	O	S(75)	Place of Birth
CountryofBirth	O	CC @Country	Country ID of Birth
PlaceofResidence	O	S(75)	Place of Residence
CountryofResidence	O	CC @Country	Country ID of Residence
Nationality	O	CC @Country	Participant’s nationality. Although this attribute is optional, in very exceptional situations it will not be known, and for this reason not ready to be sent.
MainFunctionId	O	CC @Function	Main function In the Case of Current=”true” this attribute is Mandatory.
Current	M	boolean	It defines if a participant is participating in the games (true) or is a Historical participant (false).
OlympicSolidarity	O	Y or N	Flag to indicating if the participant participates in the Olympic Scholarship program.
ModificationIndicator	M	N, U	Attribute is mandatory in the DT_PARTIC_UPDATE message only N-New participant (in the case that this information comes as a late entry) U-Update participant If ModificationIndicator=’N’, then include new participant to the previous bulk-loaded list of participants If ModificationIndicator=’U’, then update the participant to the previous bulk-loaded list of participants To delete a participant, a specific value of the Status attribute is used.

Participant /Discipline

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

Attribute	M/O	Value	Comments
Code	M	CC @Discipline	It is the discipline code used to fill the OdfBody @DocumentCode attribute.
InternationalFederationId	O	S(16)	FIS code of athlete for Snowboard

Participant /Discipline /RegisteredEvent

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

Historical athletes are not register to any event.

Attribute	M/O	Value	Comments
Gender	M	CC @DisciplineGender	Discipline Gender Code
Event	M	CC @Event	Event ID
Bib	O	N(4) 9990	Bib numbers are specified in start lists elements. Send it again when value known. When sending start list elements also send this element with this attribute filled with the value.

Participant /Discipline /RegisteredEvent /EventEntry

Send if there are specific athlete’s event entries.

Type	Code	Pos	Value	Description
E_ENTRY	E_RANK		N(3) 990	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: FIS Rank.
	E_POINTS		N(4).N(2) 9990.00	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: FIS Points
	E_STANCE		S(1) G or R	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Send G for Goofy (right foot forward on the board) or R for Regular (left foot forward on the board).

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

Type/Code	Description	Expected
E_ENTRY/ E_RANK	FIS rank	Always, as soon as this information is known and this athlete has FIS rank
E_ENTRY/ E_POINTS	FIS points	Always, as soon as this information is known and this athlete has FIS points
E_ENTRY/ E_STANCE	The position of the competitor on the board. Goofy (right foot forward) or Regular (left foot forward).	Always.

Participant /OfficialFunction

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

Attribute	M/O	Value	Comments
FunctionId	M	CC @Function	Additional officials’ function code

3.2.1.6 Message Sort

The message is sorted by Participant @Code

3.2.2 Start List

3.2.2.1 Description

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

The Start List is a mandatory message for all disciplines.

3.2.2.2 Header Values

3.2.2.2.1 PiT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DDGEEEPUU	The DocumentCode attribute in the ODF header will be sent according to the ODF Common Codes document (header values sheet).
DocumentType	DT_START_LIST	Start List message
Version	1..V	Version number associated to the message’s content. Ascendant number
FeedFlag	“P”-Production “T”-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events that extends until next day. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction. Logical Date is expressed in the local time zone where the message was produced
Venue	CC @VenueCode	Venue where the message is generated.
Serial	Numeric	Sequence number for ODF-PiT messages. Serial starts with 1 each day session at every different venue. In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

3.2.2.3 Trigger and Frequency

3.2.2.3.1 PiT Triggers

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

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

- event unit related competitors.

Trigger also after any major change.

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

3.2.2.5 Message Values

Competition

Attribute	M/O	Value	Comments
Code	M	CC @Competition	Unique ID for competition

PhaseInfos /PhaseInfo

Phase info item associated to the event unit.

Type	Code	Pos	Value	Description
PI_SB	SB_PENALTY_TIME		MM:SS.hh 99:90.00 MM=minutes SS=seconds hh=hundredth of second	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Penalty time applied according to sport rules.

Type

Code

Pos

Value

Description

PI_SB

SB_PENALTY_TIME

MM:SS.hh

99:90.00

MM=minutes

SS=seconds

hh=hundredth

of second

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Penalty time applied according to sport rules.

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

Type/Code	Description	Expected
PI_SB/ SB_PENALTY_TIME	Penalty time applied according to sport rules.	Always in the case of Finals for PGS and PSL.

UnitInfos /UnitDateTime

Scheduled start date and time.

Attribute	M/O	Value	Comments
StartDate	M	DateTime	Actual start date and time. For multiday units, the start time is on the first day.

UnitInfos /UnitInfo

Unit info item associated to the event unit.

Type	Code	Pos	Value	Description
UI_SB	SB_ALTITUDE_START		N(4).N(2) 9990.99	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Start Altitude in meters
	SB_ALTITUDE_FINISH		N(4).N(2) 9990.99	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Finish Altitude in meters
	SB_ALTITUDE_DROP		N(4).N(2) 9990.99	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Vertical Drop in meters
	SB_LENGTH		N(4).N(2) 9990.99	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Length of course in meters
	SB_COURSE_NAME		S(50)	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Name of the Course.
	SB_WIDTH_WALLS		N(4).N(2) 9990.99	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: HP Width wall to wall in meters
	SB_INCLINATION		N(2).N(1) 90.0	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: HP degrees of inclination
	SB_HEIGHT_WALLS		N(4).N(2) 9990.99	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: HP inner height of walls in meters
	SB_VERT_INCLINATION		N(2).N(2) 90.00	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: HP degrees of vertical inclination
	SB_HOMOLOGATION_NUM		S(40)	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Course Homologation Number PSL, PGS
	SB_GATES_NUM		N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Number of gates PSL, PGS
	SB_JUMPS_NUM		N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Number of jump features
	SB_JIBBING_NUM		N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Number of jibbing features
	SB_FEATURES_NUM		N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Number of features
	SB_FORERUNNERS		Do not send anything	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Do not send anything

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

Type/Code	Description	Expected
UI_SB/ SB_ALTITUDE_START	Start altitude in meters	Always, except for HP
UI_SB/ SB_ALTITUDE_FINISH	Finish altitude in meters	Always, except for HP
UI_SB/ SB_ALTITUDE_DROP	Vertical drop in meters	Always, except for HP
UI_SB/ SB_LENGTH	Course length in meters	Always
UI_SB/ SB_COURSE_NAME	Course Name	Always
UI_SB/ SB_WIDTH_WALLS	Halfpipe width from wall to wall	Always. Only for HP
UI_SB/ SB_INCLINATION	Halfipipe degrees of inclination	Always. Only for HP
UI_SB/ SB_HEIGHT_WALLS	Halfipipe inner height of walls in meters	Always. Only for HP
UI_SB/ SB_VERT_INCLINATION	Halfipipe degrees of vert inclination	Always. Only for HP
UI_SB/ SB_HOMOLOGATION_NUM	Course homologation number	Always. Only for PSL and PGS
UI_SB/ SB_GATES_NUM	Number of gates	Always. Only for PSL and PGS
UI_SB/ SB_JUMPS_NUM	SBS Number of jump features	Always. Only for SBS
UI_SB/ SB_JIBBING_NUM	SBS Number of jibbing features	Always. Only for SBS
UI_SB/ SB_FEATURES_NUM	SBX Number of features	Always. Only for SBX
UI_SB/ SB_FORERUNNERS	Code used for Forerunners information	Always

UnitInfos /UnitInfo /Competitor

Just in the case of forerunners

Attribute	M/O	Value	Comments
Organisation	M	CC @Organisation	Organisation ID of the forerunner associated to the UnitInfo/Competitor forerunner unit information
Order	O	N(3)	Order of the forerunner in the unit.

UnitInfos /UnitInfo /Competitor /Composition /Athlete

Just for the forerunners

Attribute	M/O	Value	Comments
FamilyName	O	S(25)	Family name of the forerunner associated to the UnitInfo /Competitor forerunner unit information.
GivenName	O	S(25)	Given name of the forerunner associated to the UnitInfo /Competitor forerunner unit information.

Officials /Official

Official associated to the event unit.

Attribute	M/O	Value	Comments
Code	M	S(20) with no leading zeroes	Key of the official, to uniquely identify this element
Function	M	CC @Function	Send according to the codes. Use one of the following list: For Jury: FIS Technical Delegate Head Judge Chief of Competition FIS Race Director FIS Race Director/Referee Start Referee Finish Referee Chief of Finish For Officials: FIS Assistant Race Director Chief of Halfpipe Halfpipe Technical Adviser Assistant Head Judge Judge 1 Judge 2 Judge 3 Judge 4 Judge 5 Judge 6 Chief of Parallel Giant Slalom Chief of Parallel Slalom Course Setter Video Controller Chief of Slopestyle Course Designer Chief of Course Course Builder Start Referee Finish Referee
Order	M	Numeric	According to the Sport Rules

Start

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

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

Attribute	M/O	Value	Comments
StartOrder	O	Numeric	Start order of the competitor in the start list. For PGS, PSL Qualification and Elimination runs two athletes may have the same start order (as they run in parallel at the same time, one in each course, see @SortOrder).
SortOrder	M	Numeric	In most cases, same as @StartOrder. However, in the case of the units of finals for PGS, PSL and SBX, it should be the sort order according to the brackets rules. In the case of PGS and PSL qualification and elimination, it should alternate red course / blue course with consecutive numbering (no repeating) according to the @StartOrder attribute (StartOrder 1: SortOrder is 1 and 2; StartOrder 2: SortOrder is 3 and 4 and so on).

Attribute

M/O

Value

Comments

StartOrder

Numeric

Start order of the competitor in the start list.

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

SortOrder

Numeric

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

In the case of PGS and PSL

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

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

Start /Competitor

Competitor participating in the event unit

Attribute	M/O	Value	Comments
Code	M	S(20) with no leading zeroes, TBD, Code	Competitor’s ID, TBD in case that the competitor is not known.
Type	M	A	A for athlete
Bib	O	N(4) 9990	Competitor’s bib number.

Start /Competitor /Composition /Athlete

Athlete extended information

Attribute	M/O	Value	Comments
Code	M	S(20) with no leading zeroes	Athlete’s ID
Order	M	Numeric	For individual events it will be 1
Bib	M	N(4) 9990	Bib number.

Start /Competitor /Composition /Athlete /EventUnitEntry

Individual athlete’s event unit entry.

Type	Code	Pos	Value	Description
EUE_SB	SB_BIB_COLOR		CC @BibColor	For @Type: Send proposed type. Only for PGS, PSL and SBX For @Code: Send proposed Code For @Pos: Don’t send anything. For @Value: Send one of CC @BibColor
	SB_IRM		CC @IRM	For @Type: Send proposed type. Only for PGS/PSL Qualification and Elimination Runs. For @Code: Send proposed Code For @Pos: Don’t send anything. For @Value: IRM for the particular event unit.
	SB_HEAT		N(1) 9	For @Type: Send proposed type. For @Code: Send proposed Code For @Pos: Don’t send anything. For @Value: Consecutive number of heat/pair. For HP/SBS (in case of Heats format) and PGS/PSL(Pair)/ SBX(Heat) Finals
	SB_SNOWSEED		S(1) Y or N	For @Type: Send proposed type. For @Code: Send proposed Code For @Pos: Don’t send anything. For @Value: If athlete is assigned a Snowseed send Y, otherwise send N

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

Type/Code	Description	Expected
EUE_SB/ SB_BIB_COLOR	Bib Color	Always in the case of PGS and PSL (for red and blue); for SBX, not for Qualification phase but for all final phases.
EUE_SB/ SB_IRM	IRM	PGS/PSL Qualification and Elimination Runs.
EUE_SB/ SB_HEAT	Heat or Pair Number	For HP/SBS (in case of Heats format) it is the Heat number 1 or 2; for PGS/PSL(Pair)/ SBX(Heat) Finals is the consecutive number of the pairs/heats: in 1/8 Finals from 1 to 8, in Quarterfinals from 9 to 12, etc.
EUE_SB/ SB_SNOWSEED	Snowseed: In extraordinary conditions, the Jury may change the starting order (when snowing, etc.). A group of at least six competitors, nominated in advance, start before start number one. These six competitors are drawn from among the last 20% of the start list. They will start in reverse order of their start numbers.	Just for SBX.

3.2.2.6 Message Sort

The message is sort by the Start@SortOrder attribute.

3.2.3 Event Unit Results

3.2.3.1 Description

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

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

3.2.3.2 Header Values

3.2.3.2.1 PiT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit
DocumentType	DT_RESULT	Event Unit Results message
ResultStatus	CC @ResultStatus	It indicates whether the result is official or unofficial (or intermediate, interim, partial). “OFFICIAL” / “UNOFFICIAL” / “INTERMEDIATE” / “INTERIM”/ “PARTIAL”
Version	1..V	Version number associated to the message’s content. Ascendant number
FeedFlag	“P”-Production “T”-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events that extends until next day. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction. Logical Date is expressed in the local time zone where the message was produced
Venue	CC @VenueCode	Venue where the message is generated.
DocumentSubtype	N/A	Not used in SB
Serial	Numeric	Sequence number for ODF-PiT messages. Serial starts with 1 each day session at every different venue. In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

3.2.3.2.2 RT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit
DocumentType	DT_RT_RESULT	Event Unit Real Time Results message
ResultStatus	CC @ResultStatus	It indicates whether the result is live update or live full (or live Mandatory, Live Last). “LIVE_UPDATE” / “LIVE_FULL” / “LIVE_MANDATORY” / “LIVE_LAST
Version	1..V	Version number associated to the message’s content. Ascendant number
FeedFlag	“P”-Production “T”-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events that extends until next day. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction. Logical Date is expressed in the local time zone where the message was produced
Venue	CC @VenueCode	Venue where the message is generated.
RTSerial	Numeric	Incremental and unique sequence number for ODF-RT messages.
Serial	Numeric	Sequence number for ODF-PiT messages. Serial starts with 1 each day session at every different venue. In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

3.2.3.3 Trigger and Frequency

3.2.3.3.1 PiT Triggers

Follow the general rule.

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

Then proceed with unofficial and official results, as expected.

3.2.3.3.2 RT Triggers

For ResultStatus=LIVE_UPDATE:

o T1: Trigger at the beginning of the unit.

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

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

• For ResultStatus=LIVE_FULL

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

• For ResultStatus=LIVE_MANDATORY

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

• For ResultStatus=LIVE_LAST

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

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

Attribute

M/O

Value

Comments

RT Only

RT Trigger

StartDate

DateTime

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

Not needed for Real Time.

When available

EndDate

DateTime

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

Not needed for Real Time.

When available

Result

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

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Rank	O	Text	Rank of the competitor in the result. It should be noticed that in the case of the PGS, PSL – Qualification Run, ranks are assigned independently for red course / blue course, and for this reason, two competitors could have the same rank despite of having different times, according to their participation in either the red course or the blue course.	N	T1, T3
RankEqual	O	Y or N	It identifies if a rank has been equalled. For Pit, send just ‘Y’ for equalled ranks.	N	Only if necessary
Result	O	MM:SS.hh 99:90.00 Or N(3).N(2) 900.90	Result for the particular event unit. Send just in the case @ResultType is TIME in the case of PGS, PSL and SBX (for just applies for Qualification hase if proceed) or POINTS in the case of HP and SBS (see codes section). Don’t send this attribute if the @ResultType is RANK. MM is minutes, SS is seconds, hh is hundred of second	N	T3
IRM	O	CC @IRM	IRM for the particular event unit. Send just in the case @ResultType is IRM (see codes section).	N	T3
QualificationMark	O	CC @QualificationMark	Not used for Snowboard in this message.	N	Only if necessary
SortOrder	M	Numeric	Used to sort all results in an event unit. For Real Time attribute is optional, because it should not be informed if ResultType is empty, as defined for the ResultType attribute. In the case of the PGS,PSL – Qualification Run, for the same rank, it will be listed first the participant in the red course, and then the participant in the blue course. Also for Real Time, any sort order change from the initial start list order for any competitor will be provided in this attribute regardless the competitor is ranked or not (this includes ranked, none-ranked and IRM athletes/team).	N	Always
ResultType	O	CC @ResultType	Result type, either TIME (SBX Seeding runs, PGS and PSL Qualification and Elimination runs), POINTS (HP and SBS), RANK (PG, PSL and SBX Finals), or IRM for the corresponding event unit. For Real Time, when the message arrives (to include some extended results for a particular kind of competitor), no attributes at Result element level will be included if ResultType attribute is empty. In this case, it means it is not being sent data for the Result element. On the contrary, if ResultType is informed, and the other attributes are blank, it is assumed these attributes are being reset.	N	T3

Result /Competitor

Competitor related to the result of one event unit.

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Code	M	S(20) with no leading zeroes or TBD	Competitor’s ID or TBD in case that the competitor is unknown	N	Only if necessary
Type	M	A	A for athlete	N	Only if necessary
Bib	M	N(4) 9990	Competitor’s bib number.	N	Only if necessary

Result /Competitor /Composition /Athlete

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Code	M	S(20) with no leading zeroes	Athlete’s ID	N	Only if necessary
Order	M	Numeric	For individual events it will be 1	N	Only if necessary
Bib	M	N(4) 9990	Bib number	N	Only if necessary

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

Individual athlete’s extended result.

Type	Code	Pos	Value	Description
ER_SB	SB_DIFF	N(1) 9	MM:SS.hh 99:90.00	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Run Number in the heat (1 or 2) only for Qualification (PGS and PSL) For @Value: Time difference (do not send for Result @Rank=1) In case of tie, send 0.00 for both competitors. - in qualification: time difference between the time of the rider and the best rider on the same course. - in finals: time difference between the time of the rider and the rider from the same pair, but on the other course. MM=minutes SS=seconds hh=hundredth of second
SB_JUDGE	N(1) 9	N(3) 900	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Send judge number, from 1 to 6 For @Value: Send points from the judge identified by @Pos
SB_SPLIT_RESULT_TIME	N(1) 9	MM:SS.hh 99:90.00	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Send the intermediate point (1,2,3…) For @Value: Time at the split position MM=minutes SS=seconds hh=hundredth of second
SB_SPLIT_RESULT_RANK	N(1) 9	N(2) 90	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Send the intermediate point (1,2,3…) For @Value: Rank of the competitor in the split (if SB_SPLIT_RESULT_TIME exists)
SB_ADVANCED		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Do not send anything For @Value: "Y" to indicate the competitor who is advanced to the next phase as a result of a tie-break or otherwise.
SB_CURRENT	N(1) 9	S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Send current order, from 1 to 4. Only for SBX. Do not send anything for PSL & PGS, HP & SBS For @Value: Send Y for the current athlete (see further description below)
SB_LAST_SCORED		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Send Y for the most recent score
SB_NEXT		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Send Y for the next athlete
SB_JUDGE_DISCARD	N(1) 9	S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Send judge number, from 1 to 6 For @Value: Send Y if points from the judge identified by @Pos are discarded (highest or lowest).
SB_TIEBRK_PTS		N(3).N(2) 990.00	For @Type: Send proposed type For @Code: Send proposed code For @ Pos: Do not send anything For @Value: Should be the tie-break points of the run which breaks the tie, or the total score of worst run depending on the criteria which breaks the tie.
SB_DQP		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Do not send anything For @Value: Send Y if the athlete is potentially disqualified. Only RT
SB_PFR		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Do not send anything For @Value: Send Y if Photo has been evaluated. Send P if Photo is under evaluation. Send N if no Photo is required. Only RT
SB_TIEBRKNG_FOR		MM:SS.hh 99:90.00 (PGS, PSL) MM=minutes SS=seconds hh=hundredth of second Or N(2) 90 (HP, SBS, SBX)	For @Type: Send proposed Type For @Code: Send proposed Code For @Pos: Do not send anything For @Value: Tied time (PGS, PSL) or tied rank (HP, SBS, SBX) to break
SB_RE_RUN		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code. For @Pos: Do not send anything For @Value: Send Y if Re-Run has been given to athlete. Only RT

Type

Code

Pos

Value

Description

ER_SB

SB_DIFF

N(1)

MM:SS.hh

99:90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Run Number in the heat (1 or

2) only for Qualification (PGS and PSL)

For @Value:

Time difference (do not send

for Result @Rank=1)

In case of tie, send 0.00 for

both competitors.

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

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

MM=minutes SS=seconds

hh=hundredth of second

SB_JUDGE

N(1)

N(3)

900

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Send judge number, from 1 to

For @Value:

Send points from the judge

identified by @Pos

SB_SPLIT_RESULT_TIME

N(1)

MM:SS.hh

99:90.00

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

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

For @Value:

Time at the split position

MM=minutes

SS=seconds

hh=hundredth of second

SB_SPLIT_RESULT_RANK

N(1)

N(2)

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

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

For @Value:

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

SB_ADVANCED

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

"Y" to indicate the competitor

who is advanced to the next

phase as a result of a tie-break

or otherwise.

SB_CURRENT

N(1)

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

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

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

For @Value:

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

SB_LAST_SCORED

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y for the most recent score

SB_NEXT

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send Y for the next athlete

SB_JUDGE_DISCARD

N(1)

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Send judge number, from 1 to 6

For @Value:

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

SB_TIEBRK_PTS

N(3).N(2)

990.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

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

SB_DQP

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

Send Y if the athlete is potentially disqualified. Only RT

SB_PFR

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

Send Y if Photo has been evaluated.

Send P if Photo is under evaluation.

Send N if no Photo is required.

Only RT

SB_TIEBRKNG_FOR

MM:SS.hh

99:90.00

(PGS, PSL)

MM=minutes

SS=seconds

hh=hundredth

of second

N(2)

(HP, SBS, SBX)

For @Type:

Send proposed Type

For @Code:

Send proposed Code

For @Pos:

Do not send anything

For @Value:

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

SB_RE_RUN

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code.

For @Pos:

Do not send anything

For @Value:

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

Only RT

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

Type/Code	Description	Expected	RT Only	RT Trigger
ER_SB/ SB_DIFF	Time difference (difference in regards to the total time for PGS and PSL).	Always in the case of PGS or PSL, except for rank=1	N	T3
ER_SB/ SB_JUDGE	Points from a particular judge	Always just in the case of HP and SBS	N	T3
ER_SB/ SB_SPLIT_RESULT_TIME	Result at the split position	In SBX, just for Seeding phase. Optional for PGS/PSL Qualification, Elimination and Final phases.	N	T3
ER_SB/ SB_SPLIT_RESULT_RANK	Rank at the split position	In SBX, just for Seeding phase. Optional for PGS/PSL Qualification, Elimination and Final phases.	N	T3
ER_SB/ SB_ADVANCED	Competitor who is advance to the next Phase	For PGS and PSL Finals (phases 4,3,2,1) in case of tie-break.	N	T3
ER_SB/ SB_CURRENT	Current competitor on course. During Run should be set to Y when the competitor (who has SB_NEXT to Y) enters in the course. Should be set to N when the competitor is not on course (this will happen when the competitor gets his/her result) and sets his/her SB_LAST_SCORED value to Y	Always	Y	T2, T3
ER_SB/ SB_LAST_SCORED	Most recent score. During Run should be set to Y when the competitor gets the Result. Should be set to N when another competitor sets his/her SB_LAST_SCORED value to Y.	Always	Y	T3
ER_SB/ SB_NEXT	Next Competitor. Before the start of the Unit should set to Y for the first competitor to start when is presented. During Run should be set to Y when previous competitor becomes current. Should be set to N when another competitor sets his/her SB_NEXT value to Y (this will happen when a competitor becomes current).	Always	Y	T2, T3
ER_SB/ SB_JUDGE_DISCARD	HP,SBS: points from judge discarded (Y,N)	Always just in case of HP and SBS.	N	T3
ER_SB/ SB_TIEBRK_PTS	Tie-break points of the run according to rules	Only HP and SBS all phases for athletes in a tie	N	T3
ER_SB/ SB_DQP	Athlete is potentially disqualified (Y,N)	Always	Y	T3
ER_SB/ SB_PFR	Photo Finish is Required (Y,P,N)	Always for SBX	Y	T3
ER_SB/ SB_TIEBRKNG_FOR	Affected tie-breaking for, PGS & PSL: Time HP, SBS & SBX: Rank	Only for athlete in a tie	N	T3
ER_SB/ SB_RE_RUN	Athlete has a Re-run option (Y/N)	Affected SBX (Qualification), PGS/PSL (All Phases)	Y	T3

3.2.3.6 Message Sort

Sort by Result @SortOrder

3.2.4 Phase Results

3.2.4.1 Description

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

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

3.2.4.2 Header Values

3.2.4.2.1 PiT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DDGEEEP00	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase
DocumentType	DT_PHASE_RESULT	Phase Results message
ResultStatus	CC @ResultStatus	It indicates whether the result is interim, partial, official or unofficial. "INTERIM" / “PARTIAL” / “OFFICIAL” / “UNOFFICIAL”
Version	1..V	Version number associated to the message’s content. Ascendant number
FeedFlag	“P”-Production “T”-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events that extends until next day. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction. Logical Date is expressed in the local time zone where the message was produced
Venue	CC @VenueCode	Venue where the message is generated.
Serial	Numeric	Sequence number for ODF-PiT messages. Serial starts with 1 each day session at every different venue. In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

3.2.4.2.2 RT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DDGEEEP00	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase
DocumentType	DT_RT_PHASE_RESULT	Real Time Phase Results message
ResultStatus	CC @ResultStatus	It indicates whether the result is live update or live full (or live Mandatory, Live Last). “LIVE_UPDATE” / “LIVE_FULL” / “LIVE_MANDATORY” / “LIVE_LAST”
Version	1..V	Version number associated to the message’s content. Ascendant number
FeedFlag	“P”-Production “T”-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events that extends until next day. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction. Logical Date is expressed in the local time zone where the message was produced
Venue	CC @VenueCode	Venue where the message is generated.
RTSerial	Numeric	Incremental and unique sequence number for ODF-RT messages.
Serial	Numeric	Sequence number for ODF-PiT messages. Serial starts with 1 each day session at every different venue. In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

3.2.4.3 Trigger and Frequency

3.2.4.3.1 PiT Triggers

This message is sent like follows:

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

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

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

Trigger also after any major change.

3.2.4.3.2 RT Triggers

For ResultStatus=LIVE_UPDATE:

o T1: Trigger at the beginning of the unit.

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

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

• For ResultStatus=LIVE_FULL:

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

• For ResultStatus=LIVE_MANDATORY

Send when a correction in the previous messages has been done.

• For ResultStatus=LIVE_LAST

3.2.4.5 Message Values

Competition

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Code	M	CC @Competition	Unique ID for competition	N	When available

Result

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

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Rank	O	Numeric	Rank of the competitor in the phase. In case of HP/SBS with two heats format and PGS/PSL/SBX Final phases, it is the rank of competitor within his/her heat/pair (two competitors will have same rank in phase). In case of PGS/PSL and SBX Finals it is the rank of competitor This attribute is optional because the skier may have got an invalid rank mark.	N	T3
RankEqual	O	Y or N	It identifies if a rank has been equalled.	N	Only if necessary
ResultType	O	CC @ResultType	Result type, either TIME (SBX Seeding runs, PGS and PSL Qualification and Elimination runs), POINTS (HP and SBS), RANK (PGS and PSL Finals), or IRM for the corresponding event unit. Send this attribute if there is Result or IRM.	N	T3
Result	O	MM:SS.hh 99:90.00 Or N(3).N(2) 900.90	The result of the competitor in the phase. It is the total time for PGS and PSL, best score for HP and SBS and best time for SBX. Send just in the case @ResultType is Time in the case of PGS, PSL and SBX or Points in the case of HP and SBS (see codes section). MM is minutes, SS is seconds, hh is hundreds of second.	N	T3
IRM	O	CC @IRM	The invalid rank mark, in case it is assigned. Send just in the case @ResultType is IRM (see codes section).	N	T3
QualificationMark	O	CC @QualificationMark	Send just in the case the competitor qualified according to the codes. It will be basically used after second runs (SBX, HP and SBS), as well as in the Elimination run in PGS and PSL.	N	Send when information is known and it is not going to change, for example, if there are 20 athletes competing and 6 are qualifying, when the 15th competitor finishes there is one competitor that is going to qualify for sure.
SortOrder	M	Numeric	Used to sort all results in a phase, based on rank, but to break rank ties, etc. It is mainly used for display purposes. In case of HP/SBS with two heats format and PGS/PSL/SBX Final phases, where two competitors will have same rank in phase, it will be listed (sorted) by heat/pair (first lower heat/pair).	N	Always

Result /Competitor

Competitor related to one phase result.

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Code	M	S(20) with no leading zeroes	Competitor’s ID	N	Only if necessary
Type	M	A	A for athlete	N	Only if necessary
Bib	M	N(4) 9990	Competitor’s bib number.	N	Only if necessary

Result /Competitor /Composition /Athlete

Attribute	M/O	Value	Comments	RT Only	RT Trigger
Code	M	S(20) with no leading zeroes	Athlete’s ID	N	Only is necessary
Order	M	Numeric	Always 1	N	Only is necessary
Bib	M	N(4) 9990	Competitor’s bib number.	N	Only if necessary

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

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

Type	Code	Pos	Value	Description
ER_SB	SB_DIFF		MM:SS.hh 99:90.00 MM=minutes SS=seconds hh=hundredth of second	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Time difference (do not send for Result @Rank=1) It is the time difference in regards to the total time for PGS, PSL (Qualification phase) and best time for SBX (Seeding phase).
SB_BEST_RUN		N(1) 0	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Send “0” to set undefined (in case of IRM for both runs) the best run Send “1” to set run 1 as best Send “2” to set run 2 as best
SB_COURSE_RANK	N(1) 9	N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @Pos: 1 Blue, 2 Red For @Value: Rank within course given by @Pos
SB_COURSE_ERANK	N(1) 9	S(1) Y,N	For @Type: Send proposed type For @Code: Send proposed code For @Pos: 1 Blue, 2 Red For @Value: Equalled Rank for SB_COURSE_RANK given by @Pos.
SB_COURSE_IDX	N(1) 9	N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @Pos: 1 Blue, 2 Red For @Value: Order of the athlete within course related to the SB_COURSE_RANK given by @Pos
SB_TIEBRK_PTS		N(3).N(2) 990.00	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Tie break points (HP and SBS). Should be the tie-break points of the run which breaks the tie, or the total score of worst run depending on the criteria which breaks the tie.
SB_LAST_QUALIFIED		S(1) Y or N	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: Send to Y when competitor is the last competitor qualified according to sport rules. (See table below for more information)
SB_SORT_HEAT	N(1) 9	N(2) 90	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Send the heat number For @Value: Send the sort order within the heat given by @Pos

Type

Code

Pos

Value

Description

ER_SB

SB_DIFF

MM:SS.hh

99:90.00

MM=minutes

SS=seconds

hh=hundredth

of second

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

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

SB_BEST_RUN

N(1)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

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

Send “1” to set run 1 as best

Send “2” to set run 2 as best

SB_COURSE_RANK

N(1)

N(2)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

1 Blue, 2 Red

For @Value:

Rank within course given by @Pos

SB_COURSE_ERANK

N(1)

S(1)

Y,N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

1 Blue, 2 Red

For @Value:

Equalled Rank for SB_COURSE_RANK given by @Pos.

SB_COURSE_IDX

N(1)

N(2)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

1 Blue, 2 Red

For @Value:

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

SB_TIEBRK_PTS

N(3).N(2)

990.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

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

SB_LAST_QUALIFIED

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

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

SB_SORT_HEAT

N(1)

N(2)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send the heat number

For @Value:

Send the sort order within the heat given by @Pos

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

Type/Code	Description	Expected	RT Only	RT Trigger
ER_SB/ SB_DIFF	Time difference (difference in regards to the total time for PGS and PSL and best time for SBX).	Always in the case of SBX Seeding, PGS Qualification or PSL Qualification, except for rank=1	N	T3
ER_SB/ SB_BEST_RUN	Best Run Result	Just in the case of HP, SBX Seeding and SBS. (Two runs format)	N	T3
ER_SB/ SB_COURSE_RANK	Rank within a course	Just for PGS/PSL Qualification phase	N	T3
ER_SB/ SB_COURSE_ERANK	Equalled Rank within a course	Just for PGS/PSL Qualification phase	N	T3
ER_SB/ SB_COURSE_IDX	Order for SB_COURSE_RANK	Just for PGS/PSL Qualification phase	N	T3
ER_SB/ SB_TIEBRK_PTS	Tie break points according to rules. Should be the tie-break points of the run which breaks the tie.	Just for HP and SBS. All phases, only for athletes in a tie.	N	T3
ER_SB/ SB_LAST_QUALIFIED	Y if the competitor is the last one to qualify according to rules. It is the virtual last qualified position in the current moment.	All phases when there is a qualification criteria.	N	T3
ER_SB/ SB_SORT_HEAT	Sort order within the heat	Just for HP and SBS. All phases with heats.	N	T3

3.2.4.6 Message Sort

Sort by Result @SortOrder

3.2.5 Event Final Ranking

3.2.5.1 Description

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

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

3.2.5.2 Header Values

3.2.5.2.1 PiT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DDGEEE000	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event
DocumentType	DT_RANKING	Event Final ranking message
ResultStatus	CC @ResultStatus	Result status
Version	1..V	Version number associated to the message’s content. Ascendant number
FeedFlag	“P”-Production “T”-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	Date	Logical Date of events that extends until next day. If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2). The end of the logical day is defined by default at 03:00 a.m. For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction. Logical Date is expressed in the local time zone where the message was produced
Venue	CC @VenueCode	Venue where the message is generated.
Serial	Numeric	Sequence number for ODF-PiT messages. Serial starts with 1 each day session at every different venue.

3.2.5.3 Trigger and Frequency

3.2.5.3.1 PiT Triggers

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

Attribute	M/O	Value	Comments
Code	M	CC @Competition	Unique ID for competition

3.2.7.5 Message Values

Competition

Attribute	M/O	Value	Comments
Code	M	CC @Competition	Unique ID for competition

Bracket

Attribute	M/O	Value	Comments
Code	M	CC @Bracket	Bracket code to identify a bracket item.

Bracket /BracketItems

Attribute	M/O	Value	Comments
Code	M	CC @BracketItems	Each BracketItems should include all BracketItem grouped by their CC @BracketItems

Bracket /BracketItems /BracketItem

Attribute

M/O

Value

Comments

Code

CC @BracketItems

Code that categorizes each bracket item

Order

N(2)

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

Bracket /BracketItems /BracketItem /Unit

Unit related to the BracketItem.

Attribute	M/O	Value	Comments
Phase	M	CC @Phase	Phase code for the bracket item
Unit	O	CC @Unit	Unit code for the bracket item

Bracket /BracketItems /BracketItem /ExtBracketItems /ExtBracketItem

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

Type	Code	Pos	Value	Description
EB_SB	SB_BI_ID		Numeric	For @Type: Send proposed type For @Code: Send proposed code For @Pos: Do not send anything For @Value: BracketItem sequential number (to sort BracketItem @Code) whenever it is heat, quarterfinal or semifinal.
	SB_PLACEMENT	Numeric	N(3) 990	For @Type: Send proposed type For @Code: Send proposed code For @Pos: 1 for “from” placement being assigned (e.g.: 5) 2 for “to” placement being assigned (e.g.: 6) For @Value: Placement (rank) being assigned in the bracket item. From-to
	SB_BI_CODE	Numeric	CC @NextBracketPos	For @Type: Send proposed type For @Code: Send proposed code for extended bracket athlete code For @Pos: The number that identifies the position inside the bracket item, to determine from the @Value attribute: • if the competitor with this position in the bracket item will advance to the BracketItem /NextUnit bracket item, • the BarcketItem /NextUnitLoser element • or will be out. For @Value: Extended bracket item code to indicate whether the competitor with a position inside a bracket item will advance to the next winner bracket item, the next loser bracket item or will not advance. For the competitors that will advance as winners, they will be placed in the next bracket item as it is identified by the BracketItem /NextUnit element. For the competitors that will advance as losers, they will be placed in the next bracket item as it is identified by the BracketItem /NextUnitLoser element. For the competitors that will be indicated as “Out”, they will not advance to any next bracket item

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

Type/Code	Description	Expected
EB_SB/ SB_BI_ID	BracketItem sequential number to sort BracketItem @Code (1, 2, 3, …)	When BracketItem @Code=heat, quarterfinal or semifinal
EB_SB/ SB_PLACEMENT	Placement being awarded in the bracket item (eg.: 3-4)	In PGS,PSL and SBX, when BracketItem @Code is not SFL
EB_SB/ SB_BI_CODE	Extended bracket item code to indicate whether the competitor with a position inside a bracket item will advance to the next winner bracket item, the next loser bracket item or will not advance.	Send always, except in Small and Big Final for PGS, PSL and SBX.

Bracket /BracketItems /BracketItem /NextUnit

Next event unit related to the current bracket item. It is always informed except for the terminal bracket items, which do not have continuation according to the brackets graph.

Attribute

M/O

Value

Comments

Phase

CC @Phase

Phase code of the next event unit for the current bracket item.

PGS, PSL and SBX: should be informed from the 1/8 finals event units, quarterfinals, semifinals event units.

Unit

CC @Unit

Unit code of the next event unit for the current bracket item.

Bracket /BracketItems /BracketItem /NextUnitLoser

Next event unit related to the current bracket item, but related to the loser competitor. It is always informed except for the terminal bracket items, which do not have continuation according to the brackets graph.

Attribute

M/O

Value

Comments

Phase

CC @Phase

Phase code of the next event unit for the current bracket item, but related to the loser competitor.

Only for the case of Semifinals, where the losers will advance to Small Final (PGS, PSL and SBX).

Unit

CC @Unit

Unit code of the next event unit for the current bracket item, but related to the loser competitor.

Bracket /BracketItems /BracketItem /CompetitorPlace

- If the competitors are known, this element is used to place the competitors in the bracket.

- If they are not yet known, it contains some information (on the rule to access to this bracket...)

Attribute

M/O

Value

Comments

Pos

N(3)

999

This attribute is a sequential number to place the different competitors in the bracket (1, 2 …).

Bracket /BracketItems /BracketItem /CompetitorPlace /PreviousUnit

Previous event unit related to the CompetitorPlace@Pos competitor of the current bracket item. It is always informed except for the bracket items whose CompetitorPlace@Pos competitor do not have preceding event units in the bracket graph.

Attribute

M/O

Value

Comments

Phase

CC @Phase

Phase code of the previous event unit for the CompetitorPlace @Pos competitor of the bracket item.

PGS, PSL and SBX: should be informed from the quarterfinals event units (if 32 competitors bracket), semifinals and final event units.

Unit

CC @Unit

Unit code of the previous event unit for the CompetitorPlace@Pos competitor of the bracket item.

Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor

CompetitorPlace @Pos competitor related to the bracket item. Only include if the competitor is known .

Attribute	M/O	Value	Comments
Code	M	S(20) with no leading zeroes	Competitor’s ID
Type	M	A	A for athlete

3.2.7.6 Message Sort

BracketItems @Code should be sorted by 1/8 Finals (ordered by heat), Quarterfinals (ordered by heat), semifinals (1, 2) and finals (small and big).

3.2.8 Discipline Configuration

3.2.8.1 Description

The Discipline Configuration is a message containing discipline general configuration.

Ideally the configuration for the discipline should be provided before competition. However it may be possible that the configuration for one particular event, phase or event unit is not known in advance. In that case send the unknown attributes blank (Value=“”).

3.2.8.2 Header Values

3.2.8.2.1 PiT Header

The following table describes the ODF header attributes

Attribute	Value	Comment
DocumentCode	DD0000000	DD according to CC @Discipline
DocumentType	DT_CONFIG	Discipline Configuration 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.8.3 Trigger and Frequency

3.2.8.3.1 PiT Triggers

Day INFO operations start.

• When this information was available.

3.2.8.5 Message Values

Competition

Attribute	M/O	Value	Comments
Code	M	CC @Competition	Unique ID for competition

Configs /Config

Attribute	M/O	Value	Comments
Gender	M	CC @DisciplineGender	Gender code
Event	M	CC @Event	Event code
Phase	M	CC @Phase	Phase code
Unit	O	CC @Unit	Unit code

Configs /Config /ExtendedConfig

Send by phase

Type	Code	Pos	Value	Description
EC_QUALIFICATION_RULE	SB_RANK_QUALIFY_EIGHTHFINAL	Numeric	N(4) 9990	For @Type: Send proposed type For @Code: Send the proposed code for the qualification rule. See the additional/summary table below for more information. For @Pos: Send 1 to indicate first rank included in the @Code rule Send 2 to indicate last rank included in the @Code rule For @Value: Send the rank according to @Code rule and @Pos
	SB_RANK_QUALIFY_QUARTERFINAL	Numeric	N(4) 9990	For @Type: Send proposed type For @Code: Send the proposed code for the qualification rule. See the additional/summary table below for more information. For @Pos: Send 1 to indicate first rank included in the @Code rule Send 2 to indicate last rank included in the @Code rule For @Value: Send the rank according to @Code rule and @Pos
	SB_RANK_QUALIFY_SEMIFINAL	Numeric	N(4) 9990	For @Type: Send proposed type For @Code: Send the proposed code for the qualification rule. See the additional/summary table below for more information. For @Pos: Send 1 to indicate first rank included in the @Code rule Send 2 to indicate last rank included in the @Code rule For @Value: Send the rank according to @Code rule and @Pos
	SB_RANK_QUALIFY_SMALL_FINAL	Numeric	N(4) 9990	For @Type: Send proposed type For @Code: Send the proposed code for the qualification rule. See the additional/summary table below for more information. For @Pos: Send 1 to indicate first rank included in the @Code rule Send 2 to indicate last rank included in the @Code rule For @Value: Send the rank according to @Code rule and @Pos
	SB_RANK_QUALIFY_BIG_FINAL	Numeric	N(4) 9990	For @Type: Send proposed type For @Code: Send the proposed code for the qualification rule. See the additional/summary table below for more information. For @Pos: Send 1 to indicate first rank included in the @Code rule Send 2 to indicate last rank included in the @Code rule For @Value: Send the rank according to @Code rule and @Pos
	SB_RANK_QUALIFY_FINAL	Numeric	N(4) 9990	For @Type: Send proposed type For @Code: Send the proposed code for the qualification rule. See the additional/summary table below for more information. For @Pos: Send 1 to indicate first rank included in the @Code rule Send 2 to indicate last rank included in the @Code rule For @Value: Send the rank according to @Code rule and @Pos
EC_SB	SB_INTERMEDIATES_NUMBER		N(1) 9	For @Type: Send proposed type For @Code: Send the proposed code. For @Pos: Do not send anything For @Value: Send the number of intermediate points for that phase.
	SB_HEATS_NUMBER		N(1) 9	For @Type: Send proposed type For @Code: Send the proposed code. For @Pos: Do not send anything For @Value: Send the number of heats for that phase.
	SB_RUNS_NUMBER		N(1) 9	For @Type: Send proposed type For @Code: Send the proposed code. For @Pos: Do not send anything For @Value: Send the number of runs for that phase.

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

Type/Code	Description	Expected
EC_QUALIFICATION_RULE/ SB_RANK_QUALIFY_EIGHTHFINAL	Qualification for 1/8 final based on rank	Always if the rule applies to the competition. May apply to Qualification phases on PSL, PGS and Seeding phase on SBX.
EC_QUALIFICATION_RULE/ SB_RANK_QUALIFY_QUARTERFINAL	Qualification for quarterfinal based on rank	Always if the rule applies to the competition. May apply to 1/8 Finals on PSL, PGS and SBX.
EC_QUALIFICATION_RULE/ SB_RANK_QUALIFY_SEMIFINAL	Qualification for semifinals based on rank	Always if the rule applies to the competition. May apply to Qualification on HP and SBS; Quarterfinals on PSL, PGS and SBX.
EC_QUALIFICATION_RULE/ SB_RANK_QUALIFY_SMALL_FINAL	Qualification for small final based on rank	Always if the rule applies to the competition. May apply to Semifinals on PSL, PGS and SBX.
EC_QUALIFICATION_RULE/ SB_RANK_QUALIFY_BIG_FINAL	Qualification for big final based on rank	Always if the rule applies to the competition. May apply to Semifinals on PSL, PGS and SBX.
EC_QUALIFICATION_RULE/ SB_RANK_QUALIFY_FINAL	Qualification for final based on rank	Always if the rule applies to the competition. May apply to Qualification or Semifinals on HP and SBS.
EC_SB/ SB_INTERMEDIATES_NUMBER	Number of intermediate points	Always if there are intermediate points (1 to N). May apply to PGS/PSL Qualification and Elimination Runs and to SBX Seeding.
EC_SB/ SB_HEATS_NUMBER	Number of heats	May apply to HP/SBS. Men’s common format for Qualification is 2 heats, and Ladies is 1 heat. For Semifinals and Finals is 1 heat (considered as no heats format).
EC_SB/ SB_RUNS_NUMBER	Number of runs	May apply to HP/SBS. Common format is 2 runs. To be applied also in PGS or PSL Finals

3.2.8.6 Message Sort

There is no general message sorting rule.

3.2.9 Event Unit Weather Conditions

3.2.9.1 Description

The “Event Unit Weather Conditions” is a message containing the weather conditions in the Event Unit.

3.2.9.2 Header Values

3.2.9.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_WEATHER	Weather conditions in the match 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.9.3 Trigger and Frequency

3.2.9.3.1 PiT Triggers

The message is sent if weather data conditions change during an event unit.

3.2.9.5 Message Values

Competition

Attribute	M/O	Value	Comments
Code	M	CC @Competition	Unique ID for competition

Weather /Conditions

Attribute	M/O	Value	Comments
Code	M	CC @WeatherPoints	Weather Point (START, FINISH or ALL)
Humidity	O	N(3)	Humidity in %
Wind_Direction	O	CC @WindDirection	Wind direction

Weather /Conditions /Condition

Send two times in the case of Winter conditions.

Attribute

M/O

Value

Comments

Code

SKY, SNOW, ICE

Weather conditions type

Value

CC @SnowConditions

CC @WeatherConditions

Codes that describe the Weather Condition.

Weather /Conditions /Temperature

Send with two different @Code in the case of Winter conditions.

Attribute	M/O	Value	Comments
Code	M	AIR, SNOW	Air, Snow temperature.
Unit	M	CC @TemperatureUnit	Metric system unit for temperature
Value	M	-N(3).N(1) -990.0 or N(3).N(1) 990.0	Temperature in centigrade degrees (in case of positive temperature, do not send '+')

Weather /Conditions /Wind

Attribute	M/O	Value	Comments
Code	M	SPEED	Wind Speed
Unit	M	CC @SpeedUnit	Metric system unit for Wind
Value	M	N(3).N(1) 990.0	Wind Speed in CC @SpeedUnit

3.2.9.6 Message Sort

There is no special sort order requirement for this message. Usually, Conditions@code is the attribute used to sort the conditions.

4 Messages Sequence

No sequence data defined

5 Codes

5.1 Global Codes

Code Entity	Format	Entity Description	Link
CC @AccreditationStatus	S(6)	Defined in ODF Common Codes Document See entity Accreditation Status • The entity’s attribute to be used is Id	Link
CC @Competition	S(7)	Defined in ODF Common Codes Document See entity Competition • The entity’s attribute to be used is Id	Link
CC @Country	S(3)	Defined in ODF Common Codes Document See entity Country • The entity’s attribute to be used is Id	Link
CC @Discipline	S(2)	Defined in ODF Common Codes Document See entity Discipline • The entity’s attribute to be used is Id Valid disciplines contains Non-Sport attribute=’N’	Link
CC @DisciplineGender	S(1)	Defined in ODF Common Codes Document See entity Discipline Gender • The entity’s attribute is to access to the Discipline Gender entity is the combination of Discipline + Gender	Link
CC @Event	S(3)	Defined in ODF Common Codes Document See entity Event • The entity’s attribute to be used is Event • It will be related to Discipline and Gender	Link
CC @Function	S(30)	Defined in ODF Common Codes Document See entity Function • The entity’s attribute to be used is Id	Link
CC @MedalType	S(9)	ME_BRONZE : Bronze ME_GOLD : Gold ME_SILVER : Silver
CC @Organisation	S(3)	Defined in ODF Common Codes Document See entity Organization • The entity’s attribute to be used is Id	Link
CC @PersonGender	S(1)	Defined in ODF Common Codes Document See entity Person Gender • The entity’s attribute to be used is Id	Link
CC @Phase	S(1)	Defined in ODF Common Codes Document See entity Phase • The entity’s attribute to be used is Phase • It will be related to Discipline, Gender and Event	Link
CC @PrecType	S(1)	R : Rain S : Snow
CC @RecordCode	S(12)	Defined in ODF Common Codes Document See entity Record • The entity’s attribute to be used is Id	Link
CC @RecordType	S(4)	Defined in ODF Common Codes Document See entity Record Type • The entity’s attribute to be used is RecordTye • It will be related to Discipline	Link
CC @ResultStatus	S(15)	INTERIM : Results of the top x competitors at the logical, predefined points released during or at the end of a event unit. Every next competitor may change the standing of those who already have results at a predefined point. INTERMEDIATE : Results of the top x competitors at the logical, predefined points during race or match. The results at those points cannot change. The number of competitors may vary. In the case of Bracket message its progression will be consider INTERMEDIATE until the last Event Unit is sent as OFFICIAL. LIVE_FULL : This status is used only in real time messages. LIVE_LAST : This status is used only in real time messages. LIVE_MANDATORY : This status is used only in real time messages. LIVE_UPDATE : This status is used only in real time messages. PARTIAL : Results of the top x competitors are released at the end of a race and before all competitors finished their competition. The results including the ranking, from the competitors that finished the race do not change with the results from new competitors. OFFICIAL : Results of the competition released as soon as the event is officially confirmed taking into account the resolution of the protests, etc. UNOFFICIAL : Results of the competition released as soon as the event is over, not waiting any official decision of the International Federation. The correctness of data must be assured.
CC @SportClass	S(8)	Defined in ODF Common Codes Document See entity Sport Class • The entity’s attribute to be used is Id
CC @Unit	S(2)	Defined in ODF Common Codes Document See entity Event Unit • The entity’s attribute to be used is Eventunit • It will be related to Discipline, Gender, Event and Phase	Link
CC @VenueCode	S(3)	Defined in ODF Common Codes Document See entity Venue • The entity’s attribute to be used is Id	Link
CC @WindDirection	S(3)	Defined in ODF Common Codes Document See entity Wind Direction • The entity’s attribute to be used is Id	Link

5.2 Snowboard Codes

Code Entity	Format	Entity Description
CC @BibColor	S(9)	BC_BLACK : Black BC_BLUE : Blue BC_GREEN : Green BC_RED : Red BC_WHITE : White BC_YELLOW : Yellow (Bib colour just for PGS and PSL: blue and red, and for SBX: all possibilities).
CC @Bracket	S(3)	FNL : Final
CC @BracketItems	S(8)	1_8 : Eight finals B_FNL : Big final FNL : Finals HEAT : Heat QFL : Quarterfinal SFL : Semi-final S_FNL : Small final
CC @IRM	S(5)	DNF : Did not finish DNS : Did not start DSQ : Disqualified (The codes order provided is according to the sport rules. In case of several DSQ, DNF or DNS, sort by bib number).
CC @NextBracketPos	S(1)	L : Advance the competitor to the next Bracket item according to the NextUnitLoser element O : The competitor is out and does not advance to any next bracket item W : Advance the competitor to the next bracket item according to the NextUnit element
CC @QualificationMark	S(7)	Q : Qualified QF : Qualified for final QS : Qualified for semi-final
CC @ResultPhase	S(3)	1_8 : 1/8 Final (PGS, PSL, SBX) B_F : Big final (PGS, PSL, SBX) F : Final (HP, SBS) FR1 : Final run 1 (HP, SBS, in the case of IRM) FR2 : Final run 2 (HP, SBS, in the case of IRM) Q : Did not qualify for Semi-finals or Finals (HP, SBS); did not qualify to Finals (PGS, PSL, SBX) QF : Quarterfinals (PGS, PSL, SBX) QR1 : Qualification run 1 (HP, SBS, in the case of IRM) QR2 : Qualification run 2 (HP, SBS, in the case of IRM) SFL : Semi-final (HP, SBS) SFL1 : Semi-final run 1 (HP, SBS, in the case of IRM) SFL2 : Semi-final run 2 (HP, SBS, in the case of IRM) S_F : Small final (PGS, PSL, SBX)
CC @ResultType	S(13)	CODE : Code for the group (used in event final ranking) IRM : Invalid Result Mark POINTS : Points RANK : Rank-only result used in all SBX Finals phases TIME : Time
CC @SpeedUnit	S(3)	KMH : Kilometres per hour MS : Meters per second
CC @TemperatureUnit	S(1)	C : Celsius F : Fahrenheit
CC @WeatherPoints	S(6)	ALL : Both (Start & Finish) Areas FINISH : Finish Area START : Start Area

6 General definitions

6.1 ODF Message Structure

ODF interface defines ODF messages. ODF messages are data structures based on standard XML.

<?xml version="1.0" encoding="UTF-8"?> ßDeclaration
<OdfBody DocumentType=… DocumentCode=… >		ßODF Header
[body]	ßODF Body
</OdfBody>

6.1.1 ODF Declaration

The first line in an ODF message is the XML declaration. It defines the XML version and the encoding used, UTF-8.

6.1.2 ODF Header

The next line after the declaration is the ODF header.

ODF header is the root element and it is always introduced by the element Odfbody.

Header attributes identifies ODF messages uniquely.

The message unique identifier is the aggregation of the following attributes:

· DocumentCode,

· DocumentSubcode (Optional)

· DocumentType and

· DocumentSubtype (Optional)

The following table describes the ODF header attributes. “M” designates mandatory attributes that must appear in all ODF messages. “O” designates optional attributes. Optional attributes can be required depending on other attributes in the header.

Attribute	M/O	Value	Comment
DocumentCode	M	S(9)	RSC for Results messages DDGEEEPUU, where DD=discipline, G=discipline’s gender, EEE=event, P=phase, UU=unit DocumentCode can have many different values depending on the nature of the message. Each message defines the value for this header attribute.
DocumentSubcode	O	S(10)	Extension for the DocumentCode It is used when the RSC is not enough and it is required several different messages with the same RSC.
DocumentType	M	S(30)	Message Type (e.g. DT_RESULTS)
DocumentSubtype	O	S(20)	Attribute used to extend DocumentType for some messages.
Version	M	1..V	Version of the message
ResultStatus	O	CC @ResultStatus	Status of the messages for results message
Language	O	CC @Language	Language of the content of the message. If the message accepts multi-language and the attribute is not included, then by default the language is English If the message does not accept multi-language, then the attribute must not be included
FeedFlag	M	“P”-Production “T”-Test	Test message or production message.
Date	M	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	M	MillisTime	Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.
LogicalDate	M	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	O	CC @VenueCode	Venue where the message is generated.
RTSerial	O	Numeric	Sequence number for ODF-RT messages. RTSerial starts with 1 each Real Time session at every different venue.
Serial	M	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.

6.1.3 ODF Body

The next line after the ODF header is the body of the ODF Message.

Declaration		<?xml version="1.0" encoding="UTF-8"?>
Header		<OdfBody DocumentType=… >
	<Competition Code= …>		ß <Competition> element
	….
Body	</Competition>
		<Message> Athlete nnnn disqualified… </Message>		ß <Message> element
		</OdfBody>

Some important considerations for the ODF messages:

Mandatory elements are sent always.

· Empty optional elements are not sent neither in ODF-PiT nor ODF-RT

· Mandatory attributes are sent always. If they do not have any value then they are sent empty (Attribute =”“)

· Empty optional attributes are sent either empty (Attribute = ““) or not sent.

· Order of the elements inside an ODF message must be followed as defined in the ODF documentation. Elements must be sorted according what it is stated in the corresponding ODF message definition

· All elements in an ODF message are identified by one of the attributes (e.g. Code for an Competitor element) or a set of the attributes (e.g. Type + Code for an Extension element)

· ODF is being designed in such way that elements and attributes are organized to minimize redundancy and dependency. The objective is to isolate data so that additions, deletions, and modifications of an attribute can be made with just one message and then propagated through the rest of the messages via the defined references. However, in some very special circumstances, some important information (such as team members) will be repeated in order to make some message processing a little bit easier. Also, the ODF Light definition repeats some data across messages to simplify message processing to ODF Light Customers.

· ODF Light is a set of self-contained messages with the aim of simplifying the message processing to the clients as they do not have to resolve references

<Competition> Element

An ODF message contains a mandatory element <Competition>.

Element

Attribute

M/O

Value

Comment

Competition

Code

CC @Competition

Unique ID for the competition

<Message> Element

All ODF messages can have an optional element <Message> to include free non-formatted text in case more information is needed.

<Message> element follows the <Competition> element.

<Competitor> Element

ODF messages contain an optional element <Competitor> to include information for Athletes, Teams or Groups. Group is used when competitors of same or different organizations participate in an event together but they are not considered a team and their results are individuals.

Element

Attribute

M/O

Value

Comment

Competitor

Code

S(20) with no leading zeroes

Competitor’s ID

Type

T, A, G

T = Team

A = Athlete

G = Group

If Competitor is an Athlete:

· <Competitor> element contains the attribute Type = ”A”

· <Competitor> element contains the attribute Code = AthleteID. This attribute links to an athlete appearing in the DT_PARTIC message.

· <Competitor> element contains the element <Composition>. This element is provided always.

· <Composition> element contains the mandatory element <Athlete>. Both codes in the <Athlete> and in the <Competitor> elements are the same, the AthleteID

· <Athlete> element contains the mandatory attribute Order with value 1.

· Athlete’s Bib (if applicable) will be only sent in Competitor /Composition /Athlete element.

· Sport specific extensions are in the <Athlete> element and defined in the ODF Discipline Data Dictionary.

</Composition>

</Competition>

If Competitor is a Team:

· <Competitor> element contains the attribute Type =”T”

· <Competitor> element contains the attribute Code = TeamCode. This attribute links to a team appearing in the DT_PARTIC_TEAMS message.

· <Competitor> element contains the element <Composition>. This element is optional because there are situations where the team members are not known when message is provided.

· <Composition> element contains the mandatory element <Athlete> with the list of athletes that are the team members. The Code attribute links to an athlete appearing in the DT_PARTIC (athletes) message.

· Although team members for the whole event will be able to be found in the DT_PARTIC_TEAMS message, the specific ODF Sport messages will also include always the team’s members particularized for the message.

· <Athlete> element contains the mandatory attribute Order with the team members sort order.

· Team’s Bib (if applicable) will be sent in Competitor element.

· Team members’ Bib (if applicable) will be sent in Competitor /Composition /Athlete element.

· Team sport specific extensions are in the <Competitor> element and defined in the ODF Discipline Data Dictionary.

· Team members sport specific extensions are in the <Athlete> element and defined in the ODF Discipline Data Dictionary.

…

</Composition>

</Competition>

If Competitor is a Group:

· <Competitor> element contains the attribute Code = NOC/NPC when the athletes belong to the same organization, otherwise MIXn.

· There will be several Competitor /Composition /Athlete elements, containing the group competitor members.

6.2 ODF Data Types and Formats

This chapter describes data types and formats for the attributes in the ODF messages.

Format	Format Description
CC @CodeEntity	Set of values included in the CodeEntity. CodeEntity is the name of the entity that identifies a particular set of codes.
String	Text strings without a predetermined length
S(n)	Text strings with a length of up to n characters
Date	YYYYMMDD
MillisTime	HHMMSSmmm HH: hour MM: minutes SS: seconds mmm: milliseconds All formatted with leading zeroes (example: 090303020).
DateTime	YYYY-MM-DDThh:mm:ssTZD (e.g.: 2006-02-06T13:00:00+01:00) YYYY: year MM: Month DD: day hh: hour Mm: minutes Ss: seconds TZD in the Time Zone Designator (Z or +hh:mm or -hh:mm) where the message was produced and when the message was produced. "Z" is the zone designator for the zero UTC offset
Boolean	‘true’ or ‘false’
Numeric	Number with no predetermined length If the number starts with 9 (e.g. 99), then leading zeroes are removed. Example: 10 in format 99 is 10, and 3 in format 99 is 3. If the number starts with 0 (e.g. 00), then leading zeroes are kept. Example: 10 in format 00 is 10, and 3 in format 00 is 03. · If nothing is stated, it is assumed that the leading zeroes are removed
N(n)	Number with a length up to n digits
N(n).N(m)	Number with decimal N(n) integer part up to n digits N(m) decimal part up to m digits
Specific pattern	Attributes with an specific pattern not specified in this table
Free text	Free text is never used in a message attribute, but it can be used inside the element content Example <element>Free text goes in here</element>

6.2.1 Rules for rounding numbers

This chapter describes the rules for rounding numbers to use in all messages, unless other rules are specified in the sport documentation. (sport rules are applied before the transmission of the data)

· Last digit in the number decimal part < 5 (0, 1, 2, 3, 4) à no rounding (i.e. 1,544 = 1, 54)

· Last digit in the number decimal part >= 5 (5, 6, 7, 8, 9) à rounding up (i.e. 1,545 = 1, 55)

6.2.2 Measures format

This chapter describes the measure formats and the conversion rules to use in all messages, unless other formats or rules are specified in the sport documentation.

Measure

Value

Format

Example

Height/Distance

N(1).N(2)m

N(3)cm

N(1)’N(2)’’

9.00m

900cm

9’09’’

1.83m

183cm

6’0’’

Weight

N(3)kg

N(3)lbs

900kg

900lbs

100kg

220lbs

Temperature

N(2)ºC

N(3)ºF

90ºC

990ºF

35ºC

95ºF

Distance

N(3).N(3)km

N(3).N(3)mi

90.000km

90.000m

1.789km

6.123mi

Speed

N(2).N(3)m/s

N(3).N(3)mph

N(3).N(3)km/h

90.000m/s

90.000mph

90.000km/h

1.789m/s

6.123mph

3.890km/h

Precipitation

N(2)cm

N(2)in

90cm

90in

2cm

1in

6.2.3 Rules for measures conversion

This chapter describes measure the conversion rules to use in all messages, unless other rules are specified in the sport documentation. When using these conversions for athlete heights and weights and fore mentioned rounding rules must be applied.

Measure	Conversion Rules
Distance	1 in = 0,0254 m 1 ft = 12 in = 0,3048 m 1 yd = 3 ft = 36 in = 0,9144 m 1 mi = 1.760 yd = 5.280 ft = 63360 in = 1609,344 m 1 nmi (nautical mile) = 1,852 m
Speed	1 km/h = 3,6 m/s 1 kts= 1 nmi/h
Weight	1 lbs = 0,453 592 37 kg
Temperature	T[°F] = 1,8 × T[°C] + 32 T[°C] = (T[°F] – 32) / 1.8

6.3 ODF Message Update

An update occurs when it is received a message whose identification is coinciding with the identification of an already received message.

Message identification is the combination of the header attributes: DocumentCode + DocumentSubcode + DocumentType + DocumentSubtype.

ODF PiT:

The latest message substitutes completely the previous received message.

There are specific messages, (with an UPDATE suffix) for updating some elements and keep the rest of the message, e.g. DT_SCHEDULE_UPDATE, DT_PARTIC_UPDATE, DT_PARTIC_TEAMS_ UPDATE or DT_PARTIC_HORSES_UPDATE.

ODF RT:

When the message header contains the attribute ResultStatus = LIVE_FULL or LIVE_LAST or LIVE_MANDATORY, the latest message substitutes completely the previous received message.

When the message header contains the attribute ResultStatus = LIVE_UPDATE, only the elements and attributes in the new message must be updated by message receiver. Elements and attributes provided before must be kept by message receiver.

· New message only includes the changed attributes, with the exception of the mandatory attributes that are always sent even if there is no modification.

When an attribute sent in the past has no value anymore, send the same message with ResultStatus=LIVE_MANDATORY and

· If the attribute is mandatory send it empty (Attribute=””)

· If the attribute is optional either do not send it or send it empty

7 DOCUMENT CONTROL

7.1 File Reference

ODF/INT015 R3 v4.10 APP (SB)

7.2 Version history

Version	Date	Comments
R3 v1.0	12 Mar 2012	Submitted for review version.
R3 v2.0	08 May 2012	Several changes after review and IDM. Submitted for Approval.
R3 v2.1	23 May 2012	Some changes SFR.
R3 v2.2	27 Jun 2012	Some changes SFR.
R3 v3.0	23 Jul 2012	Minor changes. After WNPA meeting changes: ODF light information deletion and new messages proposal (SFA-DRAFT).
R3 v3.1	26 Sep 2012	ODF Light changes implemented. Minor changes on sport. (SFR).
R3 v3.2	11 Oct 2012	Minor ODF Light and sport changes. Reviewer comments included. (SFA).
R3 v4.0	14 Dec 2012	Minor changes. (APP).
R3 v4.1	31 Jan 2013	Reviewer’s comments applied. (APP)
R3 v4.2	15 Mar 2013	Minor change (APP)
R3 v4.3	19 Apr 2013	Document generated using the CMS tool
R3 v4.4	28 May 2013	CR787 and CR813 applied
R3 v4.5	07 Aug 2013	CR787 (#89678), CR829 (#90698, #86828, #92577); CR862 (#92876) and CR945 (#94839) applied
R3 v4.6	09 Aug 2013	CR974, CR1078, CR666, CR906, CR827 applied
R3 v4.7	23 August 2013	CR001259, CR001300
R3 v4.8	20 September 2013	CR001269 and some defects
R3 v4.9	12 December 2013	CR001687, CR001689, CR002439, CR002496
R3 v4.10	12 December 2013	CR002433, CR001564

7.3 Change Log

Version	Status	Changes on version
R3 v1.0	SFR	• First version.
R3 v2.0	SFA	• Snowboard Codes: - @BibColor updated with White and Green. - @ResultPhase codes updated to unifiy with @BracketItem codes. - @ResultType SB_RANK updated with SBX Finals. - @WeatherPoints added for Weather Areas. - @SnowConditions and @WeatherConditions removed. • StartList: - UnitInfos / UnitInfo updated: SB_ALTITUDE_START, SB_ALTITUDE_FINISH, SB_ALTITUDE_DROP also applied for HP. Removed "HP", "SBS" and "SBX" from the codes. - Start / Competitor / Compositon / Athlete / EventUnitEntry updated with BibColor information. • Event Unit Results: - Updated elements that should NOT be included with Result / Competitor / Composition / Athlete / ExtendedResults / ExtendedResult / Extensions (and its child element) and Result / Competitor / Composition / Athlete / Stats (and its child element). - UnitInfo element updated: Weather and snow conditions removed as they are part of weather message. UI_RESULT / SB_LAST_QUALIFIED added with code for the last qualified athlete according to competition rules. - Result element updated: - Removed “RT_” from ResultType codes. - RT Triggers updated. - Updated format scores (HP/SBS). - @QualificationMark added for Result element. - Result / Competitor / Composition /Athlete /ExtendedResults /ExtendedResult Element updated: - SB_JUDGE format updated: N(3) 900. - SB_JUDGE_DISCARD code added for scores to be discarded in HP and SBS. Judge points format updated. - SB_JUDGES removed as Total judge points are included in Result / @Result. - Added Pos element for SB_SPLIT_RESULT_TIME and SB_SPLIT_RESULT_RANK for the case of severall intermediate points. - SB_RECENT changed to SB_LAST_SCORED. - SB_IDX removed as it is not used. - RT Triggers updated. - Message sort updated. • Result Summary: - CumulativeResult updated: - RT Triggers updated. - Updated format scores (HP/SBS). - CumulativeResult / Competitor / Composition / Athlete / ExtendedResults / ExtendedResult updated: - SB_BEST_RUN added with information of the best run result. - RT Triggers updated. • Event Final Ranking: - Trigger and Frequency updated. • Weather: - Competition / Weather / Conditions updated with @WeatherPoints value. - Competition / Weather / Conditions / Temperature updated: only information for Air and Snow is needed. • Discipline Configuration: - EC_SB / SB_INTERMEDIATES_NUMBER added: information for the number of intermediate points. - EC_SB / SB_HEATS_NUMBER added: information for the number of heats. - EC_SB / SB_RUNS_NUMBER added: information for the number of runs.
R3 v2.1	SFR	• Snowboard Codes: - @TemperatureUnit added for Celsius and Fahrenheit. - @SpeedUnit added for Km/h and m/s. • List of Paricipants: - DisciplineEntry modified with new Code SB_STANCE, with information of the board position for an athlete. • Start List: - Start/ @StartOrder comment updated. - Start /Competitor /Composition /Athlete /EventUnitEntry. Added SB_IRM for PGS/PSL Qualification and Elimination Runs; and SB_HEAT for HP/SBS (in case of Heats format) and PGS(Pair)/ SBX(Heat) Finals. - Start /Competitor /Composition /Athlete /PreviousResults / ExtendedDataItem Element element not used. Previous results can be taken from RESULTS for previous units. • Results Summary: - Header updated (also for RT) with clarification on DocumentCode and DocumentType - CumulativeResult /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult new Codes SB_COURSE_RANK , SB_COURSE_ERANK and SB_COURSE_IDX for Course ranks (PGS). Also added SB_TIEBRK_PTS for tie break points on HP/SBS. - CumulativeResult /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult remove SB_HEAT as is included in Start List: Start /Competitor /Composition /Athlete /EventUnitEntry. - CumulativeResult /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult BEST_RUN updated with Pos (1,2) and Value(Y, N). • Event Final Ranking: - Result /Competitor /ExtendedResults /ExtendedResult moved to Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult. - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult new Code SB_HEAT_RANK with the rank in the last heat where the athlete finished his/her competiton. • Weather: - Some minor changes.
R3 v2.2	SFR	• Snowboard Codes: - CC @Bracket added. • Start List: - Start /Competitor /Composition /Athlete /PreviousResults/@ResultType Optional. - Start /Competitor /Composition /Athlete /EventUnitEntry. SB_COLOR changed to SB_BIB_COLOR. • Event Unit Results: - UnitInfo Element not used. Last qualified information is moved to Results Summary. - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: SB_DIFF expected information updated. - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: SB_CURRENT, SB_NEXT and SB_LAST_SCORED descriptions clarified. • Results Summary: - CumulativeResult /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: SB_BEST_RUN not applied for SBX. - CumulativeResult / @QualificationMark: RT Trigger updated clarification. - CumulativeResult /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: new code SB_LAST_QUALIFIED added to inform that the athlete is the last one qualified at a certain point according to sport rules. • Medallists: - Competitor /Composition /Athlete is used now. • Real Time: - Trigger T4 removed as it is not used.
R3 v3.0	SFA (DRAFT)	• Start List: - PSL Finals added for SB_HEAT (Pairs). - PhaseInfo element now is used with SB_PENALTY_TIME code for the finals of PGS and PSL. • Results Summary: - Header clarification on two heats format for HP/SBS. - PSL added for SB_COURSE_RANK, SB_COURSE_ERANK and SB_COURSE_IDX. • New messages proposal: Added the definition of DT_PHASE_RESULT and DT_RT_PHASE_RESULT messages (marked in blue color). These messages should be used (instead of DT_RESULT_SUMMARY and DT_RT_RESULT_SUMMARY) at the moment that these changes are approved until then the deprecated messages should be still used. • Deletion messages proposal: DT_RESULT_SUMMARY and DT_RT_RESULT_SUMMARY (marked in pink color). These messages should be deleted at the moment that these changes are approved until then the deprecated messages should be still used. • Deletion extensions proposal: ODF Light extensions from the DT_START_LIST Message. Marked in pink color the ODF Light extensions. These extensions should be deleted at the moment that these changes are approved until then they should be still used.
R3 v3.1	SFR	• Light extensions: ODF Light extensions from the DT_START_LIST and DT_PHASE_RESULT messages are marked in pink colour. These extensions will be deleted at the moment that these changes are implemented by OVR for Non-Olympics projects from those messages and included in new messages. • Light extensions: DT_START_LIST PreviousResults defined as non-light extension (removed pink). • New messages: Added the definition of DT_PHASE_RESULT and DT_RT_PHASE_RESULT messages. These messages should be used (instead of DT_RESULT_SUMMARY and DT_RT_RESULT_SUMMARY). • DT_EXTRA_DATA renamed to DT_PLAY_BY_PLAY. • DT_PHASE_RESULT and DT_RT_PHASE_RESULT messages structure merged: - PhaseInfos and PhaseInfos/PhaseInfo elements of DT_PHASE_RESULT and DT_RT_PHASE_RESULT renamed to ExtendedInfos, ExtendedInfos/ExtendedInfo - Bib attribute added to Competitor and Athlete element of the DT_PHASE_RESULT and DT_RT_PHASE_RESULT messages. - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: SB_RUN_OFF code removed. • SortOrder attribute clarified so that any result sort order change from the initial start list order will be provided in the SortOrder attribute (or any extension used to sort competitors) of the DT_RT_RESULT and DT_PHASE_RESULT message (this includes ranked, none-ranked and IRM athletes/team) • Brackets: - BracketItem /ExtBracketItems /ExtBracketItem: SB_PLACEMENT expected when fase is NOT semifinal. - BracketItem /NextUnitLoser /Phase comment updated: Only for semifinals of PGS, PSL and SBX. • Event Final Ranking: - Result /SortOrder attribute comment updated. - Result /Competitor /Code: NOC ID value removed. • Config: - Config /Unit is set to Optional. - ExtendedConfig: EC_QUALIFICATION_RULE updated. SB_RANK_QUALIFY_NEXT_ROUND is removed and SB_RANK_QUALIFY_EIGHTHFINAL added.
R3 v3.2	SFA	• Start List: - Non-light extension: The PreviousResults elements are defined as part of the message. - SortOrder of Start /Competitor /Composition /Athlete /PreviousResult has been removed. • Event Unit Results: - UnitDateTime element is not used for Real Time. - Result / Competitor / Composition /Athlete /ExtendedResults /ExtendedResult Element new codes SB_DQP (Potentially DSQ, only RT), SB_PFR (Photo Finish Required, only RT) and SB_TIEBRK_PTS. • Phase Results: - Updated comment for SortOrder of the Result element (the comment regarding start list has been deleted). - Comment for TIEBRK_PTS updated. • Discipline Configuration: - Clarified how to manage information not know before competition.
R3 v4.0	APP	• 2.2: End to End data flow. Removed old sentence about previous messages. • Phase Result (PiT and RT): - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult Element. Code SB_LAST_QUALIFIED description updated. (Include defects of FR: #83818 and #83775).
R3 v4.1	APP	• Snowboard Codes, alphabetically ordered as Global Codes and Sport Codes. • Event Unit Results (PiT and RT): - Result Element. Text about run-off removed as no longer run-offs. • Phase Results (PiT and RT): - Result Element. Text about run-off removed as no longer run-offs. - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult Element. . New Code SB_SORT_HEAT.
R3 v4.2	APP	• Start List - Official Element. Attribute Function comments updated.
R3 v4.3	APP	Document generated using the CMS tool
R3 v4.4	APP	• Start List: - Trigger updated because of SBX Snowseed - Start /Competitor /Composition /Athlete /EventUnitEntry . SB_SNOWSEED attribute code added • Event Unit Results: - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult . SB_CURRENT attribute clarifies its description • Discipline Configuration: - Configs /Config /ExtendedConfig . SB_RUNS_NUMBER attribute it is used also in PGS, PSL Finals
R3 v4.5	APP	• Start List: - UnitInfos /UnitInfo: . SB_COURSE_NAME updated to be S(50) (CR829) . SB_ALTITUDE_START, SB_ALTITUDE_FINISH, SB_ALTITUDE_DROP Expected column updated (CR862) • Event Unit Results - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: . SB_CURRENT @Pos description updated (affected by CR787 and CR829) . SB_TIEBRKNG_FOR New code added (CR829) • Phase Results - Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult: . SB_BEST_RUN updated (CR945)
R3 v4.6	APP	• Start List: - UnitInfos /UnitInfo: . SB_ALTITUDE_START, SB_ALTITUDE_FINISH, SB_ALTITUDE_DROP, SB_LENGTH, SB_WIDTH_WALSS, SB_INCLINATION and SB_HEIGHT_WALSS format updated (CR1078) • Snowboard Codes redefined for unify with FR (CR1078) • CR974 - DT_WEATHER: Remove "+" symbol in weather attributes, when sending values above 0 degrees • CR666 - Added Venue attribute as mandatory for DT_PARTIC / DT_PARTIC_UPDATE message • CR906: Removed ODF Light elements from DT_START_LIST and DT_PHASE_RESULTS messages • CR827 - For DT_PARTIC / DT_PARTIC_UPDATE messages and for Participant /Discipline /RegisteredEvent /EventEntry element change entry SB_RANK by E_RANK and SB_RANK_POINTS by E_POINTS (consistency across sports)
R3 v4.7	APP	• CR001259: - SB_RE_RUN attribute added to DT_RESULTS message (Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult) - SB_PFR definition updated. • CR001300: SB_ESTANCE changed to E_ESTANCE and moved to Participant /Discipline /RegisteredEvent /EventEntry
R3 v4.8	APP	• (Event Unit Result) SB_CURRENT attribute definition updated to manage correctly SBX event (CR001269 -#96114 ) • (Event Unit Result) SB_COURSE_IDX definition clarified (#98726) • (Phase Result) PARTIAL ResultStatus added to definition (#98107)
R3 v4.9	APP	• (Start List) SB_FORERUNNERS attribute added (CR001687 - 98052 ) • (Phase Result) SB_BEST_RUN expected definition updated (CR001689 - 98403) • (Event Unit Result) Clarification for use added to QualificationMark (CR001689 - 98118) • (Event Unit Result) Clarification added in the Description of SB_DIFF, to explain the content of field in each phase. (CR002439 - 100849) • (Event Unit Results) SB_TIEBRK_PTS format updated, extra digits added (CR002496 – 100198, 101551)
R3 v4.10	APP	• (Phase Results) INTERIM status added to ResultStatus definition (CR002433) • (Event Unit Results) SB_TIEBRK_PTS clarification added to definition. • (DT_WEATHER) Weather /Conditions /Condition@Value defined as CC @WeatherConditions for SKY Conditions and as CC @SnowConditions for SNOW conditions (CR001564) • (DT_WEATHER) Weather /Conditions /Wind@Value defined as N(3).N(1) witho plus/minus symbols (CR001564)

This page has been intentionally left blank

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

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

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6
Competition
	Code
	Participant (1,N)
		Code
		Parent
		Status
		GivenName
		FamilyName
		PrintName
		PrintInitialName
		TVName
		TVInitialName
		Gender
		Organisation
		BirthDate
		Height
		Weight
		PlaceofBirth
		CountryofBirth
		PlaceofResidence
		CountryofResidence
		Nationality
		MainFunctionId
		Current
		OlympicSolidarity
		ModificationIndicator
		Discipline
			Code
			InternationalFederationId
			RegisteredEvent (0,N)
				Gender
				Event
				Bib
				EventEntry (0,N)
					*Code*
					*Type*
					*Pos*
					Value
		OfficialFunction (0,N)
			FunctionId

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6	Level 7
Competition
	Code
	PhaseInfos (0,1)
		PhaseInfo (1,N)
			*Type*
			*Code*
			*Pos*
			Value
	UnitInfos (0,1)
		UnitDateTime (0,1)
			StartDate
		UnitInfo (0,N)
			*Type*
			*Code*
			*Pos*
			Value
			Competitor (0,N)
				Organisation
				Order
				Composition (0,1)
					Athlete (1,N)
						FamilyName
						GivenName
	Officials (0,1)
		Official (1,N)
			Code
			Function
			Order
	Start (0,N)
		StartOrder
		SortOrder
		Competitor
			Code
			Type
			Bib
			Composition (0,1)
				Athlete (1,N)
					Code
					Order
					Bib
					EventUnitEntry (0,N)
						*Type*
						*Code*
						*Pos*
						Value

Level 1	Level 2	Level 3	Level 4	Level 5	Level 6	Level 7	Level 8
Competition
	Code
	UnitInfos (0,1)
		UnitDateTime (0,1)
			*StartDate*
			EndDate
	Result (1,N)
		Rank
		RankEqual
		Result
		IRM
		QualificationMark
		SortOrder
		ResultType
		Competitor (1,N)
			*Code*
			Type
			Bib
			Composition
				Athlete (1,N)
					*Code*
					Order
					Bib
					ExtendedResults (0,1)
						ExtendedResult (1,N)
							*Type*
							*Code*
							*Pos*
							Value

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

3.2.2 Start List

3.2.3 Event Unit Results

3.2.4 Phase Results

3.2.5 Event Final Ranking

3.2.6 Event’s Medallists

3.2.7 Brackets

3.2.8 Discipline Configuration

3.2.9 Event Unit Weather Conditions

5.2 Snowboard Codes

6 General definitions

6.1 ODF Message Structure