Timetable: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [checked revision] |
(Wrote a new introduction text for timetable... first draft) |
No edit summary |
||
| Line 15: | Line 15: | ||
* [[TT:timetable:passengerTextInfos|passenger text infos (passenger information content to be displayed)]] | * [[TT:timetable:passengerTextInfos|passenger text infos (passenger information content to be displayed)]] | ||
* [[TT:timetable:announcements|announcements (passenger information content to be played accoustically)]] | * [[TT:timetable:announcements|announcements (passenger information content to be played accoustically)]] | ||
{{interwiki}} | |||
Latest revision as of 12:11, 5 December 2022
General information
The timetable subschema is part of the complete railML® schema, providing a data structure in XML for the exchange of timetable information. It allows exchange of operational as well as commercial facets of a timetable and supports both concrete and conceptual data. Please also visit the railML-Website for mode information or send an email with your enquiry to the timetable coordinator.
The main subschema element is <timetable> which contains among other things subelements for:
- base itineraries (basic building blocks of a railML3 timetable)
- itineraries (used to assemble train pathes from base itineraries)
- commercial trains (allows specifying commercial aspects of trains)
- operational trains (allows specifying operational aspects of trains)
- commercial schedulings (allows connecting commercial aspects of trains to operational ones)
- validities (used to describe when an element of a schedule takes place and when it does not)
- commercial connections (connections between trains for exchanging passengers or goods)
- passenger text infos (passenger information content to be displayed)
- announcements (passenger information content to be played accoustically)