Search results
Jump to navigation
Jump to search
- (used to assemble train pathes from base itineraries) commercial trains (allows specifying commercial aspects of trains) operational trains (allows specifying2 KB (168 words) - 12:11, 5 December 2022
- railML® 2, it is possible to describe and validate that a <train> must reference one or more <trainPart>s, that all <trackElements> must have a position on the4 KB (579 words) - 16:49, 13 March 2023
- semantic constraint TT:001 was added in order to make sure that the evaluation of <operationalTrainSectionPart>s remains easy. If a train is operating differently1 KB (91 words) - 10:22, 13 October 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further1 KB (38 words) - 16:45, 13 March 2023
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further1 KB (38 words) - 16:55, 13 March 2023
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further514 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further523 bytes (38 words) - 21:56, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further549 bytes (36 words) - 21:56, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further527 bytes (38 words) - 21:56, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further523 bytes (38 words) - 21:56, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further515 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further523 bytes (38 words) - 21:55, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further519 bytes (38 words) - 21:56, 25 April 2022
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further514 bytes (38 words) - 21:56, 25 April 2022
- Main Page (section Timetable and Rostering (TT))schedule information. Trains: One or more train parts make up a train and represent either the operational or the commercial view of the train run. Connections:10 KB (1,041 words) - 10:56, 2 May 2024
- This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further525 bytes (38 words) - 21:55, 25 April 2022
- UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)least this use case needs the following elements: the elements <train> and <trainPart> to supply information about line, direction and relevant information9 KB (677 words) - 18:10, 27 June 2022
- UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)day, the <trainPart> must be divided among several commercial trains. Practically, this means that each <trainPartSequence> of a commercial train may only6 KB (688 words) - 13:26, 13 March 2023
- UC:TT:ATimetableForACompetition (category Use case (TT))<line>s are included Each <trainPart> must be covered by exactly one operational train. If commercial trains are given, each <trainPart> must be covered by exactly16 KB (1,903 words) - 13:27, 13 March 2023
- TT:commercialSchedulings TT:commercialTrain TT:commercialTrainReference TT:commercialTrainSection TT:commercialTrainVariant TT:commercialTrains TT:connectionTransferTime3 KB (756 words) - 14:47, 27 June 2022