Search results

Jump to navigation Jump to search

  • Dev:identities (redirect from CO:identities)
    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
    7 KB (807 words) - 19:07, 22 January 2024
  • Dev:Codelists (redirect from CO:codelists)
    Internationalized name of the clearance gauge. <validFor>: Gives indication, whether the clearance gauge is valid for only a national, several national or all
    10 bytes (797 words) - 12:25, 24 January 2020
  • CO:designator
    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
    315 bytes (260 words) - 19:44, 5 January 2024
  • Dev:Semantic Constraints
    stamp (e.g. endDate) if both are given. Must not overlap with other validity periods. <CO:designator> (introduced with version 2.5) TT:001 2018-11-12 2019-03-21
    10 bytes (579 words) - 15:58, 18 May 2020
  • CO:railml (section Position of CO:railml in the XML-Tree / Position von CO:railml im XML-Baum)
    CO:railml   Parent: none Children: <metadata>, <infrastructure>, <rollingstock>, <timetable>, <infrastructureVisualizations> (deprecated with version 2
    825 bytes (115 words) - 17:46, 25 March 2024
  • Dev:TrainProtectionSystems (redirect from CO:Codelist:TrainProtectionSystems)
    <name>automatische treinbeïnvloeding</name> <validFor> <vehicleSystem>ATB</vehicleSystem> <vehicleSystem>ATBEG</vehicleSystem> </validFor> </trainProtectionSystem> <
    10 bytes (422 words) - 21:38, 23 January 2020
  • Dev:TrainClearanceGauges (redirect from CO:Codelist:TrainClearanceGauges)
    Internationalized name of the clearance gauge. <validFor>: Gives indication, whether the clearance gauge is valid for only a national, several national or all
    10 bytes (294 words) - 21:36, 23 January 2020
  • Dev:InfrastructureManagers (redirect from CO:Codelist:InfrastructureManagers)
    <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)
    10 bytes (299 words) - 21:23, 23 January 2020
  • Dev:Registers (redirect from CO:Codelist:Registers)
    character "_" in the abbreviation and should not be in external, generally valid practical usage. Example: <register code="_CRL"> ... </register> Ziel der
    10 bytes (721 words) - 21:27, 23 January 2020
  • RS:operator
    </organizationalUnits> </metadata> <!-- ... --> <vehicle id='veh_123' axleSequence='Co&apos;Co&apos; de' numberDrivenAxles='6' length='20.960' speed='160' bruttoWeight='122'
    3 KB (336 words) - 06:53, 26 November 2020
  • CO:validFor trainProtectionSystem trainProtectionSystemsOnVehicle (section Position of <validFor> in the XML-Tree / Position von <validFor> im XML-Baum)
    <validFor>   Parent: <trainProtectionSystem> Children: <vehicleSystem> [1..1] If the code for the system differs between vehicle and track installation
    383 bytes (46 words) - 20:32, 15 February 2018
  • Dev:attributeSyntax (redirect from CO:xmlSyntax)
    about the correct XML syntax in attribute definitions. Which version is valid, which not? <element attribute="value"/> <element attribute='value'/> The
    2 KB (258 words) - 18:45, 22 January 2024
  • CO:trainProtectionSystem trainProtectionSystemsOnVehicle
    <trainProtectionSystem>   Parent: <trainProtectionSystemsOnVehicle> Children: <name>, <validFor> [1..1] Single entries for each train protection system, installed "on
    598 bytes (82 words) - 19:32, 21 February 2022
  • Dev:XMLtree (redirect from CO:XMLtree)
    <electrification> frequency, type, voltage <maxTrainCurrent> maxCurrent, type, validFor <powerTransmission> style, type <axleWeight> meterload, value <gauge>
    112 KB (4,754 words) - 18:02, 3 April 2022
  • Dev:fileConventions (redirect from CO:fileConventions)
    therefore not recommended. So, a valid railML® file may start with the following byte sequences: <?xml - no BOM, valid XML declaration: encoding shall be
    10 bytes (1,742 words) - 15:07, 13 October 2022
  • CO:phase
    time stamp (e.g. endDate) if both are given. Must not overlap with other validity periods. See also https://wiki2.railml.org/wiki/Dev:Defining_temporal_
    440 bytes (431 words) - 16:59, 3 April 2022
  • Dev:changes/2.3/diff (redirect from CO:changes/2.3/diff)
    - <validFor> - <trackSystem>LS</trackSystem> - </validFor> - </trainProtectionSystem> - <trainProtectionSystem code="LZB-L72"> - <name /> - <validFor>
    108 KB (9,484 words) - 10:56, 8 October 2021
  • Dev:changes/2.2/diff (redirect from CO:changes/2.2/diff)
    + <validFor> + <trackSystem>LS</trackSystem> + </validFor> + </trainProtectionSystem> + <trainProtectionSystem code="LZB-L72"> + <name /> + <validFor>
    331 KB (27,016 words) - 10:56, 8 October 2021
  • Dev:changes/2.2 (redirect from CO:changes/2.2)
    can be used in order to state, whether a certain <speedChange> shall be valid for a train or not. Therefore, a <speedProfile> is referenced from a <speedChange>
    36 KB (103 words) - 13:54, 21 February 2022
  • CO:vehicleSystem
    <vehicleSystem>   Parent: <validFor> Children: None [1..1] train protection system code of the according vehicle system restriction of xs:string with pattern
    293 bytes (56 words) - 20:36, 15 February 2018
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki2.railml.org/wiki/Special:Search"