TT:circulation
Jump to navigation
Jump to search
circulation
Scheme description / Schemenbeschreibung
Position of circulation in the XML-Tree / Position von circulation im XML-Baum
- Parent: <circulations>
- Children: Not yet described. / Noch nicht beschrieben.
Multiplicity / Anzahl
Semantics / Bedeutung
The element <circulation> is for chaining the blocks into a complete rostering.
In dem Element <circulation> werden die "Dienste" (blocks) zu einem Umlaufplan verkettet.
Attributes of circulation / Attribute von circulation
- blockRef: This refers to the id attribute of the associated <block> element.
- startDate: If this is absent operatingPeriodRef must be defined.
- endDate: If this is absent operatingPeriodRef may be defined or it is "open end".
- operatingPeriodRef: This refers to the id attribute of the associated <operatingPeriod> element.
This operatingPeriod constraints the dates the referenced block is to be fulfilled. If this is absent the referenced block runs daily from startDate to endDate.
- repeatCount: This is for abstract circulations from startDate to endDate.
- vehicleCounter (introduced with version 2.2): This indicates the right vehicle number (de: Fahrzeugnummer) within the circulations. (See also the Notes at the bottom of this page.)
- vehicleGroupCounter (introduced with version 2.2): This indicates the right vehicle group number (de: Gruppennummer) within the circulations. (See also the Notes at the bottom of this page.)
- nextBlockRef: This refers to the id attribute of the associated <block> element.
This is the block which should follow the currently referenced block.
- nextOperatingPeriodRef: This refers to the id attribute of the associated <operatingPeriod> element.
This operatingPeriod constraints the dates the following <circulation>.
- 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
- blockRef xs:IDREF, mandatory
- startDate xs:date, optional
- endDate xs:date, optional
- operatingPeriodRef xs:IDREF, optional
- repeatCount xs:nonNegativeInteger, optional
- vehicleCounter xs:nonNegativeInteger, optional
- vehicleGroupCounter xs:nonNegativeInteger, optional
- nextBlockRef xs:IDREF, optional
- nextOperatingPeriodRef xs:IDREF, optional
Best practice & Examples / Empfohlene Anwendung & Beispiele
see RailML-Beispiel Umlauf, PDF, 314 kByte
Notes / Anmerkungen
The attribute vehicleCounter is completely redundant because the information can be recreated by counting links (nextBlockRef,…) which link to earlier days (vehicleCounter) or to lower vehicles number (vehicleGroupCounter). Nevertheless, providing these values makes it easier to get the data and to avoid misunderstandings (skipping of vehicles during standstill).
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.