| Re: Introduction of TAF-TSI PrimaryLocationCode as reference [message #556 is a reply to message #555] |
Mon, 26 May 2014 12:19   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Stefan,
thank you for your remarks, which I want to comment on:
Am 14.05.2014 14:54, schrieb Stefan Jugelt:
> Dear all,
>
> as proposed during the railML-conference in Braunschweig, I would suggest
> some changes for railML to incorporate requirements from the telematics
> appplications for passengers and freight (TAF/TAP TSI).
>
> 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>
I added the proposed entry in Registers.xml and gave it the code "PLC".
Please have a look at the latest version of railML SVN directory trunk
and give me a feedback.
> Maybe in the future addtional items shall be add to this register:
> - codes for tariff purposes (e.g. company specific coding of tariff
> points for NRT-fares, formerly known as TCV fares, company specific code
> for IRT-fares)
> - reservation code
>
> I would suggest to add them, if the outcome of the current discussion in
> TAF/TAP TSI about the retail refernece data - used for timetabling
> information for the passenger, tariff data exchange and reservation
> messages - is mature enough to be incorporated in railML.
Ok, I'll wait for your suggestions at the end of the current discussion.
Thank you!
[1] https://trac.railml.org/ticket/252
Best regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
