Home » railML newsgroups » railml.timetable » Topologie-Stichtag / Topology reference date (Mehrere Topologie-Stichtage pro Trasse angeben / Specify multiple topology reference dates per train)
Re: Topologie-Stichtag / Topology reference date [message #1519 is a reply to message #1517] Thu, 02 March 2017 12:41 Go to previous messageGo to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 47
Registered: November 2013
Location: Hanover, Germany
Member
Hello Mico,

your changes corresponds to the implementation that we discussed in January in Dresden. What we have missed to document is that it is possible to provide more than one reference to the same 'register' if these are limited by startDate/endDate accordingly.
Based on the example in your first post I believe you would provide the application dates for each topology via the startDate/endDate:

<topologyReference topologyRegister="UNO" entry="170101" startDate="2017-01-01" endDate="2017-06-01"/>
<topologyReference topologyRegister="UNO" entry="170601" startDate="2017-06-01"/>


However, looking at this further I have the following question to you and the other TT developers: Is there a use case where this information would change from one trainpartSequence to the next? If not, why not provide this information as a 'train property' instead?

Best regards,

Philip

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: railML 3.x TT: Times vs. Durations in itineraries
Next Topic: Sparx Enterprise Architect for TT modelling?
Goto Forum:
  

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

Current Time: Fri Apr 19 02:59:39 CEST 2024