Home » railML newsgroups » railml.rollingstock » [railML2] extend <vehicle> with the <designator> element (<vehicle> <designator>)
[railML2] extend <vehicle> with the <designator> element [message #2484] Fri, 03 July 2020 13:52
Torben Brand is currently offline  Torben Brand
Messages: 92
Registered: March 2016
Member
Jernbanedirektoratet suggests to extend the elements under <vehicle> with the <designator> element in version 2.5.

The reason is many different code lists exists. These overlap and are not consistent. We need to be able to reference to the register used for the entry value for unique identifying specific vehicles in external registers.

In Europe the European vehicle number (EVN first 8 digits) could uniquely define a type of vehicle.

Examples of registers are:
National registers ( https://sjt.no/jernbane/tillatelser/kjoretoy/nasjonalt-koyre toyregister-snvr/oppbygging-av-evn-for-trekkraftkjoretoy-sif fer-5-8/)
https://sjt.no/jernbane/tillatelser/kjoretoy/nasjonalt-koyre toyregister-snvr/access-to-the-nvr-register/
EVR https://www.era.europa.eu/registers_en#evr
ECVVR https://www.era.europa.eu/registers_en#ecvvr
Organisational registers

The extension might need to take its relation to <classification> into consideration.
Examples of registers here are:
UIC RICS (https://uic.org/support-activities/it/rics)
ERA OCR (https://www.era.europa.eu/registers/ocr_en)
ERA TAF/TAP Company code (https://teleref.era.europa.eu/)
Vehicle keeper Marking Register (VKM) (https://www.era.europa.eu/registers/vkm_en)

This is already implemented in railML3.
Previous Topic: Different ways to model tractive effort
Next Topic: Infrastructure data for a train path finding tool
Goto Forum:
  


Current Time: Wed Aug 12 13:31:18 CEST 2020