Home » railML newsgroups » railml.timetable » @categoryPriority of <category> to be declared deprecated in version 2.5
Re: @categoryPriority of <category> in version 2.5 / Extension of train part [message #2472 is a reply to message #2414] Fri, 26 June 2020 13:38 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 139
Registered: April 2007
Senior Member
Hi all,

I wanted to update the comunity on what happend regarding this topic; After the last post we discussed this in the TT-developer group. We came to the conclusion that since there actually is usage we will not deprecate this attribute. However we decided that we improve the wiki documentation by adding a best practice description (https://wiki2.railml.org/index.php?title=TT:category). There will be no change to the xsd regarding this issue (thus no trac ticket).

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
Previous Topic: Continuation: different stop types / Mehrere Betriebshalt-Haltegründe usw.
Next Topic: [railML2] Usage of //ocpTT/times/@scope
Goto Forum:
  

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

Current Time: Sun May 05 10:08:30 CEST 2024