Search results
Jump to navigation
Jump to search
- Testimport am Mi 13. Mär 19:04:18 CET 2024 durch RailML Bot Documentation74 bytes (14 words) - 20:04, 13 March 2024
- Testimport am Mo 15. Apr 16:53:31 CEST 2024 durch RailML Bot Documentation74 bytes (14 words) - 16:53, 15 April 2024
- Testimport am Mo 15. Apr 18:02:43 CEST 2024 durch RailML Bot Documentation74 bytes (14 words) - 18:02, 15 April 2024
- Testimport am Mo 20. Mai 14:26:01 CEST 2024 durch RailML Bot Documentation74 bytes (14 words) - 14:26, 20 May 2024
- infrastructure description in railML®, tracks usually are limited by switches, crossings, bufferstops and such. In railML® that would mean that usually17 KB (2,110 words) - 12:06, 14 December 2023
- category is created to give an overview of all element documentation sites of the infrastructure railML® sub-schema.276 members (0 subcategories, 0 files) - 22:30, 22 January 2024
- category is created to give an overview of all element documentation sites of the rollingstock railML® sub-schema.164 members (0 subcategories, 0 files) - 22:35, 22 January 2024
- category is created to give an overview of all element documentation sites of the common railML® sub-schema.60 members (0 subcategories, 0 files) - 22:28, 22 January 2024
- category is created to give an overview of all element documentation sites of the timetable railML® sub-schema.183 members (0 subcategories, 0 files) - 22:36, 22 January 2024
- discussion on the documentation of railML®3, as the decisions made in this matter will affect all of us — see here (link to the railML® website). Yours4 KB (332 words) - 14:05, 13 March 2023
- Talk:Dev:Semantic Constraints (section Distinctions within element documentation / Structure and usage of an Wiki page)semantic constraints Suggestion and Discussion either in the railML® Forum or in a railML® working group →in this case the working group must present their3 KB (426 words) - 20:39, 3 April 2020
- 16:08, 16. Dez. 2014 (CET): As discussed for a long time, with the current railML 2.0..2.2 structures for <train>s and <trainPart>s, it is hard to identify2 KB (266 words) - 18:46, 1 February 2018
File:Anpassungen railML 2 -Bedarfszüge.pdf Documentation of the change adding onRequest to <trainPart>(0 × 0 (512 KB)) - 12:42, 30 June 2020- category lists pages that use {{depr|2.0}}. As railML®2.0 is no longer supported, it should contain only documentation pages.2 members (0 subcategories, 0 files) - 16:56, 19 August 2019
- this documentation further. Aspects that are only relevant with respect to one of several parents should be explaint exclusively in the documentation of244 bytes (5 words) - 17:33, 19 October 2017
- this documentation further. Aspects that are only relevant with respect to one of several parents should be explaint exclusively in the documentation of244 bytes (5 words) - 17:34, 19 October 2017
- Dev:Codelists Dev:InfrastructureManagers Dev:Registers Dev:TrainClearanceGauges Dev:TrainProtectionSystems CO:infrastructureManagerCodes CO:infrastruc1 KB (45 words) - 19:46, 15 December 2022
- //xs:element[not(xs:annotation/xs:documentation)] //xs:attribute[not(xs:annotation/xs:documentation)] //xs:element[not(xs:annotation/xs:documentation[not(starts-with(text()1 KB (102 words) - 19:46, 15 December 2022
- this documentation further. Aspects that are only relevant with respect to one of several parents should be explaint exclusively in the documentation of244 bytes (5 words) - 08:13, 19 October 2017
- Template. Element templates are intended to avoid routine work in railML® element documentation. These templates are very specific and are therefore documented4 KB (195 words) - 22:04, 22 January 2024