PROPOSED IOF
EVENT INFORMATION EXCHANGE STANDARD
Proposal version 1.2 May 10, 2000 replaces previous versions
1.0 and 1.1 (April, 2000)
This version has implemented suggestions for improvement from
Peter Löfås, Finn Arildsen, Olav Nedrelid, Pekka Pirilä received May
5, 2000.
To iofEntry we have made it possible to enter a
Person Element in case a Person list is not accompanying the
export. There has been some discussion surrounding the
id of a person and this should alleviate the problem somewhat. An
iofEntries .dtd has been added. Se examples
below for an xml sample. Entries have been removed from iofEvent
due to a conflict with transaction.
Question: What is the purpose for both an ID and a name for a
course.
Added to iofCourse. Estimate of number of
competitors before entries are finished. This is useful for
estimating control load.
Changed in iofControlInfo. Changed the structure completely in
order accomodate 2 codes for a single box. It also supports a
diagonal option. A Finish control has a description of the finish run
in. For electronic punching systems, the finish control is used
for the control on the finish line, when used for timing so therefore
I have left in a ControlInfo element. The PunchPattern has been left
as a string for the moment.
To BaseClass , I have
added:
Added a new dtd: iofIdentity.dtd for use if several
id codes are needed (for example storing owner ids in an eCard).
This has affected some of the xml examples and hopefully I have
updated all of them.
Courses :
STANDALONE ENTRIES
STANDALONE RESULTS
STANDALONE STARTLIST
STANDALONE COURSES/COURSE LIST
STANDALONE LIST OF CONTROLS
iofControlList.dtd/xml
AN EVENT CLASS
ORGANISATION
AN EVENT
Answer: The ID can be used for internal identity of the course in the
database. This becomes important when exchanging data on a
"diskette" network whereas the name is the name given to the course by
the user. See courses below.
allowedMinAge CDATA #IMPLIED
allowedMaxAge CDATA #IMPLIED
These are for use when runners run outside their normal class.
I have added a CourseID to iofCompetitor so that competitors in the
same class can run different courses (eg. looping or relays).
iofEntries.dtd/xml
iofEntry.dtd/xml
iofCCard.dtd/xml
iofPerson.dtd/xml
iofServiceRequest.dtd/xml
iofTransaction.dtd/xml
iofAddress.dtd/xml
iofTele.dtd/xml
iofResults.dtd/xml
iofCompetitor.dtd/xml
iofPerson.dtd/xml
iofServiceRequest.dtd/xml
iofTransaction.dtd/xml
iofAddress.dtd/xml
iofTele.dtd/xml
iofCCard.dtd/xml
iofSplitTimes.dtd/xml
iofTimes.dtd/xml
A ServiceRequest is an object used to detail requests for such things
as tent sites, result hard copies etc. The sort of non standard
items that each event offers to participants. A Transaction is an
object for storing financial records with.
iofStartList.dtd/xml
iofPerson.dtd/xml
iofServiceRequest.dtd/xml
iofTransaction.dtd/xml
iofAddress.dtd/xml
iofTele.dtd/xml
iofCCard.dtd/xml
iofTimes.dtd/xml
Tele is short for
telecommunication.
iofCourseList.dtd/xml
iofCourse.dtd/xml
iofControlInfo.dtd/xml
ControlInfo is another word for
ControlDescription with some e info added.
iofControlInfo.dtd/xml
iofEventClass.dtd/xml
iofBaseClass.dtd/xml
iofBadgeGroup.dtd/xml
iofBadgeLimit.dtd/xml
iofRaceClass.dtd/xml
iofPunchingUnitType.dtd/xml
Badge refers to awards which many
nations offer for reaching certain standards (percent behind winner for
example).
iofOrganisation.dtd/xml
iofOrganisationType.dtd/xml
iofPerson.dtd/xml
iofIdentity.dtd/xml
iofServiceRequest.dtd/xml
iofTransaction.dtd/xml
iofAddress.dtd/xml
iofTele.dtd/xml
iofCountry.dtd/xml
A Club is a sub class of an
organisation for example. Media, sponsors, can be considered organisations
for example.
(No entries, results or startlists as they conflict with
things like iofClub in the same xml file. Startlists, entries and results
should be created as separate documents. I would like to add such things
as sponsors and media collections at a later date.)
iofEvent.dtd/xml
iofEventForm.dtd/xml
iofEventClassification.dtd/xml
iofClub.dtd/xml
iofPerson.dtd/xml
iofServiceRequest.dtd/xml
iofTransaction.dtd/xml
iofAddress.dtd/xml
iofTele.dtd/xml
iofCountry.dtd/xml
iofEventClass.dtd/xml
iofBaseClass.dtd/xml
iofBadgeGroup.dtd/xml
iofBadgeLimit.dtd/xml
iofRaceClass.dtd/xml
iofPunchingUnitType.dtd/xml
iofEventRace.dtd/xml
iofService.dtd/xml
 |
Project Start Page |
|
IOF Data Standard |
|
IOF Message Standard |
|
Project History |
|
Organization of Work |
|
News Archive |
|
Resources on WWW |