Dev:TrainProtectionSystems: Difference between revisions
[checked revision] | [checked revision] |
({{under construction|user=~~~~}}) |
(Streamlined) |
||
Line 1: | Line 1: | ||
{{under construction|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 15:03, 9 January 2018 (CET)}} | {{under construction|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk: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 [[Dev:Downloading and using railML|{{rml}} 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 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 [[CO:Codelists|here]]. | |||
==Specification== | |||
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. | The list containes [https://en.wikipedia.org/wiki/Train_protection_system train protection systems]. It provides two container elements for track bound systems and train bound systems respectively: | ||
===At track=== | |||
Moreover, the separation of schema and codelists allows actualizing the codelists in very short cycles | |||
== | |||
*<trainProtectionSystemsAtTrack>: Container for train protection systems, installed "at the track" | *<trainProtectionSystemsAtTrack>: Container for train protection systems, installed "at the track" | ||
**<trainProtectionSystem>: Single entries for each train protection system, installed "at track" | **<trainProtectionSystem>: Single entries for each train protection system, installed "at track" | ||
Line 86: | Line 23: | ||
</trainProtectionSystem> | </trainProtectionSystem> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
===On Vehicle=== | |||
*<trainProtectionSystemsOnVehicle>: Container for train protection systems, installed "on the vehicle" | *<trainProtectionSystemsOnVehicle>: Container for train protection systems, installed "on the vehicle" | ||
**<trainProtectionSystem>: Single entries for each train protection system, installed "on vehicle" | **<trainProtectionSystem>: Single entries for each train protection system, installed "on vehicle" | ||
Line 104: | Line 41: | ||
</trainProtectionSystem> | </trainProtectionSystem> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==Affected Elements== | |||
Currently the codelist InfrastructureManagers.XML can be called from three elements: | |||
{{missing information|topic=the elements calling this codelist|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 19:42, 9 January 2018 (CET)}} | |||
==Current entries== | |||
As of January 2018, the following Systems are listed: | |||
===At Track=== | |||
{|class="wikitable sortable" | |||
!{{rml}} Code | |||
!Name | |||
!ValidFor | |||
!URL | |||
!Contact | |||
|- | |||
|} | |||
===On Vehicle=== | |||
{|class="wikitable sortable" | |||
!{{rml}} Code | |||
!Name | |||
!ValidFor | |||
!URL | |||
!Contact | |||
|- | |||
|} | |||
Are you missing an entry? The procedure to extend the list is explained [[CO:Codelists#Missing_entries|here]]. | |||
[[category:Common Concept]] | [[category:Common Concept]] |
Revision as of 20:42, 9 January 2018
|
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.
- <trainProtectionSystem>: Single entries for each train protection system, installed "at track"
- 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.
- <trainProtectionSystem>: Single entries for each train protection system, installed "on vehicle"
- 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:
|
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.