Timetable heading (de: Fahrplanüberschrift)

A heading would be nice for the tabular as well as for the graphic timetable viewer.

Typically the heading highlights large stations for the shown route. The start and end station would be the minimum.

railML does not provide a general string for this case, therefore the following selection is proposed.

1. Take the chosen train, nevertheless it's an operational (graphic timetable) or a commercial (tabular timetable) train. In both cases trains around this chosen train will be shown, but they are not considered for the heading.
2. Print train/@name if available.
3. Otherwise, print train/@description if available.
4. Otherwise, print start and end station:

ocp[@id = trainPart[@id = train/trainPartSequence[1]/trainPartRef[1]/@ref]/ocpsTT/ocpTT[1]/@ocpRef]/@name and

ocp[@id = trainPart[@id = train/trainPartSequence[last()]/trainPartRef[last()]/@ref]/ocpsTT/ocpTT[last()]/@ocpRef]/@name

At the railML-timetable-workgroup-meeting (2015-03-16, Vienna) other developers proposed to discard train/@name and train/@description because of free text input by the software user.

The name of the "master train" may not reflect the other trains, which are shown together with this "master train".

Therefore train/@name and train/@description should be skipped from the timetable header. Only start and end (4th item of the list above) should be shown.

By Deleted User on 2015-03-25T16:40:54 (imported from GitLab)

• Milestone changed from %"4. Meeting" to %"next meeting"

The "master train" is used in the heading of the tabular and the graphical timetable. It is skipped from the back direction tabular timetable.

It may be agreed on this implementation.

By Deleted User on 2015-04-09T11:48:58 (imported from GitLab)

• Resolution set to fixed
• Status changed from new to closed

By Deleted User on 2015-05-05T16:51:12 (imported from GitLab)

• Milestone %"next meeting" deleted

implemented as writen above. agreed on project meeting.

By Deleted User on 2015-05-07T10:56:57 (imported from GitLab)

mentioned in issue #42