| forgotten attribute <operatingPeriod> @dayOffset and its future [message #1602] |
Fri, 09 June 2017 12:02  |
Dirk Bräuer
Messages: 313
Registered: August 2008
|
Senior Member |
|
|
Introduced with railML 2.2, there should be a new attribute @dayOffset at <operatingPeriod>.
It now turned out that this attribute seems simply to have been forgotten.
(The attribute with the same name at <blockPartSequence> is already there since railML 2.0 and therefore no mistake.)
So obviously nobody has missed this attribute and the question arises, whether we should still introduce it and/or transfer it into railML 3.x.
There is a lengthy explanation of this attribute in [1] including several reasons for its introduction. So my suggestion is to introduce @dayOffset at <operatingPeriod> from r2.4 AND transfer it into r3.x.
@Stefan Jugelt: I know several infrastructure managers who do not allow "departureDay=1" at the first <ocp> in their data models. How does ERA deal with this issue? Is there a kind of "dayOffset" in TAP/F TSI, too, or is there "departureDay=1" allowed from the start?
Best regards,
Dirk.
[1] http://wiki.railml.org/index.php?title=TT:Midnight_overrun
|
|
|
|
Members
Search
Help
Login
Home
