PROPOSED IOF EVENT INFORMATION EXCHANGE STANDARD (Proposal version 1.5 July 22, 2000 replaces previous versions 1.0, 1.1, 1.2, 1.3 (April-May, 2000))
This version contains some minor changes from 1.3 requested from Finn Arildsen and changes we made after working with the dtd and xml files in applications.
This version contains some changes from 1.2 requested from Finn Arildsen and Kell Soennichsen.
This version has implemented suggestions for improvement from Peter Löfås, Finn Arildsen, Olav Nedrelid, Pekka Pirilä received May 5, 2000.
This version has implemented suggestions for improvement from Finn Arildsen, Kell Soennichsen received April 5 and 10, 2000.
This proposal for the IOF Standard Information Exchange using Extensible Markup Language(XML) assumes that users of these standards will want some flexibility depending on their situation. In order to achieve this I have created DataTypeDefinitions (DTD) for single Entities as much as possible. A standard set or collection of data such as Results is then created using a complex DTD which simply includes the necessary DTDs for each entity it needs to support. It has been my goal to reduce the amount of local information parsing. For example my Times.dtd splits hours, mins and secs which frees the user from having to parse something like "10.05.34". This adds extra space to the file but I consider the ease of use of greater importance.
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.
Tele is short for telecommunication.
STANDALONE COURSES/COURSE LIST
ControlInfo is another word for ControlDescription with some e info added.
STANDALONE LIST OF CONTROLS
AN EVENT CLASS
Badge refers to awards which many nations offer for reaching certain standards (percent behind winner for example).
A Club is a sub class of an organisation for example. Media, sponsors, can be considered organisations for example.
AN EVENT (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. )