Groups often cause confusion as there are a number of different types. For example, the fares data supports fare groups, zonal groups, county groups and clusters (and probably others I've forgotten!) and each has their own set of rules regarding usage. However, the question here relates to the OJP journey planner and timetable groups, which are completely separate from fare groups.
As answered above, NRE's OJP uses SilverRail's journey planning engine and SilverRail provide a concept within their journey planner of timetable groups, which group together stations for journey planning purposes (usually stations with a common name and close geography although in principle they can be any locations). These timetable groups are essentially aliases for multiple stations, allowing a single location to be specified that results in multiple locations being searched - so for example, when specifying Birmingham (all stations) timetable group the SilverRail journey planning engine actually journey plans to/from Birmingham New Street, Snow Hill
and Moor Street to find journey options.
These timetable groups may coincidently have similar names to fare groups (e.g. Croydon (All Stations) timetable group and Croydon Stations fare group) but the members are independent and may or may not include the same locations as a fare group (e.g. the Croydon (All Stations) timetable group includes South Croydon whereas the Croydon stations fare group does not). Equally, there may be a fare group with no similar timetable group or a timetable group with no similar fare group (e.g. Coulsdon (All Stations) is a timetable group but there is no Coulsdon fare group).
Whilst the OJP API isn't free for use (RDG passes on the transaction charge we get from SilverRail for using their journey planning engine) it is open in the sense that anyone can request access as long as they accept the T&C's for usage (see
http://www.nationalrail.co.uk/100299.aspx) so I will see if our agreement with SilverRail allows us to add the SilverRail group data to the Open Wiki. This would be static and subject to manual updating but it changes very infrequently so would be fit for use until/unless we can get SilverRail data into an open data source.