Home » railML newsgroups » railml.timetable » @onRequest of <operatingDay> to be declared deprecated
@onRequest of <operatingDay> to be declared deprecated [message #2279] Thu, 28 November 2019 14:58
Milan Wölke is currently offline  Milan Wölke
Messages: 33
Registered: April 2007
Member
Hi,

in der heutigen Timetable Developer Telco wurde im Rahmen der Diskussion zur Abbildung von Bedarfszügen in railML entschieden, dass das Attribut @onRequest am Element <operatingDay> ab der Version 2.5 für deprecated erklärt werden soll. Anstelle dessen soll es wie im Post https://www.railml.org/forum/index.php?t=msg&th=682& start=0& beschrieben, möglich sein am trainPart festzuhalten, dass es sich um einen Bedarfszug handelt. Sollte es Verwendungen des Attributs am <operatingDay> geben, die einem solchen Schritt entgegenstehen, bitte ich euch diese hier zu kommunizieren, damit die Entscheidung gegebenenfalls nochmal überdacht werden kann.

-------------------------------------------------

in today's Timetable Developer Telco, it was decided in the context of the discussion on the modeling of demand trains in railML that the attribute @onRequest at the element <operatingDay> should be declared deprecated from version 2.5 onwards. Instead of this it should be possible, as described in the post https://www.railml.org/forum/index.php?t=msg&th=682& start=0&, to specify on the trainPart that it is an on-demand train. If there should be uses of the attribute on <operatingDay>, which oppose such a step, I ask you kindly to communicate them here, so that the decision can be reconsidered if necessary.

Best regards, Milan


Milan Wölke - Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: Hi! / Timing links
Next Topic: Facultative trains / Bedarfszüge
Goto Forum:
  


Current Time: Mon Mar 30 12:30:00 CEST 2020