TT:operatingPeriod

operatingPeriod
 

Scheme description / Schemenbeschreibung / Description du schéma

Position of operatingPeriod in the XML-Tree / Position von operatingPeriod im XML-Baum / position de operatingPeriod dans l’aborescence XML

• Parent: <operatingPeriods>

• Children: <additionalName> (introduced with version 2.1), <operatingDay>, <specialService>, <xs:any>

Multiplicity / Anzahl / Multiplicité

[1..∞]

Semantics / Bedeutung / Sémantique

The Element <operatingPeriod> describes the operation of a train. This could either be in relation to certain days of a calendar or abstract based on a standard week (or both).

Das Element <operatingPeriod> beschreibt die Verkehrsperiode eines Zuges. Dies kann entweder im Bezug auf konkrete Kalendertage oder abstrakt über eine wochenbasierte Beschreibung mittels operatingDay erfolgen (oder beides).
 
Please, be aware of the semantic constraint(s)!

Attributes of operatingPeriod / Attribute von operatingPeriod / Attributs de operatingPeriod

• id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
  XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
• code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers.
  Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können. Bitte beachten Sie unsere Erläuterung zu den Unterschieden zwischen id, code and menschenlesbaren Kennzeichnungen.
• name: Established, human-readable short string, giving the object a name. Not intended for machine interpretation, please see our notice on human interpretable data fields.
  Etablierte, menschenlesbare kurze Zeichenkette, die das Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
• description: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields.
  Menschenlesbare, detailliertere Beschreibung als Ergänzung zu name. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
• xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
  This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other languages.
• timetablePeriodRef: This refers to the id attribute of the associated <timetablePeriod> element.

• startDate: This is the first day of the period, if the operating period is shorter than the underlying timetablePeriod.
  Die Angabe von startDate beschränkt die Anwendung der Bildungsregel des operatingDay-Elements auf diesen Datumsbereich. Please, recognize the semantic constraint.
• endDate: This is the last day of the period, if the operating period is shorter than the underlying timetablePeriod.
  Die Angabe von endDate beschränkt die Anwendung der Bildungsregel des operatingDay-Elements auf diesen Datumsbereich. Please, recognize the semantic constraint.
• bitMask: This is a bit mask with 0 or 1 for every day of the timetablePeriod.

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

• id: xs:ID (external link), required
  a string, starting with a letter (a..zA..Z) or an underscore (_),
  followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)

• code: xs:string (external link), optional

• name: xs:string (external link), optional

• description: xs:string (external link), optional

• xml:lang: xs:language (external link), language identification (external link), optional
• timetablePeriodRef xs:IDREF (external link), optional
• startDate xs:date (external link), optional; shall be lower or equal endDate if both are used.
• endDate xs:date (external link), optional; shall be higher or equal startDate if both are used.
• bitMask optional, consisting of the digits 0 and/or 1
  The "string-length" has to be the number of days in the time period defined through startDate and endDate of the <timetablePeriod> element.
  This means: If the timetable period is reduced by attributes startDate+endDate of the element operatingPeriod the difference quantity of days in the bitmask has to be set to 0 but not to be skipped.

The attributes startDate and endDate are not allowed to enhance the time period given by the referenced timetablePeriod.
startDate und endDate sind nur gemeinsam zu benutzen und dürfen nur Tage innerhalb der Gültigkeitsperiode der timetablePeriod referenzieren.

Semantic Constraints / Semantische Beschränkungen / Contraintes semantiques

Semantic Constraint "TT:001": Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other validity periods. Proposed on November 12th 2018 Approved on March 21st 2019 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples

  <operatingPeriod id="op15" name="15" description="Mo-Fr" timetablePeriodRef="tp2005" bitMask="011111001111000111100011111...111110" />

see also

• Weitere Informationen und railML^®-Beispiel zu Verkehrstagen (external link, 2012-0523, pdf, , visited on 2018-03-27; by Dirk Bräuer, iRFP Dresden)
• How to indicate midnight overruns in railML^®