TT:operatingDay: Difference between revisions
[checked revision] | [checked revision] |
(any element added) |
(intro- und depri-Tags vor 2.2 entfernt) |
||
Line 15: | Line 15: | ||
*{{Attr|operatingCode}}: a 7-digit bitmask (0/1) for the days of a normal week, Monday to Sunday | *{{Attr|operatingCode}}: a 7-digit bitmask (0/1) for the days of a normal week, Monday to Sunday | ||
*{{Attr|onRequest | *{{Attr|onRequest}}: needed for "runs Monday to Friday and additionally Sunday on request" | ||
*{{Attr|startDate}}: can be used to reduce the considered period | *{{Attr|startDate}}: can be used to reduce the considered period | ||
*{{Attr|endDate}}: can be used to reduce the considered period | *{{Attr|endDate}}: can be used to reduce the considered period |
Revision as of 15:37, 23 July 2017
operatingDay
Scheme description / Schemenbeschreibung
Position of operatingDay in the XML-Tree / Position von operatingDay im XML-Baum
- Parent: <operatingPeriod>
- Children: <operatingDayDeviance>, <xs:any> (introduced with version 2.3)
Multiplicity / Anzahl
Semantics / Bedeutung
The Element <operatingDay> gives a week based abstract description of an operating period for a normal day. Variations for certain types of days (e.g. public holidays) are dealt with in operatingDayDeviance. Two different elements <operatingDay> are valid at the same time. Therefore the startDate and endDate must be used to delimit different period parts.
Das Element <operatingDay> gibt eine wochenbasierte Beschreibung der Verkehrsperiode für normale Tage. Besondere Tagestypen wie Feiertage werden im Unterelement <operatingDayDeviance> behandelt. Zwei unterschiedliche Elemente <operatingDay> gelten dabei gleichberechtigt. Sie müssen daher über startDate und endDate zeitlich nicht überlappend voneinander abgegrenzt werden.
Attributes of operatingDay / Attribute von operatingDay
- operatingCode: a 7-digit bitmask (0/1) for the days of a normal week, Monday to Sunday
- onRequest: needed for "runs Monday to Friday and additionally Sunday on request"
- startDate: can be used to reduce the considered period
- endDate: can be used to reduce the considered 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
- operatingCode xs:string, mandatory
- onRequest xs:boolean, optional
- startDate xs:date, optional
- endDate xs:date, optional
Best practice & Examples / Empfohlene Anwendung & Beispiele
Train is operating Monday to Saturday (with no exception on public holidays):
<rail:operatingPeriod id="op16" description="Monday - Saturday"> <rail:operatingDay operatingCode="1111110"/> </rail:operatingPeriod>
see also the example of the railML developing partner iRFP:
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.