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