Search results

Multiplicity   The section Multiplicity in element documentation pages reports the occurence indicators of the respective element, by name the values of

elements, that are not referred to within the railML® file. The general railML® description states the following semantics for this attribute. id: XML-file-wide

name="InterCity" description="Fast large city connection" trainUsage="passenger" my:colour="red"/> <category id="c2" code="RE" name="RegionalExpress" description="Fast

changes between the railML® 2 minor versions are available in the following descriptions: Changes between railML® 2.0 and railML® 2.1 Changes between railML®

whole formation. <TT:stopDescription> TT:006 2018-09-03 2019-06-20 Constraints between the attributes <ocpTT>.ocpType, <stopDescription>.guaranteedPass, .commercial

{{UC title}}) What is the application behind the use case? Which data in general is required? Which kind of tool/application provides this data? Who usually

In order to get the current stable railML® package, go to the Download section (link to the railML® website) whilst logged on. Current stable releases

Downloading and using railML® This Guideline is intended to help you through the first steps in downloading and using railML®. If you are not yet registered

reference sources without weblinks (e.g. books), use Template:Source. A general outline how to include images in mediawiki can be found at Help:Images ()

UC:IS:RailInspectionData): Head/Title Description: A sketch of the task, the necessary steps and the requirements in general. What is the application behind

<alternative> code, description, id, name, rail:lang, xsi:type <additionalName> description, name, rail:lang, xsi:type <phase> code, description, endDate, id

In some cases, attributes in railML® are defined by physical units. All employed units are listed in Category:Unit. A historic overview regarding railML®

|constraints_en= |constraints_de= |notes_en= |notes_de= |name= |name_de= |description= |description_de= |childs= |inheritedAttributes= |attributes_en= |attributes_de=

Guideline for participating in the development process This guideline is supposed to explain the development of the railML® schema and how you can contribute

Generally, examples are more illustrative, if they have a real background. As a general rule, minimal examples are more convenient to convey the principles of railML®

Sometimes there is a little confusion about the correct XML syntax in attribute definitions. Which version is valid, which not? <element attribute="value"/>

Declaration Schema Components" example: <xs:attribute name="description" type="rail:tElementDescription" /> example: <xs:attribute name="id" type="rail:tGenericID"

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

This article explains basic concepts, how to handle reversing trains and formations within the timetable subschema. Dieser Artikel erklärt Grundlagen des

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

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

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

+ </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