Dev:TrainProtectionSystems

From railML 2 Wiki
Revision as of 19:42, 9 January 2018 by RailML Coord Documentation (talk | contribs) (Streamlined)
Jump to navigation Jump to search
UnderConstruction.png This page is under construction. Sorry for temporary problems. See the discussion page to find a summary of the tasks and to coordinate the work on this page. Recognize that the content of this page may change quickly. Ferri Leberl (talk) 15:03, 9 January 2018 (CET)

The codelist TrainProtectionSystems comprises of train protection systems. It provides two container elements for track bound systems and train bound systems respectively. Your railML® download will usually contain the codelists in a directory codelists, next to documentation and schema. As As the codelists have shorter cycles than railML® versions have you might want to get the current list from https://svn.railml.org/railML2/trunk/codelists.

The code lists are intended to address certain frequently used 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 codelists in very short cycles. The concept of codelists is explained here.

Specification

The list containes train protection systems. It provides two container elements for track bound systems and train bound systems respectively:

At track

  • <trainProtectionSystemsAtTrack>: Container for train protection systems, installed "at the track"
    • <trainProtectionSystem>: Single entries for each train protection system, installed "at track"
      • code: A code that should be referred to from within an railML file, typically a short name for the train protection system in latin letters.
      • <name>: Name of the system.
      • <validFor>: If the code for the system differs between vehicle and track installation, put the mapping in this container element.
        • <vehicleSystem>: Train protection system code of the according vehicle system.
Example entry
<trainProtectionSystem code="Crocodile">
 <name/>
 <validFor>
  <vehicleSystem>Crocodile</vehicleSystem>
  <vehicleSystem>Memor</vehicleSystem>
  <vehicleSystem>Memor2</vehicleSystem>
 </validFor>
</trainProtectionSystem>

On Vehicle

  • <trainProtectionSystemsOnVehicle>: Container for train protection systems, installed "on the vehicle"
    • <trainProtectionSystem>: Single entries for each train protection system, installed "on vehicle"
      • code: A code, that should be referred to from within an railML file, typically a short name for the train protection system in latin letters.
      • <name>: Name of the system.
      • <validFor>: If the code for the system differs between vehicle and track installation, put the mapping in this container element.
        • <trackSystem>: Train protection system code of the according track system.
Example entry
<trainProtectionSystem code="CIR-ELKE2">
 <name/>
 <validFor>
  <trackSystem>LZB</trackSystem>
  <trackSystem>CIR-ELKE</trackSystem>
  <trackSystem>CIR-ELKE2</trackSystem>
 </validFor>
</trainProtectionSystem>

Affected Elements

Currently the codelist InfrastructureManagers.XML can be called from three elements:

Missinginformation.png In this article there is information missing with respect to the elements calling this codelist. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion pageFerri Leberl (talk) 19:42, 9 January 2018 (CET)

Current entries

As of January 2018, the following Systems are listed:

At Track

railML® Code Name ValidFor URL Contact

On Vehicle

railML® Code Name ValidFor URL Contact

Are you missing an entry? The procedure to extend the list is explained here.