| Mapping of code and abbreviation for ocps [message #708] |
Thu, 17 March 2011 11:03  |
Simon Heller
Messages: 6
Registered: March 2011
|
Junior Member |
|
|
Hello all,
when adding a code attribute to the <ocp> element, we have to define what
real world information shall become the code and what the abbreviation.
According to the "Technical Specifications for Interoperability" (TSI) of
the UIC (I'm refering to Annex B.9 of TAP TSI: Standard numerical coding
of locations) a railway location is idetified by
- a primary code that consists of
- numerical country code (2 digits)
- railway location number (5 digits)
- check digit (1 digit)
- a unique official location name
- optional additional shortened names
Furthermore we have the letter or letter/number codes known in Germany as
"Betriebsstellenkürzel" that are not only in Germany widely used.
To avoid confusion we should clearly document which railML-attribute is
intended to be used for which identifier. Otherwise we will see in the
railML code attribute letter codes, and 5-, 6-, 7- and 8-digit number
codes, depending on who sent the data.
My view of the issue is that when I hear "code" I immediately think of the
uic code.
So I would map
uic_primary_code (all 8 digits) -> ocp.code
Ortskürzel -> ocp.abbreviation
location name -> ocp.name
Defining the code as the uic code including the county code would make
ticket #112 (attribute for uic country code)redundant.
Two interface partners could still agree on sending only 5 or 6 digits for
national implementations though I woulnd't recommend this (I spent whole
days at one of may old jobs to transform 5-digit interfaces files into
6-digit ones).
Best wishes from Berlin
Simon Heller
IVU Traffic Technologies AG
Bundesallee 88, D-12161 Berlin
Telefon: +49.30.8 59 06-343
mailto:sih(at)ivude, http://www.ivu.de
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
|
|
|
|
Members
Search
Help
Login
Home
