Search results
Jump to navigation
Jump to search
- UC:Use cases (section railML® Use Cases)page you learn what is a use case and find a list of railML® use cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up7 KB (287 words) - 16:17, 13 May 2024
- CO:positioning (category Common Elements)consequently shall be modelled in the <common> domain: <common id="co_01"> <positioning> ... </positioning> </common> The railway network topology defined11 KB (1,110 words) - 09:59, 29 April 2024
- railways and can be found in the <common> section. The attribute <infrastructureManager>@code points to a value in the railML codelist InfrastructureManagers9 KB (873 words) - 11:03, 13 May 2024
- 16, NO-0101 Oslo, NORWAY RailML Coord Common/Dev pages504 bytes (55 words) - 19:13, 15 December 2022
- the railML wiki (wiki2; wiki3) ✔ RailML Coord Documentation (talk) 16:30, 3 April 2023 (CEST) Dev:Semantic Constraints (wiki2; wiki3) ✔ RailML Coord Documentation5 KB (363 words) - 14:51, 24 April 2023
- required for railML® 3.2 and higher. For all versions of railML® 2 plus for railML® 3.1, the proposed means are xs:any, xs:anyAttribute and rail:tOtherEnumerationValue18 KB (2,309 words) - 14:28, 1 August 2022
- Dev:Simple crossing (section Comparison with railML® 2)@passable=“true” is not defined. In railML® 3 navigability is defined explicitly by a corresponding attribute. In railML® 2 <crossing> is used to describe24 KB (2,447 words) - 14:36, 13 March 2024
- also possible to locate the crossing at tracks 30 and 27 in railML® 3. According to in the railML® 2 wiki, the navigability of straight branches is described29 KB (2,876 words) - 14:34, 13 March 2024
- Dev:Railway switch (section Comparison with railML® 2)@applicationDirection railML® 3. The orientation of a switch in railML® 2 was always dependent on the direction of the track. In railML® 3 the directions specified18 KB (2,052 words) - 18:20, 15 April 2024
- Interlocking schema of railML® 3 The railML interlocking subschema contains definitions of data describing railway signalling and the use of interlocking8 KB (1,122 words) - 19:18, 4 January 2023
- format https://railML.org Latest release: 2.5 (September 1st, 2021)18 bytes (0 words) - 19:18, 4 January 2023
- </speedProfiles> </common> Shall the location of <speedSection> in railML® be provided as linear element or as area element? A railML® attribute for <speedSection>3 KB (303 words) - 19:18, 4 January 2023
- User:RailML Coord Documentation/CO:speedProfile (section Extract of a corresponding railML® modelling according to ETCS Baseline 3 (part 1 of 2):)Profile (SPP) is uniquely described by the railML® attribute @isBasicSpeedProfile. The modelling in railML® is <common id="co_01"> <speedProfiles> <speedProfile17 KB (2,081 words) - 19:18, 4 January 2023
- User:RailML Coord Documentation/IS:baliseGroup (section Semantic Rules applicable for railML® element “baliseGroup”)https://forum.railml.org (link to the railML® website) – reporting the missing information to be modelled in railML®. railML®.org will provide a suggestion for22 KB (2,620 words) - 19:18, 4 January 2023
- RAILML:railML CO:common CO:electrificationSystems CO:electrificationSystem CO:organizationalUnits CO:concessionaire CO:isConcessionaire CO:isContractor77 KB (2,609 words) - 19:18, 4 January 2023