Search results
Jump to navigation
Jump to search
- Dev:Identities (category Common Concept)Very many railML® elements require an id attribute of the W3C-Type xs:ID. This has to be provided in order to enable references, that are very much used5 KB (463 words) - 12:22, 3 November 2023
- TAF TAP TSI B.8 or UIC IRS/leaflet 920-1:2006. For an example entry see #Concept. →Main Article: Codelist Registers The file Registers.xml contains a list6 KB (797 words) - 12:50, 29 November 2023
- Dev:Changes (category Common Concept)This page is intended to inform about the schema changes by topics, that influence the XML output. As it starts as a stub please refer to the railML forum3 KB (403 words) - 15:46, 15 April 2024
- <balise> element must reference a <baliseGroup> element. Correspondent to the concept of railML® element <baliseGroup>, also the railML® element <balise> is suitable8 KB (900 words) - 17:31, 11 April 2024
- The RailTopoModel® wiki page Concept explained Object positioning in the network <RTM:spotLocation> Intrinsic positioning / referencing @intrinsicCoord949 bytes (15 words) - 16:52, 19 April 2024
- Dev:Moveable Elements (category Interlocking Concept)Moveable Elements The class of moveable elements is an abstract, which is enriched by the attributes and elements of the particular type of moveable6 KB (912 words) - 14:29, 27 May 2022
- Dev:Registers (category Common Concept)and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The container element is named <registers>13 KB (721 words) - 14:12, 9 October 2023
- Dev:catalog (category Common Concept)Structure and content types of railML files are defined in XML Schema. railML is based on a couple of such XSD files which require each other. Verwendung15 KB (1,996 words) - 12:36, 20 August 2021
- Dev:versions (category Common Concept)Reason Commited changes have affects on XML-instance files and should be announced in advance in corresponding railML® newsgroups. Decision Tagging a major9 KB (1,043 words) - 11:28, 15 February 2023
- Dev:TrainProtectionSystems (category Common Concept)and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The list contains train protection systems11 KB (422 words) - 15:50, 16 November 2022
- Dev:UsingAny (category Common Concept)Using Any This article explains how to use the xs:any-element, the xs:anyAttribute and the railML® specific type tOtherEnumerationValue. It is a subtopic23 KB (2,659 words) - 09:51, 1 June 2022
- Dev:TrainClearanceGauges (category Common Concept)and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The codelist consists of clearance gauge6 KB (294 words) - 14:03, 7 December 2023
- Dev:InfrastructureManagers (category Common Concept)single code, as to avoid repetitious work as well as ambiguity errors. The concept is explained here. The list contains infrastructure managing companies.17 KB (299 words) - 15:10, 7 December 2023
- This concept is explained on the RailTopoModel® wiki at TOPO:Topological structure (network) The children have changed. The attributes have been changed7 KB (138 words) - 15:41, 30 April 2024
- found here Category:Use_case_(IL). Interlocking Concepts — explanations of some basic modelling concepts to this subschema: Moveable Elements1 KB (153 words) - 18:26, 3 November 2023
- not located anywhere on the earth's surface. Extending the pure topology concept of RailTopoModel®, railML® 3.1 allows to define <netElement> elements with11 KB (1,110 words) - 09:59, 29 April 2024
- The RailTopoModel® wiki page Concept explained Object positioning in the network <RTM:associatedNetElement> Intrinsic positioning / referencing @intrinsicCoordBegin780 bytes (11 words) - 16:56, 19 April 2024
- IS root element — IS use cases — Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure3 KB (288 words) - 18:47, 20 March 2024
- Dev:Common Concepts (category Common Concept)Common concepts to all railML® 3 schemas Dev: is a pseudo namespace to cover general aspects or aspects interfering different subschemas. Some general872 bytes (95 words) - 11:59, 5 December 2022
- Dev:Extending railML (category Common Concept)Extending railML® There exists a wide range of means to extend XML Schemas. As railML® is intended for collaboration with other parties, there is a frame7 KB (985 words) - 10:01, 1 June 2022
- 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 case7 KB (287 words) - 15:43, 8 April 2024
- Dev:Using xsi:type (category Common Concept)Using xsi:type Before implementing any extensions to the railML® schema, please consider Dev:Extending_railML#when. The means described in this page18 KB (2,309 words) - 14:28, 1 August 2022
- Dev:fileConventions (category Common Concept)*.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 only11 KB (1,742 words) - 18:13, 29 November 2023
- early planning phases to specify the connection times used for the schedule concept. Subschema generic Parents* connectionTransferTime Children None Attributes:528 bytes (58 words) - 12:43, 8 February 2024
- RS root element — RS use cases — Concepts & examples The rollingstock subschema is part of the complete railML (link to the railML® website) schema providing3 KB (458 words) - 17:20, 29 November 2023
- The process starts with a service concept that describes the railroad service being provided. This service concept is shared with the traffic modeling5 KB (687 words) - 13:46, 13 March 2023
- 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 case7 KB (1,035 words) - 17:27, 5 February 2024
- early planning phases to specify the connection times used for the schedule concept. Subschema generic Parents* connectionTransferTime Children None Attributes:825 bytes (5 words) - 15:55, 8 February 2024
- 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 under5 KB (674 words) - 15:49, 15 April 2024
- 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 actual12 KB (1,475 words) - 15:28, 15 April 2024
- 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 network3 KB (5 words) - 12:39, 8 February 2024
- Dev:Reversing trains and formations (category Timetable Concept)This article explains basic concepts of handling formation orientation within the timetable subschema. Dieser Artikel erklärt die grundlegenden Konzepte7 KB (771 words) - 13:39, 13 March 2023
- allows a cross-check of completeness. Eulynx describes the use case in a concept document (external link) as follows:<br /> Eu.Con.97 - Data Preparation3 KB (450 words) - 17:54, 27 June 2022
- required for running multiple trains interactively in a defined timetable concept for timetable feasibility and robustness studies, amongst others through7 KB (959 words) - 14:06, 7 December 2023
- 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:6 KB (688 words) - 13:26, 13 March 2023
- network contains 20 <networkResource> objects. To better understand these concepts, the objects have human-readable IDs and references; it is strongly advised9 KB (931 words) - 12:07, 4 April 2024
- 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 results6 KB (926 words) - 17:00, 4 December 2023
- page for the preliminary documentation of railML® 3.2 Timetable scheme concepts. all <operationalTrainSectionPart> elements referenced by one <commercialScheduling>1 KB (97 words) - 07:08, 13 June 2020
- 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 and10 KB (1,041 words) - 10:56, 2 May 2024
- 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:16 KB (1,903 words) - 13:27, 13 March 2023
- the functional requirements published by ERA for RINF data, including all concepts and data required. In a first step, considering the current non-acceptance3 KB (297 words) - 13:49, 13 March 2023