rail:eOperatingPeriod

Complex Type Information

Model

rail:additionalName* , ANY element from ANY namespace OTHER than 'http://www.railml.org/schemas/2016' , rail:operatingDay* , rail:specialService*

Attributes

QName Type Fixed Default Use Inheritable Annotation
bitMask rail:tBitMask optional
a sequence of 1 and 0 for every day of the timetable period, indicating that the train runs or runs not on this specific date
code rail:tGenericName optional
for typical, specific abbreviations, used in different systems with the same understanding
description rail:tElementDescription optional
should be interpreted in its elements' context, substantiates the name
endDate xs:date optional
id rail:tGenericID required
XML-file-wide unique identity is required for later referencing that element
name rail:tGenericName optional
should be interpreted in its elements' context (e.g. track/name, vehicle/name)
startDate xs:date optional
timetablePeriodRef rail:tGenericRef optional
xml:lang xs:language optional
In due course, we should install the relevant ISO 2- and 3-letter
codes as the enumerated possible values . . .
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.railml.org/schemas/2016'

Used By

Source

<xs:complexType name="eOperatingPeriod">
  <xs:complexContent>
    <xs:extension base="rail:tOperatingPeriod">
      <xs:sequence>
        <xs:element name="operatingDay" type="rail:eOperatingDay" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation source="http://wiki.railml.org/index.php?title=TT:operatingDay"/>
          </xs:annotation>
        </xs:element>
        <xs:element name="specialService" type="rail:tSpecialService" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation source="http://wiki.railml.org/index.php?title=TT:specialService_operatingPeriod"/>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>