Olympic Data Feed

 

 

 

ODF General Messages Interface Document

PyeongChang 2018 – Games of the XXXI Olympiad

Technology and Information Department

© International Olympic Committee

 

ODF/INT401- R-WOG-2018-GEN-v1.7 APP

4 December 2017

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.

     

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

     

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

     

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

     

  5. 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 particular 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 (and have status UNSCHEDULED or SCHEDULED).

 

The arrival of the competition schedule message resets all the previous schedule information for one particular 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 usually 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.

 

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

 

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

 

Where HideStartDate="Y" is used then all start times for the units may be the same, usually the same as the first unit in the session or location (which generally will not use HideStartDate="Y") but this is not mandatory and approximate start times may be used. The specific way this is managed in each sport is detailed in the specific sport data dictionary.

 

 

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)

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"

 

 

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 the previous schedule information for one particular event unit(s) or session(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 should be sent immediately when known and usually soon 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)

 

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

 

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

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

See sport specific definition

 

Element: Competition /Session (0,N)

Attribute

M/O

Value

Description

SessionCode

M

S(5)

Code of the 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.

 

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

Attribute

M/O

Value

Description

Language

M

CC @Language

Language of the Session Description

Value

O

S(40)

Name of the 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(6)

 

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 e ach 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

Gold medal event unit or bronze medal event unit.

Do not send if not a medal event unit

Venue

M

CC @VenueCode

Venue where the unit takes place

Use TBD if the Venue is not known yet (CC).

Location

M

CC @Location

Location where the unit takes place

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

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

Code of the 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.

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

T,A

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' this 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)

 

Participant (1,N)

 

Code

 

Parent

 

Status

 

GivenName

 

FamilyName

 

PassportGivenName

 

PassportFamilyName

 

PrintName

 

PrintInitialName

 

TVName

 

TVInitialName

 

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: 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). For use after PyeongChang.

PassportFamilyName

O

S(25)

Passport Family Name (Uppercase). For use after PyeongChang.

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

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)

'Y' or 'N'

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

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

 

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

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. It is Optional in the case of  List of Team Update when the @ ModificationIndicator=D

TVTeamName

O

S(21)

Team's TV Name.

In head-to-head pairs competitions this should be in the format SMITH/JONES [max char(10) per name] else it is the organisation name unless special rules apply.

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

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

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)

 

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

 

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

Competition (0,1)

 

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

 

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

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

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

 

Result

 

ResultPoints

 

IRM

 

QualificationMark

 

Diff

 

WLT

 

SortOrder

 

StartOrder

 

StartSortOrder

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

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

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (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

 

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

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

2.1.5.5 Message Values

 

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

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

StartSortOrder

M

Numeric

 

 

See table comment

Used to sort all start list competitors in an event unit.

ResultType

O

See table comment

Type of the @Result attribute.

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

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

 

Element: Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

Speed

O

See sport specific definition

Speed at this ExtendedResult

Move

O

See sport specific definition

Change in rank compared to the previous ExtendedResult

Unchecked

O

Y

Send Y where the result @Value has not been appropriately validated (sport specific) else do not send.

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /RecordIndicators /RecordIndicator (1,N)

Result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. (Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

S(1)

Send "Y" in the case that the record has been equalled else do not send.

 

Element: Result /ResultItems /ResultItem (1,N)

Identifier of unit, for the item included the result summary. ResultItem /Result will be for one particular previous unit.

Attribute

M/O

Value

Description

Unit

M

See sport specific documentation

Unit code of the related sub-unit. It may be at phase or unit level.

Order

O

Numeric

#0

Logical order of the sub-units, usually schedule order.

 

Element: Result /ResultItems /ResultItem /Result (1,1)

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

Description

Rank

O

Text

See table comment

Rank of the competitor in the result for the event unit or phase identified by /ResultItems /ResultItem.

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute for the event unit or phase identified by /ResultItems /ResultItem. This is relative the value in Result below.

Result

O

See table comment

The result of the competitor in the event unit for the event unit or

phase identified by /ResultItems /ResultItem. This is usually the

'raw' result but is detailed in each data dictionary.

ResultPoints

O

See table comment

If the 'raw' score is converted to points to  calculate the overall result then put the points here.

IRM

O

See table comment

The invalid rank mark, in case it is assigned for the event unit or phase identified by /ResultItems /ResultItem

QualificationMark

O

See table comment

The code which gives an indication on the qualification of the competitor for the next round of the competition for the event unit or phase identified by /ResultsItems /ResultItem

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind.

For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

WLT

O

See table comment

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

for the event unit identified by /ResultItems /ResultItem. It just

applied to event units

SortOrder

O

Numeric

##0

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

StartOrder

O

See table comment

Start order for display if applicable

StartSortOrder

O

See table comment

Order at the start for sorting, not display.

 

Element: Result /ResultItems /ResultItem /Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

S(1)

Send Y where Rank at this specific ExtendedResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this  ExtendedResult

 

Element: Result /ResultItems /ResultItem /Result /ExtendedResults /ExtendedResult /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: Result /ResultItems /ResultItem /Result /RecordIndicators /RecordIndicator (1,N)

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. Can use the Order column from  CC@RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the  result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

S(1)

Send Y in the case that the record has been equalled else do not send.

 

Element: Result /Competitor (1,1)

Competitor related to the result of one event unit.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes or TBD or NOCOMP

Competitor's ID or TBD in case that the competitor is unknown at this time but will be available

 

NOCOMP is sent when  there is no competitor (and will not come later)

Type

M

T,A, H

T for team

A for athlete

H for Horse

Bib

O

See table comment

Bib number

Organisation

O

CC @Organisation

Competitor's organisation

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

 

Element: Result /Competitor /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups. Not usually for pairs (figure skating & beach volleyball are the exceptions).

IFId

O

S(16)

International Federation ID

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

 

Element: Result /Competitor /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: Result /Competitor /Coaches /Coach (1,N)

Competitor's Coach

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Official code. This code is normally expected though there may be rare exceptions.

Order

O

See table comment

Coach order (if more than one coach is needed). Send 1 if only one.

Function

O

See table comment

Official function

Bib

O

See table comment

Official 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: Result /Competitor /Coaches /Coach /Description (1,1)

Coach 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

Nationality

M

CC @Country

Coach's nationality

 

Element: Result /Competitor /Coaches /Coach /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: Result /Competitor /EventUnitEntry (0,N)

For team event information

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: Result /Competitor /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

 

Rank

O

See sport specific definition

Rank of the competitor 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 competitors for this statistic

 

Element: Result /Competitor /StatsItems /StatsItem /ExtendedStat (0,N)

Extended information for the statistics.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Result /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

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

Order

M

Numeric

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

StartOrder

O

Numeric

 

See table comment

Order of team members in a team (if Competitor @Type="T") on the start list. This is only used where the order changes from the start order to a different order during a competition or in results.

StartSortOrder

O

Numeric

 

See table comment

Order attribute used to sort team members in a team (if Competitor @Type="T") on the start list. This is only used where the order changes from the start order to a different order during a competition or in results.

Bib

O

See table comment

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: Result /Competitor /Composition /Athlete /Description (1,1)

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Result /Competitor /Composition /Athlete /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: Result /Competitor /Composition /Athlete /EventUnitEntry (0,N)

Individual athletes entry information.

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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member or individual athlete's extended result.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

Speed

O

See sport specific definition

Speed at this ExtendedResult

Move

O

See sport specific definition

Change in rank compared to the previous ExtendedResult

Unchecked

O

Y

Send Y where the result @Value has not been appropriately validated (sport specific) else do not send.

 

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /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: Result /Competitor /Composition /Athlete /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

 

Rank

O

See sport specific definition

Rank of the competitor for this statistic

RankEqual

O

S(1)

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

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors at this statistic

 

Element: Result /Competitor /Composition /Athlete /StatsItems /StatsItem /ExtendedStat (0,N)

Extended information for the statistics.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.5.6 Message Sort

Sort by Result @SortOrder

 

2.1.6 Play by Play

2.1.6.1 Description

The Play by Play is a message containing official raw data from the results provider for each action or incident.

 

The message contains a generic definition that can be used to provide results data of different nature as well as all of the actions in a unit.

2.1.6.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

 

DocumentSubcode

To be defined in each ODF Data Dictionary

Extension for the DocumentCode.

This is an optional attribute.

It is used when the RSC is not enough and it is required several different messages with the same RSC.

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

DocumentType

DT_PLAY_BY_PLAY

Play by Play message

DocumentSubtype

To be defined in each ODF Data Dictionary

Defines type of play by play

INCIDENT (generally used for incidents in races)

ACTION (generally used for actions in team sports)

Version

1..V

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

ResultStatus

SC @ResultStatus

Status of the message. Possible values are:

START_LIST (only used if there are actions before the start)

LIVE (used during the competition when nothing else applies)

INTERMEDIATE

UNOFFICIAL

OFFICIAL (when results official)

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

Each ODF Sport Data Dictionary defines triggering and frequency for that sport.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

SubEventName

 

Gender

 

VenueDescription  (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Actions (0,1)

 

Home

 

Away

 

Action (1,N)

 

Id

 

PId

 

Period

 

Order

 

Action

 

ActionAdd

 

ActionDesc

 

Comment

 

When

 

Result

 

ScoreH

 

ScoreA

 

LeadH

 

LeadA

 

SO_H

 

SO_A

 

Rally

 

Win

 

Speed

 

Loc

 

X

 

Y

 

Z

 

Line

 

TimeStamp

 

ExtendedAction (0,N)

 

Code

 

Pos

 

Value

 

Competitor (0,N)

 

Code

 

Type

 

Role

 

Order

 

Organisation

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Role

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Coaches (0,1)

 

Coach (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Nationality

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Officials (0,1)

 

Official (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

IFId

 

ExtendedDescription (0,N)

 

Code

 

Pos

 

Type

 

Value

 

ExtOfficial (0,N)

 

Code

 

Pos

 

Type

 

Value

 

ImageData (0,1)

 

-

 

ImageData (0,1)

 

-

2.1.6.5 Message Values

 

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

SubEventName

O

S(40)

EventUnit short name (not code) from Common Codes

Gender

M

CC @DisciplineGender

Gender code for the event unit

 

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

 

Element: Actions (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: Actions /Action (1,N)

Attribute

M/O

Value

Description

Id

M

S(36)

Unique identifier for the action within the message

PId

O

S(36)

If this is a related action then the ID of the original action appears here.

Period

M

See table comment

Period or timing (but not actual time) or event unit segment of the action. (for example P1,P2 for period,... or 0 for prior to start or perhaps SWIM if in swimming segment). Use period codes if applicable. Defined sport by sport.

Order

M

Numeric

Unique sequential number for all the incidents and actions, from 1 to n

 

It is used to sort Action

Action

O

See table comment

Code to describe the action, only use if a code is applicable.

ActionAdd

O

See table comment

Additional information related to the action

ActionDesc

O

S(200)

Action/Incident description where codes (Action) cannot be used (ENG)

Comment

O

S(200)

Additional comment on the action (ENG)

When

O

See table comment

Action's time relative to the period / unit. Defined by discipline though may be actual period time, lap or distance depending on the discipline requirements.

Result

O

Result of the Action

See sport documents, usually a fixed list of results

ScoreH

O

Score of the Home team

Numeric, home team score in the unit after action.

 

Depending on sport rules this may or may not include shoot out scores or could be the set score (volleyball)

ScoreA

O

Score of the Away team

Numeric, away team score in the unit after action.

 

Depending on sport rules this may or may not include shoot out scores or could be the set score (volleyball)

LeadH

O

Lead of the Home Team

Lead by Home team, may be negative. If used, both LeadH and LeadA are used for maximum flexibility.

LeadA

O

Lead of the Away team

Lead by Away team, may be negative. If used, both LeadH and LeadA are used for maximum flexibility.

SO_H

O

See table comment

Home team score in shoot-out (to break tie)

SO_A

O

See table comment

Away team score in shoot-out (to break tie)

Rally

O

See table comment

Rally number

Win

O

See table comment

Winning indicator of a rally in head to head

Speed

O

See table comment

Speed as applicable

Loc

O

See table comment

Location of the action

X

O

S(20)

X coordinate of the action location

Y

O

S(20)

Y coordinate of the action location

Z

O

S(20)

Z coordinate of the action location

Line

O

See table comment

Generally for associating line in the same rally

TimeStamp

O

DateTime

Time of the action (for alignment to video)

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

 

Element: Actions /Action /ExtendedAction (0,N)

Extended Action information.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Actions /Action /Competitor (0,N)

Competitor participating in the Action. Used when the Action is related to a competitor.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

T,A

T for team

A for athlete

Role

O

See table comment

Role of the competitor in the action

Order

O

Numeric

Order in which the competitor should appear for the action, if there is more than one competitor. Send 1 if only one.

Organisation

M

CC @Organisation

Competitors' organisation

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

 

Element: Actions /Action /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete's ID ( individual athlete or team member) related to the action

Order

O

Numeric

Order of the athletes. Used to order the athletes when there are more than one athlete related to the action. Send 1 if only one.

Bib

O

See table comment

Bib number

Role

O

See table comment

Role of the competitor in the action

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

 

Element: Actions /Action /Competitor /Composition /Athlete /Description (1,1)

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Actions /Action /Competitor /Composition /Athlete /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: Actions /Action /Competitor /Coaches /Coach (1,N)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Official code. This code is normally expected though there may be rare exceptions.

Order

O

See table comment

 

Coach order (if more than one coach is needed). Send 1 if only one.

Bib

O

See table comment

Coach bib if applicable

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

 

Element: Actions /Action /Competitor /Coaches /Coach /Description (1,1)

Coach 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

Nationality

M

CC @Country

Coach's nationality

 

Element: Actions /Action /Competitor /Coaches /Coach /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: Actions /Action /Officials /Official (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

 

Official's code

Order

O

See table comment

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

Bib

O

See table comment

Official's bib if applicable

 

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

 

Element: Actions /Action /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: Actions /Action /Officials /Official /Description /ExtendedDescription (0,N)

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: Actions /Action /Officials /Official /ExtOfficial (0,N)

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: Actions /Action /ImageData (0,1)

Attribute

M/O

Value

Description

-

M

Text

The ImageData element contains a body consisting of one Base64-encoded PNG file.

 

Element: ImageData (0,1)

Attribute

M/O

Value

Description

-

M

Text

The ImageData element contains a body consisting of one Base64-encoded PNG file.

2.1.6.6 Message Sort

Actions /Action @Order.

 

2.1.7 Results Analysis

2.1.7.1 Description

The Results Analysis is a message containing additional information for the start list and/or results.

 

Results Analysis is only used in sports where the results can be split and may not need to be updated as frequently. For example detailed splits in triathlon and diving details.

2.1.7.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC of the Unit

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

DocumentType

DT_RESULT_ANALYSIS

Event Unit Result Analisys message

DocumentSubtype

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType for some 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

INTERMEDIATE (used when the competition 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)

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

The triggered is defined on a sport by sport basis but in principle is updated each time there is a change.

 

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.

 

If there is any kind of sport specific rule, this can overwrite in the corresponding ODF Sport Data Dictionaries the general trigger rule

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

Competition (0,1)

 

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)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Partial (0,N)

 

Code

 

Score

 

OppScore

 

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

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

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

 

Result

 

ResultPoints

 

IRM

 

QualificationMark

 

Diff

 

WLT

 

SortOrder

 

StartOrder

 

StartSortOrder

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

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

 

Function

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Nationality

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (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

 

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

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Move

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

2.1.7.5 Message Values

 

Element: ExtendedInfos /UnitDateTime (0,1)

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

 

 

Actual start and/or end dates and times.

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)

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

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)

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

M

S(40)

Full RSC of the previous event unit

Order

M

Numeric

#0

Order of the units

Opponent

O

S(20) with no leading zeroes

Competitor ID of the opponent

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

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: ExtendedInfos /PreviousResults /PreviousResult /ExtendedResults /ExtendedResult /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

 

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="S2" Score="6" OppScore="0" />

   </PreviousResult>

</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---------------8FNL0001----" 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: Officials /Official (1,N)

Officials in the case there are officials receiving events medals.

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 being awarded 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

StartSortOrder

M

Numeric

 

 

See table comment

Used to sort all start list competitors in an event unit.

ResultType

O

See table comment

Type of the @Result attribute.

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

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

 

Element: Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

Speed

O

See sport specific definition

Speed at this ExtendedResult

Move

O

See sport specific definition

Change in rank compared to the previous ExtendedResult

Unchecked

O

Y

Send Y where the result @Value has not been appropriately validated (sport specific) else do not send.

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /RecordIndicators /RecordIndicator (1,N)

Result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

S(1)

Send "Y" in the case that the record has been equalled else do not send.

 

Element: Result /ResultItems /ResultItem (1,N)

Identifier of unit, for the item included the result summary. ResultItem /Result will be for one particular previous unit.

Attribute

M/O

Value

Description

Unit

M

See sport specific documentation

Unit code of the related sub-unit. It may be at phase or unit level.

Order

O

Numeric

#0

Logical order of the sub-units, usually schedule order.

 

Element: Result /ResultItems /ResultItem /Result (1,1)

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

Description

Rank

O

Text

See table comment

Rank of the competitor in the result for the event unit or phase identified by /ResultItems /ResultItem.

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute for the event unit or phase identified by /ResultItems /ResultItem. This is relative the value in Result below.

Result

O

See table comment

The result of the competitor in the event unit for the event unit or phase identified by /ResultItems /ResultItem. This is usually the 'raw' result but is detailed in each data dictionary.

ResultPoints

O

See table comment

If the 'raw' score is converted to points to calculate the overall result then put the points here.

IRM

O

See table comment

The invalid rank mark, in case it is assigned for the event unit or phase identified by /ResultItems /ResultItem

QualificationMark

O

See table comment

The code which gives an indication on the qualification of the competitor for the next round of the competition for the event unit or phase identified by /ResultsItems /ResultItem

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec in front of (better than) the leader.

WLT

O

See table comment

The code whether a competitor won, lost or tied the match / game for the event unit identified by /ResultItems /ResultItem. It just applied to event units

SortOrder

M

Numeric

##0

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

StartOrder

O

See table comment

Start order for display if applicable

StartSortOrder

O

See table comment

Order at the start for sorting, not display.

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

 

Element: Result /ResultItems /ResultItem /Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

end appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult

RankEqual

O

Y

Send Y where Rank at this specific ExtendedResult is equalled else not sent

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /ResultItems /ResultItem /Result /ExtendedResults /ExtendedResult /Extension (0,N)

Extensions of ResultItem if required.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Result /ResultItems /ResultItem /Result /RecordIndicators /RecordIndicator (1,N)

Result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

Y

Send Y in the case that the record has been equalled else do not send.

 

Element: Result /Competitor (1,1)

Competitor related to the result of one event unit.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes or TBD or NOCOMP

Competitor's ID or TBD in case that the competitor is unknown at this time but will be available

 

 

NOCOMP is sent when  there is no competitor (and will not come later)

Type

M

T,A, H

T for team

A for athlete

H for Horse

Bib

O

See table comment

Bib number

Organisation

O

CC @Organisation

Competitor's organisation

 

Element: Result /Competitor /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups. Not usually for pairs (figure skating & beach volleyball are the exceptions).

IFId

O

S(16)

International Federation ID

 

Element: Result /Competitor /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: Result /Competitor /Coaches /Coach (1,N)

Competitor's Coach

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Official code. This code is normally expected though there may be rare exceptions.

Function

O

See table comment

Official function

Order

O

See table comment

Coach order (if more than one coach is needed). Send 1 if only one.

Bib

O

See table comment

Official 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: Result /Competitor /Coaches /Coach /Description (1,1)

Coach 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

Nationality

M

CC @Country

Coach's nationality

 

Element: Result /Competitor /Coaches /Coach /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: Result /Competitor /EventUnitEntry (0,N)

For team event information

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: Result /Competitor /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

 

Rank

O

See sport specific definition

Rank of the competitor 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 competitors for this statistic

 

Element: Result /Competitor /StatsItems /StatsItem /ExtendedStat (0,N)

Extended information for the statistics.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Result /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athletes ID. Can belong to a team member or an individual athlete.

Order

M

Numeric

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

StartOrder

O

Numeric

 

See table comment

Order of team members in a team (if Competitor @Type="T") on the start list. This is only used where the order changes from the start order to a different order during a competition or in results

StartSortOrder

O

Numeric

Order attribute used to sort team members in a team (if Competitor @Type="T") on the start list. This is only used where the order changes from the start order to a different order during a competition or in results

Bib

O

See table comment

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: Result /Competitor /Composition /Athlete /Description (1,1)

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Result /Competitor /Composition /Athlete /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: Result /Competitor /Composition /Athlete /EventUnitEntry (0,N)

Individual athletes entry information.

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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member or individual athlete's extended result.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

Speed

O

See sport specific definition

Speed at this ExtendedResult

Move

O

See sport specific definition

Change in rank compared to the previous ExtendedResult

Unchecked

O

Y

Send Y where the result @Value has not been appropriately validated (sport specific) else do not send.

 

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /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: Result /Competitor /Composition /Athlete /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

 

Rank

O

See sport specific definition

Rank of the competitor for this statistic

RankEqual

O

S(1)

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

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors at this statistic

 

Element: Result /Competitor /Composition /Athlete /StatsItems /StatsItem /ExtendedStat (0,N)

Extended information for the statistics.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.7.6 Message Sort

Message sorting is the same as in the DT_RESULTS message

 

2.1.8 Current Information

2.1.8.1 Description

The Current message is a message containing the current information for a competition which is live. The message is used to send the latest applicable information and in some sports with a running clock, also the clock information.

 

The following information is the recommended way to use the clock information provided in DT_CURRENT.

- Show a running clock on the "results" page for a particular unit

- The clock should be first displayed when the ResultStatus for the unit becomes "LIVE" for the first time (i.e. no longer "START_LIST") and DT_CURRENT is received.

- The DT_CURRENT includes the clock information and a status, if the clock is running or stopped.

- The clock should be some sort of display at client side through an application/applet/widget (e.g. javascript countdown/timing clock) which continuously runs in the page, when the status of the clock is indicated as running (Running = Y) then start at the time sent in the same message.

- Whenever you receive a message with the status stopped (Running = N) you need to stop your running clock and show the time sent in the same message. The clock will only be started again, once you receive Running = Y again.

- Every time a new DT_CURRENT is received then re-synchronise the in-page clock to the time in the message and take action to start or stop the clock as described previously.

- The clock can be continuously displayed while the ResultStatus of the unit in reference is "LIVE" or "INTERMEDIATE" (users may prefer to remove when INTERMEDIATE or SCHEDULED_BREAK)

- Once a unit is "FINISHED" or the ResultStatus is not one of those above then the clock should be removed from the page as no further updates will be provided.

2.1.8.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

 

DocumentSubcode

To be defined in each ODF Data Dictionary

Extension for the DocumentCode.

This is an optional attribute.

It is used when the RSC is not enough and it is required several different messages with the same RSC.

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

DocumentType

DT_CURRENT

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

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

Each ODF Sport Data Dictionary defines triggering and frequency for that sport.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Clock (0,1)

 

Period

 

Time

 

Running

 

Periods (0,1)

 

Home

 

Away

 

Period (1,N)

 

Code

 

HomeScore

 

AwayScore

 

HomePeriodScore

 

AwayPeriodScore

 

Duration

 

ExtendedPeriods (0,1)

 

ExtendedPeriod (1,N)

 

Code

 

Type

 

Pos

 

Value

 

Actions (0,N)

 

Home

 

Away

 

Action (1,N)

 

Id

 

PId

 

Period

 

Order

 

Action

 

ActionAdd

 

ActionDesc

 

Comment

 

When

 

Result

 

ScoreH

 

ScoreA

 

LeadH

 

LeadA

 

SO_H

 

SO_A

 

Rally

 

Win

 

Speed

 

Loc

 

X

 

Y

 

Z

 

Line

 

TimeStamp

 

ExtendedAction (0,N)

 

Code

 

Pos

 

Value

 

Competitor (0,N)

 

Code

 

Type

 

Role

 

Order

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Role

 

Coaches (0,1)

 

Coach (1,N)

 

Code

 

Order

 

Bib

 

Officials (0,1)

 

Official (1,N)

 

Code

 

Order

 

Bib

 

ExtOfficial (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Result (0,N)

 

Rank

 

RankEqual

 

Result

 

IRM

 

QualificationMark

 

SortOrder

 

WLT

 

StartOrder

 

StartSortOrder

 

ResultType

 

Diff

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Competitor (1,N)

 

Code

 

Type

 

Bib

 

Organisation

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

EventUnitEntry (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Speed

 

Unchecked

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

2.1.8.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (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

 

 

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: Clock (0,1)

Clock Information

Attribute

M/O

Value

Description

Period

O

See sport specific

Current Period

Time

M

mm:ss

Value of the clock

Running

M

S(1)

Indicates if the clock is currently running.

Y to indicate the clock is running, N to indicate the clock is stopped.

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

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: Actions (0,N)

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: Actions /Action (1,N)

Attribute

M/O

Value

Description

Id

M

S(36)

Unique identifier for the action within the message

PId

O

S(36)

If this is a related action then the ID of the original action appears here.

Period

M

See table comment

Period or timing (but not actual time) or event unit segment of the action. (for example P1,P2 for period,... or 0 for prior to start or perhaps SWIM if in swimming segment). Use period codes if applicable. Defined sport by sport.

Order

M

Numeric

Unique sequential number for all the incidents and actions, from 1 to n

 

It is used to sort Action

Action

O

See table comment

Code to describe the action, only use if a code is applicable.

ActionAdd

O

See table comment

Additional information related to the action

ActionDesc

O

S(200)

Action/Incident description where codes (Action) cannot be used (ENG)

Comment

O

S(200)

Additional comment on the action (ENG)

When

O

See table comment

Action's time relative to the period / unit. Defined by discipline though may be actual period time, lap or distance depending on the discipline requirements.

Result

O

Result of the Action

See sport documents, usually a fixed list of results

ScoreH

O

Score of the Home team

Numeric, home team score in the unit after action

Depending on sport rules this may or may not include shoot out scores or could be the set score (volleyball)

ScoreA

O

Score of the Away team

Numeric, away team score in the unit after action

Depending on sport rules this may or may not include shoot out scores or could be the set score (volleyball)

LeadH

O

Lead of the Home Team

Lead by Home team, may be negative. If used, both LeadH and LeadA are used for maximum flexibility.

LeadA

O

Lead of the Away team

Lead by Away team, may be negative. If used, both LeadH and LeadA are used for maximum flexibility.

SO_H

O

See table comment

Home team score in shoot-out (to break tie)

SO_A

O

See table comment

Away team score in shoot-out (to break tie)

Rally

O

See table comment

Rally number

Win

O

See table comment

Winning indicator of a rally in head to head.

Speed

O

See table comment

Speed as applicable

Loc

O

See table comment

Location of the action

X

O

S(20)

X coordinate of the action location

Y

O

S(20)

Y coordinate of the action location

Z

O

S(20)

Z coordinate of the action location

Line

O

See table comment

Generally for associating line in the same rally

TimeStamp

O

DateTime

Time of the action (for alignment to video)

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

 

Element: Actions /Action /ExtendedAction (0,N)

Extended Action information

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Actions /Action /Competitor (0,N)

Competitor participating in the Action. Used when the Action is related to a competitor.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

T,A

T for team

 

A for athlete

Role

O

See table comment

Role of the competitor in the action

Order

O

Numeric

Order in which the competitor should appear for the action, if there is more than one competitor. Send 1 if only one.

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

 

Element: Actions /Action /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete's ID ( individual athlete or team member) related to the action

Order

O

Numeric

Order of the athletes. Used to order the athletes when there are more than one athlete related to the action. Send 1 if only one.

Bib

O

See table comment

Bib number

Role

O

See table comment

Role of the competitor in the action

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

 

Element: Actions /Action /Competitor /Coaches /Coach (1,N)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Official code. This code is normally expected though there may be rare exceptions.

Order

O

See table comment

Coach order (if more than one coach is needed). Send 1 if only one.

Bib

O

See table comment

Coach bib if applicable

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

 

Element: Actions /Action /Officials /Official (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeros

Official's code

Order

O

See table comment

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

Bib

O

See table comment

Official's bib if applicable

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

 

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

Attribute

M/O

Value

Description

Type

M

N/A

 

Code

M

N/A

 

Pos

O

N/A

 

Value

O

N/A

 

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

 

Element: Result (0,N)

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

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

SortOrder

M

Numeric

 

 

See table comment

Used to sort all the results of an  event unit

 

 

Before the competition this will be the same as the StartSortOrder and is used as the primary sort.

 

During competition 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

WLT

O

See table comment

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

StartOrder

O

Numeric

 

 

See table comment

Competitor's start order

StartSortOrder

M

Numeric

 

 

See table comment

Used to sort all start list competitors in an event unit.

ResultType

O

See table comment

Type of the @Result attribute.

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

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

 

Element: Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

Speed

O

See sport specific definition

Speed at this ExtendedResult

Unchecked

O

Y

Send Y where the result @Value has not been appropriately validated (sport specific) else do not send.

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /Competitor (1,N)

Competitor related to the result of one event unit.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes or TBD

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

Type

M

T,A

T for team

 

A for athlete

 

Bib

O

See table comment

Bib number

Organisation

M

CC @Organisation

Competitor's organisation

 

Element: Result /Competitor /EventUnitEntry (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: Result /Competitor /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

 

 

Element: Result /Competitor /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

 

 

Element: Result /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athletes ID. Can belong to a team member or an individual athlete.

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

See table comment

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: Result /Competitor /Composition /Athlete /EventUnitEntry (0,N)

Individual athlete?s entry information.

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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member or individual athlete's extended result.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

Speed

O

See sport specific definition

Speed at this ExtendedResult

Unchecked

O

Y

Send Y where the result @Value has not been appropriately validated (sport specific) else do not send.

 

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /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: Result /Competitor /Composition /Athlete /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

 

 

Element: Result /Competitor /Composition /Athlete /StatsItems /StatsItem /ExtendedStat (0,N)

Extended information for the statistics.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.8.6 Message Sort

Sort by Result @SortOrder.

 

2.1.9 Image

2.1.9.1 Description

The Image message is a message containing an image or images file(s) in .jpg or .png format encapsulated in a XML message.

 

The type of image may vary from discipline to discipline and could be a photofinish image or some other type of image to support the results of the discipline.

 

The message allows for multiple images but it is assumed the images are related (could be different resolutions, different states of a competition or different places in photofinish photos) hence only one description. Unrelated images should be sent separately.

 

When the DocumentSubtype is PHOTOFINISH or UNIFORM then no extensions are to be used to have all disciplines use the same structure.

2.1.9.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

 

DocumentSubcode

S(34)

Picture number or may be redefined by discipline as needed.

DocumentType

DT_IMAGE

Image message

DocumentSubtype

S(20)

This is defined by the needs of the sport. Sport specific values are defined in the sport

data dictionary. Examples of the possible values are:

PHOTOFINISH

STROKETRAIL

UNIFORM

Always refer to the sport specific data dictionary for use

Version

1..V

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

ResultStatus

SC @ResultStatus

Only applicable status is OFFICIAL

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

Trigger and frequency defined in ORIS (or PRIS) or may be varied in the sport specific data dictionary.

 

Trigger also after any change.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

RightsInfo (0,1)

 

CopyrightHolder

 

Notice

 

Usage

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

ContentInfo (0,1)

 

Title

 

Description

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Image (1,N)

 

Pos

 

Version

 

Revision

 

ImageType

 

Result (0,N)

 

Result

 

Rank

 

StartOrder

 

SortOrder

 

Competitor (1,1)

 

Code

 

Type

 

Organisation

 

Description (0,1)

 

TeamName

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

ImageTitle (0,1)

 

-

 

ImageDescription (0,1)

 

-

 

ImageData (1,1)

 

-

2.1.9.5 Message Values

 

Element: Competition /ExtendedInfos /ExtendedInfo (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

 

 

Element: Competition /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: Competition /RightsInfo (0,1)

Attribute

M/O

Value

Description

CopyrightHolder

O

S(50)

Name of the copyright holder

Notice

O

S(50)

The appropriate copyright notice

Usage

O

String

Usage rules

 

Element: Competition /RightsInfo /Extension (0,N)

Attribute

M/O

Value

Description

Code

M

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

N/A

See sport specific definition

 

Element: Competition /ContentInfo (0,1)

Attribute

M/O

Value

Description

Title

O

S(50)

Title of the image(s)

Description

O

String

Any Description of the image

 

Element: Competition /ContentInfo /Extension (0,N)

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

N/A

See sport specific definition

 

Element: Competition /Image (1,N)

Attribute

M/O

Value

Description

Pos

M

Numeric

#0

Used as differentiator if there are multiple images in the message.

In the case of different holes in golf the numbers 1..18 could be used.

 

Version

M

Numeric

#0

Document Version

Revision

M

Numeric

#0

Document Revision

ImageType

M

S(3)

Image type extension, jpg or png

 

Element: Competition /Image /Result (0,N)

Attribute

M/O

Value

Description

Result

O

S(20)

Result of the competitor in the image. Formatted as appropriate in the event. Use IRM code if appropriate.

Rank

O

S(10)

Rank of the competitor

StartOrder

O

S(4)

Start or lane position

SortOrder

M

Numeric

###0

This attribute is a sequential number with the order of the competitors in the image.

 

Element: Competition /Image /Result /Competitor (1,1)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Competitor's ID (Team or individual)

If it is possible to send the ID it should be included.

This information will not be sent in PyeongChang.

Type

O

S(1)

A for athlete or T for team.

If it is possible to send the type it should be included.

This information will not be sent in PyeongChang.

Organisation

O

CC @Organisation

Competitor's organisation

 

Element: Competition /Image /Result /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

O

S(73)

Name of the Team.

This information will not be sent in PyeongChang.

 

Element: Competition /Image /Result /Competitor /Composition /Athlete (1,N)

Only sent in the case of individual events. Team members are not sent in team events.

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Athlete's ID.

If it is possible to send the ID it should be included.

This information will not be sent in PyeongChang.

Order

M

Numeric

##0

Order attribute used to sort team members in a team.

Send 1 for individuals.

1 will always be sent in PyeongChang

Bib

O

S(4)

Bib number

 

Element: Competition /Image /Result /Competitor /Composition /Athlete /Description (1,1)

Attribute

M/O

Value

Description

GivenName

O

S(25)

Given name (Photofinish Name)

FamilyName

M

S(25)

Family name (Photofinish Name)

 

Element: Competition /Image /ImageTitle (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Image title if applicable.

 

Element: Competition /Image /ImageDescription (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Image description if applicable.

 

Element: Competition /Image /ImageData (1,1)

Attribute

M/O

Value

Description

-

M

Free Text

The ImageData element has a body consisting of one Base64-encoded report (a jpeg or png file)

 Sample (Photofinish - Individual)

   <Competition>

      <RightsInfo CopyrightHolder="OMEGA" Notice="rg" Usage="er" />

      <Image Pos="1" Version="1" Revision="0" ImageType="jpg">

         <Result Rank="1" StartOrder="1" SortOrder="1">

            <Competitor Organisation="NOR">

               <Composition>

                  <Athlete Order="1" Bib="1">

                     <Description GivenName="Ola Vigen" FamilyName="HATTESTAD" />

                  </Athlete>

               </Composition>

            </Competitor>

         </Result>

         <Result Rank="2" StartOrder="1" SortOrder="2">

            <Competitor Organisation="SWE">

               <Composition>

                  <Athlete Order="1" Bib="6">

                     <Description GivenName="Teodor" FamilyName="PETERSON" />

                  </Athlete>

               </Composition>

            </Competitor>

         </Result>

...

      <ImageData>/9j/4AAQSkZJRgABAQAAAQABAAD/7...Q==</ImageData>

   </Image>

</Competition>

 Sample (Photofinish - Team)

<Competition>

   <RightsInfo CopyrightHolder="OMEGA" Notice="rg" Usage="er" />

      <Image Pos="1" Version="1" Revision="0" ImageType="jpg">

         <Result Rank="1" StartOrder="1" SortOrder="1">

            <Competitor Organisation="NOR">

               <Composition>

                  <Athlete Order="1" Bib="1">

                     <Description GivenName="" FamilyName="NORWAY" />

                  </Athlete>

               </Composition>

            </Competitor>

         </Result>

         <Result Rank="2" StartOrder="1" SortOrder="2">

            <Competitor Organisation="SWE">

               <Composition>

                  <Athlete Order="1" Bib="6">

                     <Description GivenName="" FamilyName="SWEDEN" />

                  </Athlete>

               </Composition>

            </Competitor>

         </Result>

...

         <ImageData>/9j/4AAQSk...2Q==</ImageData>

   </Image>

</Competition>

 Sample (Stroke Trail)

<OdfBody CompetitionCode="OG2012" DocumentType="DT_IMAGE" DocumentSubtype="STROKETRAIL" Date="2016-08-08" Time="120830417" LogicalDate="2016-08-08" Source="GOSTA1" FeedFlag="P" DocumentCode="GLFWSTROKE------------FNL-000101--" DocumentSubcode="4352682" Version="1">

<Competition>

<Image Pos="1" Version="1" Revision="0" ImageType="png" >

<ImageData>/9j/4AAQSkZJRgABAQEAAAAAA ETC ETC Lj5OXm5+jp6vHy8/T+uit//2Q==</ImageData>

</Image>

<Image Pos="2" Version="1" Revision="0" ImageType="png" >

<ImageData>/9j/4AAQSkZJRgABAQEAAAAAA ETC ETC Lj5OXm5+jp6vHy8/T+uit//2Q==</ImageData>

</Image>

</Competition>

</OdfBody>

2.1.9.6 Message Sort

Sort by Competition /Image /Pos and SortOrder within image.

 

2.1.10 Press Photofinish

2.1.10.1 Description

The Press Photofinish message contains a link to the Press Diffusion Document for a particular event unit. It is a PDF containing the photo finish picture (uncompressed) which includes judgment markers as well as all necessary additional information.

 

It is a generic message for all sports.

2.1.10.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

 

DocumentSubcode

S(10)

Picture number

DocumentType

DT_PRESSPHOTOFINISH_LK

Press Photofinish message

Version

1..V

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

ResultStatus

SC @ResultStatus

Only applicable status is OFFICIAL

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

Trigger when available.

Trigger also after any major change.

2.1.10.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

PhotoFinish (1,1)

 

Version

 

Revision

 

Link

2.1.10.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (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

 

 

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: PhotoFinish (1,1)

Attribute

M/O

Value

Description

Version

M

Numeric

Document version: 1..9999

Revision

M

Numeric

Document version: 1..9999

Link

M

S(255)

URL of the link to the document

2.1.10.6 Message Sort

There is no message sorting requirement for this message.

 

2.1.11 Phase Results

2.1.11.1 Description

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

 

The phase message is used to compare competitors from different units within a phase where the competitors usually participate once in the phase.

 

The mandatory attributes and mandatory elements defined in this message will have to be used by all the sports, although each ODF Sport Data Dictionary will explain further details of the optional attributes or optional elements of the message.

 

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

2.1.11.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 complete the explanation regarding to this attribute

DocumentSubcode

(34)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentCode.

DocumentType

DT_PHASE_RESULT

Phase Results message

DocumentSubtype

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType.

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.

INTERMEDIATE (used after each unit in the phase)

LIVE

OFFICIAL

UNOFFICIAL

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

The general rule is that this message is sent after every unit in a phase as intermediate and then as soon as the last event unit for the corresponding phase finishes and again when the message becomes unofficial just at the end of the event unit, and afterwards when the message becomes official (when the last event unit of the phase becomes official). The official/unofficial status can be seen in ODF header (ResultStatus attribute). Depending on the nature of the units the message may also be sent as LIVE.

 

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

SubEventName

 

Gender

 

VenueDescription  (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Result (1,N)

 

Rank

 

RankEqual

 

ResultType

 

Result

 

IRM

 

Diff

 

QualificationMark

 

SortOrder

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

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

 

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)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Extension (0,N)

 

Code

 

Pos

 

Value

2.1.11.5 Message Values

 

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

SubEventName

O

S(40)

Phase level short name (not code) from Common Codes

Gender

M

CC @DisciplineGender

Gender code for the event unit

 

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

 

Element: Result (1,N)

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

Attribute

M/O

Value

Description

Rank

O

Text

 

 

See table comment

Rank of the competitor in the phase.

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute

Result

O

See table comment

The result of the competitor in the phase

IRM

O

See table comment

The invalid result mark, in case it is assigned

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

QualificationMark

O

See table comment

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

SortOrder

M

Numeric

 

See table comment

 

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

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

 

Element: Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /RecordIndicators /RecordIndicator (1,N)

Phase result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. (Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

S(1)

Send "Y" in the case that the record has been equalled else do not send.

 

Element: Result /Competitor (1,1)

Competitor related to one phase result.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

T,A

T for team

A for athlete

Bib

O

See table comment

Bib number

Organisation

M

CC @Organisation

Competitor's organisation

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

 

Element: Result /Competitor /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups. Not usually for pairs (figure skating & beach volleyball are the exceptions).

IFId

O

S(16)

International Federation ID

 

Element: Result /Competitor /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: Result /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete's ID, corresponding to either a team member or a single athlete

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

See table comment

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: Result /Competitor /Composition /Athlete /Description (1,1)

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Result /Competitor /Composition /Athlete /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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member's or individual athlete's extended result, depending on whether Competitor @Type="T" or Competitor @Type="A".

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /Extension (0,N)

Extensions of team member's or individual athlete's extended results.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.11.6 Message Sort

Result @SortOrder will be the attribute used to sort the results, as the attribute @SortOrder is defined in each of the ODF Sport Data Dictionaries. Other @Order attributes will usually be used to order the rest of elements, as these elements are being requested in each of the ODF Sport Data Dictionary Documents.

 

2.1.12 Cumulative Results

2.1.12.1 Description

The Cumulative Results is a message containing the cumulative results for the competitors in a group of units either in a single phase or over a number of phases. This message is used when the competitor scores accumulate over the different units.

 

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 is for competitions where scores of the competitors are accumulated over a number of units and/or phases.

 

The Cumulative Results message is be used to send an intermediate 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 will have to be used by all the sports, although each ODF Sport Data Dictionary will have to explain with further detail the optional attributes or optional elements of the message.

2.1.12.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 complete the explanation regarding to this attribute

DocumentSubcode

S(34)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentCode

DocumentType

DT_CUMULATIVE_RESULT

Cumulative Results message

DocumentSubtype

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType

Version

1..V

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

ResultStatus

SC @ResultStatus

It indicates the status of the results

LIVE

INTERMEDIATE

UNCONFIRMED

OFFICIAL

UNOFFICIAL

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

The cumulative results accumulate scores/results over a number of units so are generally sent after each DT_RESULT message if the cumulative message applies (usually using same ResultStatus at DT_RESULT). When there is no unit in progress the cumulative results will have INTERMEDIATE status.

 

The first version is generally triggered at the same time as the start list of the first unit is is triggered.

 

Where live updates are not appropriate (sport dependent) then the triggering is defined in the sport data dictionaries.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

SubEventName

 

Gender

 

VenueDescription  (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Result (1,N)

 

Rank

 

RankEqual

 

ResultType

 

Result

 

IRM

 

QualificationMark

 

Diff

 

SortOrder

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

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

 

Result

 

ResultPoints

 

IRM

 

QualificationMark

 

Diff

 

WLT

 

SortOrder

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

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

 

Composition (1,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Extension (0,N)

 

Code

 

Pos

 

Value

2.1.12.5 Message Values

 

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

SubEventName

O

S(40)

Phase level short name (not code) from Common Codes. Only include if in single phase.

Gender

M

CC @DisciplineGender

Gender code for the event unit

 

Element: ExtendedInfos /VenueDescription (0,1)

Venue Names in Text. DO NOT INCLUDE unless all at single venue and location.

Attribute

M/O

Value

Description

Venue

M

CC @VenueCode

Venue Code

VenueName

M

S(25)

Venue short name (not code) from Common Codes

Location

O

CC @Location

Location code

LocationName

O

S(30)

Location short name (not code) from Common Codes

 

Element: Result (1,N)

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

Description

Rank

O

Text

 

See table comment

Rank of the competitor in the cumulative result

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute

Result

O

See table comment

The cumulative result of the competitor

IRM

O

See table comment

The invalid result mark, in case it is assigned

QualificationMark

O

See table comment

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

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

SortOrder

M

Numeric

See table comment

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

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

 

Element: Result /ExtendedResults /ExtendedResult (1,N)

Team competitor's extended results.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /RecordIndicators /RecordIndicator (1,N)

Cumulative result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. (Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

S(1)

Send Y in the case that the record has been equalled else do not send.

 

Element: Result /ResultItems /ResultItem (1,N)

Identifier of unit, for the schedule item to which it is going to be included the result summary. ResultItem /Result will be for one particular previous unit.

Attribute

M/O

Value

Description

Unit

M

See table comment

Unit code of the latest RSC schedule item to which the cumulative results is updated to. It may be at phase or unit level.

Order

O

Numeric

#0

Logical order of the sub-units, usually schedule order.

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

 

Element: Result /ResultItems /ResultItem /Result (1,1)

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

Description

Rank

O

Text

 

See table comment

Rank of the competitor in the result for the event unit or phase identified by /ResultItems /ResultItem.

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute for the event unit or phase identified by /ResultItems /ResultItem. This is relative the value in Result below.

Result

O

See table comment

The result of the competitor in the event unit for the event unit or phase identified by /ResultItems /ResultItem. This is usually the 'raw' result but is detailed in each data dictionary.

ResultPoints

O

See table comment

If the 'raw' score is converted to points to calculate the overall result then put the points here.

IRM

O

See table comment

The invalid result mark, in case it is assigned for the event unit or phase identified by /ResultItems /ResultItem

QualificationMark

O

See table comment

The code which gives an indication on the qualification of the competitor for the next round of the competition for the event unit or phase identified by /ResultsItems /ResultItem

Diff

O

See table comment

Display the time / value behind the leader. All fill when applicable, 0.0 for leader, negative for in front of leader, positive for behind. For example +3.45 means 3.45 sec behind the leader, -1.23 means -1.23 sec infront of (better than) the leader.

WLT

O

See table comment

The code whether a competitor won, lost or tied the match / game for the event unit identified by /ResultItems /ResultItem. It just applied to event units

SortOrder

M

Numeric

 

See table comment

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

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

 

Element: Result /ResultItems /ResultItem /Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult

RankEqual

O

Y

Send Y where Rank at this specific ExtendedResult is equalled else not sent

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /ResultItems /ResultItem /Result /ExtendedResults /ExtendedResult / Extension (0,N)

Extensions of ResultItem if required.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Result /ResultItems /ResultItem /Result /RecordIndicators /RecordIndicator (1,N)

Result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

Y

Send Y in the case that the record has been equalled else do not send.

 

Element: Result /Competitor (1,1)

Competitor related to one cumulative result.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Or Organisation code in the case of NOC or NPC

Competitor's ID

Type

M

T,A, N

T for team

A for athlete

N for NOC or NPC

Bib

O

See table comment

Bib number

Organisation

M

CC @Organisation

Competitor's organisation

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

 

Element: Result /Competitor /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups. Not usually for pairs (figure skating & beach volleyball are the exceptions).

IFId

O

S(16)

International Federation ID

 

Element: Result /Competitor /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: Result /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete's ID, corresponding to either a team member or a single athlete

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

See table comment

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: Result /Competitor /Composition /Athlete /Description (1,1)

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Result /Competitor /Composition /Athlete /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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member's or individual athlete's extended result, depending on whether Competitor @Type="T" or Competitor @Type="A".

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /Extension (0,N)

Extensions of team member's or individual athlete's extended results.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.12.6 Message Sort

The ResultItems should be ordered in the same order in which they took place, earliest to latest.

 

Result @SortOrder will be the attribute used to sort the results, as the attribute @SortOrder is defined in each of the ODF Sport Data Dictionaries. Other @Order attributes will usually be used to order the rest of elements, as these elements are being requested in each of the ODF Sport Data Dictionary Documents.

 

Where the order is not otherwise defined by the sport, during a unit (particularly units where athletes participate one-by-one). Then the order should be:

1) All athletes finished the current unit ordered by overall rank

2) All athletes on course (in the order of their result at the intermediate; in case of several intermediates from the one further down the course to the one nearest to the start)

3) All athlete still to start in the current unit (start order)

4) All athletes not qualified, but having a score from previous units

5) All athletes with IRM (sorting according to Discipline/ORIS standard order)

 

2.1.13 Pool Standings

2.1.13.1 Description

The Pool Standings message contains the standings of a group in a competition. It is similar to the Phase Results message, except in the frequency and trigger. Here the message is triggered at the start of OVR operations and then after each event unit (game, match, etc.).

 

This report is sent independently for each of the groups / pools of the competition in a particular phase, and the group / pool can be determined from the message headers (DocumentCode and DocumentSubtype).

 

The mandatory attributes and mandatory elements defined in this message will have to be used by all the sports, although each ODF Sport Data Dictionary will have to explain with further detail the optional attributes or optional elements of the message.

2.1.13.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (at phase level)

Full Phase level RSC

DocumentSubcode

S(34)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentCode.

DocumentType

DT_POOL_STANDING

Pool Standings message

DocumentSubtype

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType.

Version

1..V

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

ResultStatus

SC @ResultStatus

Status of the message. Expected statuses are:

INTERMEDIATE (during the phase)

UNCONFIRMED (if last match is unconfirmed)

UNOFFICIAL (if last match is unofficial)

OFFICIAL (after all matches official)

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

The general rule is that this message is sent:

 

* Before the start of the competition to build in the initial tables. The message has status INTERMEDIATE

 

* When an event unit of the corresponding phase finishes (not waiting for official). The message has status INTERMEDIATE.

 

* When the phase finishes (there are no more event units/games to compete). The message has status OFFICIAL

 

The status can be seen in ODF header (ResultStatus attribute).

 

Trigger also after any change.

 

However, if there is any kind of sport specific rule, overwrite it in each of the ODF Sport Data Dictionaries.

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

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

SubEventName

 

Gender

 

VenueDescription  (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Result (1,N)

 

Rank

 

RankEqual

 

ResultType

 

Result

 

IRM

 

QualificationMark

 

SortOrder

 

Won

 

Lost

 

Tied

 

Played

 

For

 

Against

 

Diff

 

Ratio

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

RecordIndicators (0,1)

 

RecordIndicator (1,1)

 

Order

 

Code

 

RecordType

 

Equalled

 

Competitor (1,1)

 

Code

 

Type

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Opponent  (0,N)

 

Type

 

Pos

 

Code

 

Organisation

 

Date

 

Time

 

Unit

 

HomeAway

 

Result

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

IRM

 

Rank

 

RankEqual

 

SortOrder

 

Diff

 

Extension (0,N)

 

Code

 

Pos

 

Value

2.1.13.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (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 /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 /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

SubEventName

O

S(40)

Phase level short name (not code) from Common Codes. Only include if in single phase.

Gender

M

CC @DisciplineGender

Gender code for the event unit

 

Element: ExtendedInfos /VenueDescription (0,1)

Venue Names in Text. Only included where the phase is contested at a single venue

Attribute

M/O

Value

Description

Venue

M

CC @VenueCode

Venue Code

VenueName

M

S(25)

Venue short name (not code) from Common Codes

Location

O

CC @Location

Location code

LocationName

O

S(30)

Location short name (not code) from Common Codes

 

Element: Result (1,N)

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

Attribute

M/O

Value

Description

Rank

O

Text

 

See table comment

Rank of the competitor in the pool.

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute

Result

O

See table comment

The result of the competitor in the pool, usually the points scored

IRM

O

See table comment

The invalid result mark, in case it is assigned

QualificationMark

O

See table comment

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

SortOrder

M

Numeric

 

See table comment

Unique sort order for result in the pool, based on rank to break rank ties.

Won

O

Numeric

 

See table comment

Number of matches or games won

Lost

O

Numeric

 

See table comment

Number of matches or games lost

Tied

O

Numeric

 

See table comment

Number of matches or games tied

Played

O

Numeric

 

See table comment

Number of matches or games played by the competitor

For

O

Numeric

 

See table comment

Points/Goals achieved by the competitor

Against

O

Numeric

 

See table comment

Points/Goals against the competitor

Diff

O

See table comment

Difference between For and Against, see sports documents for more information.

Ratio

O

See table comment

Ratio value, see sports documents for more information

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

 

Element: Result /ExtendedResults /ExtendedResult (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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /RecordIndicators /RecordIndicator (1,1)

Result's record indicator.

Attribute

M/O

Value

Description

Order

M

Numeric

The hierarchy (priority) for types of record from 1 to n. Can use the Order column from CC @RecordType for reference).

Code

M

CC @RecordCode

Code which describes the record broken by the result value.

RecordType

M

CC @RecordType

Code which specifies the level at which the record is broken.

Equalled

O

S(1)

Send Y in the case that the record has been equalled else do not send.

 

Element: Result /Competitor (1,1)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

T,A

T for team

A for athlete

Organisation

M

CC @Organisation

Competitor's organisation

 

Element: Result /Competitor /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Result /Competitor /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: Result /Competitor /Composition /Athlete (1,N)

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

Order

M

Numeric

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

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

 

Element: Result /Competitor /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Result /Competitor /Composition /Athlete /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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member's or individual athlete's extended result, depending on whether Competitor @Type="T" or Competitor @Type="A".

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

S(1)

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /Extension (0,N)

Extensions of team member's or individual athlete's extended results.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Result /Competitor /Opponent (0,N)

Details of the opposing competitor in competitions within the pool. (The Opponent of the competitor in the Opponent @Pos column of the Pool)

Attribute

M/O

Value

Description

Type

M

T,A

T for team

 

A for athlete

Pos

M

Numeric

1 to n. Normally expected to be the same as SortOrder for the same competitor.

Code

M

S(20) with no leading zeroes

Competitor ID or TBD if unknown

Organisation

M

CC @Organisation

Competitor's organisation (code). Must include if the data is available

Date

M

Date

Date of match between the competitor and opponent (example: YYYY-MM-DD). Must include if the data is available, send even after the match is complete.

Time

O

S(5)

Time of match (example HH:MM) Must include if the data is available, send even after the match is complete.

Unit

O

CC @Unit

Full RSC of the Unit for the Pool Item

HomeAway

O

S(1)

Home / Away indicator. Send H if the opponent is the home team, send A if the opponent is the away team.

Result

O

S(50)

Result of the match if match is complete and formatted as in ORIS (separator & order, example 5-2). Must include if the data is available and the match is complete. The order of the result data is relative to the competitor and may be reversed for other competitor or depending on home/away display rules.

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

 

Element: Result /Competitor /Opponent /ExtendedResults /ExtendedResult (1,N)

Extensions of oppositions extended results.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

Y

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult)

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /Competitor /Opponent /ExtendedResults /ExtendedResult /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: Result /Competitor /Opponent /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the opposition team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Result /Competitor /Opponent /Description /ExtendedDescription (0,N)

Extensions of oppositions extended results.

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: Result /Competitor /Opponent /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athletes ID, corresponding to either a team member or an individual athlete

Order

M

Numeric

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

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

 

Element: Result /Competitor /Opponent /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Result /Competitor /Opponent /Composition /Athlete /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: Result /Competitor /Opponent /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member's or individual athlete's extended result, depending on whether Competitor @Type="T" or Competitor @Type="A".

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

IRM

O

See sport specific definition

Send appropriate IRM code if IRM at this ExtendedResult

Rank

O

See sport specific definition

Rank of the competitor for this specific ExtendedResult.

RankEqual

O

S(1)

Send Y where Rank at this specific ExtendResult is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this ExtendedResult

Diff

O

See sport specific definition

Time/Points etc behind leader at this ExtendedResult

 

Element: Result /Competitor /Opponent /Composition /Athlete /ExtendedResults /ExtendedResult /Extension (0,N)

Extensions of team member's or individual athlete's extended results.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.13.6 Message Sort

The attribute used to sort the results is Result @SortOrder.

 

2.1.14 Brackets

2.1.14.1 Description

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

2.1.14.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (event level)

Full RSC of the Event

DocumentType

DT_BRACKETS

Brackets message

Version

1..V

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

ResultStatus

SC @ResultStatus

Status of the message. Expected statuses are:

START_LIST (before any unit is complete)

INTERMEDIATE (during the competition)

UNCONFIRMED (when last match unconfirmed)

UNOFFICIAL (when last match unofficial)

OFFICIAL (when all matches official)

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

This message should be sent at the very beginning of a competition, as soon as brackets are available.

 

Send when a match/event unit is completed, including Unconfirmed, Unofficial and Official status. Therefore it is triggered up to three times (with both status) for each event unit (if unofficial is used). The message should be updated including information on each competitor in the different bracket items.

 

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

 

* Send with ResultStatus = "START_LIST" if no units are complete

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

* Send with ResultStatus = "UNCONFIRMED" when the last event unit for an event (Gold Medal match) has Unconfirmed status.

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

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

 

Trigger also after any change.

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

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

Gender

 

VenueDescription (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Bracket (1,N)

 

Code

 

BracketItems (1,N)

 

Code

 

BracketItem (1,N)

 

Code

 

Order

 

Date

 

Time

 

Unit

 

Result

 

NextUnit

 

NextUnitLoser

 

ExtBracketItems (0,1)

 

ExtBracketItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

CompetitorPlace (1,N)

 

Pos

 

Code

 

WLT

 

Result

 

IRM

 

ExtCompPlaces (0,1)

 

ExtCompPlace (1,N)

 

Type

 

Code

 

Pos

 

Value

 

PreviousUnit (0,1)

 

Unit

 

Value

 

WLT

 

Competitor (0,1)

 

Code

 

Type

 

Seed

 

Organisation

 

Bib

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtBracketComps (0,1)

 

ExtBracketComp (1,N)

 

Type

 

Code

 

Pos

 

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)

 

Type

 

Code

 

Pos

 

Value

 

ExtBracketAths (0,1)

 

ExtBracketAth (1,N)

 

Type

 

Code

 

Pos

 

Value

2.1.14.5 Message Values

 

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 /SportDescription (0,1)

Sport Description 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

 

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

O

CC @Location

Location Code

LocationName

O

S(30)

Location short name (not code) from Common Codes

 

Element: Bracket (1,N)

Attribute

M/O

Value

Description

Code

M

See table comment

Bracket code to identify a bracket item (finals, classification games...). There should be a different code for each bracket based on sport/ORIS presentation of the bracket. For example bronze bracket is a different code from that leading to gold (assuming there are matches played)

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

 

Element: Bracket /BracketItems (1,N)

Attribute

M/O

Value

Description

Code

M

See table comment

Bracket code to identify a set of bracket items. It usually refers to the round in the brackets, for example quarterfinal or semifinal etc.

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

 

Element: Bracket /BracketItems /BracketItem (1,N)

Attribute

M/O

Value

Description

Code

O

See table comment

Bracket code to identify a bracket item. Unique identifier for the BracketItem.

Order

M

Numeric

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

Date

O

Date

Date of match (example: YYYY-MM-DD). Must include if the data is available

Time

O

S(5)

Time of match (example HH:MM).

Include if the data is available, however in disciplines where match times are determined depending on the participating competitors then the time is withheld until after competitors are known and the times are approved.

Unit

O

CC @Unit

Full RSC of the unit for the BracketItem

Result

O

S(50)

Result of the match if the match is complete and formatted as in ORIS (separator & order, example 5-2). Must include if the data is available and the match is complete

NextUnit

O

CC @Unit

Full RSC of the unit where the successful competitor will progress

NextUnitLoser

O

CC @Unit

Full RSC of the unit where the unsuccessful competitor will progress

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

 

Element: Bracket /BracketItems /BracketItem /ExtBracketItems /ExtBracketItem (1,N)

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

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: Bracket /BracketItems /BracketItem /CompetitorPlace (1,N)

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

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

Attribute

M/O

Value

Description

Pos

M

Numeric

###

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

Code

O

See table comment

Code for the first competitor of the BracketItem, usually to indicate the rule to access to the bracket item and appearing as first competitor.

WLT

O

See table comment

W or L, indicates the winner or loser of the bracket item. Always send when known

Result

O

See table comment

The result of the competitor in the event unit

IRM

O

See table comment

The invalid rank mark, if applicable

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

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /ExtCompPlaces /ExtCompPlace (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

 

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /PreviousUnit (0,1)

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

Attribute

M/O

Value

Description

Unit

O

Full RSC (unit level)

Full RSC code of the previous event unit for the CompetitorPlace@Pos competitor of the bracket item. Must send if a winner/loser from a single unit.

Value

O

SC@Pool or S(2)

If the competitor in the current unit is unknown due to coming from pools or previous matches then fill this field with the code of the pool or the match number as appropriate. (may be redefined by sport)

WLT

O

W or L

If the competitor in the current unit is unknown and coming from an earlier bracketitem then fill this field with the W or L indication winner or loser of the previous unit if the information is known. Do not send if competitor comes from a pool.

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor (0,1)

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

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

T, A

T for team

A for athlete

Seed

O

S(10)

The seed of the competitor or equivalent information

Organisation

O

CC @Organisation

Competitors' organisation if known.

Bib

O

Defined by Discipline

Competitor Bib

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /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: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /ExtBracketComps /ExtBracketComp (1,N)

CompetitorPlace @Pos team competitor's extended bracket information, according to competitors' rules.

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: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /Composition /Athlete (1,N)

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

Order

M

Numeric

See table comment

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

Bib

O

Defined by Discipline

Athlete Bib

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

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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

GuideGivenName

O

S(25)

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

 

Element: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /Composition /Athlete /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: Bracket /BracketItems /BracketItem /CompetitorPlace /Competitor /Composition /Athlete /ExtBracketAths /ExtBracketAth (1,N)

CompetitorPlace @Pos team member's or individual athlete's extended bracket information, depending on whether Competitor @Type="T" or Competitor @Type="A" according to competitors' rules.

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.14.6 Message Sort

The following order applies:

* Every ODF Sport Data Dictionary making use of this message should specify the order for Bracket @Code if more than one "@Code" is possible.

* Every ODF Sport Data Dictionary should specify the order for BracketItems according to its @Code attribute. It will usually be referred to BracketItems /BracketItem /Unit (all BracketItem should be grouped by the BracketItem /Unit attribute).

* Then, the BracketItem /Unit are sorted according to their scheduled start time.

 

2.1.15 Statistics

2.1.15.1 Description

The Statistics message contains a list of statistics for a competitor (could be an individual athlete or a team), that applies at a DocumentCode level, which could be for an event unit, a phase or an event.

 

There will be a separate message (identified by the header's DocumentSubtype and DocumentSubcode) for every table where multiple statistics apply.

2.1.15.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

Depending on the statistics it could be at any level

DocumentSubcode

To be defined in each ODF Data Dictionary

Extension for the DocumentCode.

This is an optional attribute.

It is used when the RSC is not enough and it is required several different messages with the same RSC.

Each ODF Sport Data Dictionary will have to complete the explanation regarding to this attribute (it can be useful for example to separate statistics by Organisation).

DocumentType

DT_STATS

Statistics message

DocumentSubtype

S(20)

To be defined in each ODF Data Dictionary

Attribute used to extend DocumentType for some 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 intermediate etc).

LIVE (used during the competition when nothing else applies)

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

OFFICIAL (after the last unit which effects the statistics is official)

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

Each ODF Sport Data Dictionary should specify when to make use of this message, if necessary though the general rule is trigger as soon as each unit is finished (UNCONFIRMED) and on each change in the statistics.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

Gender

 

VenueDescription (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Stats (1,1)

 

Code

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

 

Competitor (0,N)

 

Code

 

Type

 

Order

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ValueType

 

Rank

 

RankEqual

 

SortOrder

 

ExtendedStat (0,N)

 

Code

 

Pos

 

Value

2.1.15.5 Message Values

 

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 /SportDescription (0,1)

Sport Description in Text

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name (not code) from Common Codes

EventName

O

S(40)

Event name (not code) from Common Codes.

Gender

O

CC @DisciplineGender

Gender code for the event unit

 

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

O

CC @Location

Location Code

LocationName

O

S(30)

Location short name (not code) from Common Codes

 

Element: Stats (1,1)

Attribute

M/O

Value

Description

Code

M

See table comment

A code to identify the statistics being listed.

 

It must be the same as the DocumentSubtype attribute in the header.

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

 

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

Statistics for the event unit / phase or event - depending on the headers' DocumentCode.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

Rank

O

See sport specific definition

Rank for this specific Item.

RankEqual

O

S(1)

Send Y where Rank at this specific Item is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all data including those without rank.

 

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

Extended information for the statistics for the event unit / phase or event – depending on the headers’ DocumentCode.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Stats /Competitor (0,N)

Competitor of the statistics.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID to be assigned a specific type of statistic.

 

The competitor should be participating in the event / phase / event unit depending on the DocumentCode in the message's header.

Type

M

T,A

T for team

A for athlete

Order

M

Numeric

Order of the competitor in the statistics

Organisation

O

CC @Organisation

Competitor's organisation if known

 

Element: Stats /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Stats /Competitor /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: Stats /Competitor /StatsItems /StatsItem (1,N)

Team competitor's stats item, according to competitors' rules.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

Rank

O

See sport specific definition

Rank of the competitor for this specific Item.

RankEqual

O

S(1)

Send Y where Rank at this specific Item is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this Item)

 

Element: Stats /Competitor /StatsItems /StatsItem /ExtendedStat (0,N)

Team competitor’s extended stat, according to competitors’ rules.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

 

Element: Stats /Competitor /Composition /Athlete (1,N)

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

Order

M

Numeric

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

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

 

Element: Stats /Competitor /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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

GuideGivenName

O

S(25)

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

 

Element: Stats /Competitor /Composition /Athlete /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: Stats /Competitor /Composition /Athlete /StatsItems /StatsItem (1,N)

Team member's or individual athlete's stats item, depending on whether Competitor @Type="T" or Competitor @Type="A" according to competitors' rules.

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

 

ValueType

O

See sport specific definition

ValueType should be used to describe the type of data @Value

Rank

O

See sport specific definition

Rank of the competitor for this specific Item.

RankEqual

O

S(1)

Send Y where Rank at this specific Item is equalled else not sent.

SortOrder

O

See sport specific definition

Similar to rank but considering all competitors (those with IRM or no rank at this Item)

 

Element: Stats /Competitor /Composition /Athlete /StatsItems /StatsItem /ExtendedStat (0,N)

Team member's or individual athlete's extended stat, depending on whether Competitor @Type="T" or Competitor @Type="A" according to competitors' rules.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.15.6 Message Sort

Sort according to the @Order attributes.

 

2.1.16 Records

2.1.16.1 Description

This message applies for all records depending on the sport.

The message contains the list of all records from the start of the Games (events depending on header).

 

Special Situations - Not Established Records:

There are some situations where there are no records for a particular event. This can happen,for example, when the sport rules change (different weights or distances) or new events are introduced.

If this occurs then the NotEstablished flag is used to indicate this situation.

If a record is established for this event in the current competition then the NotEstablished flag and description will not be sent when a new record is established.

2.1.16.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 of the Discipline

DocumentSubcode

CC @RecordCode

If the message is sent as a result of a record being modified (broken, equalled or re-instated) then this attribute will be included and is the Record Event for the modification.

DocumentType

DT_RECORD

Records message

DocumentSubtype

FULL,

PARTIAL

Send "FULL" if all records included.

Send "PARTIAL" if only one record code is included.

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

The DT_RECORD (without DocumentSubcode) message is sent as a bulk message (all records in a discipline) prior to the competition. Any new version of the DT_RECORD message should replace all previous record information, either for the RecordCode specified in DocumentSubcode or all if no DocumentSubcode is specified.

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

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

Record (1,N)

 

Code

 

Description (1,1)

 

Name

 

RecordType (1,N)

 

Order

 

RecordType

 

Subcode

 

Shared

 

NotEstablished

 

NotEstablishedLabel

 

RecordData (0,N)

 

Order

 

ResultType

 

Result

 

Unit

 

Country

 

Place

 

Date

 

Time

 

Equalled

 

Unconfirmed

 

Competition

 

Historical

 

Current

 

ModificationIndicator

 

Extension (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Competitor (0,1)

 

Code

 

Type

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Description (0,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtRecords (0,1)

 

ExtRecord (1,N)

 

Type

 

Code

 

Pos

 

Value

2.1.16.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (0,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

 

 

Element: 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: ExtendedInfos /SportDescription (0,1)

Sport Description in Text

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name (not code) from Common Codes

 

Element: Record (1,N)

Attribute

M/O

Value

Description

Code

M

CC @RecordCode

Record code. Send all record codes in the bulk message else this must match the DocumentSubcode, that is, only one per message.

 Sample (Individual Event)

<Record Code="ARCM70M72-------------------------">

<Description Name="Men 72 Arrows Ranking Round" />

<RecordType RecordType="WR" Order="1" Shared="N">

<RecordData Order="1" ResultType="POINTS" Result="699" Unit="ARCM70M---------------QUAL0001----" Country="GBR" Place="London" Date="2012-07-27" Time="105830427" Competition="The XXX Olympic Summer Games in 2012" Historical="N" Current="Y" ModificationIndicator="N" >

<Extension Code="XS_NUM" Value="22" />

<Competitor Code="1098720" Type="A" Organisation="NZL" >

<Composition>

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

<Description FamilyName="Smith" GivenName="John" Gender="M" Organisation="NZL" IFId="12920" BirthDate="1989-12-15" />

</Athlete>

</Composition>

</Competitor>

</RecordData>

</RecordType>

</Record>

 

 Sample (Not Established Record)

<Record Code="ATHM10000M------------------------">

<Description Name="10,000metres Men" />

<RecordType RecordType="FOR" Order="2" NotEstablished="Y" NotEstablishedLabel ="Not Established" Shared="N" >

</RecordType>

</Record>

 Sample (Teams)

<Record Code="ATHW4X100M------------------------">

<Description Name="Women's 4 x 100 metres Relay" />

<RecordType RecordType="WR" Order="1" Shared="N" >

<RecordData Order="1" ResultType="TIME" Result="36.84" Unit="ATHW4X100M------------FNL-0001----" Country="GBR" Place="London" Date="2012-08-11" Time="210600000" Competition="Olympic Games" Historical="N" Current="Y" ModificationIndicator="N" >

<Competitor Code="ATHW4X100M--JAM01" Type="T" Organisation="JAM" >

<Description TeamName="Jamaica" />

<Composition>

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

<Description FamilyName="Smith" GivenName="Joan" Gender="W" Organisation="JAM" BirthDate="1990-12-15" />

</Athlete>

<Athlete Code="1020467" Order="2" >

<Description FamilyName="Brown" GivenName="Mary" Gender="W" Organisation="JAM" BirthDate="1992-12-11" />

</Athlete>

<Athlete Code="1020433" Order="3" >

<Description FamilyName="White" GivenName="Jane" Gender="W" Organisation="JAM" BirthDate="1987-12-13" />

</Athlete>

<Athlete Code="1020434" Order="4" >

<Description FamilyName="Busby" GivenName="Barb" Gender="W" Organisation="JAM" BirthDate="1994-12-17" />

</Athlete>

</Composition>

</Competitor>

</RecordData>

</RecordType>

</Record>

 

 

Element: Record /Description (1,1)

Attribute

M/O

Value

Description

Name

M

S(40)

Record description (not code) from Common Codes

 

Element: Record /RecordType (1,N)

It is possible to have more than one element with the same type (as in the case of National Records).

Attribute

M/O

Value

Description

Order

M

Numeric

#0

The hierarchy (priority) for types of record from 1 to n.

(Can use the Order column from CC @RecordType to assist  in case several records are broken, from high priority to low priority but must still use 1 to n).

RecordType

M

CC @RecordType

Record type.

Subcode

O

- NOC if RecordType = "NR" or "NB"

- Rank if RecordType = "BOP", "ALL" or "SBP"

- WRC order if RecordType = "WRC"

 

It will be mandatory in case of RecordType = "NR", "NB", "BOP", "WRC", "ALL" and "SBP".

Shared

M

S(1)

Y-There is more than one competitor sharing the record

N-There is just one competitor holding the record

NotEstablished

O

S(1)

Send "Y" in the case there is no record in this category else do not send.

NotEstablishedLabel

O

S(25)

The description to be used in the case that NotEstablished="Y".

 

Element: Record /RecordType /RecordData (0,N)

RecordData is not sent for NotEstablished Records unless a "standard" applies

Attribute

M/O

Value

Description

Order

M

Numeric

#0

In the case that a record (RecordType) is provided several times in the message, then Order is the chronological order for the records (1,N). 1 will be usually the historical record and for each record broken during the competition a new order value will be provided. Usually first time the record is broken will have Order="2", second time Order="3" etc.

Send 1 for records (RecordType) not shared (historical records)

ResultType

M

See table comments

Indicates whether the record result is a distance, a time, etc.

Result

O

See table comments

Send always unless the record is not established (can be sent for not established if there is a standard).

The performance of the competitor for the record.

Unit

O

CC @Unit

Include the event unit in the current competition where the record was broken.

 

It is the full RSC

 

Send always (Mandatory) in the case Historical="N".

Country

O

CC @Country

Send always unless the record is not established.

Country code where the record was broken

Place

O

S(40)

Send always unless the record is not established.

Place (town or city) where the record was broken (example: "Salt Lake City").

Date

O

YYYY-MM-DD

Send always unless the record is not established.

Date when the record was broken (for the current competition, the date will be assumed to be the date scheduled for the @Unit attribute)

Time

O

Time

Time the record was set.

Send always (Mandatory) in the case of Historical="N".

Equalled

O

S(1)

Send "Y" if the existing record is equalled.

Do not send if the record is not equalled.

Unconfirmed

O

S(1)

Send only in the case that Historical="Y" and if it is required in the specific discipline, since some historical records / record types may not be confirmed.

Send "Y" if the record is Unconfirmed else do not send. The normal situation is do not send.

Competition

O

S(40)

Send the text of the competition name where the record was broken (example: "2013 World Championships", "2012 Olympic Games", etc.).

Historical

M

S(1)

Send "Y" if the record for competitor was not achieved during the current competition.

Send "N" if the record for the competitor was achieved during the current competition.

Current

O

S(1)

Send "Y" in the case that this is the current record else do not send (may be multiple in the case of a shared record).

ModificationIndicator

O

S(1)

The possible values are:

"N" = New broken record (not provided in a previous message)

"R" = This record is re-instated/re-established as the current record in this message (following an invalidation or similar).

Do not send this attribute for other records included in the message (not broken or not re-instated)

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

 

Element: Record /RecordType /RecordData /Extension (0,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

 

 

Element: Record /RecordType /RecordData /Competitor (0,1)

Competitor to whom the record is assigned.

Athlete's or team's information should be in DT_PARTIC (Historic) if Competitor @Type="A" or DT_PARTIC_TEAMS (Historic) if Competitor @Type="T".

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

S(1)

"T" for team

"A" for athlete

Organisation

O

CC @Organisation

Competitors' organisation if known

 

Element: Record /RecordType /RecordData /Competitor /Description (0,1)

Competitors extended information.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available.

 

Element: Record /RecordType /RecordData /Competitor /Description /ExtendedDescription (0,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

 

 

Element: Record /RecordType /RecordData /Competitor /Composition /Athlete (1,N)

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

Order

M

Numeric

#0

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

 

Element: Record /RecordType /RecordData /Competitor /Composition /Athlete /Description (0,1)

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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 in the record, used for some athletes with a disability (e.g: Paralympic Games).

GuideFamilyName

O

S(25)

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

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

GuideGivenName

O

S(25)

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

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

 

Element: Record /RecordType /RecordData /Competitor /Composition /Athlete /Description /ExtendedDescription (0,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

 

 

Element: Record /RecordType /RecordData /Competitor /Composition /Athlete /ExtRecords /ExtRecord (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

 

2.1.16.6 Message Sort

The following order applies:

- Record @Code

- RecordType @Order

- RecordData @Order

 

2.1.17 Event Final Ranking

2.1.17.1 Description

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

 

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

 

The mandatory attributes and mandatory elements defined in this message will have to be used by all the sports, although each ODF Sport Data Dictionary will have to explain with further detail the optional attributes or optional elements of the message.

 

Depending on the sport rules include all competitors in the competition as all can be ranked (as in Marathon) or only include those with a final ranking as other are unranked (as in tennis).

2.1.17.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC of the Event

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

DocumentType

DT_RANKING

Event Final ranking message

Version

1..V

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

ResultStatus

SC @ResultStatus

Result status, indicates whether the data is official or partial.

OFFICIAL

PARTIAL

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

This message is only triggered after a unit which affects the final ranking is official and that particular ranking is not subject to change.

Specific triggering conditions are defined in the sport data dictionary.

Trigger also after any major change.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

Gender

 

VenueDescription (0,1)

 

Venue

 

VenueName

 

Result (1,N)

 

Rank

 

RankEqual

 

ResultType

 

Result

 

Diff

 

Played

 

Won

 

Lost

 

Tied

 

IRM

 

SortOrder

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Competitor (1,1)

 

Code

 

Type

 

Organisation

 

Bib

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (1,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

2.1.17.5 Message Values

 

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 /SportDescription (0,1)

Sport Description in text

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name (not code) from Common Codes

EventName

O

S(40)

Event name (not code) from Common Codes. Must be included if it is a single event

Gender

O

CC @DisciplineGender

Gender code for the event unit. Must be included if it is a single gender

 

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

 

Element: Result (1,N)

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

Attribute

M/O

Value

Description

Rank

O

Text

 

See table comment

Rank of the competitor in the result.

RankEqual

O

Y

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

ResultType

O

See table comment

Type of the @Result attribute

Result

O

See table comment

The result of the competitor in the event

Diff

O

See table comment

Display the time / value behind the leader.

Played

O

Numeric

Number of matches played by the competitor in the event

Won

O

Numeric

Number of matches won by the competitor in the event

Lost

O

Numeric

Number of matches lost by the competitor in the event

Tied

O

Numeric

Number of matches tied by the competitor in the event

IRM

O

See table comment

The invalid result mark, in case it is assigned

SortOrder

M

Numeric

 

See table comment

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

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

 

Element: Result /ExtendedResults /ExtendedResult (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

 

 

Element: Result /ExtendedResults /ExtendedResult /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: Result /Competitor (1,1)

Competitor related to one final event result.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes, NOC ID

Competitor's ID.

If NOC or NPC, the value will be NOC ID.

"NOCOMP" in the case where there is no competitor in the rank due to IRM.

Type

M

T,A

T for team

A for athlete

Organisation

O

CC @Organisation

Competitor's organisation if known

Bib

O

Defined by Discipline

Competitor Bib

 

Element: Result /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Result  /Competitor /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: Result /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete's ID, corresponding to an individual athlete or a team member.

 

Team members should be participating in the event.

Order

M

Numeric

See table comments

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

Bib

O

Defined by Discipline

Athlete Bib

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

 

Element: Result  /Competitor /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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

GuideGivenName

O

S(25)

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

 

Element: Result /Competitor /Composition /Athlete /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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult (1,N)

Team member's or individual athlete's extended result, depending on whether Competitor @Type="T" or Competitor @Type="A" according to competitors' rules.

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: Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult /Extension (0,N)

Extensions of team member's or individual athlete's extended results.

Attribute

M/O

Value

Description

Code

O

See sport specific definition

 

Pos

O

See sport specific definition

 

Value

O

See sport specific definition

 

2.1.17.6 Message Sort

Sort by Result @SortOrder

 

2.1.18 Communication

2.1.18.1 Description

The Communication message contains a release of a Communication, which may be an Official Communication, Sport Communication or similar, which contains jury decisions, competition management decisions, etc.

Communications are numbered by sport separately, not globally.

2.1.18.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC of the Discipline

 

DocumentSubcode

Numeric

This is the Communication number.

Send incremental number in the case that DocumentSubtype is NOTICE, SPORT_NOTICE, COMPETITOR_NOTICE or PROTEST (one for each different Item) unless defined differently by sport.

DocumentType

DT_COMMUNICATION

Official communication message

DocumentSubtype

NOTICE

SPORT_NOTICE

COMPETITOR_NOTICE

PROTEST

ON_WATER

LIMIT

For all sports:

* NOTICE: Used for Official Communications

* SPORT_NOTICE: Used for Sport Communications

* COMPETITOR_NOTICE : Use for notifications to competitors

* PROTEST: Protest type (Except protest by Rule 42), only for Sailing.

* ON_WATER: On the water Penalties, only for Sailing.

* LIMIT: Protest Time Limit, only for Sailing

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

The message should be generated as soon as the information is available.

 

Trigger also after any change.

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

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

EventName

 

SubEventName

 

Gender

 

VenueDescription (0,1)

 

Venue

 

VenueName

 

Location

 

LocationName

 

Communication (1,1)

 

PublishTime

 

Decision (0,1)

 

ItemNum

 

IssuedTime

 

AffectsRES

 

AffectsSCH

 

AffectsOTH

 

Unit

 

Subtitle (0,1)

 

-

 

Summary (0,1)

 

-

 

Details (0,1)

 

-

 

IssuedBy (0,1)

 

-

 

SignedBy (0,2)

 

Code

 

FamilyName

 

GivenName

 

Function

 

Order

 

ExtendedComms (0,1)

 

ExtendedComm (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Protest (0,1)

 

Status

 

HearingTime

 

DecisionTime

 

Protestor

 

Protestee

 

Witness

 

Interpreter

 

Rule

 

Unit

 

Type (1,1)

 

-

 

Details (1,1)

 

-

 

DecisionShort (1,1)

 

-

 

DecisionLong (1,1)

 

-

 

Description (1,1)

 

-

 

FactsFound (1,1)

 

-

 

Conclusion (1,1)

 

-

 

Jury (1,N)

 

Code

 

FamilyName

 

GivenName

 

Order

 

SignedBy (0,1)

 

Code

 

FamilyName

 

GivenName

 

Function

 

ImageData (0,1)

 

-

2.1.18.5 Message Values

 

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 /SportDescription (0,1)

Sport Description in Text

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name

from Common Codes

EventName

O

S(40)

Event name from Common Codes

SubEventName

O

S(40)

EventUnit short name (not code) from Common Codes. Only include if single unit affected

Gender

O

CC @DisciplineGender

Gender code for the event unit

 

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

O

CC @Location

Location Code

LocationName

O

S(30)

Location short name (not code) from Common Codes

 

Element: Communication (1,1)

Attribute

M/O

Value

Description

PublishTime

M

DateTime

Date and time in which the communication is published.

 

Example:

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

 

Element: Communication /Decision (0,1)

Mandatory for DocumentSubtype NOTICE, COMPETITOR_NOTICE and SPORT_NOTICE.

 

The DocumentSubtype is always NOTICE, COMPETITOR_NOTICE or SPORT_NOTICE, except for Sailing where it is redefined in the ODF Sport Data Dictionary document.

Attribute

M/O

Value

Description

ItemNum

O

String

 

See table comment

Sport dependent, item number if applicable

IssuedTime

O

DateTime

Decision date and time. (Mandatory in the case of NOTICE, SPORT_NOTICE, COMPETITOR_NOTICE)

 

Example:

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

AffectsRES

O

Y, N

'Y' - The jury decision affects the results

'N' - The jury decision does not affect the results

Mandatory in the case of DocumentSubtype is NOTICE

AffectsSCH

O

Y, N

'Y' - The jury decision affects the schedules

'N' - The jury decision does not affect the schedules

Mandatory in the case of DocumentSubtype is NOTICE

AffectsOTH

O

Y, N

'Y' - The jury decision affects other areas

'N' - The jury decision does not affect other areas

Mandatory in the case of DocumentSubtype is NOTICE

Unit

O

CC @Unit

Full Unit RSC

Sent if the official communication applies to the gender, event, phase, or unit level. (can be at any level)

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

 

Element: Communication /Decision /Subtitle (0,1)

Attribute

M/O

Value

Description

-

M

Free Text

Communication Subtitle. It is the title placed in the ORIS report next to "Official Communication"

 

Element: Communication /Decision /Summary (0,1)

Attribute

M/O

Value

Description

-

M

Free Text

Summary of the communication. Should contain the event description.

 

Element: Communication /Decision /Details (0,1)

Attribute

M/O

Value

Description

-

M

Free Text

Body of the communication. Include the description.

 

Element: Communication /Decision /IssuedBy (0,1)

Attribute

M/O

Value

Description

-

M

Free Text

Communication author

 

Element: Communication /Decision /SignedBy (0,2)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

ID of the Signed Name, to uniquely identify this element

FamilyName

O

S(25)

Family name of the person associated to the sign

GivenName

O

S(25)

Given name of the person associated to the sign

Function

M

S(30)

Decision of the Function of the Signed person

Order

M

Numeric

Send official order

 

Element: Communication /Decision /ExtendedComms /ExtendedComm (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

 

 

Element: Communication /Decision /ExtendedComms /ExtendedComm /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: Communication /Protest (0,1)

Attribute

M/O

Value

Description

Status

M

SC @ProtestStatus

Status of protest

HearingTime

O

DateTime

Hearing time

 

Example:

2012-07-26T10:00:00+01:00

DecisionTime

O

DateTime

Protest Decision Time

Example:

2012-07-26T10:00:00+01:00

Protestor

O

Free text

 

Protestee

O

Free text

 

Witness

O

Free text

 

Interpreter

M

Y or N

Interpreter required

Rule

M

String

Rule applicable

Unit

O

CC @Unit

Full RSC at unit level

Sent if the protest applies to the gender, event, phase, or unit level. (can be at any level)

 

Element: Communication /Protest /Type (1,1)

Attribute

M/O

Value

Description

-

O

Free text

Type of protest.

Denotes the different options.

 

Element: Communication /Protest /Details (1,1)

Attribute

M/O

Value

Description

-

M

Free text

Protest details

 

Element: Communication /Protest /DecisionShort (1,1)

Attribute

M/O

Value

Description

-

M

Free text

Decision short

 

Element: Communication /Protest /DecisionLong (1,1)

Attribute

M/O

Value

Description

-

M

Free text

Decision

 

Element: Communication /Protest /Description (1,1)

Attribute

M/O

Value

Description

-

O

Free text

Description of the incident

 

Element: Communication /Protest /FactsFound (1,1)

Attribute

M/O

Value

Description

-

M

Free text

Facts Found

 

Element: Communication /Protest /Conclusion (1,1)

Attribute

M/O

Value

Description

-

O

Free text

Conclusion

 

Element: Communication /Protest /Jury (1,N)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Official ID

FamilyName

O

S(25)

Family name of the Jury

GivenName

O

S(25)

Given name of the Jury

Order

O

Numeric

Order of the official, if more than one official. Send 1 if only one.

 

Element: Communication /Protest /SignedBy (0,1)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Key of the Signed Name, to uniquely identify this element

FamilyName

O

S(25)

Family name of the person associated to the sign

GivenName

O

S(25)

Given name of the person associated to the sign

Function

M

CC @ResultsFunction

Function of the Signed person

 

Element: Communication /ImageData (0,1)

Attribute

M/O

Value

Description

-

M

Text

The ImageData element contains a body consisting of one Base64-encoded PNG or JPG file.

2.1.18.6 Message Sort

There are no specific sorting requirements

 

2.1.19 Configuration

2.1.19.1 Description

The Configuration is a message containing general configuration.

 

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

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

DocumentType

DT_CONFIG

Configuration message

Version

1..V

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

FeedFlag

"P"-Production

"T"-Test

Test message or production message.

Date

Date

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

Time

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

The message is sent prior to any ODF Sports message, if requested by one particular discipline (ODF Sport Data Dictionary).

 

Depending on the data required in this message (sport by sport) the sport data dictionary may add or modify the triggering requirements.

 

Trigger also after any major change, but considering that, if possible, the configuration for one particular event, phase or event unit must be provided before the start list. If a DT_CONFIG message is sent after a DT_RESULT in a related unit then the next version of DT_RESULT must be sent immediately.

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

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Configs (1,1)

 

Config (1,N)

 

Unit

 

ExtendedConfig (1,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtendedConfigItem (0,N)

 

Code

 

Pos

 

Value

2.1.19.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (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

 

 

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: Configs /Config (1,N)

Attribute

M/O

Value

Description

Unit

O

CC @Unit

Full RSC of the Unit. Can be at gender, phase or unit level (do not send if at discipline level).

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

 

Element: Configs /Config /ExtendedConfig (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

 

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

 

Element: Configs /Config /ExtendedConfig /ExtendedConfigItem (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

2.1.19.6 Message Sort

There is no general message sorting rule.

 

2.1.20 Federation Ranking

2.1.20.1 Description

The Federation Ranking is a message containing the rankings in a discipline. The rankings may be over the whole discipline or divided by event as appropriate for the discipline. One message may contain a single event or multiple events.

 

Rankings may be based on some points system and updated at fixed points or based on single performances and updated with each new performance.

 

Rankings may be for a fixed period, for example a calendar year or be taken over a rolling period.

2.1.20.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

Full RSC code.

-If the message contains data for only one event then the RSC will be at event level.

-If the message includes ranking for more than one event (Rankings appears multiple times) then the document code will be at discipline level.

-If the message includes ranking for more than one event in a single gender (Rankings appears multiple times) then the document code will be at discipline gender level.

DocumentSubcode

S(10)

Provides greater granularity for document if DocumentCode is not sufficient.

DocumentType

DT_FED_RANKING

Federation ranking message

DocumentSubtype

S(20)

Federation Ranking type. To be defined in each ODF Data Dictionary as needed.

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

Triggers in rankings are usually manual as the ranking may be distributed when updates are complete from multiple competitions or at fixed points in time. As a result each discipline defines its own triggers.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

DateTime (1,1)

 

Update

 

PreviousUpdate

 

NextUpdate

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DesciplineName

 

Rankings (1,N)

 

Code

 

Description

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Code

 

Pos

 

Type

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

ListComp (0,N)

 

Date

 

Place

 

Country

 

Pos

 

AddInfo

 

Status

 

Ranking (1,N)

 

Rank

 

RankEqual

 

Value

 

ValueType

 

PreviousValue

 

Movement

 

SortOrder

 

Competition

 

Date

 

Place

 

Country

 

ExtRanking (0,1)

 

ListComp (0,N)

 

Value

 

ValueType

 

Pos

 

Rank

 

RankEqual

 

Discarded

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

ExtRank (0,N)

 

Code

 

Pos

 

Type

 

Value

 

ValueType

 

Rank

 

RankEqual

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Competitor (1,1)

 

Code

 

Type

 

Current

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

 

Order

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

2.1.20.5 Message Values

 

Element: ExtendedInfos /DateTime (1,1)

Attribute

M/O

Value

Description

Update

M

Date

Applicable date for this version of the ranking.

PreviousUpdate

O

Date

Date of the previous version of the Federation Ranking if applicable

NextUpdate

O

Date

Date of the next scheduled update of the Federation Ranking if applicable

 

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 /SportDescription (0,1)

Attribute

M/O

Value

Description

DesciplineName

M

S(40)

Discipline name (not code) from Common Codes

 

Element: Rankings (1,N)

Attribute

M/O

Value

Description

Code

M

Full RSC

Full applicable RSC

Description

O

S(40)

Full name applicable to the code

 Sample (Athletics)

<Rankings Code="ATHW100M--------------------------" Description="Women's 100 metres" >

 

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

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: Rankings /ExtendedInfos /ExtendedInfo /Extension (0,N)

Attribute

M/O

Value

Description

Code

O

N/A

 

Pos

O

N/A

 

Value

O

N/A

 

 

Element: Rankings /ExtendedInfos /ListComp (0,N)

Attribute

M/O

Value

Description

Date

M

Date

Date when the related competition took place (starting date).

Place

O

S(40)

Place when the related competition took place.

Country

O

CC @Country

Country when the related competition took place.

Pos

M

Numeric

##0

Order for the related competitions

AddInfo

O

String

Additional related information

Status

O

String

Status of related competition (could be cancelled for example)

 Sample (Alpine Skiing)

<ListComp Date="2014-01-25" Place="Kitzbuhel" Country="AUT" Pos="6" />

 

Element: Rankings /Ranking (1,N)

Attribute

M/O

Value

Description

Rank

M

Defined by Discipline

Ranking related to performance or points as applicable

RankEqual

O

S(1)

Identifies if a rank has been equalled. Send 'Y' if applicable.

Value

O

Defined by Discipline

Performance value, usually actual performance or points.

ValueType

O

Defined by Discipline

 

PreviousValue

O

Defined by Discipline

Previous performance value, usually actual performance or points. Only if applicable.

Movement

O

Numeric

+##0 or

-##0

Change in rank since the last release of the ranking.

SortOrder

M

Numeric ###0

Unique sort order based on rank to break rank ties

Competition

O

S(40)

Name of the competition related to the ranking. Usually only applicable where rankings are performance based (not points)

Date

O

Date

Date of the competition related to the ranking. Usually only applicable where rankings are performance based (not points)

Place

O

S(40)

Place of the competition related to the ranking. Usually only applicable where rankings are performance based (not points)

Country

O

CC @Country

Country of the competition related to the ranking. Usually only applicable where rankings are performance based (not points)

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

 Sample (Athletics)

<Ranking Rank="2" Value="10.85" ValueType="TIME" SortOrder="2" Competition="Commonwealth Games" Place="Glasgow(Hampden Park)" Country="GBR" Date="2014-07-28">

 Sample (Alpine Skiing)

<Ranking Rank="1" Value="652" ValueType="POINTS" SortOrder="1">

 

Element: Rankings /Ranking /ExtRanking /ListComp (0,N)

Attribute

M/O

Value

Description

Value

O

Defined by Discipline

Performance value of the related competition

ValueType

O

N/A

 

Pos

O

Numeric

##0

Equivalent to the @Pos in the list of competitions.

Rank

O

Defined by Discipline

Rank in the related competition

RankEqual

O

S(1)

Send 'Y' if the rank is equalled else do not send.

Discarded

O

S(1)

Send 'Y' if the value is not counted else do not send.

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

 

Element: Rankings /Ranking /ExtRanking /ListComp /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: Rankings /Ranking /ExtRanking /ExtRank (0,N)

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

 

ValueType

O

SC @ResultType

 

Rank

O

Defined by Discipline

 

RankEqual

O

S(1)

Send 'Y' if the Rank is equalled else do not send

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

 

Element: Rankings /Ranking /ExtRanking /ExtRank /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: Rankings /Ranking /Competitor (1,1)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Competitor's ID

Mandatory for Type= "A" or "T"

Type

M

S(1)

T for team

A for athlete

N for NOC's or NPC's (in case of Organisation rank)

Current

M

S(1)

Can be redefined by discipline.

Usually send 'Y' if the competitor is taking part in the current competition or 'N' if not participating.

Organisation

O

CC @Organisation

Organisation ID

 

Element: Rankings /Ranking /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Rankings /Ranking /Competitor /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: Rankings /Ranking /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

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

Order

M

Numeric ##0

Send 1 for individual athlete; otherwise send the order of the team members within the team.

 

Element: Rankings /Ranking /Competitor /Composition /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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

GuideGivenName

O

S(25)

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

 

Element: Rankings /Ranking /Competitor /Composition /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

 

2.1.20.6 Message Sort

@Order attribute sorts each node whenever the attribute is informed.

 

2.1.21 Event Unit Weather conditions

2.1.21.1 Description

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

2.1.21.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

 

DocumentType

DT_WEATHER

Weather conditions in the match message

Version

1..V

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

FeedFlag

"P"-Production

"T"-Test

Test message or production message.

Date

Date

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

Time

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

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

2.1.21.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

Weather (1,1)

 

Conditions (1,N)

 

Code

 

Humidity

 

Wind_Direction

 

Prec_Type

 

Condition (0,3)

 

Code

 

Value

 

Precipitation (0,N)

 

Unit

 

Value

 

Pressure (0,N)

 

Unit

 

Value

 

Temperature (0,N)

 

Code

 

Unit

 

Value

 

Type

 

Wind (0,N)

 

Code

 

Unit

 

Value

 

Type

2.1.21.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (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

 

 

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: Weather /Conditions (1,N)

Attribute

M/O

Value

Description

Code

M

See table comment

Weather Points

Humidity

O

Numeric

##0

Humidity in %

Wind_Direction

O

CC @WindDirection

Wind direction

Prec_Type

O

SC @PrecType

Precipitation type

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

 

Element: Weather /Conditions /Condition (0,3)

Send three times in the case of Winter conditions.

Attribute

M/O

Value

Description

Code

M

SKY, SNOW, ICE

Weather conditions type

Value

M

CC @SnowConditions

Or

CC @WeatherCondition

Codes that describe the Weather Condition.

 

Element: Weather /Conditions /Precipitation (0,N)

Attribute

M/O

Value

Description

Unit

M

See table comment

Metric system unit for precipitation

Value

M

Numeric

###0.0

Precipitation quantity

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

 

Element: Weather /Conditions /Pressure (0,N)

Attribute

M/O

Value

Description

Unit

M

See table comment

Metric system unit for pressure

Value

M

Numeric

###0

Air pressure

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

 

Element: Weather /Conditions /Temperature (0,N)

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

Attribute

M/O

Value

Description

Code

M

AIR, SNOW, ICE, WAT, SAND

Air, Snow , Ice, Water and Sand temperature.

 

If available, Snow and Ice temperature are only mandatory in winter.

 

Water and Sand temperature are optional depending on the Discipline.

Unit

M

See table comment

Metric system unit for temperature

Value

M

Numeric

-##0.0 or

##0.0

Temperature in centigrade degrees (in case of positive temperature, do not send '+')

Type

O

See Table comment

Type of Temperature (like Maximum, Minimum, Normal, etc.)

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

 

Element: Weather /Conditions /Wind (0,N)

Attribute

M/O

Value

Description

Code

M

SPEED

Wind  Speed

Unit

M

See table comment

Metric system unit for Wind

Value

M

Numeric

##0.0

Wind speed value without plus or minus symbol

Type

O

See Table comment

 

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

2.1.21.6 Message Sort

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

 

2.1.22 Event's Medallists

2.1.22.1 Description

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

2.1.22.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (event level)

Full RSC at event level

DocumentType

DT_MEDALLISTS

Event's Medallists message

Version

1..V

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

ResultStatus

SC @ResultStatus

It indicates whether the result is official or partial.

OFFICIAL

PARTIAL

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

The message is sent with ResultStatus=PARTIAL when the information of the medallist is known but the final event Unit is not yet finished.

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

 

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

 

Trigger also after any major change.

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

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription  (0,1)

 

DisciplineName

 

EventName

 

Gender

 

VenueDescription (0,1)

 

Venue

 

VenueName

 

Medal (1,N)

 

Code

 

Unit

 

Date

 

Competitor (1,1)

 

Type

 

Code

 

Order

 

Bib

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Officials (0,1)

 

Official (1,N)

 

Code

 

Function

 

Order

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Nationality

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtCompMedals (0,1)

 

ExtCompMedal (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (1,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

ExtAthMedals (0,1)

 

ExtAthMedal (1,N)

 

Type

 

Code

 

Pos

 

Value

2.1.22.5 Message Values

 

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 /SportDescription (0,1)

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.

 

Element: ExtendedInfos /VenueDescription (0,1)

Attribute

M/O

Value

Description

Venue

M

CC @VenueCode

Venue Code

VenueName

M

S(25)

Venue short name (not code) from Common Codes

 

Element: Medal (1,N)

Attribute

M/O

Value

Description

Code

M

SC @MedalType

Medal type.

 

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

Unit

M

CC @Unit

Full RSC Unit code in which a medal was awarded.

 

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

Date

M

Date

The date of the most recent unit in which a medal was determined for this event. That is, if only the bronze medal competitor has been determined then this is the date of the bronze medal unit. If all medals are determined then this is the date of the gold medal unit. It is the date of the unit, not the date of the awarding of the medal or the date of a later change in the medallists (that is it will not change [except in the case of a re-run], even if the medallists do)

 

Element: Medal /Competitor (1,1)

Attribute

M/O

Value

Description

Type

M

T, A

T for team

A for athlete

Code

M

S(20) with no leading zeroes

Competitor's ID

Order

M

Numeric

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

Bib

O

See table comment

Bib number, send if available (team bib)

Organisation

M

CC @Organisation

Competitors' organisation

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

 

Element: Medal /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Medal /Competitor /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: Medal /Competitor /Officials /Official (1,N)

Officials in the case there are officials receiving event’s medals.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Official ID for the official code

Function

O

See table comment

Send official function

Order

O

See table comment

Send official order (if more than one official is needed). Send 1 if only one.

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

 

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

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 Code

Nationality

M

CC @Country

Coach's nationality

 

Element: Medal /Competitor /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: Medal /Competitor /ExtCompMedals /ExtCompMedal (1,N)

Team competitor’s  extended medals information, according to competitors’ rules.

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: Medal /Competitor /Composition /Athlete (1,N)

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

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

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

Order

M

Numeric

Order of the team members in a team if Competitor @Type="T".

 

1 if Competitor @Type="A".

Bib

O

See table comment

Bib number, send if available (shirt number in a team)

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

 

Element: Medal /Competitor /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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

GuideGivenName

O

S(25)

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

 

Element: Medal /Competitor /Composition /Athlete /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: Medal /Competitor /Composition /Athlete /ExtAthMedals /ExtAthMedal (1,N)

Team member’s or individual athlete’s extended result, depending on whether Competitor @Type="T" or Competitor @Type="A" according to competitors’ rules.

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.22.6 Message Sort

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

 

2.1.23 Medallists by discipline

2.1.23.1 Description

The Medallists by discipline is a message containing the list of medallists for one discipline, up to the moment the message is generated.

 

The Medallists by discipline message is a complete message that increments its content as more medals are being awarded during the competition. The arrival of this message resets the entire previous Medallists by discipline information.

2.1.23.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 of the Discipline

DocumentType

DT_MEDALLISTS_DISCIPLINE

Medallists by discipline

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

Medallists by Discipline message is sent as soon as one new medal is officially known (but not necessarily awarded) for any of the events that are part of the competition schedule. As the competition progresses, successive changes in the medallists by discipline information are made.

 

Trigger also after any major change.

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

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

 

SportDescription (0,1)

 

DisciplineName

 

Discipline (1,1)

 

Code

 

TotalEvents

 

FinishedEvents

 

Event (1,N)

 

Code

 

EventName

 

Date

 

Medal (1,N)

 

Code

 

Competitor (1,1)

 

Code

 

Type

 

Bib

 

Order

 

Organisation

 

Description (0,1)

 

TeamName

 

IFId

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Composition (1,1)

 

Athlete (1,N)

 

Code

 

Order

 

Bib

 

Description (1,1)

 

GivenName

 

FamilyName

 

Gender

 

Organisation

 

BirthDate

 

IFId

 

Class

 

Horse

 

GuideID

 

GuideFamilyName

 

GuideGivenName

 

ExtendedDescription (0,N)

 

Type

 

Code

 

Pos

 

Value

2.1.23.5 Message Values

 

Element: ExtendedInfos /ExtendedInfo (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

 

 

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 /SportDescription (0,1)

Sport Description in Text

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name (not code) from Common Codes

 

Element: Discipline (1,1)

Discipline information

Attribute

M/O

Value

Description

Code

M

Full RSC

Full RSC Discipline Code

TotalEvents

M

Numeric

Total number of competition events (events that award medals)

FinishedEvents

M

Numeric

Number of competition events that have awarded any type of medal, out of the total.

In case of sports with 2 matches have medals (Bronze and Gold), this attribute only counts when the Gold medal has been awarded (not counted for Bronze because the event has not finished yet).

 

Element: Discipline /Event (1,N)

Event information

Attribute

M/O

Value

Description

Code

M

CC @Event

Full RSC of the Event

EventName

M

S(40)

Event name (not code) from Common Codes

Date

M

YYYY-MM-DD

Date of the Gold medal match.

 

Element: Discipline /Event /Medal (1,N)

 

Attribute

M/O

Value

Description

Code

M

SC @MedalType

Medal type gold, silver or bronze. All the Competitors with the same CC@MedalType must not be grouped in the same element (it applies in the equalled medals)

 

Element: Discipline /Event /Medal /Competitor (1,1)

Competitor related to the medals.

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor's ID

Type

M

T,A

T forTeam A for Athlete

Bib

O

See table comment

Bib number, send if available (team bib)

Order

M

Numeric

Competitor order (Send 1 by default) and in the case of tie the order will be defined by the IOC rules.

Organisation

M

CC @Organisation

Competitors' organisation

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

 

Element: Discipline /Event /Medal /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

Team IF number, send if available

 

Element: Discipline /Event /Medal /Competitor /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: Discipline /Event /Medal /Competitor /Composition /Athlete (1,N)

 

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

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

Order

M

Numeric

Team member order for medal (according to each different sport rule). Send 1 if individul medal

Bib

O

See table comment

Bib number, send if available (shirt number in a team)

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

 

Element: Discipline /Event /Medal /Competitor /Composition /Athlete /Description (1,1)

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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

GuideGivenName

O

S(25)

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

 

Element: Discipline /Event /Medal /Competitor /Composition /Athlete /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

 

2.1.23.6 Message Sort

Events in the message will be sorted by discipline code and event code.

 

Within an event, medals will be sorted by medal type. Moreover, in case of tie or for the team's athletes, the order will be according to a medal order (given by each sport rule).

 

 

2.1.24 Medal Presenters

2.1.24.1 Description

The Medal Presenters message contains the information on who will present the medals for the events.

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

There is one message per event per venue containing all the information related to the presentation in the venue for that event. Updated as appropriate.

When both medals and flowers or mascot or other gifts are presented in the same ceremony:

DocumentSubType is VICTORY

When only flowers or mascot or other gifts are presented in the venue and the medals elsewhere:

If the awarded article is Flower then DocumentSubType is FLOWER

If the awarded article is mascot or other gift then DocumentSubType is MASCOT

When only medals are presented in the ceremony (Medals Plaza case or no other items):

DocumentSubType is MEDAL

2.1.24.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

CC @Unit

Full RSC of the scheduled event unit for the presentation (not competition event)

DocumentSubcode

CC @VenueCode

Venue code or the venue where the presentation will take place.

DocumentType

DT_PRESENTER

Presenters Message

DocumentSubtype

SC @PresenterType

Presenter subtype

Version

1..V

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

FeedFlag

S(1)

Refer to ODF header definition

Date

Date

Refer to ODF header definition

Time

Time

Refer to ODF header definition

LogicalDate

Date

Refer to ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.1.24.3 Trigger and Frequency

Trigger when the information is available about the presenters and for any changes.

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

 

ExtendedInfos (1,1)

 

SportDescription (0,1)

 

DisciplineName

 

VenueDescription (0,1)

 

Venue

VenueName

 

Presentation (1,N)

 

Event

EventName

Presenter (1,N)

 

Code

MedalRank

Function

Order

Description (1,1)

 

GivenName

FamilyName

Gender

Nationality

 

Detail (1,N)

 

Language

PresenterName

PresenterLongName

Role

Highlight

2.1.24.5 Message Values

Element: ExtendedInfos /SportDescription (0,1)

Attribute

M/O

Value

Description

DisciplineName

M

S(40)

Discipline name (not code) from Common Codes

 

Element: ExtendedInfos /VenueDescription (0,1)

Attribute

M/O

Value

Description

Venue

M

CC @VenueCode

Venue Code

VenueName

M

S(25)

Venue short name (not code) from Common Codes

 

Element: Presentation (1,N)

Attribute

M/O

Value

Description

Event

M

CC @Event

Full RSC of the event for the medal

EventName

O

S(40)

Short description of the event

 

Element: Presentation /Presenter (1,N)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

ID of the Presenter if the presenter was included in DT_PARTIC

MedalRank

O

Numeric

0

The rank of the medal 1, 2, 3 etc. or 0 of the same person presents all.

Must be sent for a presenter.

Do not send attribute for an accompanying person who is not making any presentation.

Function

M

SC @Pres

Function code of the Presenter in the Medal Presentation

Order

M

Numeric

#0

Order of the presenters

 

Element: Presentation /Presenter /Description (1,1)

Attribute

M/O

Value

Description

GivenName

O

S(25)

Given name (mixed case)

FamilyName

M

S(25)

Family name (mixed case)

Gender

O

CC @PersonGender

Gender of the person

Nationality

O

CC @Country

Nationality of the Presenter

 

Element: Presentation /Presenter /Detail (1,N)

Attribute

M/O

Value

Description

Language

M

CC @Language

Language code or the data

PresenterName

M

S(28)

Name of the presenter for display, may include things like Mr, HRM, Sir etc.

LongPresenterName

M

S(80)

Long name of the presenter for display, may include things like Mr, HRM, Sir etc.

Role

O

S(32)

Role of the presenter in the competition

Highlight

O

S(200)

Any additional highlight information about the person

 

Sample (one presenter for each medals and flowers)

<ExtendedInfos>
   <SportDescription DisciplineName="Alpine Skiing" />
   <VenueDescription Venue="ABC" VenueName="Skiing Venue" />
</ExtendedInfos>
<Presentation Event="ALSMDH----------------------------" EventName="Men's Downhill" >
   <Presenter MedalRank="0" Function="PRES_MEDAL" Order="1" >
      <Description GivenName="John" FamilyName="Smith" Gender="M" Nationality="SWE" />
      <Detail Language="ENG" PresenterName="Sir John Smith" LongPresenterName="Sir John Smith" Role="IOC Executive Board Member" Highlight="John is a former World Champion in this event" />
   </Presenter>
   <Presenter MedalRank="0" Function="PRES_FLOWER" Order="2" >
     <Description GivenName="Gian Franco" FamilyName="Kasper" Gender="M" Nationality="SUI" />
      <Detail Language="ENG" PresenterName="Gian Franco Kasper" LongPresenterName="Gian Franco Kasper" Role="FIS President" />
   </Presenter>
      </Presentation>

 

Sample (one presenter per medal)

<Presentation Event="ALSMDH----------------------------" EventName="Men's Downhill" >
   <Presenter MedalRank="1" Function="PRES_MEDAL" Order="1" >
      <Description GivenName="John" FamilyName="Smith" Gender="M" Nationality="SWE" />
      <Detail Language="ENG" PresenterName="HRH John Smith" LongPresenterName="HRH John Smith" Role="IOC Executive Board Member" Highlight="John is a former World Champion in this event" />  
   </Presenter>
   <Presenter MedalRank="2" Function="PRES_MEDAL" Order="2" >
     <Description GivenName="Gian Franco" FamilyName="Kasper" Gender="M" Nationality="SUI" />
      <Detail Language="ENG" PresenterName="Gian Franco Kasper" LongPresenterName="Gian Franco Kasper" Role="FIS President" />
   </Presenter>
   <Presenter MedalRank="3" Function="PRES_MEDAL" Order="3" >
      <Description GivenName="Mary" FamilyName="Smith" Gender="W" Nationality="GER" />
      <Detail Language="ENG" PresenterName="Ms Mary Smith" LongPresenterName="Ms Mary Smith" Role="IOC Executive Board Member" />
   </Presenter>
</Presentation>

2.1.24.6 Message Sort

Sort by Presenter Order

 

2.1.25 Discipline/Venue Start Transmission

2.1.25.1 Description

The “discipline/venue start transmission” is a message to indicate the start of operations for one specific discipline in one specific venue within a logical day. Operations may start and stop multiple times within a logical day. This message indicates the start of DT_KA messages for a Source.

2.1.25.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

SC @GMGNCode

Global message for all disciplines

DocumentType

DT_LOCAL_ON

Global message for all disciplines

Version

1..V

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

FeedFlag

"P"-Production

"T"-Test

Refer to ODF header definition

Date

Date

Refer to ODF header definition

Time

Time

Refer to ODF header definition

LogicalDate

Date

Refer to ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.1.25.3 Trigger and Frequency

The message is sent as soon as the operations for one particular logical day are about to begin, and always before any other message for that logical day. Send again after DT_LOCAL_OFF if operations recommence.

2.1.25.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

 

 

Competition (0,1)

 

Config (1,1)

 

KADelay

 

DelayOffSet

 

CompetitionDay

2.1.25.5 Message Values

 

Element Config (1,1)

Attribute

M/O

Value

Description

KADelay

M

Numeric

Delay in seconds for which a keep-alive message will be generated if there is no other real time activity.

By default, this value is set to 60 seconds.

DelayOffSet

M

Numeric

Delay offset in seconds to be added to the KADelay parameter, for a final customer to assume the connection is broken

By default, this value is set to 60 seconds.

CompetitionDay

O

Date

Competition date for that transmission, valid until the next DT_LOCAL_OFF.

This attribute is only used during testing activities.

 

2.1.25.6 Sample

<OdfBody CompetitionCode="OWG2018" …… >
<Competition>
<Config KADelay="60" DelayOffSet="180" />
</Competition>
</OdfBody>

2.1.25.7 Message sort

There is no sort order for this message.

 

2.1.26 Discipline/Venue Stop Transmission

2.1.26.1 Description

The “discipline/venue stop transmission” is a message to indicate the end of operations for the venue/discipline with messages (until the restart of operations or the next day). This message indicates the end of DT_KA messages for a Source (until the next DT_LOCAL_ON which may be the same day).

2.1.26.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

SC @GMGNCode

Global message for all disciplines

DocumentType

DT_LOCAL_OFF

Global message for all disciplines

Version

1..V

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

FeedFlag

"P"-Production

"T"-Test

Refer to ODF header definition

Date

Date

Refer to ODF header definition

Time

Time

Refer to ODF header definition

LogicalDate

Date

Refer to ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.1.26.3 Trigger and Frequency

The message is sent as soon as the operations for one particular logical day are finished, to formally indicate the end of that logical day though it may restart with a new DT_LOCAL_ON.

2.1.26.4 Message Structure

The message structure only includes the OdfBody element (with their ODF header attributes, but no other hierarchical element below OdfBody).

2.1.26.5 Message Values

There are no attributes to be defined in this message.

2.1.26.6 Sample

<OdfBody CompetitionCode="OWG2018" DocumentType="DT_LOCAL_OFF"…… />

2.1.26.7 Message sort

There is no sort order for this message.

 

2.1.27 Discipline/Venue Keep Alive

2.1.27.1 Description

The Discipline/Venue Keep Alive message tells the user that the transmission or session taking place in one venue is still alive, in case there is no other message activity.

2.1.27.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

SC @GMGNCode

Global message for all disciplines

DocumentType

DT_KA

Discipline/Venue Keep Alive

Version

1..V

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

FeedFlag

"P"-Production

"T"-Test

Refer to ODF header definition

Date

Date

Refer to ODF header definition

Time

Time

Refer to ODF header definition

LogicalDate

Date

Refer to ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.1.27.3 Trigger and Frequency

Message producer will send this message when no other messages are sent (control or content messages) and the delay defined in the KADelay parameter of the DT_LOCAL_ON expires.

2.1.27.4 Message Structure

The message structure only includes the OdfBody element (with their ODF header attributes, but no other hierarchical element below OdfBody).

2.1.27.5 Message Values

There are no attributes to be defined in this message.

2.1.27.6 Sample

<OdfBody CompetitionCode="OWG2018" DocumentType="DT_KA"…… />

2.1.27.7 Message sort

There is no sort order for this message.

 

2.2 Central Messages

2.2.1 Competition schedule / Competition schedule update

2.2.1.1 Description

The Competition schedule is a bulk message provided for one particular 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 (and have status UNSCHEDULED or SCHEDULED).

 

The arrival of the competition schedule message resets all the previous schedule information for one particular 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 usually 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.

 

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

 

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

 

Where HideStartDate="Y" is used then all start times for the units may be the same, usually the same as the first unit in the session or location (which generally will not use HideStartDate="Y") but this is not mandatory and approximate start times may be used. The specific way this is managed in each sport is detailed in the specific sport data dictionary.

 

 

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)

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"

 

 

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 the previous 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.2.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.2.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 should be sent immediately when known and usually soon 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.2.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)

 

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

 

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

 

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

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

See sport specific definition

 

Element: Competition /Session (0,N)

Attribute

M/O

Value

Description

SessionCode

M

S(5)

Code of the 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.

 

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

Attribute

M/O

Value

Description

Language

M

CC @Language

Language of the Session Description

Value

O

S(40)

Name of the 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(6)

 

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 e ach 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

Gold medal event unit or bronze medal event unit.

Do not send if not a medal event unit

Venue

M

CC @VenueCode

Venue where the unit takes place

Use TBD if the Venue is not known yet (CC).

Location

M

CC @Location

Location where the unit takes place

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

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

Code of the 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.

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

T,A

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' this 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.2.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.2.2 List of participants by discipline / List of participants by discipline update

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

 

Participant (1,N)

 

Code

 

Parent

 

Status

 

GivenName

 

FamilyName

 

PassportGivenName

 

PassportFamilyName

 

PrintName

 

PrintInitialName

 

TVName

 

TVInitialName

 

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

 

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). For use after PyeongChang.

PassportFamilyName

O

S(25)

Passport Family Name (Uppercase). For use after PyeongChang.

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

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)

'Y' or 'N'

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

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.2.2.6 Message Sort

The message is sorted by Participant @Code

 

2.2.3 List of teams / List of teams update

2.2.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.2.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.2.3.3 Trigger and Frequency

The DT_PARTIC_TEAMS 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_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.2.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)

 

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

 

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

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. It is Optional in the case of  List of Team Update when the @ ModificationIndicator=D

TVTeamName

O

S(21)

Team's TV Name.

In head-to-head pairs competitions this should be in the format SMITH/JONES [max char(10) per name] else it is the organisation name unless special rules apply.

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

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

See sport specific definition

2.2.3.6 Message Sort

The message is sorted by Team @Code.

 

2.2.4 List of horses / List of horses update

2.2.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.2.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.2.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.2.4.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Competition (0,1)

 

Horse (1,N)

 

Code

 

Name

 

Organisation

 

Sex

 

YearBirth

 

Passport

 

ColourCode

 

BreedCode

 

Sire

 

Owner

 

SecondOwner

 

Groom

 

ModificationIndicator

 

Entry (0,N)

 

Type

 

Code

 

Pos

 

Value

2.2.4.5 Message Values

 

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.2.4.6 Message Sort

The message will be sorted by Horse @Code

 

 

2.2.5 Participant Names

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

Depending on the needs and location of a competition the participants may need their name displayed in a language other than the default, usually in Latin or ASCII characters (sometimes referred to as English).

This message is always a full message including the names of all participants delivered in DT_PARTIC in the specified language (in header). If any of the names do not have a translation then the attribute is not sent.

The message is planned for use after PyeongChang.

2.2.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 (discipline level)

RSC at discipline level

DocumentType

DT_PARTIC_NAME

List of participants  by language

Version

1..V

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

Language

CC @Language

Language code. This is the language of the names in the message.

FeedFlag

"P"-Production

"T"-Test

Test 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

Refer to ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.5.3 Trigger and Frequency

The message is sent before the Games including all participants and is manually triggered as needed. Usually outside of competition hours.

2.2.5.4 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

 

 

 

Competition (0,1)

 

Participant (1,N)

 

Code

 

GivenName

 

FamilyName

 

PrintName

 

PrintInitialName

 

TVName

 

TVInitialName

2.2.5.5 Message Values

Element: Participant (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Participant's ID.

GivenName

O

S(25)

Given name (mixed case if applicable for the language)

FamilyName

M

S(25)

Family name (mixed case if applicable for the language)

PrintName

M

S(35)

Print name

PrintInitialName

M

S(18)

Print Initial name

TVName

M

S(35)

TV name

TVInitialName

M

S(18)

TV initial name

 

Sample

<?xml version="1.0" encoding="utf-8"?>

<OdfBody CompetitionCode="OG2020" DocumentCode="ATH------------------------------" DocumentType="DT_PARTIC_NAME" Version="1" Language="GRE" FeedFlag="P" Date="2020-07-19" Time="162653467" LogicalDate="2020-07-19" Source="OMS" >

<Competition>

<Participant Code="1007339" GivenName="Κατερίνα" FamilyName="Τσιρώνη" PrintName="ΤΣΙΡΩΝΗ Κατερίνα" PrintInitialName="ΤΣΙΡΩΝΗ Κ" TVName="Κατερίνα ΤΣΙΡΩΝΗ" TVInitialName="Κ. ΤΣΙΡΩΝΗ"/>

……

2.2.5.6 Message Sort

The message is sorted by Participant @Code

 

2.2.6 Medal Standings

2.2.6.1 Description

The medal standings table contains the official medal standings up to the moment of the message generation for all the organisations that have been awarded a medal.

Medal standings is a bulk message, provided for all disciplines. It is the complete medal standings message.

The arrival of this message resets the entire previous medals table information.

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

2.2.6.2 Header Values

The following table describes the message header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------------------

Global message for all disciplines

DocumentType

DT_MEDALS

Global message for all disciplines

Version

1..V

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

FeedFlag

"P"-Production

"T"-Test

Refer to ODF header definition

Date

Date

Refer to ODF header definition

Time

Time

Refer to ODF header definition

LogicalDate

Date

Refer to ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.6.3 Trigger and Frequency

"Medal standings" is sent as soon as any medal is officially awarded or changed (i.e. when the result is official, not the medal physically awarded) for any of the events that form part the competition schedule. As the competition progresses, successive changes in the medals’ information are made. Therefore, this message is resent multiple times, as result of the normal operation. In this case, it has to be assumed that the message resets the complete previous medals’ information.

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

 

MedalStandings (1,1)

 

DateTime

LastEvent

TotalEvents

FinishedEvents

MedalSummary (1,1)

 

MedalNumber (1,N)

 

Type

Gold

Silver

Bronze

Total

 

MedalsTable (1,1)

 

MedalLine (0,N)

 

Rank

RankTotal

SortRank

RankEqual

SortRankTotal

RankTotalEqual

Organisation

Description (1,1)

 

OrganisationName

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

MedalNumber (1,N)

 

Type

Gold

Silver

Bronze

Total

2.2.6.5 Message Values

Element: MedalStandings (1,1)

Attribute

M/O

Value

Description

DateTime

M

DateTime

Date and Time when the content has been updated

Example:

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

LastEvent

M

Full RSC at event level

Last event updating the medal standings message

TotalEvents

M

Numeric

Total number of competition events (events that award medals)

FinishedEvents

M

Numeric

Number of competition events that have awarded a type of medal, out of the total

In case of sports with 2 matches have medals (Bronze and Gold), this attribute only counts when the Gold medal has been awarded (not counted for Bronze because the event has not finished yet).

 

Element: MedalStandings /MedalSummary /MedalNumber (1,N)

The general definition states that MedalNumber 1..N, in the Olympics it will be fixed to four, for Type=(M, W, X, TOT)

Attribute

M/O

Value

Description

Type

M

SC @MedalSummaryType

Type of medal summarization (categorize by event gender and all events).

Gold

M

Numeric

Number of gold medals for MedalSummary /MedalNumber @Type event categorization

Silver

M

Numeric

Number of silver medals for MedalSummary /MedalNumber @Type event categorization

Bronze

M

Numeric

Number of bronze medals for MedalSummary /MedalNumber @Type event categorization

Total

M

Numeric

Total number of medals for MedalSummary /MedalNumber @Type event categorization

 

Element: MedalStandings /MedalSummary /MedalTable /MedalLine (0,N)

Attribute

M/O

Value

Description

Rank

M

Numeric

Organisation’s medal rank according to the medal’s colour (gold, silver, bronze)

RankTotal

M

Numeric

Organisation’s rank according to the total number of medals

SortRank

M

Numeric

Organisation’s sort based on MedalLine @Rank. If there are rank ties, the order will be defined by the IOC rules.

RankEqual

M

S(1)

Y: If there are more organisations with the same @Rank

 

N: If there are no more organisations with the same @Rank

SortRankTotal

M

Numeric

Organisation’s sort based on MedalLine @RankTotal. If there are rank ties, the order will be determined by the attribute @SortRank

RankTotalEqual

M

S(1)

Y: If there are more organisations with the same @RankTotal

 

N: If there are no more organisations with the same @RankTotal

Organisation

M

CC @Organisation

Organisation’s code.

 

Element: MedalStandings /MedalSummary /MedalTable /MedalLine /Description (1,1)

Attribute

M/O

Value

Description

OrganisationName

M

S(60)

Name of the Organisation in text. Long Description from common codes.

 

Element: MedalStandings /MedalSummary /MedalTable /MedalLine /Description /ExtendedDescription (0,N)

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions if extended

Code

M

 

 

Pos

O

 

 

Value

O

 

 

 

Element: MedalStandings /MedalSummary /MedalTable /MedalLine /MedalNumber (1,N)

(However the general definition states that MedalNumber 1..N, in Olympics it will be fixed to four, for Type=(M, W, X, TOT)

Attribute

M/O

Value

Description

Type

M

CC @MedalSummaryType

Type of medal summarization (categorize by event gender and all events).

Gold

M

Numeric

For the MedalLine @Organisation:

Number of gold medals for MedalSummary /MedalNumber @Type event categorization

Silver

M

Numeric

For the MedalLine @Organisation:

Number of silver medals for MedalSummary /MedalNumber @Type event categorization

Bronze

M

Numeric

For the MedalLine @Organisation:

Number of bronze medals for MedalSummary /MedalNumber @Type event categorization

Total

M

Numeric

For the MedalLine @Organisation:

Total number of medals for MedalSummary /MedalNumber @Type event categorization

2.2.6.6 Sample

<Competition>

<MedalStandings DateTime="2012-08-11T23:52:28+01:00" LastEvent="BKW400000" TotalEvents="302" FinishedEvents="287">

<MedalSummary>

<MedalNumber Type="M" Gold="149" Silver="151" Bronze="188" Total="488" />

<MedalNumber Type="W" Gold="130" Silver="130" Bronze="148" Total="408" />

<MedalNumber Type="X" Gold="8" Silver="8" Bronze="8" Total="24" />

<MedalNumber Type="TOT" Gold="287" Silver="289" Bronze="344" Total="920" />

</MedalSummary>

<MedalsTable>

<MedalLine Rank="1" SortRank="1" RankEqual="N" RankTotal="1" SortRankTotal="1" RankTotalEqual="N" Organisation="USA">

<Description NOCName="UnitedStates" />

<MedalNumber Type="M" Gold="15" Silver="15" Bronze="13" Total="43" />

<MedalNumber Type="W" Gold="29" Silver="14" Bronze="15" Total="58" />

<MedalNumber Type="X" Gold="0" Silver="0" Bronze="1" Total="1" />

<MedalNumber Type="TOT" Gold="44" Silver="29" Bronze="29" Total="102" />

</MedalLine>

<MedalLine Rank="2" SortRank="2" RankEqual="N" RankTotal="2" SortRankTotal="2" RankTotalEqual="N" Organisation="CHN">

<Description NOCName="China" />

<MedalNumber Type="M" Gold="17" Silver="8" Bronze="11" Total="36" />

<MedalNumber Type="W" Gold="20" Silver="18" Bronze="11" Total="49" />

<MedalNumber Type="X" Gold="1" Silver="1" Bronze="0" Total="2" />

<MedalNumber Type="TOT" Gold="38" Silver="27" Bronze="22" Total="87" />

</MedalLine>

......

2.2.6.7 Message Sort

Message should be sorted by the SortRank @Value attribute. There is no defined sort for MedalSummary.

 

2.2.7 Medallists of the Day

2.2.7.1 Description

The “medallists of the day” contains the list of medallists who achieved a medal (not necessarily awarded) during the current logical day.

The “medallists of the day” message is a complete message.

The arrival of this message resets the entire previous “medallists of the day” information.

The message is not by discipline, it could contain several disciplines.

2.2.7.2 Header Values

The following table describes the ODF header attributes (the DocumentSubtype attribute is used to identify the message along with the DocumentCode and DocumentType attributes).

 

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------------------

It is a global message for all the disciplines

DocumentType

DT_MEDALLISTS_DAY

Medallists by day

DocumentSubtype

YYYY-MM-DD

Refer to the ODF header definition

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.7.3 Trigger and Frequency

“Medallists by day” is sent at the end of the current day (Logical Date) with the official medals known for today.

In case that some medal(s) of previous days change then a new version of this (for the DocumentSubtype corresponding) will be sent as soon as possible.

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

 

Discipline (1,N)

 

Code

TotalEvents

FinishedEvents

Event (1,N)

 

Code

EventName

Date

Medal (1,N)

 

Code

Competitor (0,N)

 

Code

Type

Order

Organisation

Description (0,1)

 

TeamName

IFId

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

Composition

 

Athlete (1,N)

 

Code

Order

Description

 

 

GivenName

FamilyName

Gender

Organisation

BirthDate

IFId

Class

Horse

GuideID

GuideFamilyName

GuideGivenName

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

2.2.7.5 Message Values

Element: Discipline (1,N)

Attribute

M/O

Value

Description

Code

M

CC @Discipline

Full RSC of the Discipline

TotalEvents

O

Numeric

Total number of competition events (events that award medals)

FinishedEvents

O

Numeric

Number of competition events that have awarded a type of medal, out of the total

In case of sports with 2 matches have medals (Bronze and Gold), this attribute only counts when the Gold medal has been awarded (not counted for Bronze because the event has not finished yet).

 

Element: Discipline /Event (1,N)

Attribute

M/O

Value

Description

Code

M

CC @Event

Full RSC of the Event

EventName

M

S(40)

Event name (not code) from Common Codes

Date

O

YYYY-MM-DD

Date of the Gold medal match.

 

Element: Discipline /Event /Medal (1,N)

Where more than one medal of the same type is awarded for an event (for example two bronze medals) there must be a separate Medal element for each medal awarded (i.e. one for each competitor).

Attribute

M/O

Value

Description

Code

M

SC @MedalType

Medal type gold, silver or bronze

 

Element: Discipline /Event /Medal /Competitor (0,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor’s ID

Type

M

T, A

T for team

A for athlete

Order

M

Numeric

Competitor order (Send 1 by default) and in the case of tie the order will be defined by the IOC rules.

Organisation

M

CC @Organisation

Competitor’s organisation’s

 

Element: Discipline /Event /Medal /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

O

S(73)

Name of the team. Only applies for teams / groups. Not usually for pairs (figure skating & beach volleyball are the exceptions).

IFId

O

S(16)

Team IF number, send if available

 

Element: Discipline /Event /Medal /Competitor /Description /ExtendedDescription (0,N)

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions if extended

Code

M

 

 

Pos

O

 

 

Value

O

 

 

 

Element: Discipline /Event /Medal /Competitor /Composition /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Individual athlete’s ID (if Competitor @Type=”A” or team member’s ID (if Competitor @Type=”T”’).

Order

M

Numeric

Team member order for medal (according to each different sport rule)

Send 1 if individual medal

 

Element: Discipline /Event /Medal /Competitor /Composition /Athlete /Description

Athletes 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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

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: Discipline /Event /Medal /Competitor /Composition /Athlete /Description /ExtendedDescription (0,N)

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions if extended

Code

M

 

 

Pos

O

 

 

Value

O

 

 

 

2.2.7.6 Sample

<Competition>
<Discipline Code="CSL-------------------------------">
<Event Code="CSLMK1------------------------------" EventName="Men's K1">
<Medal Code="ME_GOLD">
<Competitor Code="1101716" Type="A" Order="1" Organisation="ESP">
<Composition>
<Athlete Code="1101716" Order="1">
<Description GivenName="John" FamilyName="Smith" Gender="M" Organisation="ESP" BirthDate="1992-12-15" />
</Athlete>
</Composition>
</Competitor>
</Medal>
<Medal Code="ME_GOLD">
<Competitor Code="1101556" Type="A" Order="1" Organisation="SUI">
<Composition>
<Athlete Code="1101556" Order="1">
<Description GivenName="John" FamilyName="Brown" Gender="M" Organisation="SUI" BirthDate="1994-12-15" />
</Athlete>
</Composition>
</Competitor>
</Medal>
......
</Event>
</Discipline>
<Discipline Code="DIV-------------------------------">
<Event Code="DIVW3mSync----------------------" EventName="Women's 3m Synchronized Diving">
<Medal Code="ME_GOLD">
<Competitor Code="DIVW3MSYNC--CHN01" Type="T" Order="1" Organisation="CHN">
<Description TeamName="China" />
<Composition>
<Athlete Code="1072148" Order="1">
<Description GivenName="Joan" FamilyName="Smith" Gender="W" Organisation="CHN" BirthDate="1992-12-15" />
</Athlete>
<Athlete Code="1072150" Order="2">
<Description GivenName="Emily" FamilyName="Brown" Gender="W" Organisation="CHN" BirthDate="1992-12-13" />
</Athlete>
</Composition>
</Competitor>
</Medal>
......
</Event>
</Discipline>
......

2.2.7.7 Message Sort

Events in the message will be sorted by discipline code and event code.

Within an event, medals will be sorted by medal type (gold, silver, bronze). In case of tie or for the team’s athletes, the order will be according to a medal order (given by each sport rule).

 

2.2.8 Global Good Morning

2.2.8.1 Description

The “global good morning” is a message to indicate the start of day of the operations for all the disciplines with some messages to be sent within a logical day.

All the messages defined in this document should send between DT_GLOBAL_GM/ DT_GLOBAL_GN messages.

2.2.8.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------------------

It is a global message for all the disciplines

DocumentType

DT_GLOBAL_GM

Global good morning

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.8.3 Trigger and Frequency

“Global good morning” is sent as soon as the operations for one particular logical day are about to begin, and always before any other message for that logical day.

2.2.8.4 Message Structure

The message structure just includes an OdfBody element (with their ODF header attributes, but no other hierarchical element below OdfBody).

2.2.8.5 Message Values

There are no attributes defined in this message.

2.2.8.6 Sample

<OdfBody CompetitionCode="OG2012" DocumentCode="GEN-------------------------------" Time="054040632" Date="2012-07-27" FeedFlag="P" LogicalDate="2012-07-27" DocumentType="DT_GLOBAL_GM" Source="PDC" Version="1" />

2.2.8.7 Message sort

There is no sort order for this message.

2.2.9 Global Good Night

2.2.9.1 Description

The “global good night” is a message to indicate the end of day of the operations for all the disciplines within a logical day.

2.2.9.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------------------

It is a global message for all the disciplines

DocumentType

DT_GLOBAL_GN

Global good night

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.9.3 Trigger and Frequency

“Global good night” is sent as soon as the operations for one particular logical day are finished, to formally indicate the end of that logical day.

2.2.9.4 Message Structure

The message structure just includes an OdfBody element (with their ODF header attributes, but no other hierarchical element below OdfBody).

2.2.9.5 Message Values

There are no attributes defined in this message.

2.2.9.6 Sample

<OdfBody CompetitionCode="OG2012" DocumentCode="GEN-------------------------------" Time="234040632" Date="2012-07-27" FeedFlag="P" LogicalDate="2012-07-27" DocumentType="DT_GLOBAL_GN" Source="PDC" Version="1" />

2.2.9.7 Message sort

There is no sort order for this message.

2.2.10 Background Document

2.2.10.1 Description

A Background document message is considered as a unique document of background information.

The arrival of this message replaces the previous Background document with the same DocumentSubcode.

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

CC @BackgroundSport

Background Category

DocumentSubcode

Numeric

Unique identifier for each background item

DocumentType

DT_BCK

Type of BCK documents

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.10.2 Trigger and Frequency

Background document will be sent every time that the document is published.

2.2.10.3 Message Structure

The following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Competition (0,1)

 

Categories (1,1)

 

Category (1,N)

 

Code

 

CategoryName

 

Main

 

Document (1,1)

 

Parent

 

ReportType

 

ReportTypeName

 

SortOrder

 

FileName

 

ReportFormat

 

ModificationIndicator

 

Title (1,1)

 

-

 

Body

 

-

2.2.10.4 Message Values

Element: Categories (1,1) / Category (1,N)

Attribute

M/O

Value

Description

Code

M

CC @BackgroundSport

Code of application Criteria level 1 (usually sport but may be other categories)

CategoryName

M

S(40)

Category Name

Main

O

S(1)

“Y” if this category is the main category else do not send. Must be one main category for each valid document.

 

Element: Document

Attribute

M/O

Value

Description

Parent

M

Numeric1

Unique identifier of parent document.

If the report has no parent ID then it takes value 0

ReportType

M

CC @BackgroundReport

Report Type code of application  (for example MDL – Past Medallists, PRE –Past Results, FCT - Facts, CER – Ceremonies Facts, etc.)

ReportTypeName

M

S(40)

Report Type Name

SortOrder

O

S(8)

This field identifies the Sort order associated to the report.  Value to be defined by the Committee.

FileName

M/O

S(10)

This field identifies the filename of the report.

This is only Mandatory for DT_BCK_IMP

ReportFormat

M

S(1)

This field identifies the format of the report. The possible values are:

 “H” for HTML Reports and “P” for PDF Reports.

ModificationIndicator

O

S(1)

Send D to Delete / Unpublish BCK document else do not send.

If ModificationIndicator=’D’, then the received version of the document should be deleted.

 

Element: Document /Title (1,1)

Attribute

M/O

Value

Description

-

M

S(100)

Text describing Document Title

 

Element: Document /Body

Attribute

M/O

Value

Description

-

M

Free text2

Accordingly to the ReportFormat field the body element will contain:

 

In the case of “H” (HTML Report) the value will be the Free Text containing the Body of the HTML report.

 

In the case of “P” (PDF Report) the value will be the PDF report encoded in Base64.

 

2.2.10.5 Sample

OdfBody CompetitionCode="OG2016" DocumentType="DT_BCK" DocumentCode="GAR" DocumentSubcode="8" Time="160052578" Origin="PDC" Date="2016-07-28" LogicalDate="2016-07-28" FeedFlag="P" Language="ENG" Version="17" >
<Competition>
<Categories>
<Category Code="GAR" CategoryName="Artistic Gymnastics" Main="Y" />
<Category Code="GTR" CategoryName="Trampoline" />
</Categories>
<Document Parent="8" ReportType="FCT" ReportTypeName="Facts" SortOrder="N86D" ReportFormat="H">
<Title>
<![CDATA[Facility Description]]>
</Title>
<Body>
<![CDATA[<p>As of 22 July 2016</p>
<p>&nbsp;</p>
<p><strong>The Powerhouse</strong></p>
<p>Text Here ...</p>]]>
</Body>
</Document >
</Competition>
</OdfBody>

2.2.10.6 Message sort

The message is not sorted.

2.2.11 Background Import Document

2.2.11.1 Description

Background import document message is considered as a unique document of background.

The arrival of this message resets the previous Background document.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.11.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

CC @BackgroundSport

Background Category

DocumentSubcode

Numeric

Unique identifier for each background item

DocumentType

DT_BCK_IMP

Type of BCK documents

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.11.3 Trigger and Frequency

Background import document will be received by the OCOG in the months before games.

2.2.11.4 Message Structure

The message structure of the Background import document message is the same as the Background document message.

2.2.11.5 Message Values

All message attributes are the same as the background document message.

2.2.11.6 Message sort

The message is not sorted.

2.2.12 Participant Biography

2.2.12.1 Description

The Participant Biography is a message containing the biography of one individual participant. The participant could be an athlete, an official, coach or a team member. The participant will have always assigned at least one discipline, although it could be more than one.

The message resets the previous Participant Biography information. There is only one participant per message.

2.2.12.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

DDDGTYP---------------------------

DDD – Discipline

G – Gender

TYP – Participant Type (ATH, COA, OFF, BIO).

 

For example ATHMCOA---------------------------:  Athletics Male Coach.

TYP BIO is usually used outside of the Olympic Games

DocumentSubcode

S(20) with no leading zeroes

Participant’s ID

DocumentType

DT_BIO_PAR

Participant’s Biography

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

 

2.2.12.3 Trigger and Frequency

Participant’s Biography messages will usually be available the first day of the press operations. These messages are sent the first time including the complete bulk information known up to that moment.

2.2.12.4 Message Structure

The following optional elements must be included, if the message is for an ATH, a COA or an OFF:

 

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

 

Competition (0,1)

 

ParticipantBiography (1,1)

 

Code

Gender

Organisation

Current

ModificationIndicator

ExternalCode (*)

ParticipantID(*)

GivenName(*)

FamilyName(*)

BirthDate(*)

Height(*)

Weight(*)

PlaceofBirth(*)

CountryofBirth(*)

PlaceofResidence(*)

CountryofResidence(*)

Nationality(*)

OlympicSolidarity(*)

Language

 

Language

CHighlights (0,1)

 

Highlights (1,3)

 

Type

-

 

Ginterest (0,1)

 

Nickname (0,1)

 

-

 

PrevNames (0,1)

 

-

 

Hobbies (0,1)

 

-

 

Occupation (0,1)

 

-

 

Education (0,1)

 

-

 

MarStatus (0,1)

 

-

 

Family (0,1)

 

-

 

LangSpoken (0,1)

 

-

 

Club_Name (0,1)

 

-

 

Coach (0,1)

 

-

 

Position_Style (0,1)

 

-

 

Hand (0,1)

 

-

 

Sporting_Relatives (0,1)

 

-

 

OtherSports (0,1)

 

-

 

Debut (0,1)

 

-

 

Injuries (0,1)

 

-

 

Music (0,1)

 

-

 

Choreographer (0,1)

 

-

 

Nat_Team (0,1)

 

-

 

Nat_League (0,1)

 

-

 

Start (0,1)

 

-

 

Reason (0,1)

 

-

 

Ambition (0,1)

 

-

 

Training (0,1)

 

-

 

Memorable (0,1)

 

-

 

Hero (0,1)

 

-

 

Influence (0,1)

 

-

 

Ritual (0,1)

 

-

 

Philosophy (0,1)

 

-

 

Award (0,1)

 

-

 

Appointment (0,1)

 

-

 

Int_Appointment (0,1)

 

-

 

WinLoss (0,1)

 

-

 

Other_Role (0,1)

 

-

 

Prev_Role (0,1)

 

-

 

AddInformation (0,1)

 

-

 

ExtendedBios (0,1)

 

ExtendedBio (1,N)

 

Type

Code

Pos

Value

ContentType

-

Extension (0,N)

 

Code

Pos

Value

 

Discipline (*)

 

Code (*)

 

OfficialFunction (0,N)

 

FunctionId

Main_Function_Flag

Table Note: (*) Field needed when the message is used to import data into the Info Diffusion System – Participant’s Biography Import message-

 

2.2.12.5 Message Values

Fields are mandatory or optional depending on the biography type.

Element: Competition /ParticipantBiography (1,1)

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

Code

M

M

M

M

S(20) with no leading zeroes

Participant’s ID

Gender

M

M

M

M

CC @PersonGender

Participant’s gender

Organisation

M

M

O

O

CC @Organisation

Organisation’s ID

Mandatory for ATH or COA

Current

M

M

M

O

boolean

true – For participants in the current event

false – For historical participants

ModificationIndicator

O

O

O

O

S(1)

Send only to delete or unpublish a biography, when needed send D for Delete.

 

Element: ParticipantBiography /Language

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

Language

M

M

M

M

CC @Language

Language code

 

Element: ParticipantBiography /Language /CHighlights (0,1) /Highlights (1,3)

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

Type

M

M

M

M

S(3)

ATH – Highlights are for an athlete

COA – Highlights are for a coach

OFF – Highlights are for an official

-

O

O

O

O

Free Text with a maximum length of 10000 characters.

Free Text describing the most important results the ATH or COA or OFF achieved during his career

 

Element: ParticipantBiography /Language/GInterest /Nickname

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 400 characters.

Nickname

 

Element: ParticipantBiography /Language/GInterest /PrevNames

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 400 characters.

Other/ previous names

 

Element: ParticipantBiography /Language/GInterest /Hobbies

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Hobbies

 

Element: ParticipantBiography /Language/GInterest /Occupation

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 120 characters.

Occupation

 

Element: ParticipantBiography /Language/GInterest /Education

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 120 characters.

Education

 

Element: ParticipantBiography /Language/GInterest /MarStatus

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

CC@MaritalStatus

Marital status

 

Element: ParticipantBiography /Language/GInterest /Family

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 120 characters.

Information about the family of the athlete

 

Element: ParticipantBiography /Language/GInterest /LangSpoken

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

O

O

Free Text with a maximum length of 120 characters.

Languages spoken

 

Element: ParticipantBiography /Language/GInterest /Club_Name

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 120 characters.

Club the athlete belongs to

 

 

Element: ParticipantBiography /Language/GInterest /Coach

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 400 characters.

Coach name

 

Element: ParticipantBiography /Language/GInterest /Position_Style

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 400 characters.

Position or style

 

Element: ParticipantBiography /Language/GInterest /Hand

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 120 characters.

Hand

 

Element: ParticipantBiography /Language/GInterest /Sporting_Relatives

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Sporting or famous relatives

 

Element: ParticipantBiography /Language/GInterest /OtherSports

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Other sports

 

Element: ParticipantBiography /Language/GInterest /Debut

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 250 characters.

Debut

 

Element: ParticipantBiography /Language/GInterest /Injuries

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 4000 characters.

Injuries

 

Element: ParticipantBiography /Language/GInterest /Music

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 400 characters.

Music for performance

 

Element: ParticipantBiography /Language/GInterest /Choreographer

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 150 characters.

Choreographer of Performance

 

Element: ParticipantBiography /Language/GInterest /Nat_Team

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 100 characters.

When started in national team

 

Element: ParticipantBiography /Language/GInterest /Nat_League

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 250 characters.

National League information

 

Element: ParticipantBiography /Language/GInterest /Start

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

When started sporting career

 

Element: ParticipantBiography /Language/GInterest /Reason

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Reasons for taking up this sport

 

Element: ParticipantBiography /Language/GInterest /Ambition

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Ambitions

 

Element: ParticipantBiography /Language/GInterest /Training

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Training

 

Element: ParticipantBiography /Language/GInterest /Memorable

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Most memorable sporting achievements

 

Element: ParticipantBiography /Language/GInterest /Hero

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Hero

 

Element: ParticipantBiography /Language/GInterest /Influence

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Most influential person in sporting career

 

Element: ParticipantBiography /Language/GInterest /Ritual

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Superstitions and rituals

 

Element: ParticipantBiography /Language/GInterest /Philosophy

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

 

 

O

Free Text with a maximum length of 1000 characters.

Sporting philosophy / motto

 

Element: ParticipantBiography /Language/GInterest /Award

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

O

O

O

Free Text with a maximum length of 2000 characters.

Awards won

 

Element: ParticipantBiography /Language/GInterest /Appointment

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

 

O

 

O

Free Text with a maximum length of 100 characters.

Year of coaching appointment

 

Element: ParticipantBiography /Language/GInterest /Int_Appointment

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

 

 

O

O

Free Text with a maximum length of 100 characters.

Year of first international appointment as an official

 

Element: ParticipantBiography /Language/GInterest /WinLoss

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

 

O

 

O

Free Text with a maximum length of 250 characters.

Win / Loss record with current team

 

Element: ParticipantBiography /Language/GInterest /Other_Role

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

 

O

O

O

Free Text with a maximum length of 2000 characters.

Other current roles

 

Element: ParticipantBiography /Language/GInterest /Prev_Role

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

 

O

O

O

Free Text with a maximum length of 2000 characters.

Previous Roles

 

Element: ParticipantBiography /Language/GInterest /AddInformation

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

-

O

O

O

O

Free Text with a maximum length of 10000 characters.

Additional information

 

Element: ParticipantBiography /Language /GInterest /ExtendedBios (0,1) /ExtendedBio (1,N)

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

Type

M

M

M

M

 

See sport descriptions

Code

M

M

M

M

 

 

Pos

O

O

O

O

 

 

Value

O

O

O

O

 

 

ContentType

O

O

O

O

 

Only filled if the data in the free text below is used. Options include:

text/html

image/jpeg

image/png

-

O

O

O

O

 

Additional information.

This field is not used in the Olympic Games and must not be filled.

 

Element: ParticipantBiography /Language /GInterest /ExtendedBios /ExtendedBio /Extension (0,N)

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

Code

M

M

M

M

 

See sport descriptions

Pos

O

O

O

O

 

 

Value

O

O

O

O

 

 

 

Element: ParticipantBiography /OfficialFunction

Attribute

M/O

Value

Description

ATH

COA

OFF

BIO

FunctionId

 

 

M

O

CC @ResultsFunction

Optional officials’ function code

Main_Function_Flag

 

 

O

O

S(1)

Y - @FunctionId is main function

N - @FunctionId is not main function

 

The following table describes extension for social media and Youth Olympic Games to be applied Competition /ParticipantBiography /Language /GInterest /ExtendedBios /ExtendedBio

Type

Code

Pos

Value

Description

Expected

EB_SOCIALMEDIA

SC @SocialMedia

 

String

For @Type:  Send proposed type

When available

For @Code:  Send proposed code

For @Pos:  Do not send anything

For @Value    Send the user name for the applicable social media site.

EB_COMPETITION

YOUTH

 

S(1)

For @Type:  Send proposed type

If applicable

For @Code:  Send proposed code

For @Pos:  Do not send anything

For @Value:

Send Y if the athlete has participated in the Youth Olympic Games else do not send]

 

2.2.12.6 Sample

<ParticipantBiography Code="1090269" Gender="M" Organisation="AUS" Current="true" >
<Language Language="ENG">
<CHighlights>
 <Highlights>
……
 </Highlights>
 </CHighlights>
<GInterest>
<Nickname>
<![CDATA[Steve, Hobbsy, Hooksy. (vis.org.au, 16 Jul 2007)]]>
</Nickname>
<Hobbies>
<![CDATA[He enjoys managing property, playing golf, reading, listening to music and skydiving. (vis.org.au, 16 Jul 2007; athletics.com.au, 13 Aug 2011)]]>
</Hobbies>
<Occupation>
<![CDATA[Athlete]]>
</Occupation>
<Education>
<![CDATA[Business - Royal Melbourne Institute of Technology, Melbourne, VIC, AUS]]>
</Education>
<LangSpoken>
<![CDATA[English]]>
</LangSpoken>
<Club_Name>
<![CDATA[Box Hill Athletics Club and WAIS, Melbourne, VIC, AUS]]>
</Club_Name>
<Coach>
<![CDATA[Alex Parnov (RUS) (sbs.com.au, 12 May 2012)]]>
</Coach>
<Sporting_Relatives>
<![CDATA[He is an amateur sprinter and he competed in the 2010 Stawell Gift race. The event is held every Easter weekend at Central Park in Western Victoria. The race is run on grass over 120m up a slight gradient. (iaaf.org, 03 Aug 2010; stawellgift.com, 03 Aug 2010) He played Australian Rules football before concentrating on pole vault. (Athletics Australia, 05 Apr 2004)]]>
</Sporting_Relatives>
<OtherSports>
<![CDATA[His mother Erica Hooker [nee Nixon] was a 1972 Olympian and a Commonwealth Games long jump silver medallist. His father, Bill, was a four-time national title holder and represented Australia in the 400m, 400m hurdles, 800m and 4x400m. (Athletics Australia, 05 Apr 2004)]]>
</OtherSports>
 <ExtendedBios>
<ExtendedBio Type="EB_SOCIALMEDIA" Code="TWITTER" Value="@IamtheBest" />
</ExtendedBios>
</GInterest>
</Language>
</Participant>

 

2.2.12.7 Message sort

There is no specific sorting for this message.

 

2.2.13 Participant Biography Import

2.2.13.1 Description

The Participant Biography Import is a message containing the biography of one individual participant. The participant could be an athlete, an official, coach or a team member. The participant will always have assigned at least one discipline, although it could be more than one.

The message resets the previous Participant Biography Import information. There is only one participant per message.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.13.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

S(20) with no leading zeroes

Participant’s external ID. This ID will start with “A” for Athletes, “C” for Coaches and”O” for Officials.

DocumentSubcode

S(3)

ATH – Athlete

COA – Coach

OFF – Official

DocumentType

DT_BIO_PAR_IMP

Participant’s Biography Import

Version

1...V

Refer to the ODF header definition

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.13.3 Trigger and Frequency

Participant’s Biography Import will be received by the OCOG some months before the games.

2.2.13.4 Message Structure

It has the same attributes (except for @Code) and elements as in the Participant’s Biography message, and adding the attributes/elements that are marked with an asterisk (*). See the next chapter.

The elements that are optional in this message depend on the DocumentSubcode attribute.

2.2.13.5 Message Values

Element: Competition / ParticipantBiography

Attribute

M/O

Value

Description

ExternalCode

M

S(20) with no leading zeroes

Participant’s Biography Import external ID. This ID will start with “A” for Athletes, “C” for Coaches and ”O” for Officials.

 

It is the same as in the @DocumentCode header’s attribute. The ID is assigned by the biography’s provider and must also match the external ID for the same athlete if supplied with records.

ParticipantID

O

S(20) with no leading zeroes

Participant’s ID (in Info Diffusion System).

 

This ID is a pre-matched value with the Accreditation ID (ie is the accreditation ID of the person for the current Games).

GivenName

O

S(25)

Given name in mixed case

FamilyName

M

S(25)

Family name mixed case

BirthDate

M

YYYY-MM-DD

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

Height

O

Numeric

###

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

Weight

O

Numeric

###

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

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

PlaceofBirth

O

S(75)

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

CountryofBirth

O

CC @Country

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

PlaceofResidence

O

S(75)

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

CountryofResidence

O

CC @Country

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

Nationality

O

CC @Country

Participant’s nationality.

 

For some participants not to be sent in exceptional circumstances when it is not known.

OlympicSolidarity

O

S(1)

Olympic Solidarity mark, Y for Yes, N for No. This information is not needed in the case of officials/referees.

 

Element: Competition / ParticipantBiography /Discipline

Attribute

M/O

Value

Description

Code

M

CC @Discipline

Full RSC Discipline’s code

 

2.2.13.6 Message sort

There is no specific sorting for this message.

 

2.2.14 Team Biography

2.2.14.1 Description

The Team Biography message contains a team participating in the event (competitor of type team).

The message resets the previous Team Biography information. This message includes only one team.

2.2.14.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline/gender level)

Discipline Gender RSC

For example BKBM------------------------------

DocumentSubcode

S(20) with no leading zeroes

Team’s ID

DocumentType

DT_BIO_TEA

Team’s Biography

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.14.3 Trigger and Frequency

Team’s Biography messages will be available the first day of the press operations. These messages are sent the first time including the complete bulk information known up to that moment.

2.2.14.4 Message Structure

The elements that are optional in this message are:

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

 

Competition (0,1)

 

TeamBiography (1,1)

 

Code

Gender

Organisation

Number

Name

Current

ModificationIndicator

ExternalCode (*)

Language

 

Language

CHighlights (0,1)

 

Highlights (1,1)

 

-

 

GInterest (0,1)

 

Nickname (0,1)

 

-

 

Music (0,1)

 

-

 

Choreographer (0,1)

 

-

 

Training (0,1)

 

-

 

Award (0,1)

 

-

 

AddInformation (0,1)

 

-

 

ExtendedBios (0,1)

 

ExtendedBio (1,N)

 

Type

Code

Pos

Value

Extension (0,N)

 

Code

Pos

Value

 

Discipline (*)

 

Code (*)

RegisteredEvent

 

Event (*)

Table Note: (*) Field needed when the message is used to import data into the Info Diffusion System - Team Biography Import message.

 

2.2.14.5 Message Values

Element: TeamBiography (1,1)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Team’s ID (example BKM400ESP01, 393553)

Gender

M

CC @DisciplineGender

Discipline Gender Code of the Team

Organisation

M

CC @Organisation

Team’s organisation ID

Number

O

Numeric

0

Team’s number.

It will be 1 when there is only one team (for one organisation in one event). Otherwise, it will be incremental, 1, 2, etc.

Mandatory in the case of @Current=true.

Name

M/O

S(73)

Team’s name.

It applies to some of the disciplines. It will be the same as @Organisation when there is no a specific rule for a discipline.

It is Optional for Team’s Biography Update when @ModificationIndicator=D

Current

M

Boolean

true – The team is participating in the event

false – The team is not participating (historical team)

ModificationIndicator

O

S(1)

Send only to delete or unpublish a biography, when needed send D for Delete.

 

Element: TeamBiography /Language

Attribute

M/O

Value

Description

Language

M

CC @Language

Language code

 

Element: TeamBiography /Language /CHighlights (0,1) /Highlights (1,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 4000 characters.

Free Text describing the most important results the team achieved during his/her career

 

Element: TeamBiography /Language /GInterest (0,1) /Nickname (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 2000 characters.

Nickname

 

Element: TeamBiography /Language /GInterest (0,1) /Music (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 400 characters.

Music for performance

 

Element: TeamBiography /Language /GInterest (0,1) /Choreographer (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 150 characters.

Choreographer of Performance

 

Element: TeamBiography /Language /GInterest (0,1) /Training (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 400 characters.

Training

 

Element: TeamBiography /Language /GInterest (0,1) /Award (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 2000 characters.

Awards

 

Element: TeamBiography /Language /GInterest (0,1) /AddInformation (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 10000 characters.

Additional Information

 

Element: TeamBiography /Language /GInterest /ExtendedBios (0,1) /ExtendedBio

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions

Code

M

 

See sport descriptions

Pos

O

 

See sport descriptions

Value

O

 

See sport descriptions

 

Element: TeamBiography /Language /GInterest /ExtendedBios (0,1) /ExtendedBio /Extension (1,N)

Attribute

M/O

Value

Description

Code

M

 

See sport descriptions

Pos

O

 

See sport descriptions

Value

O

 

See sport descriptions

 

2.2.14.6 Message sort

There is no specific sorting for this message.

2.2.15 Team Biography Import

2.2.15.1 Description

The Team Biography Import is a message containing the biography of one team.

The message resets the previous Team Biography Import information. There is only one team per message.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.15.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

S(20) with no leading zeroes

Team’s external ID. This ID will start with “T”.

DocumentType

DT_BIO_TEA_IMP

Team’s Biography Import

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.15.3 Trigger and Frequency

Team’s Biography Import will be provided to the OCOG some months before games.

2.2.15.4 Message Structure

It has the same attributes and elements as in the Team’s Biography message (except for @Code), and adding the attributes/elements that are marked with an asterisk (*).

2.2.15.5 Message Values

Element: TeamBiography

Attribute

M/O

Value

Description

ExternalCode

M

S(20) with no leading zeroes

Team’s external ID.

 

It is the same as in the @DocumentCode header’s attribute. The ID is assigned by the biography’s provider.

 

Element: TeamBiography /Discipline

Attribute

M/O

Value

Description

Code

M

CC @Discipline

Full RSC Discipline code

 

Element: TeamBiography /Discipline /RegisteredEvent

Attribute

M/O

Value

Description

Event

M

CC @Event

Full RSC of the Event

2.2.15.6 Message sort

There is not a special sorting for this message.

 

2.2.16 NOC/NPC Biography

2.2.16.1 Description

The NOC/NPC Biography message contains the NOC/NPC information.

The message resets the previous NOC/NPC information. There is only one NOC/NPC per message.

2.2.16.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------------------

Global message for all Organisation biographies

DocumentSubcode

S(3)

Organisation Code

DocumentType

DT_BIO_NOC

NOC/NPC

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.16.3 Trigger and Frequency

These messages will be available the first day of the press operations, including the complete bulk information known up to that moment.

2.2.16.4 Message Structure

The following elements describe the message structure from the OdfBody element.

The elements that are optional in this message are:

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

 

 

 

Competition (0,1)

 

Organisation (1,1)

 

Code

Current

ModificationIndicator

ExternalCode (*)

Name (*)

Language

 

Language

GInterest (0,1)

 

OCFlagBearer (0,1)

 

Code

 

Highlights (0,1)

 

-

 

AddInformation (0,1)

 

-

 

Anthem (0,1)

 

Title (0,1)

 

-

 

Composer (0,1)

 

-

 

Inducted (0,1)

 

-

 

Membership (0,1)

 

OfficialNocName (0,1)

 

-

 

CountriesIncluded (0,1)

 

-

 

FoundingDate (0,1)

 

-

 

DateIOCRecognition (0,1)

 

-

 

Officials (0,1)

 

NOCPresident (0,1)

 

-

 

NOCGenSecretary (0,1)

 

-

 

IOCMembers (0,1)

 

-

 

IOCExecBoard (0,1)

 

-

 

Participation (0,1)

 

FirstOGAppearance (0,1)

 

-

 

NumOGAppearance (0,1)

 

-

 

Summary (0,1)

 

-

Table Note: (*) Field needed when the message is used to import data into the Info Diffusion System - NOC/NPC Biography Import.

 

2.2.16.5 Message Values

Element: Organisation (1,1)

Attribute

M/O

Value

Description

Code

M

CC @Organisation

Organisation’s ID

Current

M

Boolean

true - Organisation participating in the event

false - Historical organisation

ModificationIndicator

O

S(1)

Send only to delete or unpublish a biography, when needed send D for Delete.

 

Element: Organisation /Language

Attribute

M/O

Value

Description

Language

M

CC @Language

Language code

 

Element: Organisation /Language /GInterest (0,1) /OCFlagBearer

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Flag Bearer Id. This attribute is not expected in the _IMP message.

 

Element: Organisation /Language /GInterest (0,1) /Highlights

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 4000 characters.

Free Text with highlights

 

Element: Organisation /Language /GInterest (0,1) /AddInformation (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 10000 characters.

Additional Information

 

Element: Organisation /Language /Anthem (0,1) /Title (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Anthem’s title

 

Element: Organisation /Language /Anthem (0,1) /Composer (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Anthem’s composer name

 

Element: Organisation /Language /Anthem (0,1) /Inducted (0,1)

Attribute

M/O

Value

Description

-

O

YYYY

Anthem’s inducted year

 

Element: Organisation /Language /Membership (0,1) /OfficialNocName (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Official Organisation name

 

Element: Organisation /Language /Membership (0,1) /CountriesIncluded (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Countries that composes this Organisation

 

Element: Organisation/Language /Membership (0,1) /FoundingDate (0,1)

Attribute

M/O

Value

Description

-

O

YYYY

Founding date

 

Element: Organisation /Language /Membership (0,1) /DateIOCRecognition (0,1)

Attribute

M/O

Value

Description

-

O

YYYY

IOC recognition date

 

Element: Organisation/Language /Officials (0,1) /NOCPresident (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

NOC/NPC President’s name

 

Element: Organisation /Language /Officials (0,1) /NOCGenSecretary (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

NOC/NPC General Secretary’s name

 

Element: Organisation /Language /Officials (0,1) /IOCMembers (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

IOC member’s name(s)

 

Element: Organisation /Language /Officials (0,1) /IOCExecBoard (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

IOC Executive Board Member’s name(s)

 

Element: Organisation/Language /Participation (0,1) /FirstOGAppearance (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Year of the first appearance in Olympic / Paralympic Games

 

Element: Organisation /Language /Participation (0,1) /NumOGAppearance (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Number of appearances in Olympic / Paralympic Games

 

Element: Organisation /Language /Participation (0,1) /Summary (0,1)

Attribute

M/O

Value

Description

-

O

Free Text with a maximum length of 10000 characters.

Free Text with the summary of Olympic / Paralympic Games appearances

 

2.2.16.6 Message sort

There is no specific sorting for this message

2.2.17 NOC/NPC Biography Import

2.2.17.1 Description

The NOC/NPC Biography Import is a message containing the biography of one NOC/NPC.

The message resets the previous NOC/NPC Biography Import information. There is only one biography per message.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.17.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

S(20) with no leading zeroes

Organisation’s external ID Biography. This ID will start with “N”.

DocumentType

DT_BIO_NOC_IMP

NOC/NPC Biography Import

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.17.3 Trigger and Frequency

Message is provided to the OCOG some months before games.

2.2.17.4 Message Structure

It has the same attributes and elements as in the NOC/NPC Biography message (except for @Code), and adding the attributes/elements that are marked with an asterisk (*).

2.2.17.5 Message Values

Element: Competition /Organisation

Attribute

M/O

Value

Description

ExternalCode

M

S(20) with no leading zeroes

Organisation’s Biography external ID. It is the same as in the @DocumentCode header’s attribute.

This ID starts with “N”.

Name

M

S(20)

Organisation Name

2.2.17.6 Message sort

There is not a special sorting for this message.

 

2.2.18 Horse Biography

2.2.18.1 Description

The Horse Biography message contains the Horse information.

The message resets the previous Horse’s information. There is only one Horse per message.

2.2.18.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full Discipline RSC

Message used only in Equestrian Disciplines

Full RSC of the Discipline

DocumentSubcode

S(20) with no leading zeroes

Horse’s ID

DocumentType

DT_BIO_HOR

Horse’s Biography

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.18.3 Trigger and Frequency

These messages will be available the first day of the press operations, including the complete bulk information known up to that moment

2.2.18.4 Message Structure

The following elements describe the message structure from the OdfBody element.

The elements that are optional in this message are:

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

 

 

 

Competition (0,1)

 

HorseBiography (1,1)

 

Code

Organisation

Sex

Current

Height

CountryofBirth

Dam

StudBook

Breeder

FormerName

FormerRider

ModificationIndicator

ExternalCode (*)

Name (*)

YearBirth (*)

Passport (*)

ColourCode (*)

BreedCode (*)

Sire (*)

Owner (*)

SecondOwner (*)

Groom (*)

Language

 

Language

GInterest (0,1)

 

MajorAchievements (1,1)

 

-

 

Discipline (*)

 

Code (*)

Table Note: (*) Field needed when the message is used to import data into the Info Diffusion System.

2.2.18.5 Message Values

Element: HorseBiography (1,1)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Horse’s ID

Organisation

M

CC @Organisation

Horse’s organisation

Sex

M

CC @HorseSex

Horse’s sex.

Height

O

Numeric

###

Height in cms

CountryofBirth

O

CC @Country

Country ID of Birth

Dam

O

S(25)

Dam Name

StudBook

O

S(120)

Stud book Name

Breeder

O

S(120)

Breeder Name

FormerName

O

S(120)

Former Name

FormerRider

O

S(120)

Former Rider Name

ModificationIndicator

O

S(1)

Send only to delete or unpublish a biography, when needed send D for Delete.

 

Element: HorseBiography /Language

Attribute

M/O

Value

Description

Language

M

CC @Language

Language code

 

Element: HorseBiography /Language /GInterest (0,1) /MajorAchievements

Attribute

M/O

Value

Description

-

O

Free text

Free Text with Major Achievements

2.2.18.6 Message sort

There is no specific sorting for this message

 

2.2.19 Horse Biography Import

2.2.19.1 Description

The Horse Biography Import is a message containing the biography of one Horse.

The message resets the previous Horse Biography Import information. There is only one biography per message.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.19.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

S(20) with no leading zeroes

Horse’s external ID Biography. This ID will start with “H”.

DocumentType

DT_BIO_HOR_IMP

Horse’s Biography Import

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.19.3 Trigger and Frequency

Message is provided to the OCOG some months before games.

2.2.19.4 Message Structure

It has the same attributes and elements as in the Horse Biography message (except for @Code), and adding the attributes/elements that are marked with an asterisk (*).

2.2.19.5 Message Values

Element: HorseBiography

Attribute

M/O

Value

Description

ExternalCode

M

S(20) with no leading zeroes

 

Horse’s external ID biography. It is the same as in the @DocumentCode header’s attribute. This ID will start with “H”.

Name

M

S(25)

Horse’s name in upper case.

YearBirth

M

Numeric

####

Horse’s year of birth.

Passport

O

S(12)

Horse’s passport. Send if the information is available

ColourCode

O

CC @HorseColour

Horse’s colour code. Send if the information is available

BreedCode

O

CC @HorseBreed

Horse’s breed code. Send if the information is available

Sire

O

S(25)

Horse’s sire. Send if the information is available.

The content is in upper case.

Owner

O

S(35)

Horse’s first owner. Send if the information is available.

The content is in upper case.

SecondOwner

O

S(35)

Horse’s second owner. Send if this information is available.

The content is in upper case.

Groom

O

S(35)

Horse’s groom. Send if the information is available.

The content is in upper case.

 

Element: HorseBiography /Discipline

Attribute

M/O

Value

Description

Code

M

CC @Discipline

Full RSC Discipline code

2.2.19.6 Message sort

There is not a special sorting for this message.

 

2.2.20 Alert

2.2.20.1 Description

The Alert message contains one individual alert and notifies users of important information.

2.2.20.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline level)

RSC at discipline level

DocumentSubcode

Numeric

ID of the information

DocumentType

DT_ALERT

Alert

DocumentSubtype

TICKER

NEWS

RESULTS

TICKER for CIS Ticker Information

NEWS for news alerts

RESULTS for results based alerts

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.20.3 Trigger and Frequency

For TICKER, triggered by CIS operator when appropriate information is entered in the CIS Ticker.

2.2.20.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

 

 

 

 

 

Competition (0,1)

 

Document (1,1)

 

Parent

ModificationIndicator

Message

 

-

Table Note: (*) Field needed when the message is used to import data into the Info Diffusion System.

2.2.20.5 Message Values

Element: Document (1,1)

Attribute

M/O

Value

Description

Parent

M

Numeric3

Parent’s ID.

If the report has no parent ID then it takes value 0. (Always 0 for TICKER)

Only applicable if language <> ENG then the Parent ID = ID of ENG document.

ModificationIndicator

O

S(1)

Send only to delete or unpublish information, when needed send D for Delete.

 

Element: Document /Message

Attribute

M/O

Value

Description

-

O

S(4000)

Text of the Alert

2.2.20.6 Sample

<OdfBody CompetitionCode="OG2012" DocumentCode="SYN-------------------------------" DocumentSubcode="1" DocumentType="DT_ALERT" DocumentSubtype="TICKER" Version="2" Language="ENG" FeedFlag="P" Date="2012-08-06" Time="174130012" LogicalDate="2012-08-06" Source="PDC">
<Competition>
<Document Parent="0" >
<Message>
<![CDATA[New Notificacion]]>
</Message>
</Document>
</Competition>
</OdfBody>

2.2.20.7 Message sort

There is no specific sorting for this message

 

2.2.21 TV Tracking

2.2.21.1 Description

The TV Tracking message alerts users as to which event unit or activity is currently the focus of the integrated TV production. This message only applies in athletics, artistic gymnastics and ceremonies.

2.2.21.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (event level)

RSC at event level. Event only applicable in Ceremonies otherwise discipline level.

DocumentType

DT_TV_TRACKING

TV Tracking Message

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.21.3 Trigger and Frequency

The message triggered with each change to a new activity or unit in the current discipline.

2.2.21.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

 

 

 

 

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (0,N)

 

Type

 

Code

 

Pos

 

Value

 

Extension (0,N)

 

Code

 

Pos

 

Value

2.2.21.5 Message Values

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

Attribute

M/O

Value

Description

Type

 

 

See extended definition if applicable

Code

 

 

 

Pos

 

 

 

Value

 

 

 

 

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

Attribute

M/O

Value

Description

Code

 

 

See extended definition if applicable

Pos

 

 

 

Value

 

 

 

 

The following table describes in more detail the ExtendedInfo.

Type

Code

Pos

Value

Description

Expected

EI

UNIT

 

S(9)

For @Type:

Send proposed type

In athletics when changing to a new unit.

In gymnastics when changing to a new apparatus.

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

The RSC of the current unit in CIS TV Tracking.

In athletics it is the unit, in gymnastics it will be the apparatus (phase and unit 000)

ACTIVITY

 

S(100)

For @Type:

Send proposed type

In Ceremonies when changing to a new activity.

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Title of the current CIS TV Tracking activity in ceremonies.

NOC

 

CC @NOC

For @Type:

Send proposed type

In Ceremonies when changing to a single selected NOC.

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

The NOC code of the current NOC in CIS TV Tracking if a single NOC is selected in ceremonies.

 

2.2.21.6 Sample

Athletics

<OdfBody CompetitionCode="OG2016" DocumentCode="ATH-------------------------------" DocumentType="DT_TV_TRACKING" FeedFlag="P" Date="2016-07-31" LogicalDate="2016-07-31" Time="101314696" Source="PDC" Version="25">
 <Competition>
 <ExtendedInfos>
 <ExtendedInfo Type="EI" Code="UNIT" Value="ATHM100M--------------FNL-0001----"/>
 </ExtendedInfos

<Competition>
</OdfBody>

 

Artistic Gymnastics

<OdfBody CompetitionCode="OG2016" DocumentCode="GAR-------------------------------" DocumentType=" DT_TV_TRACKING " FeedFlag="P" Date="2016-07-31" LogicalDate="2016-07-31" Time="101314696" Source="PDC" Version="25">
 <Competition>
 <ExtendedInfos>
 <ExtendedInfo Type="EI" Code="UNIT" Value="GARMVAULT-------------------------"/>
 </ExtendedInfos
 <Competition>
</OdfBody>

 

Ceremonies (Activities)

<OdfBody CompetitionCode="OG2016" DocumentCode="CER-OPENING-----------------------" DocumentType="DT_TV_TRACKING " FeedFlag="P" Date="2016-07-31" LogicalDate="2016-07-31" Time="101314696" Source="PDC" Version="25">
 <Competition>
 <ExtendedInfos>
 <ExtendedInfo Type="EI" Code="ACTIVITY" Value="Bach Speech" />
 </ExtendedInfos
 <Competition>
</OdfBody>

 

Ceremonies (March)

<OdfBody CompetitionCode="OG2016" DocumentCode="CER-OPENING-----------------------" DocumentType="DT_TV_TRACKING" FeedFlag="P" Date="2016-07-31" LogicalDate="2016-07-31" Time="101314696" Source="PDC" Version="25">
 <Competition>
 <ExtendedInfos>
 <ExtendedInfo Type="EI" Code="NOC" Value="ESP" />
 </ExtendedInfos
 <Competition>
</OdfBody>

 

2.2.21.7 Message sort

There is no specific sorting for this message

 

2.2.22 News Document

2.2.22.1 Description

The News Document message contains individual news.

The message resets the previous news. Each message includes one news document.

2.2.22.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC (discipline level)

RSC at the discipline level

DocumentSubcode

Numeric

News’ ID

DocumentType

DT_NEWS

News Document

DocumentSubtype

CC @NewsReport

News Subtype (Code of application Criteria level 2), that is code of the item type like FQ for Flash Quotes.

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.22.3 Trigger and Frequency

Trigger every time that a news document is published.

2.2.22.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

 

 

 

Competition (0,1)

 

Document (1,1)

 

Parent

ExternalCode

Category

CategoryName

Item

ItemName

ItemDate

ItemTime

Unit

ModificationIndicator

 

Related (0,1)

 

Athlete (0,N)

 

Code

Order

Bib

Description (0,1)

 

GivenName

FamilyName

Gender

Organisation

BirthDate

IFId

 

Coach (0,N)

 

Code

Function

Order

Description (0,1)

 

GivenName

FamilyName

Gender

Nationality

 

Team (0,N)

 

Code

Order

Description (0,1)

 

TeamName

IFId

 

Title

 

-

 

Body

 

-

 

2.2.22.5 Message Values

Element: Document (1,1)

Attribute

M/O

Value

Description

Parent

M

Numeric4

Parent’s ID.

If the report has no parent ID then it takes value 0.

ExternalCode

O

S(10)

External Identifier for the News article. This is only Mandatory for DT_NEWS_IMP

Category

M

CC @NewsSport

Code of application Criteria level 1 (usually sport but may be other categories)

CategoryName

M

S(40)

Category Name

Item

M

CC @NewsReport

News Subtype (Code of application Criteria level 2), that is code of the item type like FQ for Flash Quotes.

ItemName

M

S(40)

Item Name

ItemDate

O

Date

Date of publication or re-publication of the news item. Not required for import or ModificationIndicator=”D” otherwise it is required.

ItemTime

O

Time

Time of publication or re-publication of the news item. Not required for import or ModificationIndicator=”D” otherwise it is required..

Unit

O

CC @Unit

Full RSC of the Unit (can be Event, Phase or Unit level)

ModificationIndicator

O

S(1)

Send only to delete or unpublish an article, when needed send D for Delete.

 

Element: Document /Related (0,1) /Athlete (0,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete’s ID.

Order

M

Numeric

Order attribute used to sort the athletes

Bib

O

String

Bib number

 

Element: Document /Related /Athlete /Description (0,1)

Athletes extended information, this is required except when ModificationIndicator=”D”.

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

 

Element: Document /Related (0,1) /Coach (0,N)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Official code. This code is normally expected though there may be rare exceptions.

Function

O

CC @ResultsFunction

Official function

Order

M

Numeric

Coach order

 

Element: Document /Related /Coach /Description (0,1)

Coach extended information this is required except when ModificationIndicator=”D”.

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 Code

Nationality

M

CC @Country

Coach's nationality

 

Element: Document /Related (0,1) /Team (0,N)

Attribute

M/O

Value

Description

Code

O

S(20) with no leading zeroes

Competitor’s ID

Order

M

Numeric

Team order

 

Element: Document /Related /Team /Description (0,1)

Team extended information this is required except when ModificationIndicator=”D”.

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups.

IFId

O

S(16)

International Federation ID

 

Element: Document /Title

Attribute

M/O

Value

Description

-

M

S(100)

Text describing Document Title

 

Element: Document /Body

Attribute

M/O

Value

Description

-

M

Free text5

Free Text containing the Body of the HTML article.

2.2.22.6 Sample

<OdfBody CompetitionCode="OG2012" DocumentCode="ATH-------------------------------" Time="231728981" Date="2012-08-04" FeedFlag="P" LogicalDate="2012-08-04" DocumentSubcode="155276" Language="ENG" DocumentType="DT_NEWS" DocumentSubtype="FQ" Source="IDS" Version="1" >
<Competition>
<Document Parent="0" Category="AT" CategoryName="Athletics" Item="FQ" ItemName="Flash Quotes" ItemDate="2012-08-04" ItemTime="211300000" Unit="ATHMLJ----------------------------">
<Related>
<Athlete Code="1077408" Order="1" >
<Description GivenName="Mitchell" FamilyName="Watt" Gender="M" Organisation="AUS" BirthDate="1993-12-15" />
</Athlete>
<Athlete Code="1077444" Order="2" >
<Description GivenName="Will" FamilyName="Claye" Gender="M" Organisation="USA" BirthDate="1992-11-14" />
</Athlete>
</Related>
<Title>Men's Long Jump: WATT (AUS) - Silver, CLAYE (USA) - Bronze</Title>
<Body>
<![CDATA[<p>LONDON, 4 August - Comments from silver medallist Mitchell WATT (AUS) and bronze medallist Will CLAYE (USA) at a media conference following the men's long jump final at the Olympic Stadium on Saturday.</p>
<p><strong>Mitchell WATT (AUS) - silver</strong></p>
<p><em>On taking silver:</em><br />"There is a reason why the Olympic Games is the pinnacle of our sport. This is so much sweeter than the silver at the (2011) world championships."</p>
<p><em>On a slow start to the competition:</em><br />"A lot of us will not have got much sleep last night and the wind was tricky too. It was a whole lot different from a Diamond League meeting. My run was pretty scrappy in the first three runs and then I was lucky to get one out."</p>
<p><em>On the noise from the crowd:</em><br />"I think my best jump was when Jessica ENNIS (GBR) was going round doing the 800m and so I thank her for that. I was British for a few moments."</p>
<p><em>On the&nbsp; gold medallist, ;(Greg RUTHERFORD, GBR):</em><br />"He is my closest friend on the circuit. He had a tough time when he tore his hammy (hamstring, in the qualifying round of the 2011 world championships). He deserved to win. He jumped 8.31 which beats my season's best."</p>
<p><strong>Will CLAYE (USA) - bronze</strong></p>
<p><em>On taking the bronze:</em><br />"I am thankful. I wanted gold but now I will have to get the gold in the triple (jump)."</p>
<p>"This will help tremendously because I have been on the runway twice now and the triple jump is my event. I am just going to take these next few days to get my mind and body right to come back on Tuesday."</p>
<p><em>On support from the crowd:</em><br />"They showed us much love. The crowd was going crazy with their clapping. They made us feel at home and we are not even from here."</p>
<p>ONS cb/ts/jps/tc</p>]]></Body>
</Document>
</Competition>
</OdfBody>

2.2.22.7 Message sort

There is no specific sorting for this message

 

2.2.23 News Document Import

2.2.23.1 Description

The News Document Import is a message containing an individual News Document.

The message resets the previous News Document Import information. There is only one News Document per message.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.23.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Numeric

News’ identifier

DocumentType

DT_NEWS_IMP

News Document Import

DocumentSubtype

CC @NewsReport

News Subtype (Code of application Criteria level 2), that is code of the item type like FQ for Flash Quotes.

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.23.3 Trigger and Frequency

Trigger during operation period.

2.2.23.4 Message Structure

The structure of the News Document Import message is the same as the News Document message.

2.2.23.5 Message Values

All message attributes are the same as the news document message.

2.2.23.6 Message sort

There is no specific sorting for this message

 

2.2.24 Transport Document (Shuttle Service)

2.2.24.1 Description

The Transport Document (Shuttle Service) message contains individual shuttle services’ information.

The message resets the previous shuttle service data. Each message includes one shuttle service.

2.2.24.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-TTT---------------------------

TTT – Type of Shuttle Service (ATH, OFF, MED)

DocumentSubcode

Numeric

Shuttle Service’s identifier

DocumentType

DT_TRS

Transport Document

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.24.3 Trigger and Frequency

Trigger every time that a shuttle service is published.

2.2.24.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

 

 

 

 

 

Competition (0,1)

 

Document (1,1)

 

Parent

ShuttleServiceType

ShuttleServiceTypeName

LineIdentifier

AssociatedVenue (0,N)

 

Code

 

ModificationIndicator

Title

 

-

 

Body

 

-

 

2.2.24.5 Message Values

Element: Document (1,1)

Attribute

M/O

Value

Description

Parent

M

Numeric6

Parent’s ID.

If the report has no parent, 0

ShuttleServiceType

M

CC @ShuttleServiceType

Code of Shuttle Services Type

ShuttleServiceTypeName

M

S(40)

Shuttle Service Type Name

LineIdentifier

M

S(10)

Shuttle Service’s ID

 

Element: Document /AssociatedVenue (0,N)

Attribute

M/O

Value

Description

Code

M

CC @VenueCode

Venue code for a venue associated to the Shuttle Service

 

Element: Document /ModificationIndicator

Attribute

M/O

Value

Description

ModificationIndicator

O

S(1)

Send only to delete or unpublish an article, when needed send D for Delete.

 

Element: Document /Title

Attribute

M/O

Value

Description

-

M

S(100)

Text describing Document Title

 

Element: Document /Body

Attribute

M/O

Value

Description

-

M

Free text7

Free Text containing the Body of the HTML article.

2.2.24.6 Message sort

There is no specific sorting for this message

 

2.2.25 Transport Document Import (Shuttle Service)

2.2.25.1 Description

The Transport Document Import (Shuttle Service) is a message containing an individual Transport Document (Shuttle Service).

The message resets the previous Transport Document Import (Shuttle Service). There is only one Transport Document Import (Shuttle Service) per message.

Note that this message is not distributed and only used to initialise the central systems from the data provider.

2.2.25.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Numeric

Shuttle Service’s ID.

DocumentType

DT_TRS_IMP

Type of Transport documents

Version

1...V

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

Language

CC @Language

Language code

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.25.3 Trigger and Frequency

Trigger during operation period, and some days before the operation starts.

2.2.25.4 Message Structure

The structure of the Transport Document Import (Shuttle Service) message is the same as the Transport Document Import (Shuttle Service).

2.2.25.5 Message Values

All message attributes are the same as the Transport Document Import (Shuttle Services) ones.

2.2.25.6 Message sort

There is no specific sorting for this message

 

2.2.26 Extended Start List

2.2.26.1 Description

The Extended Start List is a message containing the list of competitors for one particular event unit with additional information for each competitor. Competitors could be individual athletes, teams or team members.

It is a generic message for all sports, including as much generic information as possible, considering different types of disciplines and events can have substantial differences (e.g.: mass start lists, line-ups, etc.).

The mandatory attributes and elements defined in this message will have to be used by all the sports. Each ODF Sport Data Dictionary will refine the details of this message with the peculiarities of the discipline.

2.2.26.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

 

DocumentSubcode

 

Provides greater granularity for document if DocumentCode is not sufficient.

DocumentType

DT_ESL

Extended Start List

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.26.3 Trigger and Frequency

Trigger when all the competitors for one particular event unit are known.

For team events, trigger this message when the teams are available for the event unit, and for some disciplines afterwards when team members are also known.

Trigger also after any major change.

If there is any sport-specific requirement, it is detailed in each of the ODF Sport Data Dictionaries.

2.2.26.4 Message Structure

The message structure of the Extended Start List is the same as the Start List message, but adding the element ExtCompetitor as optional in the elements Start/Competitor and Start/Competitor/Composition/Athlete (detailed in the next section).

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Level 9

Competition (0,1)

 

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

 

Athlete (1,N)

 

FamilyName

GivenName

 

SportDescription (0,1)

 

Disciplinename

EventName

SubEventName

Gender

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)

 

Type

Code

Pos

Value

 

Extension (0,N)

 

Code

Pos

Value

 

Partial (0,N)

 

Code

Score

OppScore

 

Officials (0,1)

 

Official (1,N)

 

Code

Function

Order

Bib

Description

 

GivenName

FamilyName

Gender

Organisation

IFId

ExtendedDescription (1,N)

 

Type

Code

Pos

Value

 

ExtOfficial (0,N)

 

Type

Code

Pos

Value

 

Periods (0,1)

 

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

StartSortOrder

ResultType

Diff

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

Code

Pos

Value

ValueType

IRM

Rank

RankEqual

SortOrder

Diff

Speed

Move

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

Result

ResultPoints

IRM

QualificationMark

Diff

WLT

SortOrder

StartOrder

StartSortOrder

ExtendeResults (0,1)

 

ExtendedResult

 

Type

Code

Pos

Value

ValueType

IRM

Rank

RankEqual

SortOrder

Diff

Extension

 

Code

Pos

Value

 

RecordIndicators (0,1)

 

RecordIndicator (1,N)

 

Order

Code

RecordType

Equalled

 

Competitor

 

Code

Type

Bib

Organisation

Description (0,1)

 

TeamName

IFId

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

ExtCompetitor (0,1) (see Table Note)

ExtResults (0,1) (see Table Note)

 

-

 

Coaches (0,1)

 

Coach (1,N)

 

Code

Function

Order

Bib

Description

 

GivenName

FamilyName

Gender

Nationality

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

EventUnitEntry (0,N)

 

Type

Code

Pos

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

Code

Pos

Value

Rank

RankEqual

SortOrder

ExtendedStat (0,N)

 

Code

Pos

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

Order

StartOrder

StartSortOrder

Bib

Description

 

GivenName

FamilyName

Gender

Organisation

BirthDate

IFId

Class

Horse

GuideID

GuideFamilyName

GuideGivenName

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

ExtCompetitor (0,1) (see Table Note)

ExtResults (0,1) (see Table Note)

Club (0,1)

Coach (0,1)

 

-

 

EventUnitEntry (0,N)

 

Type

Code

Pos

Value

 

ExtendedResults (0,1)

 

ExtendedResult (1,N)

 

Type

Code

Pos

Value

ValueType

IRM

Rank

RankEqual

SortOrder

Diff

Speed

Move

Unchecked

Extension (0,N)

 

Code

Pos

Value

 

StatsItems (0,1)

 

StatsItem (1,N)

 

Type

Code

Pos

Value

Rank

RankEqual

SortOrder

ExtendedStat (0,N)

 

Code

Pos

Value

Table Note: “Results” and “Extended Start List” share the same message’s structure and attributes, except for the ExtCompetitor, ExtResults, Club and Coach_ID (these two last only for Athletes) elements. These are specific elements of the “Extended Start List” message.

2.2.26.5 Message Values

All message attributes are the same as the DT_RESULT (START_LIST) message, but including the attributes defined below.

 

Element: Result /Competitor /ExtCompetitor (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Team’s extended information.

 

Element: Result /Competitor /ExtResults (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Team’s extended results information.

 

Element: Result /Competitor /Composition /Athlete /ExtCompetitor (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Athlete or team member’s extended information.

 

Element: Result /Competitor /Composition /Athlete /ExtResults (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Athlete or team member’s extended Results information.

 

Element: Result /Competitor /Composition /Athlete /Club (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Athlete or team member’s club name.

 

Element: Result /Competitor /Composition /Athlete /Coach (0,1)

Attribute

M/O

Value

Description

-

O

Free Text

Athlete or team member’s coach ID.

 

2.2.26.6 Message sort

Sort according to Result @SortOrder attribute used to sort the results (more detail in each of the ODF Sport Data Dictionaries), and other @Order attributes if used for each of the disciplines.

 

2.2.27 Pictures

2.2.27.1 Description

The Pictures message may contains pictures of athletes, coaches or officials depending on the competition and the discipline.

2.2.27.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

CC @Discipline

Full (Char34) RSC Discipline code for the participant

DocumentSubcode

S(20) with no leading zeroes

Participant’s ID (for an athlete, coach or official)l

DocumentType

DT_PIC

Picture message

DocumentSubtype

S(20)

ACR for Accreditation Photos

HEADSHOT for Higher quality photos.

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.27.3 Trigger and Frequency

Trigger the first day of the press operations, and after any change..

2.2.27.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

 

 

 

 

 

 

Competition (0,1)

 

Picture

 

ModificationIndicator

-

 

2.2.27.5 Message Values

Element: Picture

Attribute

M/O

Value

Description

ModificationIndicator

O

S(1)

Send only to delete or unpublish an image, when needed send D for Delete.

-

M

Free Text

The Picture element may have a body consisting of one Base64-encoded image as a JPEG image (.jpg).

 

2.2.27.6 Sample

<Competition>
<Picture>/9j//2wBDAQcHBwoIChMKChMoGhYaKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCj/…………kik+UaZmiiqGtj/2Q==</Picture>
</Competition>

2.2.27.7 Message sort

There is no specific sorting for this message.

 

2.2.28 Notification Message

2.2.28.1 Description

The Notification message contains a notification about the availability of an online document.

2.2.28.2 Header Values

The following table describes the ODF header attributes

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

S(34)

Document Code of the online document that is being notified.

DocumentSubcode

S(34)

Document Subcode of the online document that is being notified.

DocumentType

DT_NOTIFICATION

Notification message

DocumentSubtype

S(50)

Concatenation of the Document Type and Document Subtype attributes of the online document that is being notified.

This is needed to preserve the Key of the message.

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.28.3 Trigger and Frequency

Trigger of this message is after the reception of the original message that is made available online.

2.2.28.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

 

 

 

 

 

 

Competition (0,1)

 

DirectLink

 

Link

DocumentType

DocumentSubtype

 

2.2.28.5 Message Values

Element: DirectLink

Attribute

M/O

Value

Description

Link

M

S(255)

URL of the link to the document

DocumentType

M

S(30)

DocumentType of the original message

DocumentSubtype

O

S(20)

DocumentSubtype of the original message

 

2.2.28.6 Sample

<Competition>
<DirectLink Link="https://bif.london2012.com/bif/directaccess/your_doc_here.jpg" DocumentType="DT_NOTIFICATION" />
</Competition>

2.2.28.7 Message sort

There is no specific sorting for this message.

 

2.2.29 Schedule and Results by NOC

2.2.29.1 Description

The “Schedule and Results by NOC” message contains this information for a single organisation on a single competition day (between the global GM & GN of the day). It only contains competition activities (Phase Type=Competition). Several disciplines may appear in a single message.

It increments its content as more events units are completed by the organisation during the day, and it always includes all data for the day. The arrival of the message resets the entire previous “Schedule and Results by NOC” information.

Information includes only competitors of the current organisation or all competitors in the case an event unit is Head to Head. It also includes competitors defined as group (Competitor Type = Group). In this case, a group is treated as individual competitors and only includes the athletes of the specific organisation.

The message does not include information about horses, records, coaches, period results and actions.

2.2.29.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------DAY-dd----------

Global message for all disciplines

(sent at daily level, where dd is the Day)

DocumentSubcode

NOC Code

 

DocumentType

DT_SCHED_RES_NOC

Schedule and Results by NOC

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.29.3 Trigger and Frequency

This message is sent multiple times daily after “Global good morning” message has been sent (only for current logical date). The exact frequency is determined at a given competition.

2.2.29.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Level 9

Competition (0,1)

 

Unit (1,N)

 

Code

PhaseType

UnitNum

ScheduleStatus

StartDate

HideStartDate

EndDate

HideEndDate

ActualStartDate

ActualEndDate

Order

Medal

Venue

Location

SessionCode

StartText (0,N)

 

Language

Value

 

ItemName (1,N)

 

Language

Value

 

VenueDescription

 

VenueName

LocationName

 

Result (0,N)

 

Rank

RankEqual

ResultType

Result

IRM

QualificationMark

WLT

SortOrder

StartOrder

StartSortOrder

Competitor

 

Code

Type

Bib

Organisation

Description (0,1)

 

TeamName

IFId

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

Composition (0,1)

 

Athlete (1,N)

 

Code

Order

Bib

Description

 

GivenName

FamilyName

Gender

Organisation

BirthDate

IFId

Class

Horse

GuideID

GuideFamilyName

GuideGivenName

ExtendedDescription (0,N)

 

Type

Code

Pos

Value

 

2.2.29.5 Message Values

The values of the attributes of Result are the same as defined in the Event Unit StartList and Results message.

Element: Unit (1,N)

Attribute

M/O

Value

Description

Code

M

Full RSC

Full RSC of the Unit

PhaseType

M

CC @PhaseType

Phase type for the unit

UnitNum

O

S(6)

Match / Game / Bout / Race  Number or similar

ScheduleStatus

M

CC @ScheduleStatus

Schedule status of the Unit

StartDate

O

DateTime

Start date. This attribute may not be sent in the case of some @ScheduleStatus, such as 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.

 

Example:

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

HideStartDate

O

S(1)

SSend '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 in the case of some Unit@Status, such as those meaning cancelled, postponed.

 

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 only considered if HideStartDate = 'Y'. It should not be sent in sports which never use this concept but should be sent for all units where the concept is used.

Starts at 1 in each session each day.

Medal

O

SC @UnitMedalType

Gold medal event unit or bronze medal event unit.

Do not send if not a medal event unit

Venue

O

CC @VenueCode

VVenue where the unit takes place

Use TBD if the Venue is not known yet (CC).

Location

M

CC @Location

Location where the unit takes place

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

SessionCode

O

S(5)

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

 

Element: Unit /EstimatedStartText (0,N)

Attribute

M/O

Value

Description

Language

M

CC @Language

Code Language of the @Value

Value

M

S(20)

Text that explains when the Start Time is in the case that StartDate is an estimation (i.e. “After M.1”)

 

Element: Unit /ItemName (1,N)

Attribute

M/O

Value

Description

Language

M

CC @Language

Code Language of the @Value

Value

M

S(40)

Unit name

 

Element: Unit /VenueDescription

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: Unit/ Result (0,N)

Attribute

M/O

Value

Description

Rank

O

Text

Rank of the competitor in the result.

RankEqual

O

S(1)

Equalled rank indicator. Send “Y” if rank equalled else do not send.

ResultType

O

Same as in the Event Unit Results message for each discipline

Type of the @Result attribute

Result

O

Same as in the Event Unit Results message for each discipline

The result of the competitor in the event unit

IRM

O

Same as in the Event Unit Results message for each discipline

The invalid rank mark, in case it is assigned

QualificationMark

O

Same as in the Event Unit Results message for each discipline

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

WLT

O

Same as in the Event Unit Results message for each discipline

In head to head units:

W-Won

L-Lost

T-Tied

SortOrder

O

Same as in the Event Unit Results message for each discipline

Used to sort all results in an event unit. Prior to the competition it is the same as StartSortOrder.

StartOrder

O

Same as in the Start List message for each discipline

Competitor’s start order

StartSortOrder

M

Same as the SortOrder inthe Start List message for each discipline

Used to sort all start list competitors in an event unit

 

Element: Unit/ Result /Competitor

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Competitor’s ID

Type

M

S(1)

T - Team

A - Athlete

G - Group

Bib

O

Same as in the Start List message for each discipline

Bib number

Organisation

O

CC @Organisation

Should be sent when known.

 

Element: Unit/ Result /Competitor /Description (0,1)

Attribute

M/O

Value

Description

TeamName

M

S(73)

Name of the team. Only applies for teams / groups. Not usually for pairs (figure skating & beach volleyball are the exceptions).

IFId

O

S(16)

International Federation ID

 

Element: Unit/ Result /Competitor /Description /ExtendedDescription (0,N)

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions

Code

M

 

See sport descriptions

Pos

O

 

See sport descriptions

Value

O

 

See sport descriptions

 

 

Element: Unit/ Result /Competitor /Composition (0,1) /Athlete (1,N)

Attribute

M/O

Value

Description

Code

M

S(20) with no leading zeroes

Athlete’s ID (team member or individual athlete)

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

Bib number

 

 

Element: Unit/ Result /Competitor /Composition /Athlete /Description

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 athlete

Organisation

M

CC @Organisation

Athletes' organisation

BirthDate

O

Date

Birth date (example: YYYY-MM-DD). Must include if the data is available

IFId

O

S(16)

International Federation ID

Class

O

CC @SportClass

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

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: Unit/ Result /Competitor /Composition /Athlete /Description /ExtendedDescription (0,N)

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions

Code

M

 

See sport descriptions

Pos

O

 

See sport descriptions

Value

O

 

See sport descriptions

 

2.2.29.6 Message sort

Unit @StartDate is the attribute used to sort the Units.

Result @SortOrder will be the attribute used to sort the results. This attribute is refined in each of the ODF Sport Data Dictionaries.

 

2.2.30 List of Codes

2.2.30.1 Description

This is a simple message listing the codes used in a competition.

The data included in this message will be available as soon as practical and will usually be available in additional formats to this XML message.

2.2.30.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-------------------------------

GL is a fixed value

DocumentType

DT_CODES

List of codes

DocumentSubtype

CC @CodeSet

Code to define which code set is included in the message

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

2.2.30.3 Trigger and Frequency

The DT_CODES message is sent as soon as the data and connectivity are available and will be resent with every update.

2.2.30.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Level 9

Competition (0,1)

 

CodeSet (1,N)

 

Code

Sport

Discipline

Gender

Event

Phase

EventUnit

Schedule

Medal

Competition

Type

Group

VenueCode

Region

Country

Continent

Function

Order

Note

ExtendedCodes (0,1)

 

ExtendedCode (1,N)

 

Type

Code

Pos

Value

Extension (0,N)

 

Code

Pos

Value

 

Language (1,N)

 

Language

Description

LongDescription

 

2.2.30.5 Message Values

Element: CodeSet (1,N)

Attribute

M/O

Value

Description

Code

M

S(40)

Where there is a unique code for the codeset it appears here.

Sport

O

S(2)

Sport Code where applicable

Discipline

O

S(3)

Discipline Code where applicable

Gender

O

S(1)

Gender Code where applicable

Event

O

S(18)

Event Code where applicable (including the event modifier)

Phase

O

S(4)

Phase Code where applicable

EventUnit

O

S(8)

Event Unit Code where applicable

Schedule

O

S(1)

Y if unit is scheduled else N

Medal

O

S(1)

Medal unit indicator

Competition

O

S(1)

Y if code is related to sports competition else N for non-competition

Type

O

 

Type of Code

Group

O

 

Group of Code

VenueCode

O

S(3)

Venue code, for Location table

Region

O

S(3)

Region related to the venue

Country

O

S(3)

Country Code for Organisation Table

Continent

O

S(3)

Continent Code for Organisation Table

Function

O

S(20)

Function Code where applicable

Order

O

S(10)

Sort or for codes if applicable

Note

O

S(250)

Note or comment related to the code, informational only

 

Element: CodeSet /ExtendedCodes (0,1) /ExtendedCode (1,N)

Attribute

M/O

Value

Description

Type

M

 

See sport descriptions if extended

Code

M

 

 

Pos

O

 

 

Value

O

 

 

 

Element: CodeSet /ExtendedCodes /ExtendedCode /Extension (0,N)

Attribute

M/O

Value

Description

Code

M

 

See sport descriptions if extended

Pos

O

 

 

Value

O

 

 

 

Element: CodeSet /Language (1,N)

Attribute

M/O

Value

Description

Language

M

S(3)

Language of the Description

Description

M

S(200)

Description of the Code

LongDescription

O

S(200)

Long Description of the Code

 

2.2.30.6 Samples

Example of Country Codeset

<Competition>
…
<CodeSet Code="ERI">
<Language Language="ENG" Description="Eritrea" LongDescription="Eritrea" >
<Language Language="FRA" Description="Érythrée" LongDescription="Érythrée" >
</CodeSet>
<CodeSet Code="FIN">
<Language Language="ENG" Description="Finland" LongDescription="Finland" >
<Language Language="FRA" Description="Finlande" LongDescription="Finlande" >
</CodeSet>
…
</Competition>

 

Example of Event Codeset

<Competition>
…
<CodeSet Code="ATHMTJ----------------------------" Discipline="ATH" Gender="M" Event="TJ----------------" Order="15">
<Language Language="ENG" Description="Men's Triple Jump" >
<Language Language="FRA" Description="Triple saut - hommes" >
</CodeSet>
<CodeSet Code="ATHMHJ----------------------------" Discipline="ATH" Gender="M" Event="HJ----------------" Order="12">
<Language Language="ENG" Description="Men's High Jump" >
<Language Language="FRA" Description="Saut en hauteur - hommes" >
</CodeSet>
…
</Competition>

 

2.2.30.7 Code Sets Included

Code Set

Code

Lang.

Description

Other Fields

Note

CONTINENT

ID

Multiple

Y

 

 

COUNTRY

ID

Multiple

Y

LongDescription

 

DISCIPLINE

Char(34) unique

e.g. SWM-------------------------------

Multiple

Y

Sport
Discipline
Schedule
Order

If non-sport =Y then "non-sport"

EVENT

Char(34) unique

e.g. BKBMTEAM5-------------------------

Multiple

Y

Discipline
Gender
Event
Order

 

EVENT_UNIT

Char(34) unique

e.g. BKBMTEAM5-------------GPA-0001----

Multiple

Y

LongDescription
Discipline
Gender
Event
Phase
EventUnit
Schedule
Medal
Type (EventUnitType)

 

HORSE_BREED

ID

Multiple

Y

 

 

HORSE_COLOUR

ID

Multiple

Y

 

 

HORSE_GENDER

ID

Multiple

Y

 

 

LOCATION

ID

Multiple

Y

LongDescription
Competition
VenueCode
Order

 

MARITAL_STATUS

ID

Multiple

Y

 

 

NOC

ID

Multiple

Y

LongDescription
Country
Continent

Value of Participating

NPC

ID

Multiple

Y

LongDescription
Country
Continent

Value of Participating

ODF_SPORT_CODES

Code

ENG

Y

Discipline
Type (Code_Entity)
Order

Note

ORGANISATION

ID

Multiple

Y

LongDescription
Type

 

PHASE

Char(34) unique

e.g. BKBMTEAM5-------------GPA---------

Multiple

Y

LongDescription
Discipline
Gender
Event
Phase
Type

 

POSITION

ID

Multiple

Y

Discipline
Order

 

RECORD

ID

Multiple

Y

Discipline
Gender
Event
Order

 

RECORD_TYPE

RecordType

Multiple

Y

Discipline
Group (RecordGroup)
Order

 

DISCIPLINE_FUNCTION

ID (concatenation Discipline & Function) e.g. BKCOACH

Multiple

Y

Discipline
Function
Type (Function Category)
Order

 

SPORT

ID

Multiple

Y

 

 

VENUE

ID

Multiple

Y

LongDescription
Region
Competition

 

WTHR_CONDITION

ID

Multiple

Y

 

 

WTHR_REGION

ID

Multiple

Y

 

 

WTHR_SNOW

ID

Multiple

Y

 

 

WTHR_WIND_DIR

ID

Multiple

Y

 

 

BCK_TYPE

ID

Multiple

Y

 

 

BCK_SPORT

ID

Multiple

Y

 

 

NWS_TYPE

ID

Multiple

Y

 

 

NWS_SPORT

ID

Multiple

Y

 

 

H1_HEADING

ID (Concatenation of Discipline and ORIS_NO)

Multiple

Y

Discipline

Group(ORIS_NO)

 

 

2.2.30.8 Message sort

The message does not have any defined sort order.

 

2.2.31 Venue Conditions

2.2.31.1 Description

The weather condition is a message containing the forecast and current conditions of the venue for today and several days.

2.2.31.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-----------------------VVV-----

VVV is CC@VenueCode

DocumentType

DT_VEN_COND

Venue weather conditions message

DocumentSubtype

CC @VenueCode

Venue code

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.31.3 Trigger and Frequency

This message should be sent on an hourly basis, from 6:00 to 21:00 at least, as close as possible to the top of the hour. Past/Current hours should be updated with real data, not forecast.

An additional message is required every day before 00:15. This should be considered the first message of the day.

The forecast information to be included in the message is:

For Summer Games

First/Current day

 

 

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 1

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 2

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

 

First/Current day

 

 

 

 

12:00

15:00

18:00

21:00

Current day + 1

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 2

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

 

First/Current day

 

 

 

 

 

 

18:00

21:00

Current day + 1

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 2

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 3

0:00

3:00

6:00

 

 

 

 

 

 

First/Current day

 

 

 

 

 

 

 

 

Current day + 1

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 2

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 3

0:00

3:00

6:00

 

 

 

 

 

 

For Winter Games

First/Current day

6:00

7:00

8:00

9:00

10:00

11:00

12:00

13:00

14:00

15:00

16:00

17:00

18:00

19:00

20:00

21:00

Current day + 1

0:00

3:00

6:00

9:00

12:00

15:00

18:00

21:00

Current day + 2

0:00

3:00

6:00

9:00

12:00

15:00

18:00

 

 

2.2.31.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

 

 

 

Competition (0,1)

 

Venue

 

Code

DateTime (1,N)

 

Date

Code

Time

Conditions

 

Code

Humidity

Wind_Direction

Wind_Degree

Prec_Type

Condition (1,2)

 

Code

Value

 

Precipitation (0,N) (*)

 

Code

Value

 

Pressure (0,N)

 

Code

Value

 

Temperature (1,N)(***)

 

Code

Unit

Type

Value

 

Wind (1,N) (****)

 

Code

Unit

Value

 

Description (0,N)

 

Period

Language

-

(*) N depends on the @Unit

(**) N depends on the @Unit

(***) N depends on the @Code+@Unit+@Type

(****) N depends on the @Code+@Unit

 

2.2.31.5 Message Values

Element: Venue

Attribute

M/O

Value

Description

Code

M

CC @VenueCode

Unique ID of the Venue

 

Element: Venue /DateTime (1..N)

Attribute

M/O

Value

Description

Date

M

Date

 

Code

M

TIME, DAY, NIGHT, GLOBAL

TIME is the hourly forecast

DAY is the forecast for the morning data of the day

NIGHT is the forecast for the night data of the day

GLOBAL is the forecast for the data of the day

Time

O

Time

Time of the conditions

Only required for @Code=TIME

 

Element: Venue /DateTime /Conditions

Attribute

M/O

Value

Description

Code

M

GEN

Use “GEN” as a general Weather Point at the venue

Humidity

M

Numeric

Humidity in %

Wind_Direction

M

CC @WindDirection

Wind direction

Wind_Degree

M

Numeric

Wind Degree (direction)

Prec_Type

O

SC @PrecType

Precipitation type

 

Element: Venue /DateTime /Conditions/Condition (1,2)

Attribute

M/O

Value

Description

Code

M

SKY or SNOW

Weather conditions type

Use SNOW only for Winter.

Value

M

CC @WeatherCondition

Codes that describe the Weather Condition

 

Element: Venue /DateTime /Conditions/Precipitation (0,N)

Attribute

M/O

Value

Description

Unit

M

SC @PrecipitationUnit

System of measurement for precipitation

Value

M

###0.0

Precipitation quantity

 

Element: Venue /DateTime /Conditions/Pressure (0,N)

Attribute

M/O

Value

Description

Unit

M

SC @PressureUnit

Metric system unit for pressure

Value

M

###0

Air pressure

 

Element: Venue /DateTime /Conditions/Temperature (1,N)

Attribute

M/O

Value

Description

Code

M

AIR, SNOW, WIND

Air, Snow  or Wind Chill temperature

Snow  and Wind Chill temperature only Mandatory in Winter

Unit

M

SC @TemperatureUnit

System of measurement for temperature

Type

O

MAX, MIN, NOR

Maximum, Minimum or Normal temperature

Maximum and Minimum only required for @Code=AIR (and only for Time = DAY, NIGHT and GLOBAL)

 

NOR is the average temperature for this Date and Time.

Value

M

+/- ##0.0

Temperature value of @Code

 

Element: Venue /DateTime /Conditions/Wind (1,N)

Attribute

M/O

Value

Description

Code

M

SPEED, GUSTS

Wind Speed and Wind Gusts

Gusts is only Mandatory in Winter

Unit

M

SC @WindUnit

System of measurement for wind

Value

M

##0.00

Wind value of  @Code

 

Element: Venue /DateTime /Description

Attribute

M/O

Value

Description

Period

M

SC @WeatherPeriod

Only use at Midday and at Tonight

Language

M

CC@Language

Language

-

M

Free Text

Description of the weather in a Venue with no more than 4000 characters

 

2.2.31.6 Sample

……
<Competition>
<Venue Code="RAB">
<DateTime Date="2012-07-18" Time="030000000" Code="TIME">
<Conditions Code="C" Humidity="95" Wind_Degree="221" Wind_Direction="SW" Prec_Type="R">
<Condition Code="SKY" Value="medcld"/>
<Precipitation Value="0.0" Unit="M"/>
<Pressure Value="1018" Unit="HPA"/>
<Temperature Code="AIR" Value="16.3" Unit="C" Type="NOR"/>
<Wind Code="SPEED" Value="4.48" Unit="MS"/>
</Conditions>
</DateTime>
<DateTime Date="2012-07-18" Time="040000000" Code="TIME">
<Conditions Code="C" Humidity="94" Wind_Degree="232" Wind_Direction="SW" Prec_Type="R">
<Condition Code="SKY" Value="medcld"/>
<Precipitation Value="0.0" Unit="M"/>
<Pressure Value="1017" Unit="HPA"/>
<Temperature Code="AIR" Value="15.6" Unit="C" Type="NOR"/>
<Wind Code="SPEED" Value="4.94" Unit="MS"/>
</Conditions>
</DateTime>
<DateTime Date="2012-07-18" Time="050000000" Code="TIME">
<Conditions Code="C" Humidity="92" Wind_Degree="229" Wind_Direction="SW" Prec_Type="R">
<Condition Code="SKY" Value="medcld"/>
<Precipitation Value="0.0" Unit="M"/>
<Pressure Value="1016" Unit="HPA"/>
<Temperature Code="AIR" Value="15.2" Unit="C" Type="NOR"/>
<Wind Code="SPEED" Value="4.70" Unit="MS"/>
</Conditions>
</DateTime>
……
<DateTime Date="2012-07-18" Code="GLOBAL">
<Conditions Code="C" Humidity="87" Wind_Degree="226" Wind_Direction="SW" Prec_Type="R">
<Condition Code="SKY" Value="medcld"/>
<Precipitation Value="1.9" Unit="M"/>
<Pressure Value="1012" Unit="HPA"/>
<Temperature Code="AIR" Value="14.0" Unit="C" Type="MIN"/>
<Temperature Code="AIR" Value="18.7" Unit="C" Type="MAX"/>
<Wind Code="SPEED" Value="5.57" Unit="MS"/>
</Conditions>
<Description Language="ENG" Period="MD">Generally cloudy perhaps with rain at times.</Description>
<Description Language="FRA" Period="MD">Nuageux avec rares averses peut-etre.</Description>
<Description Language="ENG" Period="TN">No further detail.</Description>
<Description Language="FRA" Period="TN">Aucun autre détail.</Description>
</DateTime>
<DateTime Date="2012-07-18" Code="DAY">
<Conditions Code="C" Humidity="87" Wind_Degree="226" Wind_Direction="SW" Prec_Type="R">
<Condition Code="SKY" Value="medcld"/>
<Precipitation Value="1.9" Unit="M"/>
<Pressure Value="1012" Unit="HPA"/>
<Temperature Code="AIR" Value="18.7" Unit="C" Type="MAX"/>
<Wind Code="SPEED" Value="5.57" Unit="MS"/>
</Conditions>
<Description Language="ENG" Period="MD">Generally cloudy perhaps with rain at times.</Description>
<Description Language="FRA" Period="MD">Nuageux avec rares averses peut-etre.</Description>
<Description Language="ENG" Period="TN">No further detail.</Description>
<Description Language="FRA" Period="TN">Aucun autre détail.</Description>
</DateTime>
<DateTime Date="2012-07-18" Code="NIGHT">
<Conditions Code="C" Humidity="82" Wind_Degree="255" Wind_Direction="WSW" Prec_Type="R">
<Condition Code="SKY" Value="prtcld"/>
<Precipitation Value="0.0" Unit="M"/>
<Pressure Value="1008" Unit="HPA"/>
<Temperature Code="AIR" Value="14.0" Unit="C" Type="MIN"/>
<Wind Code="SPEED" Value="5.20" Unit="MS"/>
</Conditions>
<Description Language="ENG" Period="MD">Generally cloudy perhaps with rain at times.</Description>
<Description Language="FRA" Period="MD">Nuageux avec rares averses peut-etre.</Description>
<Description Language="ENG" Period="TN">No further detail.</Description>
<Description Language="FRA" Period="TN">Aucun autre détail.</Description>
</DateTime>
<DateTime Date="2012-07-19" Code="GLOBAL">
<Conditions Code="C" Humidity="65" Wind_Degree="288" Wind_Direction="WNW" Prec_Type="R">
<Condition Code="SKY" Value="lrshrd"/>
<Precipitation Value="1.9" Unit="M"/>
<Pressure Value="1010" Unit="HPA"/>
<Temperature Code="AIR" Value="14.2" Unit="C" Type="MIN"/>
<Temperature Code="AIR" Value="19.1" Unit="C" Type="MAX"/>
<Wind Code="SPEED" Value="5.14" Unit="MS"/>
</Conditions>
<Description Language="ENG" Period="MD">Cloudy with spells of rain, perhaps heavy at times.</Description>
<Description Language="FRA" Period="MD">Nuageux avec pluie persistante, peut- être forte à certains moments.</Description>
<Description Language="ENG" Period="TN">No further detail.</Description>
<Description Language="FRA" Period="TN">Aucun autre détail.</Description>
</DateTime>
……
</Venue>
</Competition>
……

2.2.31.7 Message sort

The message does not have any defined sort order.

 

2.2.32 Weather Alerts

2.2.32.1 Description

The weather alert is a message containing the current alerts for the Regions (Summer Games) or for the Venues (in Winter Games).

When there is a weather situation that makes it necessary to alert the audience, one message has to be provided. Region/Venue Alert messages are produced only in exceptional conditions.

2.2.32.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

GEN-----------------------VVV-----

VVV is CC@VenueCode  (for Winter Games)  or CC@WeatherRegion (for Summer Games)

DocumentType

DT_WEA_ALERT

Weather alert message

DocumentSubtype

CC @VenueCode or

CC@WeatherRegion

Venue code (for Winter Games) or Region code (for Summer Games)

Version

1...V

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

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

Source

SC @Source

Code indicating the system which generated the message.

2.2.32.3 Trigger and Frequency

Whenever there is a weather situation that makes it necessary to alert the audience.

 

2.2.32.4 Message Structure

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

 

 

 

 

Competition (0,1)

 

Place

 

Code

Alert (1,N)

 

Code

ValidFrom

 

Date

Time

 

ValidTo

 

Date

Time

 

Description

 

Language

-

 

2.2.32.5 Message Values

Element: Place

Attribute

M/O

Value

Description

Code

M

CC @VenueCode or

CC@WeatherRegion

Unique ID of the Venue or Region

 

Element: Place /Alert (1,N)

Attribute

M/O

Value

Description

Code

M

Numeric

Alert Sequential Number

 

Element: Place /Alert /ValidFrom

Attribute

M/O

Value

Description

Date

M

Date

Start date of validity

Time

M

Time

Start time of validity

 

Element: Place /Alert /ValidTo

Attribute

M/O

Value

Description

Date

M

Date

End date of validity

Time

M

Time

End time of validity

 

 

Element: Place /Alert /Description

Attribute

M/O

Value

Description

Language

M

CC@Language

Language

-

M

Free Text

Description of the weather alert

 

2.2.32.6 Sample

……
<Competition>
<Place Code="SFV">
<Alert Code="1">
<ValidFrom Date="2014-02-15" Time="080000000"/>
<ValidTo Date="2014-02-15" Time="210000000"/>
<Description Language="ENG">The temperature increase up to 6-13 degrees will be expected.</Description>
<Description Language="FRA">L'élévation de la température jusqu'à 6 à 13 degrés.</Description>
</Alert>
</Place>
<Competition>
……

2.2.32.7 Message sort

The message does not have any defined sort order.

 

1  Parent: background documents are originally created in English. If the Press Operations staff consider it appropriate to translate any report, the translations can be created from the English one. For translated items Parent element is the DocumentSubcode of the English version. Example:

English version -> DocumentSubcode =”1230”

French translation -> Parent=”1230”

2  The information provided should be codified in UTF-8.

3  Parent: Breaking News Documents are originally created in English. If Press Operation staff considers interesting to translate any report, the translations are created from the English one. @Parent links to the DocumentSubcode of the English version for translated messages. Example: English version. DocumentSubcode =”1230”, then French translation -> @Parent=”1230”

4  Parent: News Documents are originally created in English. If Press Operation staff considers interesting to translate any report, the translations are created from the English one. @Parent links to the DocumentSubcode of the English version for translated messages. Example: English version -> DocumentSubcode =”1230”, then French translation -> @Parent=”1230”

5  Codified in UTF-8.

6  Parent: Shuttle Service documents are originally created in English. If Press Operation staff considers interesting to translate any report, the translations are created from the English one. @Parent links to the DocumentSubcode of the English version for translated messages. Example: English version -> DocumentSubcode =”1230”, then French translation -> @Parent=”1230”

7  Codified in UTF-8.

3 PDF Feed

3.1 Overall perspective

ODF-PDF is another feed to send messages; this feed includes messages that have a PDF file inside of them.

3.1.1 PDF list of messages

The following table lists the ODF-PDF feed messages.

Message Type

Message Name

DT_PDF

PDF messages, these messages includes a PDF file inside of them based on the ORIS (or PRIS) type

3.1.2 Messages Definition

There is only one type of PDF message:

3.1.3 PDF Message Triggers

These triggers will be defined in ORIS (or PRIS).

3.2 PDF Feed Messages

3.2.1 PDF Message

3.2.1.1 Description

The PDF message is a PDF file encapsulated in a XML message for one particular event unit. This PDF message is a generic message for all sports.

3.2.1.2 Header Values

The following table describes the ODF header attributes.

Attribute

Value

Comment

CompetitionCode

CC @Competition

Unique ID for competition

DocumentCode

Full RSC

Depending on the PDF the RSC could be at any level.

DocumentSubcode

S(10)

This is an optional attribute

Refer to the ODF header definition

It can be useful for example to separate pdf statistics by NOC or Daily Schedules pdf by date (with format YYYY-MM-DD) or Official or Sport Communications pdf by Item Number

DocumentType

DT_PDF

PDF Message

DocumentSubtype

ORIS Type (or PRIS Type)

Refer to the ODF header definition

It can be useful for example to say the type of the PDF, i.e. C51A, C73R,…

 

There are two special subtypes used GM (Good Morning) and GN (Good Night) which are used as the first and last PDF messages each day. These contain a PDF with the sport code and venue code and the words “Good Morning” and “Good Night” as appropriate. Document follows look of the Games. In this case the DocumentCode should be the venue RSC.

Version

1...V

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

ResultStatus

S(15)

Refer to the ODF header definition

The status should reflect the status of the enclosed PDF (as in ORIS). Possible values are:

INTERMEDIATE

PARTIAL

UNOFFICIAL

OFFICIAL

The ResultStatus is only included where it adds value and should be used in the following ORIS reports:

C7x - Status of the corresponding xml message (Results, Phase, Cumulative, Pools, Brackets, Ranking)

C8x - INTERMEDIATE if during a unit/tournament, otherwise OFFICIAL when complete

C9x - PARTIAL if not all medals are included for a unit, OFFICIAL if all medals are included

Language

S(3)

Refer to the ODF header definition

FeedFlag

“P”-Production

“T”-Test

Refer to the ODF header definition

Date

Date

Refer to the ODF header definition

Time

Time

Refer to the ODF header definition

LogicalDate

Date

Refer to the ODF header definition

3.2.1.3 Trigger and Frequency

The general rule is that this message will be sent depending on the trigger and frequency defined in ORIS (or PRIS).

Trigger also after any major change.

3.2.1.4 Message Structure

The following elements describe the message structure from the OdfBody element.

The following elements describe the message structure from the OdfBody element.

Level 1

Level 2

Level 3

Level 4

Level 5

 

 

 

 

Competition (0,1)

 

ExtendedInfos (0,1)

 

ExtendedInfo (1,N)

 

Type

Code

Pos

Value

Extension (0,N)

 

Code

Pos

Value

 

PDFData

 

-

 

3.2.1.5 Message Values

Be aware of all mandatory attributes that must appear in any ODF PDF message.

Element: ExtendedInfos /ExtendedInfo

See sport specific definition for additional values

Attribute

M/O

Value

Description

Type

M

Text (see below)

Type (categorization) of ExtendedInfo. See list below.

Code

M

See detail below.

Code as appropriate

Pos

 

 

 

Value

M

See detail below

Applicable Value

 

Element: ExtendedInfos /ExtendedInfo /Extension

Attribute

M/O

Value

Description

Code

 

 

See sport specific definition

Pos

 

 

 

Value

 

 

 

 

Element: Competition /PDFData

Attribute

M/O

Value

Description

-

M

Free Text

The PDFData element may have a body consisting of one Base64-encoded report (a PDF file)

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

 

More detail of the ExtendedInfos

 

More detail of the ExtendedInfos

Type

Code

Description

Expected

EI

REPORT_TITLE

For @Type:

Send proposed type

Always when available

For @Code:

Send proposed code

For @Value:

Send the title of the PDF or “GOOD MORNING” or “GOOD NIGHT” as appropriate.

VERSION

For @Type:

Send proposed type

Always when available

For @Code:

Send proposed code

For @Value:

Send the version/revision data as used in the footer of the PDF message.

OFFIC_COMM

SUBTYPE

For @Type:

Send proposed type

If applicable and only when the PDF is official communication.

For @Code:

Send proposed code

For @Value:

DocumentSubtype from the applicable official communication

SUBTITLE

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Subtitle from the applicable official communication

ITEMNUM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Numeric to uniquely identify the Official Communication Number. (ItemNum)

 

3.2.1.6 Sample (Good Morning)

……
<?xml version="1.0" encoding="utf-8"?>
<OdfBody CompetitionCode="OG2016" DocumentType="DT_PDF" Date="2016-06-27" Time="161907638" LogicalDate="2016-06-27" Source="SCV" FeedFlag="T" DocumentCode="HOC-----------------------HOC-----" DocumentSubtype="GM" Version="1" >
<Competition>
<ExtendedInfos>
<ExtendedInfo Type="EI" Code="REPORT_TITLE" Code="GOOD MORNING" />
</ExtendedInfos>
<PDFData>

[encoded PDF]

</PDFData>
</Competition>
</OdfBody>
……

 

3.2.1.7 Sample (Normal Message)

……
<?xml version="1.0" encoding="utf-8"?>
<OdfBody CompetitionCode="OG2016" DocumentCode="BKBMTEAM5-------------GPA-0001----" DocumentType="DT_PDF" DocumentSubtype="C73" ResultStatus="OFFICIAL" Date="2012-06-27" LogicalDate="2012-06-27" Time="161907638" Source="SCV" FeedFlag="T" Version="1" >
<Competition>
<ExtendedInfos>
<ExtendedInfo Type="EI" Code="REPORT_TITLE" Value="RESULTS" />
<ExtendedInfo Type="EI" Code="VERSION" Value="1.0" />
</ExtendedInfos>
<PDFData>

[encoded PDF]

</PDFData>
</Competition>
</OdfBody>
……

3.2.1.8 Message sort

The message does not have any defined sort order.

 

4 Document Control

Version history

Version

 Date

 Comments

v0.1

04 May 2015

First Version

v0.2

9 July 2015

New Federation Ranking included and other updates

v0.3

16 July 2015

Editorial corrections

v0.4

9 Sept 2015

Change Requests applied

v0.5

7 October 2015

Change Request Applied

v0.6

6 November 2015

Change Request Applied

v0.7

24 March 2016

Change requests and minor editing

v0.8

19 May 2016

Minor corrections

v0.9

24 June 2016

CRs, Minor corrections/typographical errors

v1.0

22 Sep 2016

Minor corrections

v1.1

10 Nov 2016

Typographical correction and minor improvement

v1.2

22 Dec 2016

Typographical corrections and CRs

v1.3

23 Feb 2017

Typographical corrections and change requests

v1.4

20 April 2017

Typographical corrections and change requests

v1.5

25 May 2017

Change Requests

V1.6

2 Oct 2017

Change Requests

V1.7

4 Dec 2017

Change Request

 

File Reference: ODF/INT401 R-WOG-2018-GEN-v1.7 APP

Change Log

Version

 Status

 Changes on version

v0.1

SFR

First Version

v0.2

SFR

Updated with changes from Rio GL document (not marked)

Updated samples to use new code system (CR7454),

Added ExtendedInfos extensions in DT_SCHEDULE for use when generated from the competition schedule application.

v0.3

SFR

Clarified the term "Full RSC" to use it consistently.

Some minor typographical errors

Added some winter sport samples

Corrected field sizes in the codes message

v0.4

SFR

Applied Change Results

CR7429 - Add date in DT_MEDALLISTS message

CR7452 -  Rename stats elements in DT_RESULT (and therefore DT_RESULT_ANALYSIS and DT_ESL)

CR7455 -  ExtendedResults in DT_CUMULATIVE_RESULT

CR7456 - Add support for teams of Teams in DT_PARTIC_TEAMS

CR7457 - Add ResultItems to DT_RESULT message (and therefore DT_RESULT_ANALYSIS and DT_ESL)

v0.5

SFR

LIVE Status added to DT_BRACKETS message

Correct error in Disciple Medallists to be clear

CR8126 - Add statistics in DT_CURRENT

v0.6

SFR

CR8254 - Add discipline in DT_PIC

Includes changes made in Rio documentation

v0.7

SFA

For consistency, TeamName in the Competitor/Description is changed to always mandatory (though Description is not). Previously different depending on the message.

Updated text in Order attribute related to sending 1 if only one exist.

CR8928 - DT_RESULT/ANALYSIS/ESL add 'Attendance' as attribute at ExtendedInfos/VenueDescription

         DT_BRACKETS add Bib at Competitor and Competitor\Composition/Athlete

         DT_RANKING add 'Diff' as an attribute at Result and 'Bib' as an attribute at Competitor and at Competitor/Composition/Athlete

         DT_PARTIC and DT_PARTIC_TEAM add 'Substitute' and 'Status' at Discipline/RegisteredEvent

CR8930 - Consistent use of DocumentSubtype and DocumentSubcode (add DocumentSubcode in Phase, Cumulative and pool messages.)

CR8933 - Applied default sort order for DT_CUMULATIVE_RESULTS

CR8934 - Add START_LIST and IRMs to brackets and remove LIVE ResultStatus

CR8936 - Add H1 Headings to DT_CODES message.

CR8938 - Normalising the ExtendedInfos for DT_PDF

CR9036 - Change <Competition> element to cardinality (0,1)  to allow for message invalidation.

CR9360 - Play by Play message improvements (in play by play and current messages)

CR9361 - Communication message improvements

CR9941 - Add Result attribute at CompetitorPlace in DT_BRACKETS

CR9942 - Add home/away indicator in Pool Standings

v0.8

SFA

Clarify that only the ENG description of the unit is expected in the schedule messages.

v0.9

SFA

Correct typographical errors in samples

In DT_SCHEDULE updated to support SC @StartText

CR10294 - DT_ALERT: Add two new DocumentSubtypes of NEWS and RESULTS (2.2.19.2)

CR10246 - Add TVTeamName to Team participants message (DT_PARTIC_TEAMS).

CR11930 - Remove DocumentSubcode from DT_SCHEDULE & DT_SCHEDULE_UPDATE

 

v1.0

APP

DT_RECORD: Clarify the order of the data in the message. Also clarify that <RecordData> can be send for not established records where a standard applies.

v1.1

APP

- DT_FED_RANKING: Rankings /Ranking /ExtRanking /ExtRank should have cardinality of  (0,N)

- DT_BRACKETS: Provide more information on when the time should be included at Bracket /BracketItems /BracketItem.

v1.2

APP

- Correct typo. Add TVTeamName in DT_PARTIC_TEAMS which was accidentally removed.

- Correct type. Add extension in DT_SCHEDULE for status and version which was accidentally removed.

- DT_CURRENT: Update to include information on how to use the clock data.

- DT_IMAGE: CR14627 - Add Result Element to include competitors in the message.

v1.3

APP

- DT_PARTIC: Clarify that all applicable participants are included regardless of status [CR14576]

- DT_RESULT: Add Rank, RankEqual and SortOrder to StatisticItem (athlete and competitor) [CR14580]

- DT_RESULT: Add DocumentSubcode in the Header [CR14628]

- DT_RESULT: Remove StartListMod in the ODF Header [CR14579]

- DT_RESULT: In ExtendedInfos change StartDate and EndDate to be actual only, do not include until unit starts/ends [CR14578]

- DT_PLAY_BY_PLAY/DT_CURRENT: Modify the TimeStamp to be in DateTime format. [CR14577]

- DT_GPS_DATA: Message Removed [CR14586]

- DT_POOL_STANDING: Update the description Result/Ratio to "Ratio value, see sports documents for more information" thus making it more generic and flexible.

- DT_PIC: Added 'HEADSHOT' as possible DocumentSubtype. [CR14630]

- Correct samples of team code where incorrect(typo) [ATHM4X400M--ESP01].

- Other minor typographical errors without changing the meaning

v1.4

APP

- DT_RESULT: Add duration in ExtendedInfos [CR14578]

- DT_SCHEDULE: Add attributes PreviousWLT and PreviousUnit at element Unit/StartList/Start

v1.5

APP

- DT_SCHEDULE: Description of use for the Order@Unit attribute updated to be more clear when special ordering is required

- DT_CONFIG: Triggering updated to clarify that new version of DT_RESULT as soon as DT_CONFIG changes.

- DT_IMAGE: Type@Result/Competitor changed to Optional

- DT_CURRENT: DocumentSubtype added to support distinction when DT_CURRENT is used  for more than one purpose.

- DT_RESULT: Triggering: ResultStatus description updated to provide more detail.

- DT_BIO_PAR/DT_BIO_PAR_IMP: Add flag as an extension to indicate that the athlete participated in the Youth Olympic Games.

V1.6

APP

- CR08929 Add Add new message for Medal Presenters (DT_PRESENTER)

- CR15039 Add DT_PARTIC_NAME message (for use after PyeongChang)

- CR15219 Add passport names to DT_PARTIC message (for use after PyeongChang)

- CR15263 Add support uniform images in DT_IMAGE (for use after PyeongChang)

V1.7

APP

- CR15803: Update DT_SCHEDULE for non-competition items
- DT_SCHEDULE: Minor editorial.