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