Topology reference dates (de: Topologie Stichtage)

Description

It shall be possible to specify so called topology reference dates for a train. Such a reference specifies the corresponding topoology that the receiving system shall use for the train for a particular timeframe.

Suggested change:

• final discussion is taking place during the development phone confereneces

Background

The topology reference is similar to the designator register for an ocp which allows the receiving system to retrieve additional information from an external register.

Please note, that the actual topology is not part of the railML file and must exist in or be accessible to the receiving system.

Links

• Forum discussion
• Mićo Mićić (SBB) (de/en), November 2016: Mehrere Topologie-Stichtage pro Trasse angeben / Specify multiple topology reference dates per train
• Wiki Documentation
• TT:topologyReference (NEW)
• Dev:Registers (Updated)
• TT:trainPartSequence (Needs to be updated when 2.4 is released)

Changes in railML 2.4

A cancelled train or trainPart is written to the railML file including all regular attributes and elements. The @NEWATTRIBTE attribute with a value of 'true' allows the importing system to process this information accordingly - e.g. to inform passengers of a cancellation.

railML elements

The following new attributes are available:

1. railml/timetable/trains/train/trainPartSequence/topologyReference
2. railml/timetable/trains/train/trainPartSequence/topologyReference/@register
3. railml/timetable/trains/train/trainPartSequence/topologyReference/@entry
4. railml/timetable/trains/train/trainPartSequence/topologyReference/@startDate
5. railml/timetable/trains/train/trainPartSequence/topologyReference/@endDate
6. railml/timetable/trains/train/trainPartSequence/topologyReference/@any##other The following XSD file(s) have been updated:
7. timetable.xsd
8. timetableTypes.xsd The following codelist XML file(s) have benn updated:
9. Registers.xml

Development Branch

In order to facilitate the development a branch of railML 2.3 called 'topology-reference' was created - all ongoing development work for this ticket is done in this branch:

• railML/railML2/branches/topology-reference topology-reference

Changesets in branch

• [changeset:"692/railML"] - Branch used for the first proposal
• [changeset:"693/railML"] - First proposal
• [changeset:"745/railML"] - Created topology register files. Changed topology reference element by definition from the timetable developer meeting of 23th March 2017 in Bern.
• [changeset:"760/railML"] - The topology reference is defined by the attribute "entry" and not the attribute "tag". Attribute renamed as decided at the timetable developer telco on 20.11.2017.
• [changeset:"764/railML"] - As decided at the telco of 18 December 2017: All topology registers should be described in the existing Registers.xml file.
• [changeset:"765/railML"] - Use same naming for "register" attribute as already defined for the ocp designator element.
• [changeset:"766/railML"] - Fixed mismatch between documentation and xsd implementation regarding the start and end date definition.

Changesets in trunk

• [changeset:"777/railML"] - Merged changes from branches\topology-reference: New element added to , closes #306 (closed)

### Documentation Tasks
* Document the changes for 2.4
* Update the wiki pages for the Registers.xml