Table of content

Table of content 3

1   Introduction   7

1.1.. This document 7

1.2.. Objective. 7

1.3.. Main Audience. 7

1.4.. Glossary. 7

1.5.. Related Documents. 9

2   Overall Perspective  10

2.1.. Objective. 10

2.2.. End to End data flow. 10

3   Messages  11

3.1.. Applicable Messages. 11

3.2.. Messages. 13

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

3.2.1.1    Description. 13

3.2.1.2    Header Values. 13

3.2.1.2.1     PiT Header 13

3.2.1.3    Trigger and Frequency. 14

3.2.1.3.1     PiT Triggers. 14

3.2.1.4    Message Structure. 15

3.2.1.5    Message Values. 17

3.2.1.6    Message Sort 20

3.2.2... List of teams / List of teams update. 21

3.2.2.1    Description. 21

3.2.2.2    Header Values. 21

3.2.2.2.1     PiT Header 21

3.2.2.3    Trigger and Frequency. 22

3.2.2.3.1     PiT Triggers. 22

3.2.2.4    Message Structure. 23

3.2.2.5    Message Values. 24

3.2.2.6    Message Sort 25

3.2.3... Start List 26

3.2.3.1    Description. 26

3.2.3.2    Header Values. 26

3.2.3.2.1     PiT Header 26

3.2.3.3    Trigger and Frequency. 27

3.2.3.3.1     PiT Triggers. 27

3.2.3.4    Message Structure. 28

3.2.3.5    Message Values. 30

3.2.3.6    Message Sort 32

3.2.4... Event Unit Results. 33

3.2.4.1    Description. 33

3.2.4.2    Header Values. 33

3.2.4.2.1     PiT Header 33

3.2.4.2.2     RT Header 34

3.2.4.3    Trigger and Frequency. 35

3.2.4.3.1     PiT Triggers. 35

3.2.4.3.2     RT Triggers. 35

3.2.4.4    Message Structure. 36

3.2.4.5    Message Values. 38

3.2.4.6    Message Sort 47

3.2.5... Cumulative Results. 48

3.2.5.1    Description. 48

3.2.5.2    Header Values. 48

3.2.5.2.1     PiT Header 48

3.2.5.2.2     RT Header 49

3.2.5.3    Trigger and Frequency. 50

3.2.5.3.1     PiT Triggers. 50

3.2.5.3.2     RT Triggers. 50

3.2.5.4    Message Structure. 52

3.2.5.5    Message Values. 53

3.2.5.6    Message Sort 58

3.2.6... Pool Standings. 59

3.2.6.1    Description. 59

3.2.6.2    Header Values. 59

3.2.6.2.1     PiT Header 59

3.2.6.3    Trigger and Frequency. 60

3.2.6.3.1     PiT Triggers. 60

3.2.6.4    Message Structure. 61

3.2.6.5    Message Values. 62

3.2.6.6    Message Sort 64

3.2.7... Event Final Ranking. 65

3.2.7.1    Description. 65

3.2.7.2    Header Values. 65

3.2.7.2.1     PiT Header 65

3.2.7.3    Trigger and Frequency. 66

3.2.7.3.1     PiT Triggers. 66

3.2.7.4    Message Structure. 67

3.2.7.5    Message Values. 68

3.2.7.6    Message Sort 69

3.2.8... Statistics. 70

3.2.8.1    Description. 70

3.2.8.2    Header Values. 70

3.2.8.2.1     PiT Header 70

3.2.8.3    Trigger and Frequency. 71

3.2.8.3.1     PiT Triggers. 71

3.2.8.4    Message Structure. 72

3.2.8.5    Message Values. 74

3.2.8.6    Message Sort 88

3.2.9... Event’s Medallists. 89

3.2.9.1    Description. 89

3.2.9.2    Header Values. 89

3.2.9.2.1     PiT Header 89

3.2.9.3    Trigger and Frequency. 90

3.2.9.3.1     PiT Triggers. 90

3.2.9.4    Message Structure. 91

3.2.9.5    Message Values. 92

3.2.9.6    Message Sort 92

3.2.10   Brackets. 93

3.2.10.1  Description. 93

3.2.10.2  Header Values. 93

3.2.10.2.1     PiT Header 93

3.2.10.3  Trigger and Frequency. 94

3.2.10.3.1     PiT Triggers. 94

3.2.10.4  Message Structure. 95

3.2.10.5  Message Values. 97

3.2.10.6  Message Sort 99

3.2.11   Discipline Configuration. 100

3.2.11.1  Description. 100

3.2.11.2  Header Values. 100

3.2.11.2.1     PiT Header 100

3.2.11.3  Trigger and Frequency. 101

3.2.11.3.1     PiT Triggers. 101

3.2.11.4  Message Structure. 102

3.2.11.5  Message Values. 103

3.2.11.6  Message Sort 105

3.2.12   Event Unit Weather Conditions. 106

3.2.12.1  Description. 106

3.2.12.2  Header Values. 106

3.2.12.2.1     PiT Header 106

3.2.12.3  Trigger and Frequency. 107

3.2.12.3.1     PiT Triggers. 107

3.2.12.4  Message Structure. 108

3.2.12.5  Message Values. 109

3.2.12.6  Message Sort 109

3.2.13   Play by Play. 110

3.2.13.1  Description. 110

3.2.13.2  Header Values. 110

3.2.13.2.1     PiT Header 110

3.2.13.2.2     RT Header 111

3.2.13.3  Trigger and Frequency. 112

3.2.13.3.1     PiT Triggers. 112

3.2.13.3.2     RT Triggers. 112

3.2.13.4  Message Structure. 113

3.2.13.5  Message Values. 114

3.2.13.6  Message Sort 116

4   Messages Sequence  119

5   Codes  120

5.1.. Global Codes. 120

5.2.. Curling Codes. 122

6   General definitions  125

6.1.. ODF Message Structure. 125

6.1.1... ODF Declaration. 125

6.1.2... ODF Header 125

6.1.3... ODF Body. 127

6.2.. ODF Data Types and Formats. 130

6.2.1... Rules for rounding numbers. 131

6.2.2... Measures format 132

6.2.3... Rules for measures conversion. 132

6.3.. ODF Message Update. 133

7   DOCUMENT CONTROL   135

7.1.. File Reference. 135

7.2.. Version history. 135

7.3.. Change Log. 135

 

1   Introduction

1.1  This document

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

1.2  Objective

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

1.3  Main Audience

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

1.4  Glossary

The following abbreviations are used in this document

Acronym

Description

IF or International Federation

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

IOC

International Olympic Committee

IPC

International Paralympic Committee

NOC

National Olympic Committee recognized as such by the IOC

NPC

National Paralympic Committee as recognized by the IPC

ODF

Olympic Data Feed

ODF Light

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

ODF-PiT

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

ODF-RT

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

OPNS

Olympic and Paralympic News Service

RSC

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

Sport

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

WNPA

World News Press Agencies

 

 

 


 

1.5  Related Documents

 

Document Reference

Document Title

Document Description

ODF/INT001

ODF Message Transmission Document

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

ODF/COD001

ODF Common Codes Document

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

ODF/INT004

ODF General Messages Interface Document

This document describes the ODF general messages

 

 

2   Overall Perspective

2.1  Objective

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

2.2  End to End data flow

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


3   Messages

3.1  Applicable Messages

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

 

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

 

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

 

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

 

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

 

Message Type

Message Name

Feed

Message extended

DT_SCHEDULE

Competition schedule

PiT

 

DT_SCHEDULE_UPDATE

Competition schedule update

PiT

 

DT_PARTIC / DT_PARTIC_UPDATE

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

PiT

X

DT_PARTIC_TEAMS / DT_PARTIC_TEAMS_UPDATE

List of teams / List of teams update

PiT

X

DT_MEDALS

Medal standings

PiT

 

DT_MEDALLISTS_DAY

Medallists of the day

PiT

 

DT_GLOBAL_GM

Global good morning

PiT

 

DT_GLOBAL_GN

Global good night

PiT

 

DT_START_LIST

Start List

PiT

X

DT_RESULT

Event Unit Results

PiT/RT

X

DT_CUMULATIVE_RESULT

Cumulative Results

PiT/RT

X

DT_POOL_STANDING

Pool Standings

PiT

X

DT_RANKING

Event Final Ranking

PiT

X

DT_STATS

Statistics

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_PLAY_BY_PLAY

Play by Play

PiT/RT

X

DT_RT_KA

RT Discipline/Venue keep alive

RT

 

DT_PDF

PDF Message

PDF

 

DT_PDF_GM

PDF Discipline/Venue good morning

PDF

 

DT_PDF_GN

PDF Discipline/Venue good night

PDF

 

DT_PDF_SERIAL

List of Current PDF Serial

PDF

 

DT_RT_GM

RT Discipline/venue good morning

RT

 

DT_RT_GN

RT Discipline/venue good night

RT

 

 

 

 

 


 

3.2  Messages

 

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

3.2.1.1  Description

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

 

3.2.1.2  Header Values

3.2.1.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD is defined according to CC @Discipline

DocumentType

DT_PARTIC / DT_PARTIC_UPDATE

List of participants  by discipline message

Version

1..V

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

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

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

Time

MillisTime

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

LogicalDate

Date

Logical Date of events that extends until next day.

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

 

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

 

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

 

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

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

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

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.1.3  Trigger and Frequency

3.2.1.3.1  PiT Triggers

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

 

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

 

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

 

 


3.2.1.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Participant (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Parent

 

 

 

 

 

Status

 

 

 

 

 

GivenName

 

 

 

 

 

FamilyName

 

 

 

 

 

PrintName

 

 

 

 

 

PrintInitialName

 

 

 

 

 

TVName

 

 

 

 

 

TVInitialName

 

 

 

 

 

Gender

 

 

 

 

 

Organisation

 

 

 

 

 

BirthDate

 

 

 

 

 

Height

 

 

 

 

 

Weight

 

 

 

 

 

PlaceofBirth

 

 

 

 

 

CountryofBirth

 

 

 

 

 

PlaceofResidence

 

 

 

 

 

CountryofResidence

 

 

 

 

 

Nationality

 

 

 

 

 

MainFunctionId

 

 

 

 

 

Current

 

 

 

 

 

OlympicSolidarity

 

 

 

 

 

ModificationIndicator

 

 

 

 

 

Discipline

 

 

 

 

 

 

Code

 

 

 

 

 

InternationalFederationId

 

 

 

 

 

RegisteredEvent (0,N)

 

 

 

 

 

 

Gender

 

 

 

 

 

Event

 

 

 

 

 

Bib

 

 

 

 

 

Class

 

 

 

 

 

Guide

 

 

 

 

 

EventEntry (0,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

Pos

 

 

 

 

 

Value

 

 

OfficialFunction (0,N)

 

 

 

 

 

 

FunctionId

 

 

 


3.2.1.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Participant

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Participant’s ID.

 

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

 

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

 

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

 

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

Parent

M

S(20) with no leading zeroes

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

 

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

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

Status

O

CC @AccreditationStatus

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

 

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

GivenName

O

S(25)

Given name in WNPA format (mixed case)

FamilyName

M

S(25)

Family name in WNPA format (mixed case)

PrintName

M

S(35)

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

PrintInitialName

M

S(18)

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

TVName

M

S(35)

TV name

TVInitialName

M

S(18)

TV initial name

Gender

M

CC @PersonGender

Participant’s gender

Organisation

M

CC @Organisation

Organisation ID

BirthDate

O

YYYYMMDD

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

Height

O

N(3)

999

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

Weight

O

N(3)

999

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

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

PlaceofBirth

O

S(75)

Place of Birth

CountryofBirth

O

CC @Country

Country ID of Birth

PlaceofResidence

O

S(75)

Place of Residence

CountryofResidence

O

CC @Country

Country ID of Residence

Nationality

O

CC @Country

Participant’s nationality.

 

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

MainFunctionId

O

CC @Function

Main function

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

Current

M

boolean

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

OlympicSolidarity

O

Y or N

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

ModificationIndicator

M

N, U

Attribute is mandatory in the  DT_PARTIC_UPDATE message only

 

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

U-Update participant

 

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

 

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

 

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

 

Participant /Discipline

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

Attribute

M/O

Value

Comments

Code

M

CC @Discipline

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

InternationalFederationId

O

S(16)

Competitor’s federation number for the corresponding discipline (include if the discipline assigns international federation codes to athletes).

 

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(2)

Bib number.

 

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

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

Class

O

CC @SportClass

Not used in Olympics.

Guide

O

S(20) with no leading zeroes

Not used in Olympics.

 

Participant /Discipline /RegisteredEvent /EventEntry

Send if there are specific athlete’s event entries.

Type

Code

Pos

Value

Description

E_ENTRY

E_POSITION

 

CC @Position

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Position in the team

E_HAND

 

CC @Hand

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Hand

E_ROLE

 

CC @Role

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Role in the team

E_IRM

 

CC @EntryIRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Athlete’s status in the team.

When the athlete has been suspended or disqualified.

(see codes section)

 

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

 

Type/Code

Description

Expected

E_ENTRY/ E_POSITION

N/A

N/A

E_ENTRY/ E_HAND

N/A

N/A

E_ENTRY/ E_ROLE

N/A

N/A

E_ENTRY/ E_IRM

N/A

N/A

 

 

 

Participant /OfficialFunction

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

Attribute

M/O

Value

Comments

FunctionId

M

CC @Function

Additional officials’ function code

 

 

3.2.1.6  Message Sort

The message is sorted by Participant @Code


 

 

3.2.2    List of teams / List of teams update

3.2.2.1  Description

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

 

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

 

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

 

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

 

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

 

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

 

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

 

 

3.2.2.2  Header Values

3.2.2.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD is defined according to CC @Discipline

DocumentType

DT_PARTIC_TEAMS_UPDATE / DT_PARTIC_TEAMS

List of participant teams message

Version

1..V

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

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

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

Time

MillisTime

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

LogicalDate

Date

Logical Date of events that extends until next day.

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

 

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

 

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

 

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

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

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

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.2.3  Trigger and Frequency

3.2.2.3.1  PiT Triggers

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

 

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

 

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

 

 


3.2.2.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition

 

 

 

 

 

Code

 

 

 

 

Team (1,N)

 

 

 

 

 

Code

 

 

 

 

Organisation

 

 

 

 

Number

 

 

 

 

Name

 

 

 

 

Gender

 

 

 

 

Current

 

 

 

 

ModificationIndicator

 

 

 

 

Composition (0,1)

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

Code

 

 

 

 

Order

 

 

TeamOfficials (0,1)

 

 

 

 

 

Official (1,N)

 

 

 

 

 

Code

 

 

 

 

Function

 

 

Discipline (0,1)

 

 

 

 

 

Code

 

 

 

 

InternationalFederationId

 

 

 

 

RegisteredEvent (0,1)

 

 

 

 

 

Event

 

 

 

 

Gender

 


3.2.2.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Team

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Team’s ID (example ATM001ESP01, 393553)

 

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

Organisation

M

CC @Organisation

Team organisation’s ID

Number

M

N(2)

Team’s number.

 

If there is not more than one team for one organisation participating in one event, it is 1. Otherwise, it will be incremental, 1 for the first organisation’s team, 2 for the second organisation’s team, etc.

 

Required in the case of current teams.

Name

M

CC @Organisation

Code of the team’s organisation. It will be Optional in the case of  List of Team Update when the @ ModificationIndicator=D

Gender

M

CC @DisciplineGender

Discipline Gender Code of the Team

Current

M

boolean

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

ModificationIndicator

M

N, U, D

Attribute is mandatory in the DT_PARTIC_TEAMS_UPDATE  message only

 

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

U-Update team

D-Delete team

 

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

 

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

 

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

 

Team /Composition /Athlete

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

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

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

 

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

Order

O

Numeric

Team member order

 

Team /TeamOfficials /Official

Send if there are specific team’s officials.

 

Not apply to historical teams.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Official’s ID of the listed team’s official.

 

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

 

You should be able to find further information about the official in the list of officials’ message according to its @Code

Function

M

CC @Function

Official’s function for the team.

 

Team /Discipline

Each team is assigned just to one discipline.

Attribute

M/O

Value

Comments

Code

M

CC @Discipline

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

InternationalFederationId

O

S(16)

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

 

Team /Discipline /RegisteredEvent

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

Attribute

M/O

Value

Comments

Event

M

CC @Event

Event ID

Gender

M

CC @DisciplineGender

Discipline Gender Code

 

 

3.2.2.6  Message Sort

The message is sorted by Team @Code.


 

 

3.2.3    Start List

3.2.3.1  Description

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

 

The Start List is a mandatory message for all disciplines.

 

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

 

 

3.2.3.2  Header Values

3.2.3.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

UU according to CC @Unit

DocumentType

DT_START_LIST

Start List message

Version

1..V

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

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

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

Time

MillisTime

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

LogicalDate

Date

Logical Date of events that extends until next day.

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

 

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

 

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

 

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

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

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

 

 

3.2.3.3  Trigger and Frequency

3.2.3.3.1  PiT Triggers

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.

 

 


3.2.3.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Competition

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

StartDate

 

 

 

 

Officials (0,1)

 

 

 

 

 

 

 

Official (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Function

 

 

 

 

 

 

Order

 

 

 

 

Start (0,N)

 

 

 

 

 

 

 

StartOrder

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Type

 

 

 

 

 

 

Coaches (0,1)

 

 

 

 

 

 

 

Coach (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Function

 

 

 

 

 

 

Order

 

 

 

 

EventUnitEntry (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Order

 

 

 

 

 

 

EventUnitEntry (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 


3.2.3.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

UnitInfos /UnitDateTime

Scheduled start date and time.

Attribute

M/O

Value

Comments

StartDate

M

DateTime

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

 

Officials /Official

Official associated to the event unit.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Official’s code

Function

M

CC @Function

Send the function code for:

Chief Umpire

Deputy Chief Umpire

Game Umpire

Chief Ice Technician

Deputy Chief Ice Technician

Chief Timer

Deputy Chief Timer

Order

M

Numeric

Order of the Officials following the Sports Rule.

 

Start

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

Attribute

M/O

Value

Comments

StartOrder

M

Numeric

First, home team, then visiting team

SortOrder

M

Numeric

Used to sort all start list competitors in an event unit (for example, if there is not StartOrder). It is mainly used for display purposes.

 

Start /Competitor

Competitor participating in the event unit

 

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

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes or TBD

Competitor’s ID,

TBD is sent when the competitor is not known.

Type

M

T,A

T for team

A for athlete

 

Start /Competitor /Coaches /Coach

Competitor’s coach.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Official ID for the official code.

Function

M

CC @Function

Send the function code for the coach.

Order

M

Numeric

Coach order (1,2,…9)

 

Start /Competitor /EventUnitEntry

Type

Code

Pos

Value

Description

EU_ENTRY

E_HOME

 

Not used

Key of the EventUnitEntry to uniquely identify if the Competitor is the Home Team.

E_AWAY

 

Not used

Key of the EventUnitEntry to uniquely identify if the Competitor is the Away Team.

 

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

 

Type/Code

Description

Expected

EU_ENTRY/ E_HOME

Key of the EventUnitEntry to uniquely identify if the Competitor is the Home Team.

if the Competitor is the Home Team.

EU_ENTRY/ E_AWAY

Key of the EventUnitEntry to uniquely identify if the Competitor is the Away Team.

if the Competitor is the Away Team.

 

 

 

Start /Competitor /Composition /Athlete

Athlete or team member’s extended information.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

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

Order

M

Numeric

N/A

 

Start /Competitor /Composition /Athlete /EventUnitEntry

Team member or individual athlete’s event unit entry.

Type

Code

Pos

Value

Description

EU_CU

CU_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

IRM if applies

CU_POSITION

 

CC @Position

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Position in the team

CU_FUNCTION

 

CC @Role

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Role in the team

 

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

 

Type/Code

Description

Expected

EU_CU/ CU_IRM

IRM if applies

As soon as known

EU_CU/ CU_POSITION

Position in the team

As soon as known

EU_CU/ CU_FUNCTION

Role in the team (Skip, Vice Skip)

As soon as known

 

 

 

 

3.2.3.6  Message Sort

The message is sorted by the Start@SortOrder attribute.


 

 

3.2.4    Event Unit Results

3.2.4.1  Description

The Event Unit Results is a message containing the results for the list of competitors in one event unit, either competing as single athletes or as aggregated athletes according to the team definition as it can be seen in the List of teams’ message in the ODF General Messages Interface Document.

 

 

3.2.4.2  Header Values

3.2.4.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

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

DocumentType

DT_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 CU

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

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

 

3.2.4.2.2  RT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

UU according to CC @Unit

DocumentType

DT_RT_RESULT

Event Unit Real Time Results message

ResultStatus

CC @ResultStatus

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

“LIVE_UPDATE” /

“LIVE_FULL” /

“LIVE_MANDATORY” /

“LIVE_LAST

Version

1..V

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

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

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

Time

MillisTime

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

LogicalDate

Date

Logical Date of events that extends until next day.

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

 

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

 

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

 

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

Venue

CC @VenueCode

Venue where the message is generated.

RTSerial

Numeric

Incremental and unique sequence number for ODF-RT messages.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

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

 

 

3.2.4.3  Trigger and Frequency

3.2.4.3.1  PiT Triggers

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

After each end, the message should be sent for intermediate results:

ResultStatus in the headers will have the value “INTERMEDIATE”

In this case, the element Result will contain the result at the moment after the end, as it can also be determined in the Period element (the end can be seen in Period @Code).

 

Then proceed with unofficial and official results, as expected.

 

 

3.2.4.3.2  RT Triggers

For ResultStatus=LIVE_UPDATE:

 

o T1: Trigger at the beginning of the event unit.

 

o T2: Trigger when the competitor becomes current.

 

o T3: Trigger after the delivery (throw) of a stone, when the statistics are known.

 

o T4: Trigger after a change in the scores (when an end finishes).

 

o T5: Trigger when last stone draw result of a team is known.(Only in Round Robin)

 

o T6: After a line-up change

 

•  For ResultStatus=LIVE_FULL

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

Use "LFDelay=999".

 

•  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.4.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Competition

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

 

 

EndDate

 

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Periods (0,1)

 

 

 

 

 

 

 

 

Period (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

HomeScore

 

 

 

 

 

 

 

AwayScore

 

 

 

 

 

 

 

HomePeriodScore

 

 

 

 

 

 

 

AwayPeriodScore

 

 

 

 

 

 

 

ExtendedPeriods (0,1)

 

 

 

 

 

 

 

 

ExtendedPeriod (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

WLT

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

Competitor (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Stats (0,1)

 

 

 

 

 

 

 

 

Stat (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Composition

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Stats (0,1)

 

 

 

 

 

 

 

 

Stat (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 


3.2.4.5  Message Values

Competition

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

CC @Competition

Unique ID for competition

N

When available

 

UnitInfos /UnitDateTime

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

 

This element is just for PiT.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

StartDate

O

DateTime

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

 

Not needed for Real Time.

N

Not needed for Real Time

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

Not needed for Real Time

 

UnitInfos /UnitInfo

Unit info item associated to the event unit.

Type

Code

Pos

Value

Description

UI_GENERAL

CU_ATTENDANCE

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Number of spectators

UI_GAME

CU_EE

 

Y / N

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Y if the game has Extra-Ends.

N if not.

CU_LASTEND

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Number of the last completed end.

CU_LAST_SCORE_HOME

 

Y / N

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

 Send Y if the Home team was the last team to score or in case of a blank end (0:0) or no score (X:X).

Else, send N.

CU_LAST_SCORE_AWAY

 

Y / N

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

 Send Y if the Away team was the last team to score or in case of a blank end (0:0) or no score (X:X).

Else, send N.

UI_MIS

CU_SHOT_NUMBER

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Number of the Most Important Shot.

CU_SHOT_DESC

 

S(n)

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Explanation of the Most Important Shot.

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

UI_GENERAL/ CU_ATTENDANCE

Number of spectators

As soon as known

N

Not needed in RT

UI_GAME/ CU_EE

Y if the game has Extra-Ends.

N if not.

As soon as known

N

If needed

UI_GAME/ CU_LASTEND

Number of the last completed end in the current game.

After each end.

N

T4

UI_GAME/ CU_LAST_SCORE_HOME

Send Y if the Home team was the last team to score or in case of a blank end (0:0) or no score (X:X).

Else, send N.

After each end.

Y

T4

UI_GAME/ CU_LAST_SCORE_AWAY

Send Y if the Away team was the last team to score or in case of a blank end (0:0) or no score (X:X).

Else, send N.

After each end.

Y

T4

UI_MIS/ CU_SHOT_NUMBER

Number of the most important shot of match.

As soon as known

N

Not needed in RT

UI_MIS/ CU_SHOT_DESC

Explanation related with the most important shot of match.

As soon as known

N

Not needed in RT

 

 

 

Periods /Period

Period in which the event unit message arrives.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

Numeric

Numeric, beginning from 1, to indicate the end (key of Period element)

N

When available

HomeScore

M

Numeric

L, W

Home competitor score up to the end of the @Code end

N

When available

AwayScore

M

Numeric

L, W

Away competitor score up to the end of the @Code end

N

When available

HomePeriodScore

M

Numeric

X, /, or blank (nothing)

Home competitor score achieved in the @Code end (as isolated end)

N

When available

AwayPeriodScore

M

Numeric

X, /, or blank (nothing)

Away competitor score achieved in the @Code end (as isolated end)

N

When available

 

Periods /Period /ExtendedPeriods /ExtendedPeriod

ExtendedPeriod  information.

Type

Code

Pos

Value

Description

EP_CU

CU_TIME

N(1)

9

Text

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Pos:

Send 1 for the first (Home) Team, 2 for the second (Away) Team

For @Value:

 Send the remaining time

CU_LSCE

 

Text

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

 Send which team gets the last stone in the current end corresponding to the period.

Send 1 for the first (Home) Team, 2 for the second (Away) Team

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

EP_CU/ CU_TIME

Time remaining after this end.

Only if it is needed.

N

if needed

EP_CU/ CU_LSCE

Who gets the last stone in the current end corresponding to the period.

Send 1 for the first (Home) Team, 2 for the second (Away) Team

When available

N

T4

 

 

 

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.

N

If needed

RankEqual

O

Y or N

It identifies if a rank has been equalled.

 

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

N

When available

Result

O

N(2)

OR W OR L

The result of the competitor in the event unit

N

Never. Only PiT.

IRM

O

CC @IRM

The invalid rank mark, in case it is assigned

N

If needed.

WLT

O

CC @WLT

The code whether a competitor won or lost the match / game

N

If needed.

SortOrder

M

Numeric

Used to sort all the results of an  event unit

 

For Real Time this attribute is optional. Do not inform when the ResultType is empty.

 

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

If needed.

ResultType

O

CC @ResultType

Type of the @Result attribute.

 

In Real Time, when the ResultType attribute is sent empty that means that the Result element is not used. The message is used just to include some extended results for a particular kind of competitor.

 

On the contrary, if ResultType is informed, and the other attributes are blank (‘’‘’), it is assumed that these attributes are being reset.

 

In Real Time, when the ResultType attribute is sent empty that means that the Result element is not used. The message is used just to include some extended results for a particular kind of competitor.

 

On the contrary, if ResultType is informed, and the other attributes are blank (‘’‘’), it is assumed that these attributes are being reset.

N

If needed

 

Result /Competitor

Competitor related to the result of one event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Competitor’s ID

N

If needed

Type

M

T,A

T for team

A for athlete

N

If needed

 

Result /Competitor /ExtendedResults /ExtendedResult

Type

Code

Pos

Value

Description

ER_CU

CU_LSFE

 

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Send Y to indicate that the team throws the “Last Stone First End”.

CU_LSD

 

N(3).N(1)

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Send “Last Stone Draw” in cm.

CU_LSD_D

 

CC @LSD

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

 Send the proposed codes

CU_GAME_SITUATION

 

String

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Send the description of the game situation.

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

ER_CU/ CU_LSFE

Send Y to indicate that the team throws the “Last Stone First End”.

Always, if the information is known

N

When available

ER_CU/ CU_LSD

Last Stone Draw

Only in Round Robin games

N

T5

ER_CU/ CU_LSD_D

Last Stone Draw description

Only if it is needed and only for Round Robin

N

T5

ER_CU/ CU_GAME_SITUATION

Send the description of the game situation.

When this information is available

N

T4

 

 

 

Result /Competitor /Stats /Stat

Type

Code

Pos

Value

Description

ST_CU

CU_CUM_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Cumulative percentage of the team until the end of the current game

CU_GAME_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Game percentage of the team

CU_GAME

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Game Total of the team

CU_DRAWS

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Draws number for the team

CU_DRAWS_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Draws  percentage of the team

CU_TAKEOUTS

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Takeouts number of the team

CU_TAKEOUTS_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Takeouts percentage of the team

CU_IN

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the In-Turn number in that game for the team.

CU_IN_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the In-Turn percentage of the team

CU_OUT

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the Out-Turn number in that game for the team.

CU_OUT_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the Out-Turn percentage of the team

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

ST_CU/ CU_CUM_PER

Cumulative percentage of the team until the end of the current game

Always

N

If needed

ST_CU/ CU_GAME_PER

Game percentage of the team

Always

N

If needed

ST_CU/ CU_GAME

Total number of stones considered in that game for the team

Always

N

If needed

ST_CU/ CU_DRAWS

Number of Draws considered in that game for the team

Always

N

If needed

ST_CU/ CU_DRAWS_PER

Draws percentage of the team

Always

N

If needed

ST_CU/ CU_TAKEOUTS

Number of Takeouts considered in that game  for the team

Always

N

If needed

ST_CU/ CU_TAKEOUTS_PER

Takeouts percentage of the team

Always

N

If needed

ST_CU/ CU_IN

In-Turn number in that game for the team.

Always

N

If needed

ST_CU/ CU_IN_PER

In-Turn Percentage of the team.

Always

N

If needed

ST_CU/ CU_OUT

Out-Turn number in that game for the team.

Always

N

If needed

ST_CU/ CU_OUT_PER

Out-Turn Percentage of the team.

Always

N

If needed

 

 

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Athlete’s ID. Can belong to a team member or an individual athlete.

N

Only if necessary

Order

M

Numeric

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

N

Only if necessary

 

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

Team member or individual athlete’s extended result.

Type

Code

Pos

Value

Description

ER_CU

CU_CURRENT

 

S(1)

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Send “Y” if the athlete is the current player.

Send “N” if he is not.

CU_LAST_PLAYER_DRAW

 

S(1)

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Send “Y” if the athlete is the last to have played AND the shot was a Draw.

Send “N” if he is not.

CU_LAST_PLAYER_TAKEOUT

 

S(1)

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Send “Y” if the athlete is the last to have played AND the shot was a Takeout.

Send “N” if he is not.

CU_POSITION

 

CC @Position

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Position in the team

CU_ROLE

 

CC @Role

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Role in the team

CU_STARTING_END

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

The end where the player started.

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

ER_CU/ CU_CURRENT

Send “Y” if the athlete is the current player.

Send “N” if he is not.

Just if applies

Y

T2, T3

ER_CU/ CU_LAST_PLAYER_DRAW

Send “Y” if the athlete is the last to have played AND the shot was a Draw.

Send “N” if he is not.

Just if applies

Y

T2, T3

ER_CU/ CU_LAST_PLAYER_TAKEOUT

Send “Y” if the athlete is the last to have played AND the shot was a Takeout.

Send “N” if he is not.

Just if applies

Y

T2, T3

ER_CU/ CU_POSITION

Position in the team

As soon as known

Y

T6

ER_CU/ CU_ROLE

Role in the team (Skip, Vice Skip)

As soon as known

Y

T6

ER_CU/ CU_STARTING_END

End where the player started

Only after a line-up change

Y

T6

 

 

 

Result /Competitor /Composition /Athlete /Stats /Stat

Type

Code

Pos

Value

Description

ST_CU

CU_CUM_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Cumulative percentage of the player until the end of the current game

CU_GAME

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Game Total of the player

CU_GAME_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Game percentage of the player

CU_DRAWS

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Draws number for the player

CU_DRAWS_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Draws  percentage of the player

CU_TAKEOUTS

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Takeouts number of the player

CU_TAKEOUTS_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed type

For @Value:

Takeouts percentage of the player

CU_IN

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the In-Turn number in that game for the member.

CU_IN_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the In-Turn percentage for the member.

CU_OUT

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the Out-Turn number in that game for the member.

CU_OUT_PER

 

N(3)

999

or “-“

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send the Out-Turn percentage for the member.

 

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

 

Type/Code

Description

Expected

RT Only

RT Trigger

ST_CU/ CU_CUM_PER

Cumulative percentage of the team member until the end of the current game

Always

N

if needed

ST_CU/ CU_GAME

Total number of stones considered in that game for the member

Always

N

if needed

ST_CU/ CU_GAME_PER

Game percentage of the member

Always

N

if needed

ST_CU/ CU_DRAWS

Number of Draws considered in that game for the member

Always

N

if needed

ST_CU/ CU_DRAWS_PER

Draws percentage of the team member

Always

N

if needed

ST_CU/ CU_TAKEOUTS

Number of Takeouts considered in that game  for the team member

Always

N

if needed

ST_CU/ CU_TAKEOUTS_PER

Takeouts percentage of the team member

Always

N

if needed

ST_CU/ CU_IN

In-Turn number in that game for the member.

Always

N

if needed

ST_CU/ CU_IN_PER

In-Turn Percentage of the member.

Always

N

if needed

ST_CU/ CU_OUT

Out-Turn number in that game for the member

Always

N

if needed

ST_CU/ CU_OUT_PER

Out-Turn Percentage of the member.

Always

N

if needed

 

 

 

 

3.2.4.6  Message Sort

Sort by Result @SortOrder.


 

 

3.2.5    Cumulative Results

3.2.5.1  Description

The Cumulative Results is a message containing the cumulative results for the list of competitors in one phase, up to the end of this phase (including information regarding to previous phases), or up to the end of an event unit within a phase (including also the units prior the current one) either competing as single athletes or as aggregated athletes according to the team definition.

 

The difference between the Phase Results message (DT_PHASE_RESULTS) and the Cumulative Results (DT_CUMULATIVE_RESULT) is that the first one includes only the results for the phase independently from previous phases, while the Cumulative Results takes into account the results of previous phases, and therefore it gives an idea about how a competition is progressing up to the end of an intermediate phase.

 

The Cumulative Results message may be used to send an interim summary of results (including rank) part way through a phase. In this case, the DocumentSubtype is used to specify the last phase or event unit that contributed results to the message.

 

The mandatory attributes and mandatory elements defined in this message should to be used.

 

Only RealTime message is used for Curling.

 

 

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

 

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

DocumentType

DT_CUMULATIVE_RESULT

Cumulative Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or unofficial.

“OFFICIAL” /

“UNOFFICIAL”

DocumentSubtype

DDGEEEP00 or

DDGEEEPUU

It is the DocumentCode code up to the moment the cumulative message contains information:

 

E.g.: DDGEEEPUU would be cumulative results up to the end of the referenced event unit

E.g.: DDGEEEP00 would be cumulative results up to the end of the referenced phase

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.5.2.2  RT 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_RT_CUMULATIVE_RESULT

Cumulative Real Time Results message

DocumentSubtype

CC @Phase

It is the RSC code up to the moment the cumulative message contains information:

 

E.g.: DDGEEEP00 would be cumulative results up to the end of the referenced phase

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”

 

For Real Time, live update (for the normal operative), or live full for the resynchronization messages, as explained in chapter 6.1 and ResultStatus codes as seen in chapter 3, live Mandatory when there is a correction of previous messages and Live Last for the last message of this key of messages.

Version

1..V

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

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

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

Time

MillisTime

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

LogicalDate

Date

Logical Date of events that extends until next day.

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

 

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

 

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

 

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

Venue

CC @VenueCode

Venue where the message is generated.

RTSerial

Numeric

Incremental and unique sequence number for ODF-RT messages.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

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

 

 

3.2.5.3  Trigger and Frequency

3.2.5.3.1  PiT Triggers

This message is used only in RealTime.

 

 

3.2.5.3.2  RT Triggers

• For ResultStatus=LIVE_UPDATE:

It is send after any change in the scores.

•  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 sending when a correction in the previous messages has been done.

• For ResultStatus=LIVE_LAST

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

 

 


3.2.5.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

ExtendedInfos (0,1)

 

 

 

 

 

 

ExtendedInfo (1,N)

 

 

 

 

 

 

Type

 

 

 

 

 

Code

 

 

 

 

 

Pos

 

 

 

 

 

Value

 

 

 

Result (1,N)

 

 

 

 

 

 

Rank

 

 

 

 

 

RankEqual

 

 

 

 

 

ResultType

 

 

 

 

 

QualificationMark

 

 

 

 

 

SortOrder

 

 

 

 

 

ResultItems

 

 

 

 

 

 

ResultItem (1,N)

 

 

 

 

 

 

Phase

 

 

 

 

 

Result

 

 

 

 

 

 

SortOrder

 

 

Competitor

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

Composition

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 


3.2.5.5  Message Values

Competition

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

CC @Competition

Unique ID for competition

N

When available

 

ExtendedInfos /ExtendedInfo

Type and extension Type

Code

Extension Code

Pos or extension Pos

Value or extension Value

Description

EI_CU

CU_TENTATIVE_STANDINGS

 

N(2)

90

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send the position in the tentative standings (from 1 to 10)

For @Value:

Send the id of the team in the tentative.

CU_RANK

 

N(2)

90

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send the rank of the team in the tentative standings.

CU_RANK_EQUAL

 

Y/N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send Y if the Rank is equalled.

Send N if not.

CU_GAMES_PLAYED

 

N(1)

0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send the number of games played

CU_ GAMES_WON

 

N(1)

0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not sent anything

For @Value:

Send the number of games won

CU_ GAMES_LOST

 

N(1)

0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send the number of games lost

CU_QUALIFICATION_MARK

 

CC @QualificationMark

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

The code which gives an indication on the qualification

CU_WINS_TIED

 

Text

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send the wins against tied number.

CU_DSC

 

Text

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send the draw shot challenge

 

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

 

Type/Code/Extension Code

Description

Expected

RT Only

RT Trigger

EI_CU/ CU_TENTATIVE_STANDINGS

Code of the team for the tentative standings.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_RANK

Rank of the team in the  tentative standing.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_RANK_EQUAL

Send Y if the rank is equalled, N if it is not.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_GAMES_PLAYED

Number of games played by the team at the group.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_ GAMES_WON

Number of games won by the team at the group.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_ GAMES_LOST

Number of games lost by the team at the group

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_QUALIFICATION_MARK

The code which gives an indication on the qualification.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_WINS_TIED

Wins against tied number.

If available, in the games of the last session of the round robin.

Y

T4

EI_CU/ CU_TENTATIVE_STANDINGS/ CU_DSC

Draw shot challenge

If available, in the games of the last session of the round robin.

Y

T4

 

 

 

Result

For any cumulative results message, there should be at least one competitor being awarded a cumulative result after one event unit or phase.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Rank

O

Numeric

Rank of the competitor in the cumulative result

N

T4

RankEqual

O

Y or N

It identifies if a rank has been equalled.

In PiT message only Y value has sense.

N

T4

ResultType

O

CC @ResultType

Type of the @Result attribute

N

T4

QualificationMark

O

CC @QualificationMark

The code which gives an indication on the qualification of the competitor for the next round of the competition

N

T4

SortOrder

M

Numeric

Used to sort all cumulative results, based on rank, but to break rank ties, etc. It is mainly used for display purposes.

N

T4

 

Result /ResultItems /ResultItem

Identifier of either phase or unit, for the schedule item to which it is going to be included the result summary. ResultItem /Result will be for either one particular previous phase -identified by @Phase- or unit (if @Unit is also informed or just phase otherwise.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Phase

M

See table comment

Phase code of the latest RSC schedule item (either phase or unit) to which the cumulative results is updated to.

N

Only if necessary

 

Result /ResultItems /ResultItem /Result

For any Event Unit Results message, there should be at least one competitor being awarded a result for the event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

SortOrder

M

Numeric

See table comment

Used to sort all results in an event unit or phase identified by /ResultItems /ResultItem

N

Only if necessary

 

Result /Competitor

Competitor related to one cumulative result.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Or Organisation code in the case of NOC or NPC

Competitor’s ID

N

Only if necessary

Type

M

T,A, N

T for team

A for athlete

N for NOC or NPC

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, corresponding to either a team member or a single athlete

N

Only if necessary

Order

M

Numeric

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

N

Only if necessary

 

 

3.2.5.6  Message Sort

The message sorting order is the same as that explained in the Event Unit / Phase Results messages.


 

 

3.2.6    Pool Standings

3.2.6.1  Description

The pool standings message contains the standings of a group in a competition. This message is triggered after each event unit and will be at phase level.

 

 

3.2.6.2  Header Values

3.2.6.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEP00

Message at the phase level.

 

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

DocumentType

DT_POOL_STANDING

Pool Standings message

DocumentSubtype

Round Robin : 9

For Round Robin, the value will be 9.

ResultStatus

CC @ResultStatus

Status of the message

Version

1..V

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

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

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

Time

MillisTime

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

LogicalDate

Date

Logical Date of events that extends until next day.

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

 

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

 

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

 

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

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

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

 

 

3.2.6.3  Trigger and Frequency

3.2.6.3.1  PiT Triggers

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

•  INTERIM: After each game of the preliminaries is finished

 

•  OFFICIAL: After last game of the preliminaries

 

 


3.2.6.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

Rank