TT:timetablePeriod

timetablePeriod
 

Scheme description / Schemenbeschreibung

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

• Parent: <timetablePeriods>
• Children: <additionalName> (introduced with version 2.1), <holidays>

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The Element <timetablePeriod> defines a timetable period, lasting typically about a year.

Das Element <timetablePeriod> bezeichnet eine Fahrplanperiode, die üblicher Weise etwa ein Jahr dauert.

Attributes of timetablePeriod / Attribute von timetablePeriod

• 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.
• startDate: This is the first day of the period.

• endDate: This is the last day of the period.

Syntactic Constraints / Syntaktische Beschränkungen

• id: xs:ID, 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, optional
• name: xs:string, optional
• description: xs:string, optional
• xml:lang: xs:language, language identification, optional

• startDate xs:date, optional

• endDate xs:date, optional

Best practice & Examples / Empfohlene Anwendung & Beispiele

<timetablePeriod id="tp09" id="TT2009" description="Timetable 2009" startDate="2008-12-07" endDate="2009-12-05"/>

see also

• Weitere Informationen und RailML-Beispiel zu Verkehrstagen, PDF, 185 kByte

Notes / Anmerkungen

A RailML file may but needs not necessarily to have a timetable period. A RailML file may also have more than one timetable period but each train part (and therefore also each train) can refer to only one timetable period.

RailML files without timetable period do either not have an element 'timetablePeriod' at all or only elements 'timetablePeriod' without 'startDate' and 'endDate'. It there is no timetable period defined the elements 'operatingPeriod' must also not have attributes 'startDate', 'endDate' and 'bitMask' and must also not have sub-elements 'specialService'.

'StartDate' and 'endDate' may be used together only, so there are no "open" periods allowed. The numerical difference of the attributes 'startDate' and 'endDate' defines the length of the attribute 'bitMask' of the elements operatingPeriod (=startDate-endDate+1).

{{{1}}}

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.