Search results

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

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

short name for the train clearance gauges in latin letters Children <description>: Internationalized name of the clearance gauge. <validFor>: Gives indication

<any>, <dc:contributor>, <dc:coverage>, <dc:creator>, <dc:date>, <dc:description>, <dc:format>, <dc:identifier>, <dc:language>, <dc:publisher>, <dc:relation>

of the same register of the same enclosing element. <CO:designator> (introduced with version 2.5) CO:001 2018-11-12 2019-03-21 Any starting time stamp (as

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®

Semantic Constraint "CO:001":   Any starting time stamp (as it may result e.g. from a combination

CO:railml   Parent: none Children: <metadata>, <infrastructure>, <rollingstock>, <timetable>, <infrastructureVisualizations> (deprecated with version 2

organizationalUnits   Parent: <metadata> Children: <infrastructureManager>, <vehicleManufacturer>, <vehicleOperator>, <vehicleOwner> (introduced with version

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

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

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

Réseau nl-BE: Netverklaring fr-BE: Infrabel nl-BE: Infrabel fr-BE: courte description et la source nl-BE: korte beschrijving en de bron Belgium () ENEE ENEE

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

Example entry <trainClearanceGauge code="GA"> <description>stucture gauge GA according European standard</description> <validFor>interoperable</validFor> </trainClearanceGauge>

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

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

format and language for the data to be exchanged. The aim of the use case description is to formulate requirements on the technical implementation of the data

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

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

<trainProtectionSystem>   Parent: <trainProtectionSystemsOnVehicle> Children: <name>, <validFor> [1..1] Single entries for each train protection system

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

projects   Parent: <metadata> Children: <project> [0..1] Container element for <project> instances.(introduced with version 2.5) None None Not yet described

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

Reason Commited changes have affects on XML-instance files and should be announced in advance in corresponding railML® newsgroups. Decision Tagging a major

</organizationalUnits> </metadata> <!-- ... --> <vehicle id='veh_123' axleSequence='Co&apos;Co&apos; de' numberDrivenAxles='6' length='20.960' speed='160' bruttoWeight='122'

format, physical medium, or dimensions of the resource." Dublin Core description "Examples of dimensions include size and duration. Recommended best practice

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:

projectArea   Parent: <project> Children: None [0..∞] Reference to a project area.(introduced with version 2.5) {{{attributes}}} ref: Reference is required

objectsRevised   Parent: <revision> Children: <objectRevised> [0..1] Container for references to objects changed in this revision.(introduced with version

related resource from which the described resource is derived." Dublin Core description "The described resource may be derived from the related resource in whole

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