Search results

namespace (identical string) as defined by its corresponding XML Schema. For general information about namespaces see Defining namespaces and validating railML®

The following templates may be used at every wiki page for referring to a certain railML® element documentation page. The link is shown in angle brackets:

Defaults Optional attributes may have defaults. Please, employ Template:Constraint, wherever defaults are employed. All pages where defaults are defined

has to be used by exactly one operational and one commercial train. In general, if we have the situation of train coupling and sharing, there is one ‘long’

name="Schienenersatzverkehr" lang="de"/> <category id="cat_3" code="EC" name="EuroCity" description="Schnellfahrende Reisezüge im internationalen Verkehr mit besonderem Komfort"

railML® schema changes between railML® 2.0 and railML® 2.1   This site collects sources helping you to compare railML® 2.0 and railML® 2.1. Changes are

If a train is not included in the railML® file with its entire itinerary and already has a midnight transition before "entering" the railML® file network

Guidelines for implementing new elements in railML® schemes This page gives instructions for implementing new elements for the railML® XML schema in the

agreed. They may occur in German railML® files but should not be used as general “pattern”. No infrastructural difference to a simple halt, just difference

<xs:annotation> <xs:documentation>additional names and its according descriptions to be provided in other languages, dialects, encodings...</xs:documentation>

<infrastructureManager> code, description, id, name, rail:lang <additionalName> description, name, rail:lang, xsi:type <vehicleManufacturer> code, description, id, name,

<infrastructureManager> code, description, id, name, rail:lang <additionalName> description, name, rail:lang, xsi:type <vehicleManufacturer> code, description, id, name,

railVIVID® railVIVID® is the railML® validation and viewer tool. It was financed by several European Railway Infrastructure Managers through and was initial

imes /trainParts/trainPart/ocpsTT/ocpTT/stopDescription /trainParts/trainPart/ocpsTT/ocpTT/stopDescription/stopTimes /trains/train/trainPartSequence /

the use case here. The headline is made with Template: UC description (type {{UC description}}) In this section the data flows should be drafted. The headline

availability of infrastructure elements and speed profiles Representation of general time restrictions using newly introduced attributes in railML® 2.4 IS New

gPeriodRef /ocpTT/stopDescription/trackInfo@track /ocpTT/stopDescription/trackInfo@platform New elements: /ocpTT/stopDescription/trackInfo

Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure including all its various facets

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

+ </xs:annotation> + </xs:element> <xs:element name="generalInfraAttributes" type="rail:eGeneralInfraAttributes" minOccurs="0"> <xs:annotation> <xs:documentation

trackBegin   Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]

trackEnd   Parent: <trackTopology> Children: (introduced with version 2.2) <geoCoord>, <bufferStop>, <connection>, <openEnd>, <macroscopicNode> [1..1]

</xs:annotation> + </xs:attribute> <xs:attribute name="remarks" type="rail:tElementDescription"> <xs:annotation> <xs:documentation>This is to further explain the 'state'

<speedProfile id="sp1" name="Basis" influence="increasing" description="speed profile as general basis for other overlaying profiles"/> <speedProfile id="sp2"

in a feature branch to not contaminate the branches that are of a more general nature with intermediate solutions. Merge back your changes when you are

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

menschenlesbaren Datenfeldern. (introduced with version 2.1) description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

generalInfraAttribute   Parent: <generalInfraAttributes> Children: <attributes> [0..∞] The element generalInfraAttribute describes a single pre-defined

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

siehe Hinweise zu menschenlesbaren Datenfeldern. description: Human-readable, more detailed description as addition to the name. It should give additional

generalInfraAttributes   Parent: <infraAttributes> Children: <generalInfraAttribute> [0..1] The element <generalInfraAttributes> works as a "container