Well, our JSON interface interface is working nicely, and currently looks something like this:
Code:
http://frcdb.net/event/whatever/json (single event, includes match data and standings)
http://frcdb.net/team/####/json
http://frcdb.net/json/teams (all teams)
http://frcdb.net/json/events (all events)
This works fairly well at least (via initial testing with the android app we‘re working on) save for trouble with database speed. It could be tested now save for some hosting issues that I‘m working on resolving (current server is down due to hardware problems...).
Anyway, it‘s a good thing someone‘s thought to make a standard XML format! We‘ve been planning to offer that but lost some priority when it was decidedly too hard to parse, but standardizing it can make this a ton easier.
CSV is still in the works, but converting our data to a relational model tends to be more time consuming than simply dumping it out
Apparently that‘s what we get for storing everything with mass serialization instead of in an SQL database like we should have...