Home » railML newsgroups » railml.interlocking » [railML3.2] dublicate element name itinerary
[railML3.2] dublicate element name itinerary [message #2878] Mon, 17 January 2022 13:51
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 89
Registered: March 2016
Dear all,

when the development of interlocking schema started there was the request to
have list of sequential routes for train to navigate the railway network.
However, such list is needed in the timetable and the interlocking domain. At
that time no timetable development for railML3 was active. Thus no one did
intervene, when the element name "itinerary" was used in interlocking provoking
the later conflict with timetable.

In mutual discussions we found the name "itinerary" more suitable in the
timetable domain. Therefore the need of element renaming in existing
interlocking schema arose. The decision was to rename "itineraries"/"itinerary"
in Controller element to "routeSequences"/"routeSequence".

If someone has arguments against this renaming, please, respond to this post.

Best regards,
Joerg v. Lingen - Interlocking Coordinator
Read Message
Previous Topic: railML 3.2: Overlap/flank protection variants
Next Topic: [railML3]: special infrastructure in IL - bascule bridge, tunnel gates
Goto Forum:

Current Time: Thu Jul 25 07:44:46 CEST 2024