Home » railML newsgroups » railml.timetable » [railML3] Suggested change for railML 3.3 Timetable regarding times at passing points
Re: [railML3] Suggested change for railML 3.3 Timetable regarding times at passing points [message #3235 is a reply to message #3214] Mon, 29 April 2024 10:24 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 79
Registered: March 2015
Member
Hello Milan,

I think your suggestion is an improvement to the schema. As there are already different sub-elements for stops and pass throughs, we can also use these for a specialised representation of times. I'm still considering whether it would make sense to rename the element for passages from "departure" to "pass" (or similar), but that wouldn't make much difference.

I also share your concerns that we will temporarily have the old and the new solution in parallel in the schema due to the change rules between railML versions. But in my opinion, this is a general problem of the change rules, which we will have in future with all changes to existing attributes/elements. So I think that this issue should not play a role if we have to decide in favour of or against a specific change in the scheme.

Best Regards
Christian

--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: [railML2] Adding the RouteId to the TafTapTsiTrainID
Next Topic: [railML3] Request for feedback on changes of our deprecation policy
Goto Forum:
  

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

Current Time: Thu May 08 05:53:42 CEST 2025