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

The RailTopoModel® wiki page Concept explained Object positioning in the network <RTM:spotLocation> Intrinsic positioning / referencing @intrinsicCoord

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

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

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

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

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

not located anywhere on the earth's surface. Extending the pure topology concept of RailTopoModel®, railML® 3.1 allows to define <netElement> elements with

The RailTopoModel® wiki page Concept explained Object positioning in the network <RTM:associatedNetElement> Intrinsic positioning / referencing @intrinsicCoordBegin

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

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

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

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

*.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 only

early planning phases to specify the connection times used for the schedule concept. Subschema generic Parents* connectionTransferTime Children None Attributes:

RS root element — RS use cases — Concepts & examples The rollingstock subschema is part of the complete railML (link to the railML® website) schema providing

The process starts with a service concept that describes the railroad service being provided. This service concept is shared with the traffic modeling

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

early planning phases to specify the connection times used for the schedule concept. Subschema generic Parents* connectionTransferTime Children None Attributes:

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 under

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 actual

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

This article explains basic concepts of handling formation orientation within the timetable subschema. Dieser Artikel erklärt die grundlegenden Konzepte

allows a cross-check of completeness. Eulynx describes the use case in a concept document (external link) as follows:<br /> Eu.Con.97 - Data Preparation

required for running multiple trains interactively in a defined timetable concept for timetable feasibility and robustness studies, amongst others through

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:

network contains 20 <networkResource> objects. To better understand these concepts, the objects have human-readable IDs and references; it is strongly advised

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 results

page for the preliminary documentation of railML® 3.2 Timetable scheme concepts. all <operationalTrainSectionPart> elements referenced by one <commercialScheduling>

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 and

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:

the functional requirements published by ERA for RINF data, including all concepts and data required. In a first step, considering the current non-acceptance