| Extension suggestion for <upTime> [message #2330] |
Mon, 17 February 2020 15:06  |
Torben Brand
Messages: 157
Registered: March 2016
|
Senior Member |
|
|
Dear railML-community,
For the Norwegian railway sector, we are looking for a way to model an ocp, that is unmanned on certain timely restrictions. The restrictions we would like to model are specific days, for example Saturdays or public holidays.
The element <upTime> (https://wiki2.railml.org/index.php?title=IS:uptime) makes it possible to state that an ocp is unmanned with @mode="unmanned". But it doesn't give us the possibility to restrict this property to certain days, but only certain times in a day with @from and @until.
The element <propOther/states/state> on the other hand would give us the option to refer to an operating period via @operatingPeriodRef and thus makes it possible to model restrictions for certain days (in the sub element <operatingDay>).
We would like to propose a solution to extend the element <upTime> with the time attributes of <state>: @operatingPeriodRef and @endDayOffset. The existing attributes @from and @until seem to be semantically equivalent to @startTime and @endTime. So, we suggest keeping them as is, but to change their semantic constraint from mandatory to optional.
Furthermore, we are looking for a description of the value "off" in <upTime>@mode. What does this value stand for?
What does the community think?
|
|
|
|
Members
Search
Help
Login
Home
