| Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod [message #1772 is a reply to message #1754] |
Mon, 23 April 2018 14:51   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
may I briefly summarize the solution that we agreed on in Berlin last
week with a short example:
<infrastructure ...>
<track ...>
<states>
<state disabled="true" operatingPeriodRef="opp01"
startTime="22:00:00" endTime="06:00:00" endDayOffset="1"/>
</states>
...
</track>
</infrastructure>
<timetable ...>
<operatingPeriods>
<operatingPeriod id="opp01" startDate="2018-04-28"
endDate="2018-04-29"/>
</operatingPeriods>
</timetable>
This example describes the (non-repeating) closing of the track from
Saturday, 10 pm, to Sunday, 6 am.
Any comments from your side?
Best regards
Christian
Am 09.04.2018 um 12:25 schrieb Philip Wobst:
> Dear all,
>
> this topic has been posted in the forum in order to obtain
> feedback from the community. However, there has been no
> feedback so far. Please provide this feedback as the next
> steps for an implementation in railML 2.4 would need to take
> place within the next two weeks.
> Please let us know if 1. you prefer a specific scenario for your use
> case and why
> 2. both scenarios would work for your use cases
> 3. this does not apply for your use cases and you have no
> preferences
>
> Best regards,
>
> Philip Wobst
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
