Search results

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-up

railways and can be found in the <common> section. The attribute <infrastructureManager>@code points to a value in the railML codelist InfrastructureManagers

consequently shall be modelled in the <common> domain: <common id="co_01"> <positioning> ... </positioning> </common> The railway network topology defined

@passable=“true” is not defined. In railML® 3 navigability is defined explicitly by a corresponding attribute. In railML® 2 <crossing> is used to describe

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 described

@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 specified

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:tOtherEnumerationValue