Support for Active and Inactive statuses for IOF XML export

[maleksware]

It would be great to somehow detect competitors in forest based on IOF XML export, for instance, by using the intended statuses Active (started, in forest) and Inactive (not started, for instance, when a start time has been allocated but there is no Check punch).

At the moment, the runners in the forest don't seem to be exported to IOF XML via MeOS IS unless they have a punch (the allocated start time is not enough), and changing their status to something other than - (unknown) makes them appear in the export. This makes it hard to detect the current runner status for third party services (like meshO Leaderboard which I am the developer of) before the download or the radio punch. Would be great to have that!

[fediskhakov]

To describe the problem in slightly more detail: we are using MeOS information server API to get the IOF XML file for presenting on the result screens (meshO Leaderboard). In the events when starts are allocated, it would be great to show start lists, but MeOS does not include into XML output competitors with unknown status -.

Elaboration: allocated start time, punched start time (transmitted back to event computer via SRR and our radio controls system meshO) or check punch do not change the status of the competitor, who are then too not included in XML export. However, MeOS does report Last seen time for the competitors who has at least one of the 'technical' punches.

Proposed solution:

• include competitors with any punch but unknown status - into the IOF XML export with status Active (these would be the same competitors for whom MeOS reports last seen time)
• include competitors registered in the event but not having any punches and having unknown status - into the IOF XML export with status Inactive.

Reference: list of IOF statuses is available at IOF xsd XML standard definition, lines 2903-3016