Home » railML newsgroups » railml.timetable » @categoryPriority of <category> to be declared deprecated in version 2.5
Re: @categoryPriority of <category> to be declared deprecated in version 2.5 [message #2289 is a reply to message #2284] Mon, 09 December 2019 13:56 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 139
Registered: April 2007
Senior Member
Hi Janne,
thanks for your feedback and welcome to the community. Can you please outline the usecase for your intended use of these priorities? You mentioned simulation, could you provide some detail so we can better understand what you need to do. Maybe there is a better way of modelling this, after all the @categoryPriority is just a string...

Thanks in advance.

Best regards, Milan


Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Continuation: different stop types / Mehrere Betriebshalt-Haltegründe usw.
Next Topic: [railML2] Usage of //ocpTT/times/@scope
Goto Forum:
  


Current Time: Sun May 05 02:26:40 CEST 2024