2 Messages

2.1 Applicable Messages

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

The column “Message type“ indicates the DocumentType that identifies a message
The column “Message name“ is the message name identified by the message type
The column “Message extended“ indicates whether a particular message has extended definition in regards to those that are general for all sports. If one particular message is not extended, then it should follow the general definition rules.

Message Type	Message Name	Message extended
DT_SCHEDULE / DT_SCHEDULE_UPDATE	Competition schedule / Competition schedule update
DT_PARTIC / DT_PARTIC_UPDATE	List of participants by discipline / List of participants by discipline update	X
DT_PARTIC_TEAMS / DT_PARTIC_TEAMS_UPDATE	List of teams / List of teams update	X
DT_MEDALS	Medal standings
DT_MEDALLISTS_DAY	Medallists of the day
DT_GLOBAL_GM	Global good morning
DT_GLOBAL_GN	Global good night
DT_RESULT	Event Unit Start List and Results	X
DT_CUMULATIVE_RESULT	Cumulative Results	X
DT_RANKING	Event Final Ranking
DT_COMMUNICATION	Official Communication
DT_CONFIG	Configuration	X
DT_MEDALLISTS	Event's Medallists
DT_MEDALLISTS_DISCIPLINE	Medallists by discipline
DT_LOCAL_OFF	Discipline/venue stop transmission
DT_LOCAL_ON	Discipline/venue start transmission
DT_KA	Keep Alive

2.2 Messages

2.2.1 List of participants by discipline / List of participants by discipline update

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

It is important to note that all the sport messages that make references to athletes (start list, event unit results, etc.) will always match the athlete ID with the athlete ID in this message.

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

List of participants by discipline update (DT_PARTIC_UPDATE) is an update message. It is not a complete list of participants' information by discipline message, only the participant data being modified, i.e. if some data of one participant changes, the element Participant for it with all its children and attributes must 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.1.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DD0000000	DD is defined according to CC @Discipline
DocumentType	DT_PARTIC / DT_PARTIC_UPDATE	List of participants by discipline message
Version	1..V	Version number associated to the message's content. Ascendant number
FeedFlag	"P"-Production "T"-Test	Test message or production message.
Date	Date	Date when the message is generated, expressed in the local time zone where the message was produced.
Time	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.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.1.3 Trigger and Frequency

The DT_PARTIC 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_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.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
Competition (1,1)
	Code
	Participant (1,N)
		Code
		Parent
		Status
		GivenName
		FamilyName
		PrintName
		PrintInitialName
		TVName
		TVInitialName
		Gender
		Organisation
		BirthDate
		Height
		Weight
		PlaceofBirth
		CountryofBirth
		PlaceofResidence
		CountryofResidence
		Nationality
		MainFunctionId
		Current
		OlympicSolidarity
		ModificationIndicator
		Discipline (1,1)
			Code
			RegisteredEvent (0,N)
				Gender
				Event
				EventEntry (0,N)
					Code
					Type
					Pos
					Value

2.2.1.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

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)
PrintName	M	S(35)	Print name (family name in upper case + given name in mixed case)
PrintInitialName	M	S(18)	Print Initial name (for the given name it is sent just the initial, without dot)
TVName	M	S(35)	TV name
TVInitialName	M	S(18)	TV initial name
Gender	M	CC @PersonGender	Participant's gender
Organisation	M	CC @Organisation	Organisation ID
BirthDate	O	YYYY-MM-DD	Date of birth. It will be included if available
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	It is the discipline code used to fill the OdfBody @DocumentCode attribute.

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
Gender	M	CC @DisciplineGender	Discipline Gender Code
Event	M	CC @Event	Event ID

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

Send if there are specific athlete's event entries.

	Type	Code	Pos	Description
ENTRY		SUBSTITUTE	N/A	Element Expected: As soon as this information is available (this information can be sent in both messages). Send only for the Teams event - not Duets.
	Attribute	M/O	Value	Description
	Value	O	S(1)	Send "Y" if the competitor is a reserve, else do not send

2.2.1.6 Message Sort

The message is sorted by Participant @Code

2.2.2 List of teams / List of teams update

2.2.2.1 Description

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

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

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.2.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DD0000000	DD is defined according to CC @Discipline
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.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.2.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.2.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5
Competition (1,1)
	Code
	Team (1,N)
		Code
		Organisation
		Number
		Name
		Gender
		Current
		ModificationIndicator
		Composition (0,1)
			Athlete (1,N)
				Code
				Order
		TeamOfficials (0,1)
			Official (1,N)
				Code
				Function
		Discipline (0,1)
			Code
			RegisteredEvent (0,1)
				Event
				Gender

2.2.2.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition.

Code is deprecated and value is duplicated in the header.

Element: Team (1,N)

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Team's ID (example ATM001ESP01, 393553) When the Team is an historical one, then this ID starts with "T".
Organisation	M	CC @Organisation	Team organisation's ID
Number	O	Numeric #0	Team's number.
Name	O	S(73)	Team's name.
Gender	M	CC @DisciplineGender	Discipline Gender Code of the Team
Current	M	boolean	It defines if a team is participating in the games (true) or it is a Historical team (false)
ModificationIndicator	M	N, U, D	Attribute is mandatory in the DT_PARTIC_TEAMS_UPDATE message only N-New team (in the case that this information comes as a late entry) U-Update team D-Delete team If ModificationIndicator='N', then include new team to the previous bulk-loaded list of teams If ModificationIndicator='U', then update the team to the previous bulk-loaded list of teams If ModificationIndicator='D', then delete the team to the previous bulk-loaded list of teams

Element: Team /Composition /Athlete (1,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.
Order	O	Numeric	Team member order

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

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

CC @ResultsFunction

Official's function for the team

Send the function code for:

-Coach

-Choreographer

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	It must be the discipline code used to fill the OdfBody @DocumentCode attribute

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	Event ID
Gender	M	CC @DisciplineGender	Discipline Gender Code

2.2.2.6 Message Sort

The message is sorted by Team @Code.

2.2.3 Event Unit Start List and Results

2.2.3.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.2.3.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DDGEEEPUU	DD according to CC @Discipline G according to CC @DisciplineGender EEE according to CC @Event P according to CC @Phase UU according to CC @Unit
DocumentType	DT_RESULT	Event Unit Start List and Results message
DocumentSubtype	Not used in SY	Not used in SY
Version	1..V	Version number associated to the message's content. Ascendant number
ResultStatus	SC @ResultStatus	It indicates whether the result is official , unofficial, etc. START_LIST UNOFFICIAL OFFICIAL LIVE (used during the competition when nothing else applies).
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.
StartListMod	S(1)	Send Y if the start list has been changed with this message and the ResultStatus is not START_LIST. Do not send the attribute if it is not Y. Only send once for each start list change. In this case the full current message is sent with whatever is the current ResultStatus. The Start List is considered to be changed if any of the following changes: * Competitors or athletes are added, changed or removed including in <ExtendedInfos /Competitor> * Any change in <Officials> * Any change in StartOrder or StartSortOrder * Any changes in <Coaches> * Any changes in <EventUnitEntry> Changing descriptions is not considered a start list change.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.3.3 Trigger and Frequency

-As soon as the start list is available and any updates [inc. IRMs] (START_LIST)

-(First LIVE) First competitor preparation, ready for competition; including the first current synchronised swimmer (refer to ODF Principles).

-When the first competitor starts and during the unit with all updates (LIVE)

-After the unit has finished (UNOFFICIAL)

-After the Result is approved (OFFICIAL)

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 (1,1)
	Code
	ExtendedInfos (0,1)
		UnitDateTime (0,1)
			StartDate
		ExtendedInfo (0,N)
			Type
			Code
			Pos
			Value
			Extension (0,N)
				Code
				Pos
				Value
		SportDescription (0,1)
			DisciplineName
			EventName
			Gender
			SubEventName
		VenueDescription (0,1)
			Venue
			VenueName
			Location
			LocationName
	Officials (0,1)
		Official (1,N)
			Code
			Function
			Order
			Description (1,1)
				GivenName
				FamilyName
				Gender
				Organisation
			ExtOfficial (0,N)
				Type
				Code
				Pos
				Value
	Result (1,N)
		Rank
		RankEqual
		Result
		IRM
		SortOrder
		StartOrder
		StartSortOrder
		ResultType
		Diff
		Competitor (1,1)
			Code
			Type
			Organisation
			Description (0,1)
				TeamName
			ExtendedResults (0,1)
				ExtendedResult (1,N)
					Type
					Code
					Pos
					Value
					Extension (0,N)
						Code
						Pos
						Value
			Composition (0,1)
				Athlete (1,N)
					Code
					Order
					Description (1,1)
						GivenName
						FamilyName
						Gender
						Organisation
						BirthDate
					EventUnitEntry (0,N)
						Type
						Code
						Pos
						Value

2.2.3.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

Element: ExtendedInfos /UnitDateTime (0,1)

Scheduled start date and time. (where available update with actual start time)

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

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

Element: ExtendedInfos /ExtendedInfo (0,N)

	Type	Code	Pos	Description
UI		PANEL	Numeric 0	Pos Description: Panel order Element Expected: When available
	Attribute	M/O	Value	Description
	Value	O	SC @PanelType	Judges' Panels, which panel apply in this unit
	Sub Element: ExtendedInfos /ExtendedInfo /Extension Expected: When available
	Attribute	Value	Description
	Code	PERCENT
	Pos	N/A	N/A
	Value	Numeric #0	Weighted for this panel. (e.g.: 30 as 30% for the score in Execution panel)
DISPLAY		CURRENT	N/A	Element Expected: Send the current/next competitor with every LIVE update
	Attribute	M/O	Value	Description
	Value	O	S(20) with no leading zeroes	Send the competitor ID of the current/next competitor
DISPLAY		LAST_COMP	N/A	Element Expected: Send the last competitor to receive a score with every LIVE update
	Attribute	M/O	Value	Description
	Value	O	S(20) with no leading zeroes	Send the competitor ID of the last competitor to finish

Sample (In a Free Routine unit)

</ExtendedInfo>

</ExtendedInfo>

</ExtendedInfo>

...

...

</ExtendedInfos>

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	M	S(40)	Text short description or the Event Unit, not code

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

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Official's ID
Function	M	CC @ResultsFunction	Official's function for the event unit. Send the function code for: -Referee -Assistant Referee And for judges, there are three different panels (depending on the event unit routine), i.e.: -for Technical routines (Execution, Impression, Elements) -for Free routines (Execution, Artistic Impression, Difficulty) with five judges in each panel of judges i.e.: for each of the corresponding panel of judges: -Judge 1 -Judge 2 -Judge 3 -Judge 4 -Judge 5
Order	M	Numeric	Order of the Officials (described above). Send by order for each official

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

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

	Type	Code	Pos	Description
EO		TECH_MEMBER	N/A	Element Expected: As soon as it is known
	Attribute	M/O	Value	Description
	Value	O	S(1)	Send "Y" if the official is member of the FINA Technical Synchronised Swimming Committee, else does not send.
EO		PANEL	Numeric 0	Pos Description: Order of the Judge within the panel Element Expected: As soon as it is known. This should be sent according with the Official/@Function (except for Referee and Assistant Referee).
	Attribute	M/O	Value	Description
	Value	O	SC @PanelType	Panel Type. Indicates in which panel is the judge. Only send for the Judges

Sample (In a Free Routine unit)

</Official>

...

</Official>

</Official>

...

</Official>

</Official>

...

</Official>

</Official>

...

</Officials>

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	String	Rank of the competitor in the corresponding event unit. This attribute is optional because the competitor could get an invalid result mark.
RankEqual	O	S(1)	Send "Y" in the case of equalled rank else do not send
Result	O	Numeric ##0.0000	Result (Points) for the particular event unit.
IRM	O	SC @IRM	Invalid result mark for the particular event unit Send just in the case @ResultType is IRM
SortOrder	M	Numeric	This attribute is a sequential number with the order of the competitors for the particular event unit, if they were to be presented. It is mostly based on the rank, but it should be used to sort out rank ties as well as results without rank. Prior to the start it is the same as StartSortOrder.
StartOrder	O	Numeric	Start order of the competitor in the start list.
StartSortOrder	M	Numeric	Start list order according to the sport rules (used to sort all start list competitors in an event unit).
ResultType	O	SC @ResultType	Result type, either POINTS or IRM for the corresponding event unit.
Diff	O	Numeric ##0.0000 Or blank (for leader)	Points behind the leader (send just in the case @ResultType is POINTS). Send blank if the competitor is the leader (for Result @Rank=1).

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	Competitor's ID For Competitor @Type=T, it will be: Team's ID
Type	M	T	T for team
Organisation	M	CC @Organisation	Competitor's organisation

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

Competitors extended information.

Attribute	M/O	Value	Description
TeamName	O	S(73)	Name of the team.

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

	Type	Code	Pos	Description
ER		SC @PanelType	Numeric 0	Pos Description: Do not send except in the case of @Code=TE (Elements panel in Technical Routines). Send 0 for overall panel score, and 1..5 for each element. Element Expected: Always
	Attribute	M/O	Value	Description
	Value	O	Numeric ##0.0000	Weighted score. Total Points for that panel. In the case of @Code=TE (Elements): total points for overall @Pos=0, and for each element (1..5), points for the element.
	Sub Element: Result /Competitor /ExtendedResults /ExtendedResult /Extension Expected: Only for Elements panel -each element (do not send for overall, @Code=TE and @Pos=0)
	Attribute	Value	Description
	Code	DIFFICULTY
	Pos	N/A	N/A
	Value	Numeric 0.0	Send the degree of difficulty for the technical element @Pos (1..5)
	Sub Element: Result /Competitor /ExtendedResults /ExtendedResult /Extension Expected: If applicable (do not send in Elements panel for overall, @Code=TE and @Pos=0)
	Attribute	Value	Description
	Code	DISCARDED
	Pos	Numeric 0	Judge's sequential number in the panel
	Value	S(1)	Send "Y" if the judge score does not contribute to total score. Otherwise, do not send.
	Sub Element: Result /Competitor /ExtendedResults /ExtendedResult /Extension Expected: When available (do not send in Elements panel for overall, @Code=TE and @Pos=0)
	Attribute	Value	Description
	Code	SCORE_J
	Pos	Numeric 0	Judge's sequential number in the panel.
	Value	Numeric #0.0	Score awarded by that judge. Send 10 -without decimal-, for perfect score
ER		PTY	N/A	Element Expected: If applicable
	Attribute	M/O	Value	Description
	Value	O	-Numeric -#.0	Send the penalty points (only if not zero) for the competitor.
ER		REQ_PTY	N/A	Element Expected: If applicable in Technical Routines only
	Attribute	M/O	Value	Description
	Value	O	-Numeric -#.0	Send the penalty points (only if not zero) for required elements. Send only for technical routines.
ER		PTS_NEEDED	Numeric #0	Pos Description: Send 1, 2, 3 or 12. Send 1 for pts for gold Send 2 for pts for silver Send 3 for pts for bronze Send 12 for pts to qualify for final in Duet. Element Expected: In Preliminary - Technical Routine (duets) and, in Final - Free Routines (duets and teams) Only when this competitor is the current competitor (with LIVE).
	Attribute	M/O	Value	Description
	Value	O	Numeric ##0.0000 Or "-"	The points the current competitor has to achieve a medal, or, qualify for the final. Use "-", if not team currently in the 1, 2, 3, 12 positions as applicable. Positions 1, 2, 3 only apply for Free Routine Finals (duets and teams), and, the 12 only applies in Duets Technical Routine Preliminary.

Sample (In a Free Routine unit)

....

....

</ExtendedResult>

....

</ExtendedResult>

....

</ExtendedResult>

</ExtendedResults>

</Athlete>

</Athlete>

</Composition>

</Competitor>

</Result>

Sample (In a Technical Routine unit)

....

</ExtendedResult>

....

</ExtendedResult>

</ExtendedResult>

...

</ExtendedResult>

....

....

</ExtendedResult>

</ExtendedResults>

</Athlete>

</Composition>

</Competitor>

</Result>

Sample (In a Duet Free Routine - Preliminary (current))

</ExtendedResults>

Sample (In a Free Routine - Final (current))

First:

</ExtendedResults>

</ExtendedResults>

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

Attribute

M/O

Value

Description

Code

S(20) with no leading zeroes

Athlete's ID, corresponding to a duets/teams member.

Order

Numeric

Order attribute used to sort team members in a team.

Send the order of the athletes within the duets/teams.

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

Element: Result /Competitor /Composition /Athlete /EventUnitEntry (0,N)

Individual athletes entry information.

	Type	Code	Pos	Description
EUE		SUBSTITUTE	N/A	Element Expected: As soon as available. Send only for the Teams event, not Duets.
	Attribute	M/O	Value	Description
	Value	O	S(1)	Send "Y" if the competitor is the reserve, else do not send

2.2.3.6 Message Sort

Sort by Result @SortOrder

2.2.4 Cumulative Results

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

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	DDGEEEP00	The DocumentCode should be [DD][G][EEE][P]00 In the case of Duets the message will be sent with phase 9 (preliminary) and 1 (final) while in the Teams event only phase 1 (final) is used.
DocumentType	DT_CUMULATIVE_RESULT	Cumulative Results message
DocumentSubtype	DDGEEEPUU	The DocumentSubtype should be [DD][G][EEE][P][UU] to indicate the current only most recently complete unit (if not current). In the case of Duets the message will be sent with phase 9 (preliminary) and 1 (final) while in the Teams event only phase 1 (final) is used.
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.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.4.3 Trigger and Frequency

-After each competitor completes the routine -during a phase- (LIVE)

-After every phase routine is over (INTERMEDIATE)

-Update after last routine -up to the end of the phase- (UNCONFIRMED / UNOFFICIAL / OFFICIAL)

2.2.4.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 (1,1)
	Code
	ExtendedInfos (0,1)
		ExtendedInfo (0,N)
			Type
			Code
			Pos
			Value
		SportDescription (0,1)
			DisciplineName
			EventName
			Gender
		VenueDescription (0,1)
			Venue
			VenueName
			Location
			LocationName
	Result (1,N)
		Rank
		RankEqual
		ResultType
		Result
		IRM
		QualificationMark
		Diff
		SortOrder
		ResultItems (0,1)
			ResultItem (1,N)
				Phase
				Unit
				Result (1,1)
					Rank
					RankEqual
					ResultType
					Result
					IRM
					SortOrder
		Competitor (1,1)
			Code
			Type
			Organisation
			Description (0,1)
				TeamName
			Composition (1,1)
				Athlete (1,N)
					Code
					Order
					Description (1,1)
						GivenName
						FamilyName
						Gender
						Organisation
						BirthDate
					ExtendedResults (0,1)
						ExtendedResult (1,N)
							Type
							Code
							Pos
							Value

2.2.4.5 Message Values

Element: Competition (1,1)

Attribute

M/O

Value

Description

Code

CC @Competition

Unique ID for competition

Code is deprecated and value is duplicated in the header.

Element: ExtendedInfos /ExtendedInfo (0,N)

	Type	Code	Pos	Description
UI		LAST_QUAL	Numeric #0	Pos Description: Show the rank of the competitor. Element Expected: When known during Duets Technical routine
	Attribute	M/O	Value	Description
	Value	O	S(20) with no leading zeroes	Send the last qualifying place ID (during Duets Technical routine in Preliminary only) In the situation where insufficient competitors have participated to show the last qualifying position then show the current last place

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

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	M	CC @Location	Location code
LocationName	M	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	String	Overall Rank of the competitor in the phase. This attribute is optional because the competitor could get an invalid result mark (in this case, it will be blank).
RankEqual	O	S(1)	Send Y in case of the Rank has been equalled else do not send.
ResultType	O	SC @ResultType	Result type, either POINTS or IRM in any routine for the corresponding phase.
Result	O	Numeric ##0.0000	Result (Total points) for the phase Duets Preliminary: is the Free Routine Preliminary Points plus the Technical Routine Points. Duets Final: is the Technical Routine Points (in Preliminary) plus Free Routine Final Points. Teams Final: is the Technical Routine Points plus Free Routine Final Points.
IRM	O	SC @IRM	Invalid result mark in the phase. Send just in the case @ResultType is IRM
QualificationMark	O	SC @QualificationMark	Indicates whether the team is qualified for next round is confirmed. Don't send for the final. (only applies in Preliminary phase)
Diff	O	Numeric ##0.0000 Or blank (for leader)	Points behind the leader (send just in the case @ResultType is POINTS). Send blank if the competitor is the leader (for Result @Rank=1).
SortOrder	M	Numeric	This attribute is a sequential number with the order of the results, if they were to be presented. It is mostly based on the rank, but it should be used to sort out disqualified teams.

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

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

Attribute

M/O

Value

Description

Phase

CC @Phase

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

Possible values are:

(9) Qualification -only for Duets-

(1) Final -for Duets and Teams-

Unit

CC @Unit

Unit code of the latest RSC schedule item to which the cumulative results is updated to.

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	String	Rank of the competitor in the result for the event unit identified by /ResultItems /ResultItem.
RankEqual	O	S(1)	Send "Y" in the case of equalled rank else do not send
ResultType	O	SC @ResultType	Type of the @Result attribute for the event unit identified by /ResultItems /ResultItem, either IRM or POINTS.
Result	O	Numeric ##0.0000	Result (Points) of the competitor for the particular event unit identified by /ResultItems /ResultItem Send just in the case @ResultType is POINTS
IRM	O	SC @IRM	The invalid result mark, in case it is assigned for the event unit identified by /ResultItems /ResultItem Only send in the case @ResultType is IRM
SortOrder	M	Numeric	Used to sort all results in an event unit identified by /ResultItems /ResultItem

Element: Result /Competitor (1,1)

Competitor related to one cumulative result.

Attribute	M/O	Value	Description
Code	M	S(20) with no leading zeroes	Competitor's ID For Competitor @Type=T, it will be: Team's ID
Type	M	T	T for team
Organisation	M	CC @Organisation	Competitor's organisation

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

Competitors extended information.

Attribute	M/O	Value	Description
TeamName	O	S(73)	Name of the team.

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

Attribute

M/O

Value

Description

Code

S(20) with no leading zeroes

Athlete's ID, corresponding to a duets/teams member.

Order

Numeric

Order attribute used to sort team members in a team.

Send the order of the athletes within the duets/teams.

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

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

Team member's extended result.

	Type	Code	Pos	Description
ER		PARTIC	N/A	Element Expected: In Teams only as soon as it is known
	Attribute	M/O	Value	Description
	Value	O	SC @Participation	Send the appropriate code if applicable (for the reserve participation in teams). Do not send if swam in both (Technical and Free).

Sample (General)

</ResultItem>

</ResultItem>

</ResultItems>

</Athlete>

</Athlete>

</Composition>

</Competitor>

</Result>

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

2.2.5 Configuration

2.2.5.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.2.5.2 Header Values

The following table describes the message header attributes.

Attribute	Value	Comment
CompetitionCode	CC @Competition	Unique ID for competition
DocumentCode	DDGEEEPUU	This message is only sent for the Duets Technical Routine (in Preliminary) so the header will contain the RSC of that unit (DDWEEE902).
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.
Serial	Numeric	Sequence number (positive integer) for ODF messages. Serial starts with 1 each day for each Source.

2.2.5.3 Trigger and Frequency

The message is sent prior to any ODF Sports message.

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.

2.2.5.4 Message Structure

The following table defines the structure of the message.

Level 1	Level 2	Level 3	Level 4	Level 5
Competition (1,1)
	Code
	Configs (1,1)
		Config (1,N)
			Gender
			Event
			Phase
			Unit
			ExtendedConfig (1,N)
				Type
				Code
				Pos
				Value

2.2.5.5 Message Values

Element: Competition (1,1)

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

Element: Configs /Config (1,N)

Attribute	M/O	Value	Description
Gender	M	CC @DisciplineGender	Gender code of the RSC.
Event	M	CC @Event	Event code of the RSC
Phase	M	CC @Phase	Phase code of the RSC
Unit	M	CC @Unit	Unit code of the RSC

Element: Configs /Config /ExtendedConfig (1,N)

	Type	Code	Pos	Description
EC		QUAL_RULE	N/A	Element Expected: When was available.
	Attribute	M/O	Value	Description
	Value	O	String	Qualification rule text
EC		QUAL_RANK	Numeric 0	Pos Description: Send 1 to indicate first rank included in the @Code rule. Send 2 to indicate last rank included in the @Code rule. Element Expected: Always if the rule applies to the competition
	Attribute	M/O	Value	Description
	Value	O	Numeric #0	Send the rank according to @Pos

Sample (General)

</Config>

</Configs>

2.2.5.6 Message Sort

There is no general message sorting rule.