Search results
Jump to navigation
Jump to search
- CO:speedProfile (category Missing Element Documentation/CO)which the speed limit given by a speedSection element shall be valid. A speed profile valid for ETCS can be (among others): according to UNISIG SUBSET-02619 KB (2,085 words) - 21:02, 15 January 2024
- appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:validityTime> that might have replaced515 bytes (58 words) - 18:46, 19 December 2019
- RAILML:railML (redirect from CO:railml)supported railML version should be declared for software compatibility reasons, valid for all subschemas, don't mix railML versions between subschemas in one XML513 bytes (4 words) - 18:40, 19 December 2019
- generic subschema. It is available only in railML® 3.2. There exists an element <CO:name> that might have preceded it. Do not hesitate to contact railML.org for512 bytes (58 words) - 12:39, 8 February 2024
- The children have changed. The attributes have been changed. A speed limit valid for a speed section is presented in railML® by a speedSection element. The2 KB (250 words) - 18:16, 15 January 2024
- subschema. It is available only in railML® 3.2. There exists an element <CO:validityTime> that might have preceded it. Do not hesitate to contact railML.org520 bytes (58 words) - 12:41, 8 February 2024
- appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:validForSpeedProfile> that might have652 bytes (78 words) - 13:57, 27 October 2023
- CO:screenPositioningSystem (category Missing Element Documentation/CO)Autoexport from the XML-Schema for element CO:screenPositioningSystem of railML® version 3.2 UML-visualization of CO Documentation This element is not documented526 bytes (9 words) - 18:40, 19 December 2019
- CO:trainType (category Missing Element Documentation/CO)Autoexport from the XML-Schema for element CO:trainType of railML® version 3.2 UML-visualization of CO Documentation a speedProfile can be linked with512 bytes (15 words) - 18:40, 19 December 2019
- infrastructure and consequently shall be modelled in the <common> domain: <common id="co_01"> <positioning> ... </positioning> </common> The railway network topology11 KB (1,110 words) - 09:59, 29 April 2024
- CO:validityTime:period (category Missing Element Documentation/CO)This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® . Do not hesitate to contact railML.org for further759 bytes (36 words) - 13:44, 18 April 2024
- exists an element <CO:bitmaskValidity> that might have preceded it. In contrast to the operatingPeriod in railML 2 the <bitmaskValidity>'s bitmask does not1 KB (161 words) - 16:02, 7 March 2024
- CO:periodGeneric (category Missing Element Documentation/CO)This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:periodGeneric>516 bytes (58 words) - 18:46, 19 December 2019
- This element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further513 bytes (38 words) - 21:49, 25 April 2022
- contact railML.org so that it can be easily added to the code list. <common id="co_01"> <organizationalUnits> <infrastructureManager id="im_01" code="SZDC"/>9 KB (873 words) - 14:24, 11 April 2024
- CO:periodBitmask (category Missing Element Documentation/CO)This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:periodBitmask>516 bytes (58 words) - 18:46, 19 December 2019
- generic subschema. It is available only in railML® 3.2. There exists an element <CO:periodBitmask> that might have preceded it. Do not hesitate to contact railML521 bytes (58 words) - 12:41, 8 February 2024
- This element does not appear in railML® 3.1 within the CO subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further510 bytes (38 words) - 21:49, 25 April 2022
- generic subschema. It is available only in railML® 3.2. There exists an element <CO:weekDayPeriod> that might have preceded it. Do not hesitate to contact railML521 bytes (58 words) - 12:41, 8 February 2024
- subschema. It is available only in railML® 3.2. There exists an element <CO:validForSpeedProfile> that might have preceded it. Do not hesitate to contact528 bytes (58 words) - 12:40, 8 February 2024