|
Data Standard, version 2.0.3
This is the first standard that will be widely implemented by software
developers including the two EKT system, Emit and Sport Ident.
The standard is a total rewrite as a result of the experiences gained
in the Swedish OLA Project and the development of Condes. Also major
input have been made by Emit and Sport Ident developers.
The changes from version 1.0 includes:
- A total rewrite of nearly all elements.
- Instead of having several Document Type Declaration (DTD) files
each holding a small part of the standard and depending on each other
the DTD is now assembled in a single file.
- A number of messages, i.e. specification of the lists to be send
from one software element to another, have been made. There still are
some messages missing and they will be developed concurrently with
demand for them.
- Some example files of the messages to exchange have been made.
Please read the comments in the DTD file for further information.
/Kell Sønnichsen (kell@soenniksen.dk)
IOF Data Standard DTD
IOFdata.dtd / txt
Example files
EventList
This list is used to exchange event information for a number of
events, e.g. fixtures.
These are actual events from the Danish fixtures of March 2002.
ClubList
This list is used to exchange information of a number of clubs,
e.g. contact addresses and bank accounts. This could be used by a
national club register.
CompetitorList
This list is used to exchange non-event specific information on a
number of Competitors. This could be used by a national competitor
register.
EntryList
This list is used to send entries from a single club to an organizer
of an event.
A normal entry list.
A normal entry list using teams for a relay.
An entry list with all information that possibly can be included. Only
one entry is in the file.
The same as Example 3 but with a team entry for a relay.
StartList
This list is used for the start list of an event. In fact it could be
put on WWW using XSLT (XML Style Language Transformation).
A normal start list.
A normal start list for a relay.
ResultList
This list is used for the result list of an event. In fact it could be
put on WWW using XSLT (XML Style Language Transformation).
A result list comes in three types:
- complete
- This is a complete list including all competitors. It should only
be used after the event.
- snapshot
- This is also a complete list including all competitors but some
may not have started yet, others may still be out running. It is a
snapshot of the current standing.
- delta
- This is a file containing only the changes since the last file was
sent. It is also a snapshot.
The last two types are intended to be used for "real time" results
during the event. The first type is for the final standing after the
event.
A result list using competitor IDs. This should only be used if the
reciever uses the same competitor database and uses the same IDs.
The list is also a "snapshot" result file.
A result list also using competitor IDs. It looks much the same as
Example 1 but this is a "delta" result file. Only the changes since
the last file was sent are included.
A relay result list also using competitor IDs. It is a "snapshot" file
just as Example 1.
CourseData
These data contains courses and controls including starting points and
finish controls. This defines all the control and course
information. It is typically exchanged between the course setting
software and the event software for this to be able to perform punch
checking. The data also contains information about the position of the
controls on the map so it can be used by map printing software.
An ordinary event. In fact this is "real" data from Spring Cup.
A relay event. This is also "real" data from Spring Cup. Beware, it is
a quite big file.
Download
You can download the DTD and example files in one package here:
IOFdata-2.0.3.tar.gz (19 kB) | IOFdata203.zip (20 kB)
|
|