Home » railML newsgroups » railML.infrastructure » Introduction of TAF-TSI PrimaryLocationCode as reference
Re: Introduction of TAF-TSI PrimaryLocationCode as reference [message #1247 is a reply to message #1233] Wed, 11 February 2015 10:01 Go to previous message
Stefan Jugelt is currently offline  Stefan Jugelt
Messages: 3
Registered: May 2014
Junior Member
Christian Rahmig wrote:
>
> Dear everyone,
>
>> Am 14.05.2014 14:54, schrieb Stefan Jugelt:
>>>
>>> 1. The element "tsi" in operationalControlPoints/ocp/ and the type
>>> "tOcpTsi" shall be marked as deprecated and removed in further
>>> versions of
>>> railML. These elements dedicated for the usage in conjunction with TAP
>>> TSI
>>> shall be replced by a more generic approach as proposed in bullet
>>> point 2.
>>
>> I opened a ticket addressing that issue [1]. If agreed by the users, the
>> marking can be realized with the next railML version.
>>
>>> 2. The file Registers.xml shall be extended by an addtional entry:
>>>
>>> <register code="PrimaryLocationCode">
>>> <name>Primary location code for the TAF/TAP TSI, stored in the
>>> central
>>> reference database</name>
>>> <organization xml:lang="en">CRD</organization>
>>> <remarks xml:lang="en">Used for the communication between the
>>> railway
>>> undertaking and the infrastructure manager. format: country code as
>>> ISO-3366-1 + 5 digits</remarks>
>>> </register>
>>
>> [1] https://trac.railml.org/ticket/252
>
> The modifications described here and in ticket #252 have been
> implemented with SVN revision 611.
>
> Best regards
>

Dear Christian,

I agree with the change.

Best regards,

Stefan Jugelt

--
----== posted via PHP Headliner ==----
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: odometry, pos and absPos
Next Topic: train protection systems
Goto Forum:
  


Current Time: Sat May 04 15:15:02 CEST 2024