Discussion: RouteGadget & latest IOF XML formats

After the last race I organized I was unable to get RouteGadget to work. I think that I thought at the time that the problem was that RG was not supporting the latest IOF XML data formats. I'm about to try again this upcoming weekend and I wonder if there is any known issue, or if anyone has suggestions

Here is a more detailed report from my previous event:

I am using Condes to generate the course data XML file.
The results are coming from MeOS, which is new timing software.
MeOS is providing results in the latest IOF XML data format.

These files seem to confuse RouteGadget - in the end it seems that I can create the event, but all of the course names are blank and the animations only seem to work for one control then stop. During the creation of the event in RouteGadget, there is one screen which should show a list of course names (with drop down list for each course, so we can match) but this screen is messed up quite a lot, and is displaying a lot of XML text, which looks like it is perhaps from the results file.

Pretty sure that it is an XML compatibility issue.

Below is a few lines from an XML 3 files. I changed the line after ClassResult from Name (XML 3 format) to ClassShortName (XML 2 format), and it seemed to work fine now. Need to do this for each course. <> thingees removed so it would display below...

Original:
Event
ClassResult
Class
Id 1 Id
Name White Name
Class

New:
Event
ClassResult
Class
Id 1 Id
ClassShortName White ClassShortName
Class

Exporting XML 2 from OE works just fine still.

Which version of condes? Have you upgraded to the new one that just came out? We've had no problems from condes 7 or 8 but just purchased the new one.

As Invis said, use xml 2

Condes 9 will export in version 2 or 3, it looks like. Is there a description of the differences? I haven't looked at MeOS except just now at the webpage. I see it's open source.

It should be possible to use XSLT to translate from IOF XML v3 to v2, given a specification and time.