Search results
Jump to navigation
Jump to search
- Dev:Wiki Documentation Guidelines (category Pages using Tabber parser tag) (section Edit element documentation pages)release candidate version of railML®. The core of this wiki are pages documenting single railML® elements. The framework for such pages is provided by template:ElementDocu10 bytes (1,478 words) - 18:13, 5 March 2021
- the following template for showing it: {{Intro | <version-number>}} example: {{Intro | 2.1}} results in (introduced with version 2.1) There is no difference10 bytes (575 words) - 21:29, 23 January 2020
- IS:mileageChange (category Intro/2.2)<mileageChanges> Children: <additionalName>, <any>, <geoCoord> (introduced with version 2.2) [0..∞] A <mileageChange> defines the position of a track where metering9 KB (1,586 words) - 15:01, 17 July 2023
- Dev:changes/2.3 (section usingAny for timetable)changes between railML® 2.2 and railML® 2.3 This site is intended to collect the schema changes between railML® 2.2 and railML® 2.3 by topics, that influence20 KB (238 words) - 18:57, 22 January 2024
- Guidelines for implementing new elements in railML® schemes This page gives instructions for implementing new elements for the railML® XML schema in the10 KB (1,376 words) - 17:53, 3 December 2023
- must use this extension. railML® version 2.0 or 2.1 files / exports shall use *.xml extension, if the programme was delivered before July 1st 2013 and is10 bytes (1,742 words) - 15:07, 13 October 2022
- TT:times ocpTT ocpsTT trainPart (category Intro/2.2) (section Data exchange for DAS and TMS / Datenaustausch für FAS und RBL)provides an extension point for non-railML® attributes in a foreign namespace. How to use it? (introduced with version 2.2) scope: tTimeScope (union of23 KB (2,742 words) - 17:27, 24 September 2023