Home » railML newsgroups » railML.infrastructure » Fwd: Mapping of code and abbreviation for ocps
Re: Fwd: Mapping of code and abbreviation for ocps [message #357 is a reply to message #315] Sat, 15 September 2012 20:29 Go to previous messageGo to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Hello everyone,

> re-opening the trac ticket #112 (see [1]) we thought about the problem
> of different ocp codes again. We propose a new element <designator> with
> the parameters 'register' and 'entry'. Using this new element, it will
> be possible to address "local" register codes for the same <ocp>.
>
> Example:
> <ocp ...>
> <designator register='IBNR' entry='8509404'/>
> <designator register='DB640' entry='Bc'/>
> <designator register='Ril100' entry='XSBU'/>
> <designator register='DIDOK' entry='BU'/>
> </ocp>
>
> There are also different versions of certain registers, e.g. one for
> each year. An optional attribute for the publishing date may be helpful.
>
> Any comments appreciated...
>
> [1] https://trac.assembla.com/railML/ticket/112

the above proposed solution has been implemented in railML 2.2. The
element <designator> now contains three attributes:
'register' defines a (local) register for an OCP's name/code.
'entry' contains the OCP's name/code in the certain register.
'date' defines the publishing date of the register.

Regards

--
Christian Rahmig
railML.infrastructure coordinator

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: ocp's/stations and their properties
Next Topic: Identical signal representation [de:Gruppenausfahrsignal]
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Jul 23 00:53:30 CEST 2024