Hi Linus
RDG, basically ATOC and the various schemes evolved, are starting to become transparent and open. Don't think that means that there's not a role for the community to play - you can't just release data and say "Hey, we're open" - you need to release data that people want to use and, ideally, starting with the data that is most valuable, otherwise it looks a bit like marketing material.
When you say that there's quite a lot of data that's still closed, I read that as "not yet open". Taking fares data as an example, I bet there are two-way discussions that need to take place between RDG and the community to work through some of the issues surrounding correct use of data. We're lucky to have a good example - the Darwin Push Port - which shows that complex, real-time data can be processed by the community. But the fares data is more complex, despite not being real-time, so the detail surrounding the risks of being wrong are going to be quite different.
There's also the issue that, if you make the fares data sets 'free at the point of use', you may lose the cost-covering funds you get for distributing the data in the first place, especially to TIS manufacturers. A way around that could (and I'm not saying this is right, but it's a start) be to mandate that you must use the paid-for source of fares data for selling tickets, but if you're not selling tickets, you can use the 'open' version, with probable caveats on data availability of the latter.
As for approaching RDG - there are some people from RDG who read the list and just by discussing it here will likely mean it gets read and filters up. As with Network Rail, I'm not sure how effective starting with a top-down approach might be.
Finally, NRE used to have 'Developer Days', but the last one was about 18 months ago, and I think it's time to have another. We've come a long way and there's more to discuss!
Peter