Search results

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 used

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 list

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 forum

<balise> element must reference a <baliseGroup> element. Correspondent to the concept of railML® element <baliseGroup>, also the railML® element <balise> is suitable

Moveable Elements   The class of moveable elements is an abstract, which is enriched by the attributes and elements of the particular type of moveable

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

and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The container element is named <registers>

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. Verwendung

Reason Commited changes have affects on XML-instance files and should be announced in advance in corresponding railML® newsgroups. Decision Tagging a major

and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The list contains train protection systems

Using Any   This article explains how to use the xs:any-element, the xs:anyAttribute and the railML® specific type tOtherEnumerationValue. It is a subtopic

and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained here. The codelist consists of clearance gauge

found here Category:Use_case_(IL). Interlocking Concepts — explanations of some basic modelling concepts to this subschema: Moveable Elements

single code, as to avoid repetitious work as well as ambiguity errors. The concept is explained here. The list contains infrastructure managing companies.

The children have changed. The attributes have been changed. This concept is explained on the RailTopoModel® wiki at TOPO:Topological structure (network)

IS root element — IS use cases — Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure

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

Common concepts to all railML® 3 schemas   Dev: is a pseudo namespace to cover general aspects or aspects interfering different subschemas. Some general

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 frame

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