Search results
Jump to navigation
Jump to search
- Dev:Examples (section Real World Examples)Examples Like pictures, illustrative examples can say more than a thousand words. Therefore, they can be valuable to grasp the concepts of railML®. railML10 bytes (674 words) - 21:20, 23 January 2020
- Timetable (section Timetable and Rostering (TT))following pages: <timetable> — documentation of the main element Timetable Elements — overview off all XML elements found in the timetable subschema UML visualization2 KB (260 words) - 21:06, 22 January 2024
- TT:timetable (category Timetable Elements) (section Position of timetable in the XML-Tree / Position von timetable im XML-Baum)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
- 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 (287 words) - 16:31, 3 February 2020
- TT:trainPart (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)</trainOrder> </formation> </formations> </rollingstock> <timetable> <trainParts> <!-- Example a): One of the two vehicles is closed for passengers -->12 KB (1,930 words) - 15:44, 13 May 2024
- TT:train (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)operational: The timetable of this train is seen from the railway operational point of view (by the IM or RU). commercial: The timetable of this train is12 KB (2,023 words) - 20:58, 22 January 2024
- TT:operatingPeriod (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)period defined through startDate and endDate of the <timetablePeriod> element. This means: If the timetable period is reduced by attributes startDate+endDate3 KB (711 words) - 12:48, 14 May 2024
- TT:organizationalUnitBinding trainPart (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)<organizationalUnitBinding> Parent: <trainPart>, <patternTrainPart> Children: <vehicleOperator>, <customer>, <railwayUndertaking>, <operationalUndertaking>967 bytes (68 words) - 19:21, 9 February 2022
- TT:organizationalUnitBinding trainNumber (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)TT:organizationalUnitBinding trainNumber Parent: <trainNumber> Children: <vehicleOperator>, <customer>, <railwayUndertaking>, <operationalUndertaking>776 bytes (60 words) - 09:51, 11 May 2023
- collection of use cases for the RS-subschema Examples (link to the railML® website) — collection of examples provided by the railML® partners All elements3 KB (452 words) - 20:21, 22 January 2024
- 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
- TT:metadata (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)metadata Parent: <timetable> Children: <dc:creator>, <dc:date>, <dc:format>, <dc:identifier>, <dc:language>, <dc:source>, <dc:title> [1..1] The element899 bytes (112 words) - 20:32, 22 January 2024
- collection us use cases for the IS-subschema Examples (link to the railML® website) — collection of examples provided by the railML® partners (railML.org3 KB (350 words) - 19:56, 22 January 2024
- TT:trainParts (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)trainParts Parent: <timetable> Children: <trainPart> [0..1] The Element <trainParts> groups trainPart elements. Das Element <trainParts> gruppiert trainPart-Elemente386 bytes (39 words) - 22:00, 25 November 2018
- 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
- TT:startTime (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)<startTime> Parent: <periodic>, <activationTime> Children: <eventTrigger>, <ocpTrigger>, <timingTrigger>, <geoTrigger>, <informationAreaTrigger> [1.412 bytes (52 words) - 16:55, 28 March 2022
- TT:endTime (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)<endTime> Parent: <periodic>, <activationTime> Children: <eventTrigger>, <ocpTrigger>, <timingTrigger>, <geoTrigger>, <informationAreaTrigger> [1..1]408 bytes (52 words) - 16:55, 28 March 2022
- 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
- the timetable. Timetables that aim more at passenger information will define as <ocp> what a traveller perceives as an access point - for example, consider18 KB (2,618 words) - 16:53, 19 March 2024
- TT:formationTT (category Timetable Elements) (section Best practice & Examples / Empfohlene Anwendung & Beispiele)speed of the formation while in use timetableLoad: (introduced with version 2.1) planned load according to the timetable, excluding any possible engine(s)3 KB (356 words) - 17:36, 8 August 2022