Re: Mapping of code and abbreviation for ocps [message #779 is a reply to message #763] |
Fri, 27 April 2012 17:26 ![Go to previous message Go to previous message](/forum/theme/default/images/up.png) ![Go to next message Go to previous message](/forum/theme/default/images/down.png) |
Susanne Wunsch railML
Messages: 0 Registered: January 2020
|
|
|
|
Hello Dirk and others interested,
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
> We now intend to allow a kind of enumeration of two-valued elements
> (elements with two attributes) per station. Each one can handle one
> external primary key of the station, which may be either a string
> (abbreviation) or a number.
<ocp id="" name="" code="" description="">
<additionalCode register="" value=""/>
...
</ocp>
Is there any globally unique code for any kind of railway locations?
This could be fixed for the general "code" attribute. Otherwise it
would be better to leave this attribute absent and require the
definition of the "register" together with the code "value".
UIC manages the ENEE database. [1]
I don't have any access to the UIC leaflet 920. Does these location
codes serve as additional keys to the well-known
country/company-specific ones? Or does the UIC offer a really unique
code for each location?
The "register" values should be pre-defined by enumeration values. It
may be extended without changing the XML schemas.
> I herewith apply for the following 'registers' to be defined from the
> very beginning:
> - 'DS100' for the German "Betriebsstellenkürzel" (referring to the
> former "Dienstvorschrift"; I would not agree with "Richtlinie" since
> it is not a recommendation to use them but a directive!)
> - 'DB640' which is the Austrian pendent to DS100 (DB="Dienstbehelf" -
> has nothing to do with Deutsche Bahn nor Dirk Bräuer).
> - 'EFA' for the numbers used in some German public timetable databases
> and some RaiLML-reading programmes (EFA="elektronische
> Fahrplanauskunft" - or however they are called officially - Vasco
> know how).
Good starting point. Thanks.
The "value" should be a pure xs:string, allowing letters, numbers,
spaces, underscores, slashes, dashes, points and so on.
[1] http://www.uic.org/spip.php?article378
--
Kind regards...
Susanne
|
|
|