Re: Mapping of code and abbreviation for ocps [message #780 is a reply to message #779] |
Thu, 17 May 2012 12:49 ![Go to previous message Go to previous message](/forum/theme/default/images/up.png) |
Dirk Bräuer
Messages: 311 Registered: August 2008
|
Senior Member |
|
|
Dear Susanne,
> Is there any globally unique code for any kind of railway locations?
No, surely not.
> 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".
I would prefer the latter, so leaving the attribute 'code' absent.
> UIC manages the ENEE database. [1]
ENEE should be one of the 'register' enumerations but not the 'code'.
> 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?
Even if UIC would try do provide such a word-wide unique code (which they
do not) we should not consider it as a general 'code' for reasons of
universality. RailML shall be usable really universally by internal
structure. Therefor, it should not be forced to UIC territory but also for
Asia, Africa or America. But more important, if you consider that the
following two aspects:
- What in detail will ever be assumed to be an OCP - the general
'stations' or also parts of a station or also block posts and may be also
some virtual location spots?
- RailML shall be usable in any time-relation: Not only with the existing
OCPs/stations but also with future ones (which nobody of UIC knows so far)
and with abandoned ones.
I think that there cannot be a really unique 'code' for all of that and
therefor we should always define the 'register' together with the 'value'
- which is the new principle.
> The "register" values should be pre-defined by enumeration values. It
> may be extended without changing the XML schemas.
Very good.
> The "value" should be a pure xs:string, allowing letters, numbers,
> spaces, underscores, slashes, dashes, points and so on.
Yes, I agree.
Best regards,
Dirk.
|
|
|