Search results
Jump to navigation
Jump to search
- railML® version 3.2 UML-visualization of IS Documentation TSI category of line as defined in TSI INF section 4.2.1; There should be one code for each type518 bytes (5 words) - 18:43, 19 December 2019
- TAP TSI Id (obligatory; xs:int), core: The core part of the TAF TAP TSI Id (obligatory; xs:string), objectType: The object type of the TAF TAP TSI Id (obligatory;514 bytes (38 words) - 21:56, 25 April 2022
- CommercialTrainNumber OperationalTrainNumber TafTapTsiCaseReferenceId TafTapTsiPathId TafTapTsiPathRequestId TafTapTsiRouteId TafTapTsiTrainId, variant: Specifies the variant513 bytes (38 words) - 21:55, 25 April 2022
- flag, whether a TSI complaint pantograph head is required (optional; xs:boolean), compliantTSITypes: space separated list of accepted TSI compliant pantograph519 bytes (5 words) - 18:42, 19 December 2019
- alpha-2] (external link). <companyCode>: Company codes according TAF TAP TSI B.8 or UIC IRS/leaflet 920-1:2006. For an example entry see #Concept. →Main6 KB (797 words) - 12:50, 29 November 2023
- March 13th 2023 by User:RailML Coord Documentation TT IS TAF/TAP TSI requirements TAF/TAP TSI Anforderungen writer: ERA; reviewer: Bahnkonzept draft December7 KB (287 words) - 15:43, 8 April 2024
- for the cancellation. The enumeration used here is inspired by the Taf/Tap Tsi top level interruption reasons and can be extended if necessary. (optional;514 bytes (38 words) - 21:55, 25 April 2022
- Parents* externalTrainReference Children externalTrainNumber (1..1), tafTapTsiId (1..1) Attributes: None *Notice: Elements may have different parent elements508 bytes (38 words) - 21:56, 25 April 2022
- TAP TSI static timetable Information; Fahrplanauskunft; Timetable information for the TAP TSI (EC 454/2011) http://eur-lex.europa.eu/LexUriServ/LexUriServ4 KB (592 words) - 18:06, 7 December 2023
- Automatic Schemaexport for Element tafTapTsiId1 KB (5 words) - 12:43, 8 February 2024
- CommercialTrainNumber OperationalTrainNumber TafTapTsiCaseReferenceId TafTapTsiPathId TafTapTsiPathRequestId TafTapTsiRouteId TafTapTsiTrainId, variant: Specifies the variant2 KB (5 words) - 12:43, 8 February 2024
- railML® version 3.1 UML-visualization of IS Documentation TSI category of line as defined in TSI INF section 4.2.1; There should be one code for each type807 bytes (5 words) - 18:16, 23 December 2019
- railML® version 3.2 UML-visualization of IS Documentation TSI category of line as defined in TSI INF section 4.2.1; There should be one code for each type807 bytes (5 words) - 16:14, 5 March 2021
- the clearance gauge is valid for only a national, several national or all TSI-compliant networks. Allowed values are "interoperable", "multinational" and6 KB (294 words) - 14:03, 7 December 2023
- Operational Train Categories.pdf ETCS Operational Train Categories (Source: TSI OPE Version 4) Note: The presented page 79 of Figure 2 is taken from Appendix19 KB (2,085 words) - 21:02, 15 January 2024
- Children None Attributes: compliantTSITypes: space separated list of accepted TSI compliant pantograph heads (optional; tTSIPantoHeadTypeList), contactStripMaterials:912 bytes (5 words) - 12:40, 8 February 2024
- flag, whether a TSI complaint pantograph head is required (optional; xs:boolean), compliantTSITypes: space separated list of accepted TSI compliant pantograph912 bytes (5 words) - 18:42, 19 December 2019
- 3166-1 alpha-2 (external link). <companyCode>: Company codes according TAF TAP TSI B.8 or UIC IRS/leaflet 920-1:2006 (also called RICS or Railway Interchange17 KB (299 words) - 15:10, 7 December 2023
- Parents* externalTrainReference Children externalTrainNumber (1..1), tafTapTsiId (1..1) Attributes: None *Notice: Elements may have different parent elements453 bytes (5 words) - 21:56, 25 April 2022
- information Netherlands () PLC en: Primary Location Code for the TAF/TAP TSI en: RailNetEurope for ERA en: Used for the communication between the railway13 KB (721 words) - 14:12, 9 October 2023