Search results

When UUIDs are used, the ids can also provide valid references across files and data sources. In case of valid railML® files, no problems will occur. In case

Internationalized name of the clearance gauge. <validFor>: Gives indication, whether the clearance gauge is valid for only a national, several national or all

with the validity periods of other entries of the same register of the same enclosing element. <CO:designator> (introduced with version 2.5) CO:001 2018-11-12

or became valid. The entry can be considered as "valid since ever" if this attribute is not used (no other entry of that register was valid during the

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

<name>automatische treinbeïnvloeding</name> <validFor> <vehicleSystem>ATB</vehicleSystem> <vehicleSystem>ATBEG</vehicleSystem> </validFor> </trainProtectionSystem> <

Internationalized name of the clearance gauge. <validFor>: Gives indication, whether the clearance gauge is valid for only a national, several national or all

<infrastructureManager> with the code list. Children <name>: The company name <validity>: Time of validity, as defined with the attributes: begin: An xs:date (YYYY-MM-DD)

character "_" in the abbreviation and should not be in external, generally valid practical usage. Example: <register code="_CRL"> ... </register> Ziel der

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

about the correct XML syntax in attribute definitions. Which version is valid, which not? <element attribute="value"/> <element attribute='value'/> The

<validFor>   Parent: <trainProtectionSystem> Children: <vehicleSystem> [1..1] If the code for the system differs between vehicle and track installation

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

<electrification> frequency, type, voltage <maxTrainCurrent> maxCurrent, type, validFor <powerTransmission> style, type <axleWeight> meterload, value <gauge>

therefore not recommended. So, a valid railML® file may start with the following byte sequences: <?xml - no BOM, valid XML declaration: encoding shall be

- <validFor> - <trackSystem>LS</trackSystem> - </validFor> - </trainProtectionSystem> - <trainProtectionSystem code="LZB-L72"> - <name /> - <validFor>

or became valid. The entry can be considered as "valid since ever" if this attribute is not used (no other entry of that register was valid during the

or became valid. The entry can be considered as "valid since ever" if this attribute is not used (no other entry of that register was valid during the

or became valid. The entry can be considered as "valid since ever" if this attribute is not used (no other entry of that register was valid during the

+ <validFor> + <trackSystem>LS</trackSystem> + </validFor> + </trainProtectionSystem> + <trainProtectionSystem code="LZB-L72"> + <name /> + <validFor>