Search results

Jump to navigation Jump to search
  • Dev:Identities (category Error)
    Very many railML® elements require an id attribute of the W3C-Type xs:ID. This has to be provided in order to enable references, that are very much used
    5 KB (463 words) - 11:22, 3 November 2023
  • collection of signals applicable for emergency stop command errors: control of element error indicators fireAlarm: control of a collection of fire detectors
    519 bytes (38 words) - 15:16, 5 March 2021
  • Structuring Guidelines for Element Pages   This page explains, how to structure an element documentation page within The railML® 3 wiki. A General outline
    5 KB (653 words) - 15:05, 3 April 2023
  • specifying technical installations to ensure safe operation in the event of human error. Subschema infrastructure Parents* trainProtectionElements Children areaLocation
    1 KB (70 words) - 10:41, 30 January 2024
  • restriction sections), Planning of the required maintenance measures (defect type, error degree, date of report), Operational planning of the rail examination trains
    4 KB (354 words) - 15:37, 4 December 2023
  • TT:PreliminaryDocumentation (category Error)
    This is the page for the preliminary documentation of railML® 3.2 Timetable scheme concepts. all <operationalTrainSectionPart> elements referenced by one
    1 KB (97 words) - 06:08, 13 June 2020
  • specifying technical installations to ensure safe operation in the event of human error. Subschema infrastructure Parents* trainProtectionElements Children areaLocation
    3 KB (5 words) - 11:41, 8 February 2024
  • the mileages of the element-ends with consideration of error profile data. According to the error profile data lengths at certain mileage values are added
    4 KB (571 words) - 12:51, 13 March 2023
  • collection of signals applicable for emergency stop command errors: control of element error indicators fireAlarm: control of a collection of fire detectors
    3 KB (5 words) - 11:41, 8 February 2024
  • entities with a single code, as to avoid repetitious work as well as ambiguity errors. For instance in railML® 2, using <infrastructureManager>, you can address
    6 KB (797 words) - 11:50, 29 November 2023
  • entities with a single code, as to avoid repetitious work as well as ambiguity errors. Moreover, the separation of schema and codelists allows actualizing the
    13 KB (721 words) - 13:12, 9 October 2023
  • entities with a single code, as to avoid repetitious work as well as ambiguity errors. Moreover, the separation of schema and codelists allows actualizing the
    11 KB (422 words) - 14:50, 16 November 2022
  • entities with a single code, as to avoid repetitious work as well as ambiguity errors. Moreover, the separation of schema and codelists allows actualizing the
    6 KB (294 words) - 13:03, 7 December 2023
  • entities with a single code, as to avoid repetitious work as well as ambiguity errors. The concept is explained here. The list contains infrastructure managing
    17 KB (299 words) - 14:10, 7 December 2023
  • Validate the code (XSD-files) and examples (XML-files) together. Correct all errors before committing. Make sure that newly added files are committed. If they
    8 KB (1,082 words) - 12:18, 26 July 2023
  • required data regarding certain aspects. static (not changing) in cases of error-corrections: weekly .. daily in rare cases during a short period (of submission);
    16 KB (1,903 words) - 12:27, 13 March 2023
  • the data from paper into the supplier’s tool chain is likely to introduce errors that must be found and corrected by testing. Automated exchange and conversion
    11 KB (828 words) - 12:25, 13 March 2023