Search results

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

Xerces with some additional flags/parameter: <target name="xml-validate" description="Validate ${xml-file} against its schema files"> <schemavalidate file="${xml-file}

approach is focussed on providing a very detailed description. In a microscopic infrastructure description in railML®, tracks usually are limited by switches

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

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

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’

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

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

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

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

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

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

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

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

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

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

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

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