ODF General Messages Interface Document

Tokyo 2020 – Games of the XXXII Olympiad

Technology and Information Department

© International Olympic Committee

 

R-SOG-2020-GEN-V1.5

11 November 2019

License

The document accompanying this license and the information contained therein (the Document), whether in a paper or electronic format, is made available to you subject to the terms stated below. By using and/or copying all or part of the Document, you (the licensee) agree that you will comply with the following terms and conditions.

 

  1. You may, on a non-exclusive basis, use the Document only on the condition that you abide by the terms of this license. Subject to this condition and other terms and restrictions contained herein, the Document and the information contained therein may be used (i) to further develop the standards described in the Document for use in relation with the Olympic and Paralympic Games and/or (ii) to develop similar standards for other events than the Olympic and Paralympic Games (both (i) and (ii) are hereinafter designated as the Permitted Use, and works further developing these standards for the Olympic and Paralympic Games or developing similar standards for other events are hereinafter referred to as Derivative Works), and copies of the Document or of Derivative Works may be made and distributed for the purpose of the Permitted Use, PROVIDED THAT the COPYRIGHT and references to the IOC appearing in the Document and the TERMS OF THIS LICENSE are included on ALL such COPIES, and further PROVIDED THAT you do not charge any fee or any other monetary compensation for the distribution of the Document to others.  The copyright and other intellectual property rights in the Document remain vested in the IOC and the IOC remains entitled to assert his copyright or other intellectual property rights in the Document against any person or entity who does not comply with the terms of this License.

 

  1. A copy of any Derivative Work shall be provided to the IOC free of charge. Moreover, the IOC is granted a worldwide, perpetual, unrestricted, royalty-free non-exclusive license to use any Derivative Work for the further development of the standards made by or for the IOC in relation to the Olympic and Paralympic Games (these standards and the documents describing them are hereinafter referred to as Further Standards) and to make or have made all kinds of exploitation of the Further Standards, with the right to grant sub-licenses.

 

  1. Except if reproduced in the Document, the use of the name and trademarks of the IOC is strictly prohibited, including, without limitation, for advertising, publicity, or in relation to products or services and their names. Any use of the name or trademarks of the IOC, whether registered or not, shall require the specific written prior permission of the IOC.

 

  1. NO WARRANTY, EXPRESSED OR IMPLIED, IS MADE REGARDING THE ACCURACY, ADEQUACY, COMPLETENESS, RELIABILITY OR USEFULNESS OF ANY INFORMATION CONTAINED IN THE DOCUMENT. The Document and the information contained herein are provided on an "as is" basis. THE IOC DISCLAIMS ALL WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF NON-INFRINGEMENT OF PROPRIETARY RIGHTS, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL THE IOC BE LIABLE TO ANYONE FOR DAMAGES OF ANY KIND ARISING FROM OR RELATING TO YOUR ACQUISITION, USE, DUPLICATION, DISTRIBUTION, OR EXPLOITATION OF THE DOCUMENT OR ANY PORTION THEREOF, INCLUDING BUT NOT LIMITED TO, COMPENSATORY DAMAGES, LOST PROFITS, LOST DATA OR ANY FORM OF SPECIAL, INCIDENTAL, DIRECT, INDIRECT, CONSEQUENTIAL OR PUNITIVE DAMAGES, WHETHER BASED ON BREACH OF CONTRACT OR WARRANTY, TORT OR OTHERWISE. THE IOC FURTHER DISCLAIMS ANY LIABILITY FOR ANY DAMAGE CAUSED WHEN THE DOCUMENT IS USED IN A DERIVATIVE WORK. The IOC further disclaims any liability regarding the existence or inexistence of any intellectual property or other rights that might be claimed by third parties with respect to the implementation or use of the technology or information described in the Document.

 

The same conditions as those described in this Section shall apply mutatis mutandis to the license granted to the IOC on the Derivative Works in Section 2 above.

 

  1. This License is perpetual subject to your conformance to its terms and conditions. The IOC may terminate this License immediately upon your breach of any of its terms and, upon such termination you will cease all use, duplication, distribution, and/or exploitation in any manner of the Document.

 

  1. This License is governed by the laws of Switzerland. You agree that any disputes arising from or relating to this License will be resolved in the courts of Lausanne, Switzerland.

 

IF YOU DO NOT AGREE TO THESE TERMS YOU MUST CEASE ALL USE OF THE DOCUMENT NOW.

 

 

1 Introduction

1.1 This document

This document builds on the ODF Foundation Principles document to provide the details of the implementation of each message which forms part of ODF.

The ODF Foundation Principles should be read prior to reading this document.

1.2 Objective

The objective of this document is to provide a complete and formal definition of the ODF General Data Dictionary.

1.3 Main Audience

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

1.4 Glossary

The following abbreviations are used in this document.

 

Acronym

Description

Full RSC

Full 34 character results system code in the form:

DDDGEEEEEEEEEEEEEEEEEEPPPPUUUUUUUU

DDD according to CC @Discipline

G according to CC @DisciplineGender

EEEEEEEEEEEEEEEEEE according to CC @Event

PPPP according to CC @Phase

UUUUUUUU according to CC @Unit

IF

International Federation

IOC

International Olympic Committee

NOC

National Olympic Committee

ODF

Olympic Data Feed

RSC

Results System Codes

WNPA

World News Press Agencies

1.5 Related Documents

Document Reference

Document Title

Document Description

ODF/INT400

ODF General Principles Document

The document explains the environment and general principles for ODF.

ODF/COD404

ODF Common Codes

The document describes the ODF Common codes used across all  ODF documents.

ODF/COD405

ODF Sport Codes

The document describes the ODF Sport codes used across all ODF documents

ODF/COD406

ODF Header Values

The document details the header values which shows which RSCs are used in which messages.

2 Messages

2.1 Sport Messages

2.1.1 Competition schedule / Competition schedule update

2.1.1.1 Description

The Competition schedule is a bulk message provided for one discipline. As a general rule, it contains the complete schedule information for all event units needed to run a competition and excludes event units for activities such as unofficial training and press conferences.

 

This message contains the competition timetable for a complete discipline as well as status for each competition unit and is updated from OVR via the schedule update message.

 

All event units in codes which have the 'schedule' flag set to 'Y' are included in schedule messages regardless of status (those without status must be sent as UNSCHEDULED if the schedule flag is 'Y').

 

The arrival of the competition schedule message resets all the previous schedule information for one discipline.

 

The StartList component of the message is only included in the case that the Unit Type is one of HATH, HCOUP, HNOC or HTEAM and at least one of the competitors are known.

 

The Composition component (i.e. listing athletes) is only included in the case that the Unit Type is one of HATH or HCOUP.

 

For reference the applicable unit types (from common codes) are:

 

HATH Individual Head to Head units (e.g. ARC, BDM, TEN, SBD etc)

HCOUP Pairs/Couples Head to Head units (e.g. BDM, TEN etc)

HNOC NOC Head to Head units (e.g. ARC, ALP )

HTEAM Teams Head to Head units (e.g. BKB, VBV, HBL, CUR, IHO etc)

 

 

Managing when start times are not known.

 

In some disciplines the start time of each unit is not known and the unit are managed by order rather than time.

 

In these disciplines only the time of the first unit (or first unit per location) is known and distributed. In this case all units should be sent with the same start time and those following units flagged as HideStartDate (and finish). To be able to correctly order these units then the Order attribute is used (and must be sent from the venue).

 

To ensure there are no incorrectly ordered units then the start time must not be updated to the actual start time (there is an actual start time field to cater for this). For example:

 

Start Time  Display             Unit      HideStartDate   Location    Order

in message

12:00       12:00               Unit 1    N               Court 2     1

12:00       Match 2 Court 2     Unit 2    Y               Court 2     2

12:00       Match 3 Court 2     Unit 3    Y               Court 2     3

16:30       Not before 16:30    Unit 4    Y               Court 2     4

 

If the discipline requires some text describing the order then StartText is used. Typical uses include "Not before 17:00" or "SUN 29 - 2nd match on CC" or "Follows".

 

Advice for end users - how to sort event units and use DT_SCHEDULE:

- When displaying the schedule users must use the following sort order to display as intended:

1. By day (or filter by day)

2. By location if applicable (in a small number of sports, when EventOrder = LOC in Discipline codes)

3. By Time (regardless if HideStartDate="Y")

4. By Order

- The Order is sent for all units where HideStartDate="Y" or if special ordering is required else not sent. Start with 1 each new session each day

- End users should display StartText if HideStartDate="Y"

 

If a StartText value of "Not before hh:mm" is used then it is expected that the StartDate sent is the same hh:mm.

 

Competition schedule update:

 

Competition schedule update is an update message. It is not a complete schedule information message, but only the schedule data being modified.

 

The arrival of this message updates thes tovious schedule information for one particular event unit(s) or sessions(s), but does not notify any other change for the rest of the event units/sessions except for those contained in the message.

 

The key of the information updated is Unit @Code. Therefore, any new unit, deleted unit or updated unit will be identified by all this attribute.

 

It has to be understood that if one DT_SCHEDULE message arrives, then all previous DT_SCHEDULE_UPDATE messages should be discarded.

 

When message is sent from Competition Schedule application in advance of the Games the element ExtendedInfos/EntendedInfo will contain following information:

- Type=CS, Code=VERSION, the attribute Value will indicate the version details from the competition schedule application

- Type=CS, Code=STATUS the attribute Value will indicate the status details from the competition schedule application

2.1.1.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline level)

Full RSC at the discipline level

DocumentType

DT_SCHEDULE / DT_SCHEDULE_UPDATE

Competition schedule bulk / update

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

Refer to the ODF header definition

Time

Time

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. This is the same as the physical day except when the unit or message transmission extends after midnight.

 

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 message will all 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 day of the correction.

 

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

Source

SC @Source

Code indicating the system which generated the message.

2.1.1.3 Trigger and Frequency

The competition schedule will be sent as a bulk message (DocumentType="DT_SCHEDULE") when available before the Games and then sent multiple times until a date to be confirmed after which only update messages will be sent (DocumentType="DT_SCHEDULE_UPDATE") by OVR. There is no automatic triggering and this (DT_SCHEDULE) message must not be sent after the transfer of control to OVR.

 

The competition schedule update message should be triggered at any time there has been a competition schedule modification for any previously sent competition schedule bulk message or update message including the addition of start list details (H2H).

 

Generally start list details for H2H units should be sent immediately when officially known which should be as soon as possible after the preceding unit changes to official.

 

The triggers for status changes are described in each sport data dictionary where differences are needed.

 

If any text descriptions change in a message (as opposed to the code) then this message is not resent to correct previous messages however the new data is to be used in future messages.

2.1.1.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Level 9

Level 10

Competition (0,1)

 

Gen

 

Sport

 

Codes

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Session (0,N)

 

SessionCode

 

StartDate

 

EndDate

 

Leadin

 

Venue

 

VenueName

 

ModificationIndicator

 

SessionStatus

 

SessionType

 

Medal

 

SessionName (1,N)

 

Language

 

Value

 

Unit (0,N)

 

Code

 

PhaseType

 

UnitNum

 

ScheduleStatus

 

StartDate

 

HideStartDate

 

EndDate

 

HideEndDate

 

ActualStartDate

 

ActualEndDate

 

Order

 

Medal

 

Venue

 

Location

 

MediaAccess

 

SessionCode

 

ModificationIndicator

 

StartText  (0,N)

 

Language

 

Value

 

ItemName  (1,N)

 

Language

 

Value

 

ItemDescription (0,N)

 

Language

 

-

 

VenueDescription (1,1)

 

VenueName

 

LocationName

 

StartList  (0,1)

 

Start  (1,N)

 

StartOrder

 

SortOrder

 

PreviousWLT

 

PreviousUnit

 

Competitor (1,1)

 

Code

 

Type

 

Organisation

 

Bib

 

Description  (0,1)

 

TeamName

 

IFId

 

ExtendedDescription  (0,N)

 

Code

 

Pos

 

Type

 

Value

 

Composition  (0,1)

 

Athlete  (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription  (0,N)

 

Pos

 

Type

 

Code

 

Value

2.1.1.5 Message Values

 

Element: Competition (0,1)

Table Note: "Competition schedule" and "Competition schedule update" share the same message structure and message attributes, except for the two ModificationIndicator attributes, which are specific to the "Competition schedule update message".

Attribute

M/O

Value

Description

Gen

O

S(20)

Version of the General Data Dictionary applicable to the message

Sport

O

S(20)

Version of the Sport Data Dictionary applicable to the message

Codes

O

S(20)

Version of the Codes applicable to the message

 Sample (Sample)

<Competition Gen="SOG-2020-1.10" Sport="SOG-2020-DDD-1.10" Codes="SOG-2020-1.20" >

 

Element: Competition /ExtendedInfos /ExtendedInfo (1,N)

Attribute

M/O

Value

Description

Type

M

See sport specific definition

 

Code

M

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Competition /ExtendedInfos /ExtendedInfo /Extension (0,N)

Attribute

M/O

Value

Description

Code

M

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Competition /Session (0,N)

Attribute

M/O

Value

Description

SessionCode

M

S(10)

Code of the sports competition session which contains this event unit. Usually in the format DDD00. DDD is the discipline and 00 is the session number within the discipline. For example ARC02 for the second session in Archery.

StartDate

M

DateTime

Start date.

Example: 2006-02-26T10:00:00+01:00

 

EndDate

M

DateTime

End date.

Example: 2006-02-26T10:00:00+01:00

 

Leadin

O

m:ss

Amount of time from session start to first scheduled unit.

Venue

M

CC @VenueCode

Venue where the session takes place

VenueName

M

S(25)

Name of venue

ModificationIndicator

O

S(1)

Attribute is mandatory in the  DT_SCHEDULE_UPDATE message.

 

N = New or U = Update.

SessionStatus

O

CC @ScheduleStatus

Only use CANCELLED if applicable. All other sessions are assumed to be scheduled. There is no change to running or finished.

SessionType

O

CC @SessionType

Session type of the Session.

Medal

O

S(1)

Send Y if this session includes at least one unit where a medal (any type of medal) is to be decided.

Do not send if no such unit.

Intended for use in Beijing 2022.

 

Element: Competition /Session /SessionName (1,N)

Attribute

M/O

Value

Description

Language

M

CC @Language

Language of the Session Description

Value

M

S(40)

Name of the sports competition session

 Sample (Sample)

<Session Code="ATH01" StartDate="2016-08-12T10:00:00+01:00" EndDate="2016-08-

12T14:00:00+05:00" LeadIn="5:00" Venue="STA" VenueName="Olympic Stadium" >

     <SessionName Language="ENG" Value="Athletics Session 1" />

</Session>

<Session Code="ATH02" StartDate="2016-08-12T18:00:00+01:00" EndDate="2016-08-

12T21:00:00+05:00" LeadIn="5:00" Venue="STA" VenueName="Olympic Stadium" >

     <SessionName Language="ENG" Value="Athletics Session 2" />

</Session>

 

Element: Competition /Unit (0,N)

Attribute

M/O

Value

Description

Code

M

Full RSC for the unit

 

PhaseType

M

CC @PhaseType

Phase type for the unit

UnitNum

O

S(15)

 

Match / Game / Bout / Race Number or similar

ScheduleStatus

M

CC @ScheduleStatus

Unit Status

StartDate

O

DateTime

Start date. This attribute may not be sent when the @ScheduleStatus is UNSCHEDULED. For other statuses the StartDate is expected otherwise ordering is display is incorrert (including CANCELLED and POSTPONED.

 

This is the scheduled Start date and time and will not be updated when an event unit starts (updated only with RESCHEDULED status)

 

Where HideStartDate="Y" then this should be filled with the session start time or the start time of a group of units for all similar units and Order used for sorting. This method is not used in team sports where HideStartDate="Y" is only used temporarily to remove times.

 

Example: 2006-02-26T10:00:00+01:00

HideStartDate

O

S(1)

Send 'Y' if StartDate (scheduled start time) should not be displayed. It may be an estimate or 'fake' time.

Do not send if StartDate (scheduled start time) is to be displayed.

 

Start times of some units depend on the finalisation of previous event units and therefore there is no fixed start time in these cases this field is set to 'Y'.

 

When the flag is set to 'Y' then the time is used for sorting purposes but should not be displayed.

 

EndDate

O

DateTime

End date. This attribute may not be sent when the @ScheduleStatus is UNSCHEDULED, POSTPONED or CANCELLED.

 

Example:

2006-02-26T10:00:00+01:00

 

HideEndDate

O

S(1)

Send 'Y' if EndDate scheduled end time is not to be displayed.

 

Some event units have a scheduled end time well bounded, however, some event units in some circumstances have a scheduled end time not quite variable (example, some press conferences or tennis matches, etc.) in these cases this field is set to 'Y' and should not be displayed.

 

ActualStartDate

O

DateTime

This attribute is expected once the event unit has started.

Example: 2006-02-26T10:03:22+01:00

ActualEndDate

O

DateTime

This attribute is expected once the event unit has finished.

Example: 2006-02-26T12:43:51+01:00

Order

O

Numeric

###0

Order of the units when displayed. This field is considered in two situations:

 

1. If HideStartDate = 'Y' then send at least for all Units in an affected session though it is suggested to be sent for all units in a discipline where the concept is used in the discipline.

 

2. If some units start at the same time and a particular order of the units is expected.

 

It is generally recommended to start at 1 in each session each day though may be ordered independently by location starting at 1 for each location in each session (where the schedule is ordered by location) or using other numbers to ensure the order of two using starting at the same time are displayed in the

appropriate order.

Medal

O

SC @UnitMedalType

Indicator of medal awarded for this unit.

Venue

O

CC @VenueCode

Venue where the unit takes place

Mandatory unless UNSCHEDULED

Can use TBD if the Venue is not known yet (see CC).

Location

O

CC @Location

Location where the unit takes place.

Mandatory unless UNSCHEDULED.

Can use TBD if the Location is not known yet or a generic code for the discipline (see CC).

MediaAccess

O

S(6)

Only applicable for non-competition.

If unit is open to media send "Open", if the unit is closed then send "Closed".

SessionCode

O

S(10)

Code of the sports competition session which contains this event unit. Usually in the format DDD00. DDD is the discipline and 00 is the session number within the discipline. For example ARC02 for the second session in Archery.

If a unit finishes in a different session (due to interuption) from the starting one then the SessionCode remains the starting code.

ModificationIndicator

O

N, U

Attribute is mandatory in the  DT_SCHEDULE_UPDATE message only

 

N-New event unit

U-Update event unit

If ModificationIndicator='N', then include new event unit. It will be rarely used as most added units were available in "UNSCHEDULED" status.

 

If ModificationIndicator="U", then update the event unit.

 

 

 

Element: Competition /Unit /StartText  (0,N)

This element is only used for Competition Schedules when HideStartDate is 'Y'. In this case, English Language is mandatory.

Attribute

M/O

Value

Description

Language

M

CC @Language

Code Language of the @Value

Value

M

S(20)

or a code set to be defined discipline by discipline

Text to be displayed in the case that StartDate is not to be displayed (e.g. "After M.1" or "Followed by")

Using a code set or fixed text will also be directly displayed and allow end user translation.

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Competition /Unit /ItemName  (1,N)

Attribute

M/O

Value

Description

Language

M

CC @Language

Code Language of the @Value

Value

M

S(40)

Item Name / Unit Description.

 

For competition units show the short unit description from common codes which matches the RSC. As in all messages with

a description only the ENG description is expected.

 

For non-competition schedules (where the item description is not in common codes) then add the description.

 

 

Element: Competition /Unit /ItemDescription (0,N)

Attribute

M/O

Value

Description

Language

M

CC @Language

Code Language of the @Value

-

M

Free Text

Item Description for non-competition schedule

 

Element: Competition /Unit /VenueDescription (1,1)

Attribute

M/O

Value

Description

VenueName

M

S(25)

Venue name in first language. This is the CC value from unit/venue

LocationName

M

S(30)

Location name in first language. This is the CC value from unit/location.

 

Element: Competition /Unit /StartList  /Start  (1,N)

StartList information is only sent in the case that the Unit type is one of HATH, HCOUP, HNOC or HTEAM and at least one of the competitors are known. (Sent as soon as known for applicable units)

Attribute

M/O

Value

Description

StartOrder

O

Numeric

Competitor's start order

SortOrder

M

Numeric

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

PreviousWLT

O

S(1)

W or L for winner of loser of a particular previous unit plays in this unit. This attribute is only filled if the competitors are 100% confirmed as participating at this time and not subject to change depending on TV times etc. Further, the data is removed when the real teams are known.

PreviousUnit

O

S(34)

The full RSC of the unit where this competitor came from. This attribute is only filled if the competitors are 100% confirmed as participating at this time and not subject to change depending on TV times etc. Further, the data is removed when the real teams are known.

 

Element: Competition /Unit /StartList  /Start  /Competitor (1,1)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes,

TBD or NOCOMP.

 

Competitor's ID, TBD in case that the competitor is not known at this time AND the other competitor is known. NOCOMP is sent when  there is no competitor (and will not come later)

Type

M

S(1)

T for team

A for athlete

 

Organisation

O

CC @Organisation

Should be sent when known

Bib

O

Same as in the Start List message for each discipline

Team bib number (if Competitor @Type="T")

 

Element: Competition /Unit /StartList  /Start  /Competitor /Description  (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Team Name where known, must send when available

IFId

O

S(16)

Team IF number, send if available

 

Element: Competition /Unit /StartList  /Start  /Competitor /Description  /ExtendedDescription  (0,N)

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Type

M

See sport specific definition

 

 

Value

O

See sport specific definition

 

 

Element: Competition /Unit /StartList  /Start  /Competitor /Composition  /Athlete  (1,N)

Only send in the case that the Unit type is one of HATH (AR, BD, TE etc) or HCOUP (BD, TE etc),

In case of the Competitor @Code='TBD' the Competitor element should not be sent.

 

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete's ID, corresponding to either a team member or an individual athlete in the event unit.

Order

M

Numeric

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

Bib

O

Same as in the Start List message for each discipline

Individual athlete's bib number (if Competitor @Type="A") or team member's bib number (if Competitor @Type="T").

 

Element: Competition /Unit /StartList  /Start  /Competitor /Composition  /Athlete  /Description (1,1)

Attribute

M/O

Value

Description

GivenName

O

S(25)

Given name in WNPA format (mixed case). Send if not null.

FamilyName

M

S(25)

Family name in WNPA format (mixed case)

Gender

M

CC @PersonGender

Participant's gender

Organisation

M

CC @Organisation

Organisation ID

BirthDate

O

YYYY-MM-DD

Date of birth.

IFId

O

S(16)

Athlete IF number, send if available, only for the current discipline.

Class

O

CC @SportClass

Code to identify the sport class in the case of events with athletes with a disability (e.g: Paralympic Games).

 

This attribute is optional because it is not used in events without such athletes.

 

Horse

O

S(25)

Name of the athlete's horse

GuideID

O

S(20) without leading zeros

ID of the Guide, used for some athletes with a disability (e.g: Paralympic Games).

GuideFamilyName

O

S(25)

Family Name of the athlete's guide (mixed case).

Used for some athletes with a disability (e.g: Paralympic Games).

 

GuideGivenName

O

S(25)

Given Name of the athlete's guide (mixed case).

Used for some athletes with a disability (e.g: Paralympic Games).

 

 

Element: Competition /Unit /StartList  /Start  /Competitor /Composition  /Athlete  /Description /ExtendedDescription  (0,N)

Attribute

M/O

Value

Description

Pos

O

See sport specific definition

 

Type

M

See sport specific definition

 

Code

M

See sport specific definition

 

Value

O

See sport specific definition

 

 Sample (Team Head to Head)

<Unit Code="BKBMTEAM5-------------GPA-0001----" PhaseType="3" UnitNum="11"

ScheduleStatus="SCHEDULED" StartDate="2016-08-12T15:00:00+05:00" EndDate="2016-08-

12T17:00:00+05:00" Medal="1" Venue="NGA" Location="BK2" SessionCode="BKB01" >

     <ItemName Language="ENG" Value="Men's Preliminary Round Pool A"/>

     <VenueDescription VenueName="Green Arena" LocationName="Green Arena"/>

     <StartList>

        <Start SortOrder="1" StartOrder="1">

           <Competitor Code="BKBMTEAM5---CZE01" Type="T" Organisation="CZE">

              <Description TeamName="Czech Republic" />

           </Competitor>

        </Start>

        <Start SortOrder="2" StartOrder="2">

           <Competitor Code="BKBMTEAM5---USA01" Type="T" Organisation="USA">

              <Description TeamName="United States" />

           </Competitor>

        </Start>

     </StartList>

</Unit>

 

 Sample (Individual Head to Head)

<Unit Code="TENMSINGLES-----------FNL-0001----" PhaseType="3" UnitNum="11"

ScheduleStatus="SCHEDULED" StartDate="2016-08-05T13:00:00+05:00" HideStartDate="Y"

EndDate="2016-08-05T13:30:00+05:00" HideEndDate="Y" Medal="1" Venue="WEM" Location="TE0"

SessionCode="TEN12" >

     <StartText Language="ENG" Value="followed by"/>

     <ItemName Language="ENG" Value="Men's Singles Gold Medal Match"/>

     <VenueDescription VenueName="Wimbledon" LocationName="Centre Court"/>

     <StartList>

        <Start SortOrder="1" StartOrder="1">

           <Competitor Code="1051631" Type="A" Organisation="BLR">

              <Composition>

                 <Athlete Code="1051631" Order="1">

                    <Description GivenName="Barry" FamilyName="Smith" Gender="M" Organisation="BLR" BirthDate="1983-07-23" IFId="397806" />

                 </Athlete>

              </Composition>

           </Competitor>

        </Start>

        <Start SortOrder="2" StartOrder="2">

           <Competitor Code="1131104" Type="A" Organisation="USA">

              <Composition>

                 <Athlete Code="1131104" Order="1">

                    <Description GivenName="Bobby" FamilyName="Jones" Gender="M" Organisation="USA" BirthDate="1969-10-23" IFId="573006" />

                 </Athlete>

              </Composition>

           </Competitor>

        </Start>

     </StartList>

</Unit>

 Sample (Non Head to Head)

<Unit Code="ATHM100M---------------FNL-0001----" PhaseType="3"

ScheduleStatus="SCHEDULED" StartDate="2016-08-12T15:00:00+05:00" EndDate="2016-08-

12T17:00:00+05:00" Medal="1" Venue="NGA" Location="BK2" SessionCode="ATH12" >

     <ItemName Language="ENG" Value="Men's 100m Final"/>

     <VenueDescription VenueName="Olympic Stadium" LocationName="Olympic Stadium"/>

</Unit>

2.1.1.6 Message Sort

Sort by Session @SessionCode.

 

The message is sorted by Unit@StartDate then by Unit@Order then Unit@Code.

In case of event unit with no Unit@StartDate defined (example, they are in an event unit status such as UNSCHEDULED), they will be listed at the end in Unit@Code order.

 

2.1.2 List of participants by discipline / List of participants by discipline update

2.1.2.1 Description

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

 

Although the participant may participate in more than one event or more than one discipline, this message just contains the information for the discipline of the message, 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 note that all the sport messages that make references to athletes (event unit start list and results, phase results, medallists etc.) will always match the athlete ID with the athlete ID in this message. The historical athletes will be used to match historical athlete information as it appears 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.

 

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 includes a list of current athletes, officials, coaches, guides, technical officials, reserves and historical athletes regardless of their status.

 

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

2.1.2.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline level)

Full RSC at the discipline level

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

Time

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. This is the same as the physical day except when the unit or message transmission extends after midnight.

 

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 message will all 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 day of the correction.

 

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

Source

SC @Source

Code indicating the system which generated the message.

2.1.2.3 Trigger and Frequency

The DT_PARTIC message is sent as a bulk message prior to the Games. It is sent several times up to the date of transfer of control to OVR after which only DT_PARTIC_UPDATE messages are sent.

 

The DT_PARTIC_UPDATE message is triggered when there is a modification in the data for any individual after the transfer of control to OVR.

2.1.2.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition (0,1)

 

Gen

 

Sport

 

Codes

 

Participant (1,N)

 

Code

 

Parent

 

Status

 

GivenName

 

FamilyName

 

PassportGivenName

 

PassportFamilyName

 

PrintName

 

PrintInitialName

 

TVName

 

TVInitialName

 

TVFamilyName

 

LocalFamilyName

 

LocalGivenName

 

Gender

 

Organisation

 

BirthDate

 

Height

 

Weight

 

PlaceofBirth

 

CountryofBirth

 

PlaceofResidence

 

CountryofResidence

 

Nationality

 

MainFunctionId

 

Current

 

OlympicSolidarity

 

ModificationIndicator

 

Discipline (1,1)

 

Code

 

IFId

 

DisciplineEntry (0,N)

 

Code

 

Type

 

Pos

 

Value

 

RegisteredEvent (0,N)

 

Event

 

Bib

 

Class

 

Substitute

 

Status

 

EventEntry (0,N)

 

Code

 

Type

 

Pos

 

Value

 

OfficialFunction (0,N)

 

FunctionId

2.1.2.5 Message Values

 

Element: Competition (0,1)

Attribute

M/O

Value

Description

Gen

O

S(20)

Version of the General Data Dictionary applicable to the message

Sport

O

S(20)

Version of the Sport Data Dictionary applicable to the message

Codes

O

S(20)

Version of the Codes applicable to the message

 Sample (Versions)

<Competition Gen="SOG-2020-1.10" Sport="SOG-2020-DDD-1.10" Codes="SOG-2020-1.20" >

 

Element: Participant (1,N)

Attribute

M/O

Value

Description

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 @ParticStatus

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)

PassportGivenName

O

S(25)

Passport Given Name (Uppercase).

PassportFamilyName

O

S(25)

Passport Family Name (Uppercase).

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

TVFamilyName

M

S(25)

TV family name

LocalFamilyName

O

S(25)

Family name in the local language in the appropriate case for the local language (usually mixed case)

LocalGivenName

O

S(25)

Given name in the local language in the appropriate case for the local language (usually mixed case)

Gender

M

CC @PersonGender

Participant's gender

Organisation

M

CC @Organisation

Organisation ID

BirthDate

O

YYYY-MM-DD

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

S(3)

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

"-" may be used where the data is not available.

Weight

O

S(3)

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

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

"-" may be used where the data is not available.

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 @ResultsFunction

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

S(1)

Send Y if the participant is a member of the Solidarity / Scholarship Program else not sent.

ModificationIndicator

M

S(1)

'N' or '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.

 

Element: Participant /Discipline (1,1)

All participating athletes will be assigned at least one discipline, it could be more. Each 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

Description

Code

M

CC @Discipline

Full RSC of the Discipline

IFId

O

S(16)

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

 

Element: Participant /Discipline /DisciplineEntry (0,N)

Send if there is specific discipline information.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Type

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Participant /Discipline /RegisteredEvent (0,N)

All accredited athletes 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 registered to any event.

Attribute

M/O

Value

Description

Event

M

CC @Event

Full RSC of the Event

Bib

O

See table comment

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

Code to identify the handicap class in the case of events with handicapped athletes (e.g: paralympic games).

 

This attribute is optional because is not used in other type of events without handicapped athletes.

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

Substitute

O

See table comment

Substitute information. By default send "Y" if substitute else do not send but can vary by discipline.

Status

O

See table comment

Participant status in the event

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Participant /Discipline /RegisteredEvent /EventEntry (0,N)

Send if there are specific athlete's event entries.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Type

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Participant /OfficialFunction (0,N)

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

Attribute

M/O

Value

Description

FunctionId

M

CC @ResultsFunction

Additional officials' function code

2.1.2.6 Message Sort

The message is sorted by Participant @Code

 

2.1.3 List of teams / List of teams update

2.1.3.1 Description

The List of teams message 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 data of a team being modified.

2.1.3.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline level)

Full RSC at the discipline level

DocumentType

DT_PARTIC_TEAMS / DT_PARTIC_TEAMS_UPDATE

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

Time

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. This is the same as the physical day except when the unit or message transmission extends after midnight.

 

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 message will all 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 day of the correction.

 

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

Source

SC @Source

Code indicating the system which generated the message.

2.1.3.3 Trigger and Frequency

The DT_PARTIC_TEAMS message is sent as a bulk message before the Games. It is sent several times up to the date of transfer of control to OVR after which only DT_PARTIC_TEAMS_UPDATE messages are sent.

 

The DT_PARTIC_TEAMS_UPDATE message is triggered when there is a modification in the data for any team after the transfer of control to OVR.

2.1.3.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Competition (0,1)

 

Gen

 

Sport

 

Codes

 

Team (1,N)

 

Code

 

Organisation

 

Number

 

Name

 

TVTeamName

 

Gender

 

Current

 

ModificationIndicator

 

Composition (0,1)

 

Athlete (0,N)

 

Code

 

Order

 

Team (0,N)

 

Code

 

Number

 

Name

 

Gender

 

IFId

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

RegisteredEvent (0,1)

 

Event

 

EventEntry (0,N)

 

Code

 

Pos

 

Type

 

Value

 

TeamOfficials (0,1)

 

Official (1,N)

 

Code

 

Function

 

Order

 

Discipline (0,1)

 

Code

 

IFId

 

RegisteredEvent (0,1)

 

Event

 

Bib

 

Substitute

 

Status

 

EventEntry (0,N)

 

Code

 

Type

 

Pos

 

Value

2.1.3.5 Message Values

 

Element: Competition (0,1)

Attribute

M/O

Value

Description

Gen

O

S(20)

Version of the General Data Dictionary applicable to the message

Sport

O

S(20)

Version of the Sport Data Dictionary applicable to the message

Codes

O

S(20)

Version of the Codes applicable to the message

 

Element: Team (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Team's ID (example ATHM4X400M--ESP01, 393553)

 

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

Organisation

M

CC @Organisation

Team organisation's ID

Number

O

Numeric

#0

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

S(73)

Team name.

 

If there is no rule for the discipline then send the Description of the code CC@Organisation.

TVTeamName

M

S(21)

Team's TV Name.

In events with teams of two this should be in the format JONES/SMITH [max char(10) per name] else it is the organisation name unless a special rule applies for the discipline.

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

 

Element: Team /Composition /Athlete (0,N)

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

Attribute

M/O

Value

Description

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

 

Element: Team /Composition /Team (0,N)

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

Attribute

M/O

Value

Description

Code

M

S(20) with no leading

zeroes

Team's ID (example ATHM4X400m--ESP01, 393553)

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

Number

M

Numeric

#0

Team's number.

Incremental number for each team within the team.

Name

O

S(73)

see table comment

Team's name.

It will apply to some of the disciplines. If there is not any special

rule for that discipline, send the Description of the code

CC@Organisation.

Gender

M

CC @DisciplineGender

Discipline Gender Code of the Team

IFId

O

S(16)

Federation number for the corresponding discipline (include if the

discipline assigns international federation codes to teams)

 

Element: Team /Composition /Team /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

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

Therefore, he/she is part of the team's composition.

Order

O

Numeric

Team member order

 

Element: Team /Composition /Team /RegisteredEvent (0,1)

Each current team is assigned to one event. Historical teams will not be registered to any event.

Attribute

M/O

Value

Description

Event

M

CC @Unit

Full RSC of the subevent

 

Element: Team /Composition /Team /RegisteredEvent /EventEntry (0,N)

Send if there are specific team's event entries.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Type

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Team /TeamOfficials /Official (1,N)

Send if there are specific officials for the team. Does not apply to historical teams.

Attribute

M/O

Value

Description

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.

Function

M

CC @ResultsFunction

Official's function for the team.

Order

O

Numeric

#0

Official's order in the team.

 

Element: Team /Discipline (0,1)

Each team is assigned just to one discipline. Discipline is expected unless ModificationIndicator="D"

Attribute

M/O

Value

Description

Code

M

CC @Discipline

Full RSC of the Discipline

IFId

O

S(16)

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

 

Element: Team /Discipline /RegisteredEvent (0,1)

Each current team is assigned to one event. Historical teams will not be registered to any event.

Attribute

M/O

Value

Description

Event

M

CC @Event

Full RSC of the Event

Bib

O

See table comment

Bib number.

Substitute

O

See table comment

Substitute information. By default send "Y" if substitute else do not send but can vary by discipline.

Status

O

See table comment

Team status in the event

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Team /Discipline /RegisteredEvent /EventEntry (0,N)

Send if there are specific team's event entries.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Type

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.3.6 Message Sort

The message is sorted by Team @Code.

 

2.1.4 List of horses / List of horses update

2.1.4.1 Description

The List of horses is a bulk message containing a complete list of horses and provided only for equestrian (not for the horses in modern pentathlon). The arrival of this message resets all the previous equestrian horses' information.

 

List of horses update (DT_PARTIC_HORSES_UPDATE) is not a complete list, it only contains the data that has been modified and it is available for both equestrian and modern pentathlon.

 

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

2.1.4.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline level)

Full RSC at the discipline level

DocumentType

DT_PARTIC_HORSES_UPDATE / DT_PARTIC_HORSES

List of horses 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

Time

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. This is the same as the physical day except when the unit or message transmission extends after midnight.

 

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 message will all 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 day of the correction.

 

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

Source

SC @Source

Code indicating the system which generated the message.

2.1.4.3 Trigger and Frequency

The DT_PARTIC_HORSES message is sent as a bulk message approximately one month before the Games. It is sent several times up to the date of transfer of control to OVR after which only DT_PARTIC_HORSES_UPDATE messages are sent.

 

The DT_PARTIC_HORSES_UPDATE message is triggered when there is a modification in the data for any horse after the transfer of control to OVR.

2.1.4.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Competition (0,1)

 

Gen

 

Sport

 

Codes

 

Horse (1,N)

 

Code

 

Name

 

Organisation

 

Sex

 

YearBirth

 

Passport

 

ColourCode

 

BreedCode

 

Sire

 

Owner

 

SecondOwner

 

Groom

 

ModificationIndicator

 

Entry (0,N)

 

Type

 

Code

 

Pos

 

Value

2.1.4.5 Message Values

 

Element: Competition (0,1)

Attribute

M/O

Value

Description

Gen

O

S(20)

Version of the General Data Dictionary applicable to the message

Sport

O

S(20)

Version of the Sport Data Dictionary applicable to the message

Codes

O

S(20)

Version of the Codes applicable to the message

 

Element: Horse (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Horse's ID

Name

M

S(25)

Horse's name in upper case.

Organisation

O

CC @Organisation

Horse's organisation. It's mandatory except for the message List of Horses Update of Modern Pentathlon.

Sex

O

CC @HorseSex

Horse's sex. Send when information is available

YearBirth

O

Numeric

####

Horse's year of birth. Send when information is available

Passport

O

S(12)

Horse's passport. Send if the information is available

ColourCode

O

CC @HorseColour

Horse's colour code. Send when information is available

BreedCode

O

CC @HorseBreed

Horse's breed code. Send when information is available

Sire

O

S(25)

Horse's sire. Send when information is available.

 

The content is expected in upper case.

Owner

O

S(35)

Horse's primary (first) owner. Send when information is available.

 

The content is expected in upper case.

SecondOwner

O

S(35)

Horse's secondary owner. Send when available.

 

The content is expected in upper case.

Groom

O

S(35)

Horse's groom. Send when information is available.

 

The content is expected in upper case.

ModificationIndicator

M

N, U, D

Attribute is mandatory in the DT_PARTIC_HORSES_UPDATE message only

 

N - New horse (any horse but particularly for modern pentathlon when it is sent the first time)

U - Update horse

D - Delete horse

 

If ModificationIndicator='N', then adds the new horse to the previous bulk-loaded list of horses

 

If ModificationIndicator='U', then updates the horse information to the existing one

 

If ModificationIndicator='D', then deletes the horse

 

Element: Horse /Entry (0,N)

Only when there are entries  specific for the horse.

Attribute

M/O

Value

Description

Type

O

See sport specific definition

 

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.4.6 Message Sort

The message will be sorted by Horse @Code

 

2.1.5 Event Unit Start List and Results

2.1.5.1 Description

The Event Unit Start List and Results is a message containing both the start list and results information of the competitors in one (individual or team) event unit.

 

The Event Unit Start List and 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...).

 

This is always a full message and all applicable elements and attributes are always sent.

2.1.5.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

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

DocumentSubcode

To be defined in each ODF Data Dictionary

Provides greater granularity for document if DocumentCode is not sufficient.

DocumentType

DT_RESULT

Event Unit Start List and Results message

DocumentSubtype

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType for some messages.

Optional attribute only for special cases in result messages.

Version

1..V

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

ResultStatus

SC @ResultStatus

It indicates whether the result is official or unofficial (or intermediate etc).

START_LIST

OFFICIAL

UNOFFICIAL

PARTIAL (used after competition is started and is not finished, but some

results are already known and will not change, other results are missing

due to athletes still competing)

INTERMEDIATE (used after the competition has started and is not finished but not currently live)

LIVE (used during the competition when nothing else applies).

UNCONFIRMED (used after the competition is completed and before either UNOFFICIAL or OFFICIAL. It may be sent multiple times if modifications are required and the status has not changed)

 

Note: For the use of UNCONFIRMED / UNOFFICIAL / OFFICIAL there will be variations defined in the sport data dictionaries as some statuses may not apply in some sports.

PROTESTED

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

Time

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. This is the same as the physical day except when the unit or message transmission extends after midnight.

 

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 message will all 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 day of the correction.

 

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

Source

SC @Source

Code indicating the system which generated the message.

2.1.5.3 Trigger and Frequency

This message is sent with ResultStatus 'START_LIST' as soon as the expected information is available and any changes to the information. Possible information is:

 

* Event Unit related information like ExtendedInfos and Officials

* Event Unit competitors

* Addition of IRMs prior to the start of the unit

 

This message is then sent with ResultStatus 'LIVE' as soon as the unit starts and continues to be triggered on all updates. The message is also sent with ResultStatus 'UNCONFIRMED' when the competition finishes. In relation to the above mentioned ResultStatuses, the following generic rules apply:

 

* Use UNCONFIRMED when the action in FOP is finished but still some data need to be entered or photo finish needs to be evaluated or UNOFFICIAL/OFFICIAL cannot be used for some other specific reason;

* Use UNOFFICIAL once all data has been captured or this status has a particular meaning in a sport;

* Use OFFICIAL as soon as results are approved by the competition authority

 

* The purpose of UNCONFIRMED is to send out results as soon as competition is over without any delay due to competition procedures

* The purpose of UNOFFICIAL is to notify that all results have been captured but approval is still pending. Use of UNOFFICIAL should be minimised. New version of UNOFFICIAL results should be expected in case of disqualification or any sanction which is the outcome of detailed review against competition rules

* The purpose of OFFICIAL is to notify that results data has been validated by competition authorities. A new version of OFFICIAL results should be expected in case of corrections of results data after official approval due to any reason.

 

This message also must be triggered immediately after a DT_CONFIG message is sent for the same unit if a DT_RESULT was previously distributed.

 

This message is also sent when the event unit finishes and the results are still unofficial. Also, this message is expected when the results become official. The official/unofficial status is included in the ODF headers (ResultStatus attribute). The message is sent as 'INTERMEDIATE' during extended breaks (including unplanned due to weather conditions etc).

 

Trigger also after any change.

 

If there is any kind of sport specific rule, this can be overwritten in the corresponding ODF Sport Data Dictionaries.

2.1.5.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Level 9

Level 10

Level 11

Competition (0,1)

 

Gen

 

Sport

 

Codes

 

ExtendedInfos (0,1)

 

UnitDateTime (0,1)

 

StartDate

 

EndDate

 

Duration

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Competitor (0,N)

 

Organisation

 

Order

 

Composition (0,1)

 

Athlete (1,N)

 

FamilyName

 

GivenName

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

Gender

 

SubEventName

 

UnitNum

 

VenueDescription  (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Attendance

 

PreviousResults  (0,N)

 

Code

 

Win

 

Loss

 

Tie

 

PreviousResult  (0,N)

 

Unit

 

Order

 

Opponent

 

WLT

 

Result

 

OppResult

 

ResultType

 

IRM

 

ExtendedResults  (0,1)

 

ExtendedResult (1,N)

 

Code

 

Pos

 

Type

 

Value

 

Extension (0,N)

 

Pos

 

Code

 

Value

 

Partial (0,N)

 

Code

 

Score

 

OppScore

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Attempt

 

Avg

 

Percent

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

 

Officials (0,1)

 

Official (1,N)

 

Code

 

Function

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtOfficial (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Periods (0,1)

 

Home

 

Away

 

Period (1,N)

 

Code

 

HomeScore

 

AwayScore

 

HomePeriodScore

 

AwayPeriodScore

 

Duration

 

ExtendedPeriods (0,1)

 

ExtendedPeriod (1,N)

 

Code

 

Type

 

Pos

 

Value

 

Result (1,N)

 

Rank

 

RankEqual

 

Result

 

Unchecked

 

IRM

 

QualificationMark

 

WLT

 

SortOrder

 

StartOrder

 

StartSortOrder

 

ResultType

 

Diff

 

Pty

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Value2

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Pty

 

Discard

 

Arrive

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

RecordIndicators (0,1)

 

RecordIndicator (1,N)

 

Order

 

Code

 

RecordType

 

Equalled

 

ResultItems (0,1)

 

ResultItem (1,N)

 

Unit

 

Order

 

Result (1,1)

 

Rank

 

RankEqual

 

ResultType

 

Unchecked

 

Result

 

ResultPoints

 

IRM

 

QualificationMark

 

Diff

 

WLT

 

SortOrder

 

StartOrder

 

StartSortOrder

 

Pty

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Value2

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Pty

 

Discard

 

Arrive

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

RecordIndicators (0,1)

 

RecordIndicator (1,N)

 

Order

 

Code

 

RecordType

 

Equalled

 

Competitor (1,1)

 

Code

 

Type

 

Bib

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Coaches (0,1)

 

Coach (1,N)

 

Code

 

Order

 

Function

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Nationality

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtCoach (0,N)

 

Type

 

Code

 

Pos

 

Value

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Attempt

 

Avg

 

Percent

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (0,N)

 

Code

 

Order

 

StartOrder

 

StartSortOrder

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Value2

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Pty

 

Discard

 

Arrive

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Attempt

 

Avg

 

Percent

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

 

Team (0,N)

 

Code

 

Order

 

Bib

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Value2

 

Valuetype

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Pty

 

Discard

 

Arrive

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

StartOrder

 

StartSortOrder

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Value2

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Pty

 

Discard

 

Arrive

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

2.1.5.5 Message Values

 

Element: Competition (0,1)

Attribute

M/O

Value

Description

Gen

O

S(20)

Version of the General Data Dictionary applicable to the message

Sport

O

S(20)

Version of the Sport Data Dictionary applicable to the message

Codes

O

S(20)

Version of the Codes applicable to the message

 Sample (Versions)

<Competition Gen="SOG-2020-1.10" Sport="SOG-2020-DDD-1.10" Codes="SOG-2020-1.20" >

 

Element: ExtendedInfos /UnitDateTime (0,1)

Actual start date and time / end date and time. (do not include until unit starts)

Attribute

M/O

Value

Description

StartDate

O

DateTime

Actual start date and time. For multi-day units, the start time is on the first day. (do not include until unit has started)

EndDate

O

DateTime

Actual end date-time (The attribute should only be included when required in the particular sport). Generally do not include.

Duration

O

h:mm

Duration of the unit as defined in the sport.

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: ExtendedInfos /ExtendedInfo (0,N)

Attribute

M/O

Value

Description

Type

O

See sport specific definition

 

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: ExtendedInfos /ExtendedInfo /Extension (0,N)

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: ExtendedInfos /ExtendedInfo /Competitor (0,N)

Used for forerunners and similar who do not participate in the competition. Not usually part of DT_PARTIC.

Attribute

M/O

Value

Description

Organisation

O

CC @Organisation

Organisations ID

Order

O

Numeric

Order of the competitor associated to the ExtendedInfo, if more than one competitor associated. Send 1 if only one.

 

Element: ExtendedInfos /ExtendedInfo /Competitor /Composition /Athlete (1,N)

Used when the ExtendedInfo is related to a person or a team member.

 

 

The FamilyName and GivenName because, in many cases, the person related to the ExtendedInfo is not an athlete.

Attribute

M/O

Value

Description

FamilyName

M

S(25)

Family name of the person associated to the ExtendedInfo.

 

 

This person may not be appearing in the List of athletes by discipline message. For this reason a @Code attribute is not possible.

GivenName

O

S(25)

 

 

See table comment

Given name of the person associated to the ExtendedInfo

 

 

This person may not be appearing in the List of athletes by discipline message. For this reason a @Code attribute is not possible.

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: ExtendedInfos /SportDescription (0,1)

Sport Descriptions in Text.

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name (not code) from Common Codes

EventName

M

S(40)

Event name (not code) from Common Codes

Gender

M

CC @DisciplineGender

Gender code for the event unit

SubEventName

O

S(40)

EventUnit short name (not code) from Common Codes

UnitNum

O

S(15)

Match / Game / Bout / Race  Number or similar if applicable

 

Element: ExtendedInfos /VenueDescription (0,1)

Venue Names in Text.

Attribute

M/O

Value

Description

Venue

M

CC @VenueCode

Venue Code

VenueName

M

S(25)

Venue short name (not code) from Common Codes

Location

M

CC @Location

Location code

LocationName

M

S(30)

Location short name (not code) from Common Codes

Attendance

O

#####0

Total attendance (do not send if unknown)

 

Element: ExtendedInfos /PreviousResults  (0,N)

PreviousResults is normally only added to the message after all previous units for the competitors involved are complete.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Win

O

See sport specific definition

Number of matches won

Loss

O

See sport specific definition

Number of matches lost

Tie

O

See sport specific definition

Number of matches tied

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: ExtendedInfos /PreviousResults  /PreviousResult  (0,N)

Attribute

M/O

Value

Description

Unit

O

S(40)

Full RSC of the previous event unit. Must always send unless it does not exist (like for a bye)

Order

M

Numeric

#0

Order of the units. This will be chronological with the most recent at the bottom.

Opponent

O

S(20) with no leading zeroes or BYE

Competitor ID of the opponent or in the case of a bye send BYE

WLT

O

S(1)

Indicates if the competitor at PreviousResults/Code is the winner (W), loser (L) or tied (T)

Result

O

See sport specific definition

 

OppResult

O

See sport specific definition

 

ResultType

O

See sport specific definition

 

IRM

O

See sport specific definition

 

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: ExtendedInfos /PreviousResults  /PreviousResult  /ExtendedResults  /ExtendedResult (1,N)

Attribute

M/O

Value

Description

Code

M

See sport specific definition

 

Pos

O

See sport specific definition

 

Type

M

See sport specific definition

 

Value

O

See sport specific definition

 

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: ExtendedInfos /PreviousResults  /PreviousResult  /ExtendedResults  /ExtendedResult /Extension (0,N)

Attribute

M/O

Value

Description

Pos

O

See sport specific definition

 

Code

M

See sport specific definition

 

Value

O

See sport specific definition

 

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 Sample (Tennis)

<PreviousResults Code="123456" Win="2" Loss="0">

   <PreviousResult Unit="TENWSINGLES-----------R64-0001----" Order="1" Opponent="2222" WLT="W" Result="2" OppResult="0">

      <Partial Code="S1" Score="6" OppScore="3" />

      <Partial Code="S2" Score="6" OppScore="2" /> </PreviousResult>

   <PreviousResult Unit="TENWSINGLES-----------R32-0002----" Order="2" Opponent="4444" WLT="W" Result="2" OppResult="1">

      <Partial Code="S1" Score="6" OppScore="3" />

      <Partial Code="S2" Score="3" OppScore="6" />

      <Partial Code="S3" Score="6" OppScore="0" />

</PreviousResult>

</PreviousResults>

 Sample (Ice Hockey)

<PreviousResults Code="IHOMTEAM6---USA01" Win="2" Loss="0">

   <PreviousResult Unit="IHOMTEAM6------------GPA-0001----" Order="1" Opponent="IHOMTEAM6---FRA01" WLT="W" Result="7" OppResult="2" />

   <PreviousResult Unit="IHOMTEAM6------------GPA-0004----" Order="2" Opponent="IHOMTEAM6---

NOR01" WLT="W" Result="2" OppResult="1" />

</PreviousResults>

 Sample (Basketball)

<PreviousResults Code="BKBWTEAM5---FRA01" Win="2" Loss="1">

   <PreviousResult Unit="BKBWTEAM5------------GPA-0001----" Order="1" Opponent="BKBWTEAM5---NZL01" WLT="W" Result="76" OppResult="76" />

   <PreviousResult Unit="BKBWTEAM5------------GPA-0004----" Order="2" Opponent="BKBWTEAM5---USA01" WLT="L" Result="75" OppResult="77" />

   <PreviousResult Unit="BKBWTEAM5------------GPA-0007----" Order="3" Opponent="BKBWTEAM5---RSA01" WLT="W" ResultType="IRM" IRM="DSQ" />

</PreviousResults>

 Sample (Wrestling)

<PreviousResults Code="123456" Win="2" Loss="0">

<PreviousResult Unit="WREW59K--------------R32-0001----" Order="1" Opponent="2222"

WLT="W" Result="5" OppResult="0"/>

<PreviousResult Unit="WREW59K--------------8FNL-0001----" Order="2" Opponent="4444"

WLT="W" Result="4" OppResult="0"/>

</PreviousResults>

 

Element: ExtendedInfos /PreviousResults  /PreviousResult  /Partial (0,N)

Attribute

M/O

Value

Description

Code

M

See sport specific redefinition

 

Score

O

See sport specific redefinition

Usually for the competitor in the period

OppScore

O

See sport specific redefinition

Usually for the opposing competitor in the period

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Competition /StatsItems /StatsItem (1,N)

Attribute

M/O

Value

Description

Type

O

See sport specific definition

 

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

Attempt

O

See sport specific definition

 

Avg

O

See sport specific definition

Related to average

Percent

O

See sport specific definition

Related to percentage

Rank

O

See sport specific definition

Rank for this statistic

RankEqual

O

S(1)

Send Y where Rank for this statistic is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all data for this statistic

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Competition /StatsItems /StatsItem /ExtendedStat (0,N)

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Officials /Official (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Official's code

Function

M

See table comment

Official's function (example: referee, etc.).

 

 

Can be different from the function sent in the DT_PARTIC message.

Order

O

See table comment

Official's order (if the discipline specificity required it).

Bib

O

See table comment

Official's Bib number

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Officials /Official /Description (1,1)

Officials extended information.

Attribute

M/O

Value

Description

GivenName

O

S(25)

Given name in WNPA format (mixed case)

FamilyName

M

S(25)

Family name in WNPA format (mixed case)

Gender

M

CC @PersonGender

Gender of the official

Organisation

M

CC @Organisation

Officials' organisation

IFId

O

S(16)

International Federation ID

 

Element: Officials /Official /Description /ExtendedDescription (0,N)

Attribute

M/O

Value

Description

Type

O

See sport specific definition

 

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Officials /Official /ExtOfficial (0,N)

Attribute

M/O

Value

Description

Type

O

See sport specific definition

 

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Periods (0,1)

Attribute

M/O

Value

Description

Home

O

S(20) with no leading zeroes

Home Competitor ID

Away

O

S(20) with no leading zeroes

Away Competitor ID

 

Element: Periods /Period (1,N)

Period in which the event unit message arrives.

Attribute

M/O

Value

Description

Code

M

See table comment

Period's code

HomeScore

M

See table comment

Overall score of the home competitor at the end of the period

AwayScore

M

See table comment

Overall score of the away competitor at the end of the period

HomePeriodScore

O

See table comment

Score of the home competitor just for this period

AwayPeriodScore

O

See table comment

Score of the away competitor just for this period

Duration

O

See table comment

Duration of the period

Table comment: Attribute to be set Mandatory from Optional or redefined. Refer to the ODF Sport Data Dictionary for each of the disciplines

 

Element: Periods /Period /ExtendedPeriods /ExtendedPeriod (1,N)

ExtendedPeriod  information.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Type

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Result (1,N)

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

Attribute

M/O

Value

Description

Rank

O

Text

 

 

See table comment

Rank of the competitor

RankEqual

O

Y

Identifies if a rank has been equalled. Only send if applicable

Result

O

See table comment

The result of the competitor in the event unit

Unchecked

O

See table comment

Send with ="Y" in the case that there is a value which needs to be validated. For example by reading photo to change from transponder times. Do not send if not ="Y"

IRM

O

See table comment

The invalid result mark, in case it is assigned

QualificationMark

O

See table comment

Indicates the qualification of the competitor for the next round of the competition

WLT

O

See table comment

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

SortOrder

M

Numeric

 

 

See table comment

Used to sort all the results of an  event unit

 

Before the start of any event unit this will be the same as the StartSortOrder and is used as the primary sort except in the case where a Rank is available (from earlier event units) and in this case the SortOrder will consider Rank in the same way as if the competition had already started.

 

During the event unit 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.

 

StartOrder

O

Numeric

 

 

See table comment

Competitor's start order