Define use cases for railML (de: Anwendungsfälle für railML definieren)
The "use-case"-approach defines several sets of mandatory and optional data: use-case 0: no information on an operating period (for schematic/long-term planning) use-case 1: startDate and bitmask mandatory, bitmask covers seven days to specify a sample week (to define operating patterns in a schematic timetable), no holidays, deviances or offsets use-case 2: real timetable: start date, bitmask, holidays, ... and all the complex stuff with deviances, specialServices ... use-case n: user-defined descrition of a timetable/operating period based on any calendar
http://www.railml.org/forum/rw/index.php?group=2&offset=0&thread=117&id=418