Unique train identification (de: Eindeutige Zugnummer)

Description

There shall be a new, optional sub-element for the train for the TAF/TAP TSI train ID used for identification of the objects handled in the messages such as train, path, path request or case refernce.

The new element shall be documented together with the existing elements/attributes for train identification on a separate wiki page.

Background

railML partners declared a need for extension of the railML schemes by forum posts or in the railML conferences. At the last timetable developer meeting in Berlin the following change was decided:  * rail:eTrain shall be modified in such a way to allow an optional TAF/TAP TSI specific train ID element  * create general wiki page for "unique train identification" issues, referenced from the "TT:train" wiki page.

Links

• Forum discussion  * Christian Rößiger (de), October 2015: Protokoll Treffen 2015-0619 Berlin  * Andreas Tanner, January 2013: wiki: missing attribute description for additionalTrainNumber at
• Wiki Documentation
• TT:train  * TT:tafTapTsiTrainID (NEW)
• ERA TAP TSI specification

Changes in railML 2.3

A new attribute has been added to the base type for the places and service. It is limited to a 1-3 digit string corresponding directly to the TAP TSI code value.

railML elements

The following element has been added:  1. timetable/trains/train/tafTapTsiTrainID The following XSD file(s) have been updated:  1. timetable.xsd  1. timetableTypes.xsd

Changesets

 * [changeset:"641/railML"] - added TAF/TAP TSI train ID

• [changeset:"644/railML"] - made StartDate attribute for TAP TSI TrainID optional
• [changeset:"652/railML"] - Added wiki documentation link for tafTapTsiTrainID
• [changeset:"655/railML"] - Updated tafTapTsiTrainID attributes

Documentation Tasks

• Documented the new sub-element for train
• Stefan Jugelt created a wiki page for tafTapTsiTrainID
• Add an actual railML example to the wiki (OPEN)