TT:specialService operatingPeriodRef

specialService
 

Schema description / Schemabeschreibung

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

• Parent: <operatingPeriodRef>
• Children: None

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

(deprecated with version 2.2) — use reference to individual operating period instead.
 
The Element <specialService> describes a calendar based modification of the operatingPeriod by including or excluding certain days or periods. The maximal duration of the underlying timetablePeriod and operatingPeriod may not be expanded with a this <specialService>.

There are 2 options for specifying the days on which the modification described here is valid. On the one hand, the @singleDate attribute can be used to describe a validity limited to a single day. Alternatively, the validity can be defined using a combination of the attributes @startDate/@endDate, possibly together with @startTime/@endTime. If no @startTime is specified, then it must be assumed that the validity refers to the entire specified @startDate. If no @endTime is specified, then it must be assumed that the validity refers to the entire specified @endDate. If no @startDate is specified, it must be assumed that the validity begins with the referenced <operatingPeriod>; if no @endDate is specified, it must be assumed that the validity ends with the referenced <operatingPeriod>. Specifying neither @singleDate, @startDate or @endDate, although syntactically possible, makes no sense for this element.

Das Element <specialService> beschreibt die auf einen Kalender bezogene Modifizierung einer Verkehrsperiode operatingPeriod um einzelne Zusatz- und/oder Ausfalltage oder auch Zusatz- und/oder Ausfallperioden. Die maximale Dauer der zugrundeliegenden Fahrplanperiode timetablePeriod beziehungsweise der darauf basierenden Verkehrsperiode operatingPeriod darf dabei aber nicht erweitert werden.
Um festzulegen, an welchen Tagen die hier beschriebene Modifizierung gültig ist, gibt es 2 Möglichkeiten. Einerseits kann das Attribut @singleDate genutzt werden um eine Gültigkeit beschränkt auf einen einzelnen Tag zu beschreiben. Alternativ kann die Gültigkeit über eine Kombination der Attribute @startDate/@endDate, ggf. zusammen mit @startTime/@endTime. Wenn keine @startTime angegeben wird, dann muss angenommen werden, dass die Gültigkeit sich über den gesamten angegebenen @startDate bezieht. Wenn keine @endTime angegeben wird, dann muss angenommen werden, dass die Gültigkeit sich über den gesamten angegebenen @endDate bezieht. Wird kein @startDate angegeben, muss angenommen werden, dass die Gültigkeit zusammen mit der referenzierten <operatingPeriod> beginnt, wird kein @endDate angegeben, muss angenommen werden, dass die Gültigkeit mit der referenzierten <operatingPeriod> endet. Weder @singleDate, @startDate oder @endDate anzugeben, obwohl syntaktisch möglich macht für dieses Element keinen Sinn.
Please, be aware of the semantic constraint(s)!

Attributes of specialService / Attribute von specialService

• type: It has to follow the constraints of xs:string. Possible values are:

• include for additional traffic days
• exclude to exclude days

• singleDate: This is used to include or exclude a single day.
• startDate: This is used to include or exclude a time period. Please, take notice of the semantic constraint.
  
• endDate: This is used to include or exclude a time period. Please, take notice of the semantic constraint.
  
• startTime: (deprecated with version 2.4) This is used for a more detailed description of the time period.
• endTime: (deprecated with version 2.4) This is used for a more detailed description of the time period.
• 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

• type xs:string, mandatory

• singleDate xs:date, optional

• startDate xs:date, optional; shall be lower or equal endDate if both are used.

• endDate xs:date, optional; shall be higher or equal startDate if both are used.

• startTime xs:time, optional

• endTime xs:time, optional

Semantic Constraints / Semantische Beschränkungen

Semantic Constraint "CO:002":   Relation of starting and ending timestamps of a time period   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.   Proposed on November 12th 2018 Approved on March 21st 2019 FIXME Forum missing Please, recognize our guidelines on semantic constraints

Semantic Constraint "TT:021":   Within the same <operatingPeriod> element, a date must not be contained in more than one <specialService> element.   Proposed on February 13th 2025 Approved on April 07th 2025 https://www.railml.org/forum/index.php?t=msg&th=1014&start=0& Please, recognize our guidelines on semantic constraints

Semantic Constraint "TT:022":   The values of @singleDate, @startDate and @endDate of <specialService> must not be outside of the time period defined in the enclosing <operatingPeriod>.   Proposed on February 13th 2025 Approved on April 07th 2025 https://www.railml.org/forum/index.php?t=msg&th=1014&start=0& Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele

<specialService type="include" singleDate="2009-12-24"/>

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.