Extension of time reference in (de: Erweiterung des Zeitbezugs in Element )

Description

The current implementation of is missing a clear time reference. So far, it is only possible to use attribute @operatingPeriodRef to link from a state to an operating period. Main problem: it is not possible to model exact times for begin and end of a time span.

Task: Find a better solution for implementing explicit time reference in .

Background

Time aspects linked with have an explicit timetable focus. The intended use in infrastructure domain would require a modification of the existing time concept (extension with hours, minutes and seconds). In order not to mix data model requirements, it is suggested to create a purely IS solution.

Links

• Forum discussion
  • Milan Wölke, 19.03.2018: https://www.railml.org/forum/index.php?t=msg&th=559&start=0&
• Trac ticket
  • #329
• Wiki documentation
  • railML 2: IS:state: https://wiki2.railml.org/wiki/IS:state
  • railML 3: IS:infrastructureState: https://wiki3.railml.org/wiki/IS:infrastructureState

Proposed solution in railML 2.4

Let's have a look at quite a simple example:

<track id="trc01" ...>
  <states>
    <state disabled="true" operatingPeriodRef="opp01" startTime="22:00:00" endTime="06:00:00" endDayOffset="1"/>
  </states>
</track>

The track "trc01" is blocked from 28.04.2018, 22:00h CEST, until 29.04.2018, 06:00h CET. The state defines the time and the "offset" to correctly calculate the duration of the blocking. The referenced operating period defines the dates (xs:date) for the blocking.

In parallel to the infrastructure scheme extension the operating period concept need to be adapted: the attributes @startTime and @endTime shall be marked DEPRECATED since they cannot be used from practical perspective.

Proposed solution in railML 3.x

In railML 3.x the implementation shall be adapted: time aspects have to modelled intependently from infrastructure and timetable domain in order to ensure generic usaage.