Renaming itinerary in IL to routeSequence
When the development of interlocking schema started there was the request to have list of sequential routes for train to navigate the railway network. However, such list is needed in the timetable and the interlocking domain. At that time no timetable development for railML3 was active. Thus no one did intervene, when the element name "itinerary" was used in interlocking provoking the later conflict with timetable.
In mutual discussions we found the name "itinerary" more suitable in the timetable domain. Therefore the need of element renaming in existing interlocking schema arose. The decision was to rename "itineraries"/"itinerary" in Controller element to "routeSequences"/"routeSequence".