Good to see that others have already been thinking about this.
Granted, I'm biased in my thoughts on design and implementation, since I already started to try to repurpose my team's 2007 application for this year's game (and have been doing a huge amount of refactoring as a result)... so my thoughts.
- I think I'd try to make the software as hardware/software independent as possible. (Which was the original reason I did it in Java that year. Mono could be another option.)
- Exports should probably be in some universally understood format, like CSV or XML.
- I'd assume that it's not live. Having attempted a live system in the past caused more headaches than it was worth, at least insofar as our experience of it.
Some of the issues I'm coming into are data-storage issues mostly (since I'm thinking of working it in Java, I'm thinking embedded Derby more than likely, though perhaps with an option for file-based saving, and probably doing it with Web Start again to allow for easy update), as well as simply building it in a fashion that'll allow for the program to be easily ported to whatever the 2010 game is... Though I'm more than willing, certainly, to team up with others to work on this.
I should have more time this year.