Home » railML newsgroups » railml.timetable » Extension suggestion for alternativeSectionTT (railML2, railML2.5, railML3 dev suggestion, nor:alternativeSectionTT)
Extension suggestion for alternativeSectionTT [message #2337] Thu, 20 February 2020 13:03 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 156
Registered: March 2016
Senior Member
Dear TT community,

For the use case TT:LongTermStrategicTimetabling, TT:ATimetableForACompetition, TT:SlotOrdering we would like to indicate the alternative paths to be available for a train or pattern/template train of a train group to be used if the planned path is not available. This being in a simulation, short term scheduling, dispatching decisions or data preparation for long term planning.

We suggest adding an extension in railML2.4 for Norwegian sector purposes, and if the community thinks this is beneficial to add the new element in railML2.5.

The proposed solution is to copy the element <sectionTT> with all attributes and sub elements, with the new name <nor:alternativeSectionTT>. Placement would be parallel to <sectionTT under <ocpTT>.
We will add one extra attribute @rank to indicate the rank between the different elemnts, if more than one <nor:alternativeSectionTT>.
For info on @rank see separate forum posting: https://www.railml.org/forum/index.php?t=msg&th=691& goto=2332&#msg_2332
nor:alternativeSectionTT@rank has a semantic constraint of the value 2 or higher. This as <sectionTT> is always @rank="1".

What does the community think?

[Updated on: Thu, 20 February 2020 13:06]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Attribute processStatus to be declared deprecated for <train>, <trainPart> and <trainGroup>
Next Topic: [railML2] Extension proposal: Stopping point reference for elements not of type <stopPost>
Goto Forum:
  


Current Time: Fri Apr 19 08:53:55 CEST 2024