Search results

elements in a bottom-up approach, we also try to help users to capture the concepts of railML® via examples and use cases in a top down approach. A use case

Using xsi:type   Before implementing any extensions to the railML® schema, please consider Dev:Extending_railML#when. The means described in this page

*.xml or *.railml, that is the question. The answer is: Both. It was not a convention from the beginning, but best practice should be: *.railml shall only

early planning phases to specify the connection times used for the schedule concept. Subschema generic Parents* connectionTransferTime Children None Attributes:

RS root element — RS use cases — Concepts & examples The rollingstock subschema is part of the complete railML (link to the railML® website) schema providing

The process starts with a service concept that describes the railroad service being provided. This service concept is shared with the traffic modeling

elements in a bottom-up approach, we also try to help users to capture the concepts of railML® via examples and use cases in a top down approach. A use case

early planning phases to specify the connection times used for the schedule concept. Subschema generic Parents* connectionTransferTime Children None Attributes:

more than a thousand words. Therefore, they can be valuable to grasp the concepts of railML®. railML.org publishes several example files on its website under

a redirect e.g. from topo:RTM Modelling Concepts from topo:RTM modelling concepts or topo:RTM Modeling Concepts. The railML® wiki should document the actual

railML® version 3.2 UML-visualization of RTM Documentation defines the concept of punctual location on a net element of a logical topology of a network

This article explains basic concepts of handling formation orientation within the timetable subschema. Dieser Artikel erklärt die grundlegenden Konzepte

allows a cross-check of completeness. Eulynx describes the use case in a concept document (external link) as follows:<br /> Eu.Con.97 - Data Preparation

required for running multiple trains interactively in a defined timetable concept for timetable feasibility and robustness studies, amongst others through

better modelling for this aspect is, in the author’s opinion, to use the concept of commercial trains in a different way than currently described in Wiki:

network contains 20 <networkResource> objects. To better understand these concepts, the objects have human-readable IDs and references; it is strongly advised

basis for planning would be a timetable, or possibly even a rough timetable concept. As part of this use case, data that has been determined as the results

page for the preliminary documentation of railML® 3.2 Timetable scheme concepts. all <operationalTrainSectionPart> elements referenced by one <commercialScheduling>

railML® 3 interfaces and inform you about the basic elements and modelling concepts of the railML® 3 schema. You are invited to contribute to this wiki and

better modelling for this aspect is, in the author’s opinion, to use the concept of commercial trains in a different way than currently described in Wiki: