Orienteering Interface Standards Project
Data Standard, version 0.1.3

PROPOSED IOF EVENT INFORMATION EXCHANGE STANDARD

Proposal version 1.3 May 22, 2000 replaces previous versions 1.0, 1.1, 1.2 (April-May, 2000)

This version contains some changes from 1.2 requested from Finn Arildsen and Kell Soennichsen.

iofIdentity.dtd -> ELEMENT Identity
This change was introducedin version 1.2 and is now made more general so as to not lock us down to INT,NAT,LOCAL etc.  I've added Identity to Persons and Clubs.

iofCompetitor.dtd -> ELEMENT Competitor -> ATTLIST
StartNumber Changed to IMPLIED from REQUIRED as not all runners have a startNumber necessarily.

iofAddress.dtd -> ELEMENT Address -> ATTLIST Country
No longer REQUIRED

iofRaceClass.dtd -> ELEMENT RaceClass -> ATTLIST
administrationLineCode Changed to AdministrationCode for more general use.

iofControlInfo.dtd -> ELEMENT Box -> ATTLIST
hasDiagonal Changed to Y/N with N as the default.

iofControlInfo.dtd -> ELEMENT Box -> ATTLIST column
Changed to an enumeration as per the IOF columns A-F in a control description. eg. column (A|B|C|D|E|F|G|H) #REQUIRED

Kell wrote...
"There is still one problem left regarding multiday events: the start number and class of the competitor is situated in the Competitor element. That means that the competitor should use the same start number all days and run in the same class. A possible solution is to move the start number and class information from the Competitor to the Startlist and Resultlist respectively:

<!ELEMENT Competitor (Person)>
<!ATTLIST Competitor 
  Status CDATA #IMPLIED
  CourseID CDATA #IMPLIED
  ModifyDate CDATA #IMPLIED
>

<!ELEMENT Result (Competitor,((CCard,SplitTimes,Times)+ | Day+))>
<!ATTLIST Result
  EntClass CDATA #REQUIRED
  StartNumber CDATA #REQUIRED
  ModifyDate CDATA #IMPLIED
>

<!ELEMENT StartList (Starter)*>

<!ELEMENT Starter (Competitor,((CCard?,Times) | Day+))>
<!ATTLIST StartList 
  EntClass CDATA #REQUIRED
  StartNumber CDATA #REQUIRED	
  ModifyDate CDATA #IMPLIED
>
Possibly the StartNumber attribute is not needed in the Result entity."

I would like to keep the start number and class with the competitor so will return with a solution that solves Kell's concerns above at a later time.

Ted de St. Croix


STANDALONE ENTRIES
iofEntries.dtd/xml
    iofEntry.dtd/xml
          iofCCard.dtd/xml
        iofPerson.dtd/xml
             iofServiceRequest.dtd/xml
                 iofTransaction.dtd/xml
             iofAddress.dtd/xml
             iofTele.dtd/xml

STANDALONE RESULTS
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.

STANDALONE STARTLIST
iofStartList.dtd/xml
    iofCompetitor.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.

STANDALONE COURSES/COURSE LIST
iofCourseList.dtd/xml
    iofCourse.dtd/xml
        iofControlInfo.dtd/xml

ControlInfo is another word for ControlDescription with some e info added.

STANDALONE LIST OF CONTROLS
iofControlList.dtd/xml
    iofControlInfo.dtd/xml

AN EVENT CLASS
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).

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

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

Copyright © International Orienteering Federation
Revised: 2000-05-22