Search results
Jump to navigation
Jump to search
- elements necessary for the use case. This description may also reference other existing use cases. Are there any partial use cases distinguished, which build2 KB (263 words) - 17:26, 5 February 2024
- Dev:Use case example/old (category Use case (unknown subschema)) (section Use case / Anwendungsfall)good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases. Please2 KB (220 words) - 16:25, 4 December 2023
- IL:tvdSection (category Pages using Tabber parser tag)<signalIL> which protects the exit from this TVD section. It shall be used in case @isBerthingTrack is set to true. Within the simple example there are7 KB (829 words) - 15:11, 27 May 2022
- IL:levelCrossingIL (category Pages using Tabber parser tag)element the related type is called levelCrossingIL in railML interlocking subschema. The features of the particular level crossing can be detailed as below18 KB (1,997 words) - 15:11, 4 June 2022
- IL:tunnelGateIL (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further5 KB (599 words) - 14:26, 27 May 2022
- conditions, i.e. when not in use. For most level crossings this would be the open state. (optional; xs:string) Possible values: unknown closing opening closed3 KB (5 words) - 14:21, 24 January 2020
- Here the functional aspects for interlocking operation are considered. Subschema interlocking Parents* levelCrossingsIL Children activationCondition (04 KB (5 words) - 12:41, 8 February 2024
- The railML® wiki offers a number of Use Cases. A Guideline to implementing Use Cases can be found under Dev:Use cases. In contrast to railML® 2, railML®12 KB (1,475 words) - 15:28, 15 April 2024