Home » railML newsgroups » railml.timetable » Extension suggestion for alternativeSectionTT (railML2, railML2.5, railML3 dev suggestion, nor:alternativeSectionTT)
Re: Extension suggestion for alternativeSectionTT [message #2388 is a reply to message #2337] Tue, 10 March 2020 15:14 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 145
Registered: April 2007
Senior Member
Hi Torben,

thanks for your input. I have put this topic on the agenda for the next TT developer group telco. One question in advance though, why create a new element for this at all. Shouldnt it already be enough to change the cardinalities of sectionTT and extend it with the priority. Like this we dont need the semantic constraint and it should still be semantically clear.

Best regards, Milan

Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
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:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Sep 16 15:43:40 CEST 2024