| [railML2] New concept LineTT [message #2711] |
Wed, 05 May 2021 13:00  |
Thomas Kabisch
Messages: 8
Registered: September 2020
|
Junior Member |
|
|
Hello everybody,
as a result of the discussions within the TT working group I would like to separately discuss the concept lineTT that is one suggested concept to integrate the requirements of the use case "Passenger Information within trains".
The aim of lineTT is to describe features of a line in the few of passengers such as a specific line designation (e.g. "S1", "Red line"), a specific announcement ("This is a red line train"), a specific symbol for a line, etc.
Each of its attributes need to be expressed in different languages and need to be assigned to specific output devices (such as a specific PIS screen).
The idea is to introduce this concept within the TT subscheme and link it to specific trainparts and/or trains.
Currently, such lines can be expressed only in form of a single string value. Unfortunately this implementation is not sufficient for the needs within the passenger information use cases.
|
|
|
|
| Re: [railML2] New concept LineTT [message #2779 is a reply to message #2711] |
Wed, 30 June 2021 14:33  |
Thomas Nygreen
Messages: 66
Registered: March 2008
|
Member |
|
|
Hello Thomas,
I like the concept, but I think the name "line" is a false friend in this case. As far as I know, what we in Germanic languages call "Linienbezeichnung", "linjenummer" etc. is in English a "service code" or "service number", and multiple (train) services can be operating on a railway line. Unfortunately, "service" is a very generic term, already used multiples times in railML, but maybe a composition such as "serviceCode" may work.
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
[Updated on: Wed, 30 June 2021 16:09] Report message to a moderator |
|
|
|
| Re: [railML2] New concept LineTT [message #2823 is a reply to message #2779] |
Tue, 07 September 2021 15:10 |
Milan Wölke
Messages: 139
Registered: April 2007
|
Senior Member |
|
|
Hi,
I think since we have been using that name for this in railML 2.x for a long time we should not change it here. You are right, Thomas N., but introducing a serviceTT besides a line attribute, that we still need to support due to our compatibility policy would do more harm than help.
However I think this is valuable input for railML 3 where we were about to make the same mistake again.
Best regards, Milan
Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
