This is the page for the preliminary documentation of railML^{®} 3.2 Timetable scheme concepts.

This page is under construction since May 27^{th} 2020. Task: Add description of priciples and elements. Sorry for temporary problems. See the discussion page to find a summary of the tasks and to coordinate the work on this page. Recognize that the content of this page may change quickly. Coordination (talk) 15:15, 27 May 2020 (CEST)


❗

Please note, that this page is made for saving ideas, concepts and descriptions for the upcoming railML^{®} 3.2 Timetable scheme. This page shall be replaced by the official documentation inside this wiki and must not be used for development or certification pourposes.



<commercialScheduling>
Semantic constraints
 all <operationalTrainSectionPart> elements referenced by one <commercialScheduling> element must belong to the same <operationalTrainSection> element
 a <commercialScheduling> links one <commercialTrainSection> and one <operationalTrainSection> (indirectly via reference to one or more <operationalTrainSectionPart> elements). Both must reference the same <itinerary> with an identical offset
 if more than one <commercialScheduling> elements reference the same <commercialTrainSection>, they must not overlap each other locally
 if more than one <commercialScheduling> elements reference the same <operationalTrainSection> (indirectly via reference to <operationalTrainSectionPart>), they must not overlap each other locally
Task 2
Task 2.1
Task 2.2
Task 3
Task 3.1
Task 3.2
Task 3.3