TT:operatingDayDeviance

operatingDayDeviance
 

Scheme description / Schemenbeschreibung

Position of operatingDayDeviance in the XML-Tree / Position von operatingDayDeviance im XML-Baum

• Parent: <operatingDay>
• Children: None

Multiplicity / Anzahl

[0..∞]

Semantics / Bedeutung

The Element operatingDayDeviance describes the operation modifications of the standard week described in operatingDay. This description is also week based but also related to public holidays. Each element operatingDayDeviance characterizes a set of days (e.g. Mondays and Tuesdays on a days before a public Holiday).

Das Element operatingDayDeviance beschreibt die Abweichungen gegenüber der in operatingDay beschriebenen Standardwoche. Dies erfolgt ebenfalls wochentagsbezogen, aber auch im Hinblick auf zeitlich benachbarte Feiertage. Jedes Element operatingDayDeviance charakterisiert dabei eine Menge von Tagen (z.B. alle Montage und Dienstage, die gleichzeitig Vor-Feiertage sind).

Attributes of operatingDayDeviance / Attribute von operatingDayDeviance

• operatingCode: This is a 7-digit week bit mask, describing for Monday to Sunday if a train is driving or not (1/0) on this day of the week. Monday being represented by the first character and Sunday being represented by the 7th character.

• onRequest (introduced with version 2.1) (deprecated with version 2.5): This is needed for "runs Monday to Friday and additionally Sunday on request".

• holidayOffset: Specifies the relation of the day indicated with a 0 or 1 in the operatingCode to a public holiday, e.g. 0 means the day represented by the 1 or 0 represents the holiday, 1 means its the day after a holiday. So if operatingCode is given with "0011100" and holidayOffset is given with 2 then this would mean that this rule would apply for all Wednesday, Thursdays and Fridays. So if a Monday would be a holiday the plus 2 would point to the 3rd character in the bitmask which is a 1 and thus indicate that a train would run. If however a Thursday would be a holiday the plus 2 would point to the 6th character in the bitmask, which would be 0 and indicate no operation.

• ranking: Each <operatingDayDeviance> is to be considered as an instruction on how to overlap the provided bitmasks. The attribute ranking specifies the order in which to perform this overlay.

• xs:anyAttribute: (introduced with version 2.3) This provides an extension point for non-railML^® attributes in a foreign namespace. How to use it?

Syntactic Constraints / Syntaktische Beschränkungen

• operatingCode mandatory

• onRequest xs:boolean, optional

• holidayOffset xs:integer, mandatory

• ranking xs:positiveInteger, optional

Two or more conditions described by elements <operatingDayDeviance> with the same or no ranking have to be fullfilled at the same time. For days which happen to be in two sets with different ranking, the one with the lower rank is the right one.

Best practice & Examples / Empfohlene Anwendung & Beispiele

On Sundays and on public holidays

<operatingPeriod id="op1" name="S">
 <operatingDay operatingCode="0000001"/>
  <operatingDayDeviance operatingCode="1111111" holidayOffset="0"/>
 </operatingDay>
</operatingPeriod>

On Saturdays which are no public holidays and on public holidays before other public holidays

<operatingPeriod id="op2" name="Sa[S] + FvF">
 <operatingDay operatingCode="0000010">
  <operatingDayDeviance operatingCode="0000000" holidayOffset="0" />
 </operatingDay>
 <operatingDay operatingCode="0000000">
  <operatingDayDeviance operatingCode="1111111" holidayOffset="0" ranking="1" />
  <operatingDayDeviance operatingCode="1111111" holidayOffset="-1" ranking="1" />
 </operatingDay>
</operatingPeriod>

see also

• Weitere Informationen und railML^®-Beispiel zu Verkehrstagen (external link, PDF, 🇩🇪, visited on 2018-03-27; by Dirk Bräuer, iRFP Dresden)

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.