Search results
Jump to navigation
Jump to search
- Dev:UsingAny (section Example for an extension XML Schema defining new elements without any railML® re-use)tOtherEnumerationValue. It is a subtopic of dev:Extending railML. Before implementing any extensions to the railML® schema, please consider Dev:Extending_railML#when. The10 bytes (2,659 words) - 17:25, 30 May 2022
- TT:timetable (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)2.1) [1..1] The Element <timetable> is the root element of the subtree related to timetable information. Das Element <timetable> ist das Basiselement des2 KB (574 words) - 13:22, 6 October 2022
- semantic constraint on the respective list below (Dev:Semantic_Constraints/table2 for railML® 2 and Dev:Semantic_Constraints/table3 for railML® 3). assign10 bytes (579 words) - 15:58, 18 May 2020
- TT:trainPart (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)current train part. For more information on trains an train parts, see examples below and Train Coupling And Sharing. additionalTrainNumber: The precise12 KB (1,930 words) - 15:44, 13 May 2024
- TT:train (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)and Sharing and notes section of this page for further descriptions and examples for this attribute. Für weiter Beschreibungen und Beispiele zu diesem Attribut12 KB (2,023 words) - 20:58, 22 January 2024
- TT:operatingPeriod (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)and/or description in other languages. timetablePeriodRef: This refers to the id attribute of the associated <timetablePeriod> element. startDate: This is3 KB (711 words) - 12:48, 14 May 2024
- its child elements. A detailed list of examples how to specify the different types of OCPs can be found here: Dev:Types_of_ocps As described above <ocp>s18 KB (2,618 words) - 16:53, 19 March 2024
- the associated <rollingstock> element. timetableRef: This refers to the id attribute of the associated <timetable> element. id: xs:ID, required a string2 KB (574 words) - 17:47, 25 March 2024
- How to use it? timetableRef: This refers to the id attribute of the associated <timetable> element. This is the reference to a timetable data set. infrastructureRef:1 KB (584 words) - 12:11, 24 January 2022
- TT:annotation (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)consumer. Below both ways of referencing an image are shown as an example: <timetable id="tt01"> ... <annotations> <annotation id="annotationWithCodeCo4 KB (918 words) - 15:35, 14 September 2023
- implementation of the data exchange. What distinguishes a use case from an example is, that examples will typically consist of pieces of railML®-code, whereas use cases10 bytes (1,035 words) - 21:45, 23 January 2020
- TT:timetablePeriod (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)only one timetable period. railML® files without timetable period do either not have an element <timetablePeriod> at all or only elements <timetablePeriod>4 KB (836 words) - 20:50, 22 January 2024
- Làraich probably means nothing - as Bischofswerda of German examples) let’s assume the following example: A train leaves London St Pancras bound for Paris and24 KB (3,449 words) - 18:37, 22 January 2024
- TT:announcement (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)for passenger information systems that are used by the timetable. Several elements of the timetable allow references to announcements to indicate that a712 bytes (439 words) - 11:13, 12 September 2022
- of railML the use case is dependent upon if any, e.g. infrastructure, timetable, rolling stock, interlocking. Please also clarify if this dependency is10 bytes (263 words) - 21:42, 23 January 2020
- Dev:How To Reference Infrastructure (category Timetable Concept) (section Referencing Infrastructure from Timetable)infrastructure as demonstrated in the two examples above. For more information on how to specify station tracks refer to Dev:How to define track usage of a train15 KB (1,768 words) - 18:26, 19 January 2024
- Dev:Registers (section Example entry)by the registry is guaranteed. The further procedure is explained on the dev:Codelists#Missing_entries page. Use of a project-specific independent register10 bytes (721 words) - 21:27, 23 January 2020
- TT:rostering (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)later referencing that element internally. For a detailed explanation see Dev:identities. XML-Datei-weit eindeutige, maschineninterpretierbare Identität7 KB (1,167 words) - 20:40, 22 January 2024
- TT:blockPart (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)later referencing that element internally. For a detailed explanation see Dev:identities. XML-Datei-weit eindeutige, maschineninterpretierbare Identität12 KB (1,612 words) - 12:52, 14 May 2024
- Dev:Midnight overrun (category Timetable Concept) (section Example 1: Midnight overruns during an intermediate stop / Beispiel 1: Mitternachtsübergang während eines Zwischenaufenthalts)und railML®-Beispiel zu Verkehrstagen (external link, PDF; 185 kByte) [2] Examples for a non-zero operating day offset at the first ocpTT of a train run19 KB (2,347 words) - 18:40, 19 January 2024