TT:operatingDay: Difference between revisions
[checked revision] | [checked revision] |
No edit summary |
(multiplicity) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 9: | Line 9: | ||
|childs = {{TT:Tag|operatingDayDeviance}}, {{any}} {{intro|2.3}} | |childs = {{TT:Tag|operatingDayDeviance}}, {{any}} {{intro|2.3}} | ||
|minocc=0 | |||
|maxocc=∞ | |||
|inheritedAttributes | |inheritedAttributes | ||
Line 16: | Line 17: | ||
*{{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}}: needed for "runs Monday to Friday and additionally Sunday on request" | *{{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{{StartEndDoc}} | ||
*{{Attr|endDate}}: can be used to reduce the considered period | *{{Attr|endDate}}: can be used to reduce the considered period{{StartEndDoc}} | ||
{{InheritAnyAttribute | {{InheritAnyAttribute | ||
|comment={{intro|2.3}} | |comment={{intro|2.3}} | ||
Line 27: | Line 28: | ||
*{{Attr|operatingCode}} {{xsdType|string}}, mandatory | *{{Attr|operatingCode}} {{xsdType|string}}, mandatory | ||
*{{Attr|onRequest}} {{xsdType|boolean}}, optional | *{{Attr|onRequest}} {{xsdType|boolean}}, optional | ||
*{{Attr|startDate}} {{xsdType|date}}, optional | *{{Attr|startDate}} {{xsdType|date}}, optional; shall be lower or equal {{Attr|endDate}} if both are used. | ||
*{{Attr|endDate}} {{xsdType|date}}, optional | *{{Attr|endDate}} {{xsdType|date}}, optional; shall be higher or equal {{Attr|startDate}} if both are used. | ||
|semcon={{startEndCon}} | |||
|example = | |example = | ||
Train is operating Monday to Saturday (with no exception on public holidays): | Train is operating Monday to Saturday (with no exception on public holidays): | ||
Line 36: | Line 37: | ||
</rail:operatingPeriod> | </rail:operatingPeriod> | ||
see also the example of the | see also the example of the {{rml}} {{site|http://www.railml.org/en/introduction/partners.html|developing partner}} iRFP: | ||
* {{external|http://www.irfp.de/download/railml_beispiel_verkehrstage.pdf|Weitere Informationen und | * {{external|http://www.irfp.de/download/railml_beispiel_verkehrstage.pdf|Weitere Informationen und {{rml}}-Beispiel zu Verkehrstagen|type=PDF|comment=by Dirk Bräuer, iRFP Dresden|date=2012-05-23|visited=2018-03-26|lang=DE}} | ||
|backHome = TT:elements | |backHome = TT:elements | ||
}} | }} |
Revision as of 22:29, 25 November 2018
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.
Please, be aware of the semantic constraint(s)!
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 Please, recognize the semantic constraint.
- endDate: can be used to reduce the considered period Please, recognize the semantic constraint.
- 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; shall be lower or equal endDate if both are used.
- endDate xs:date, optional; shall be higher or equal startDate if both are used.
Semantic Constraints / Semantische Beschränkungen
|
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 (link to the railML® website) iRFP:
- Weitere Informationen und railML®-Beispiel zu Verkehrstagen (external link, 2012-05-23, PDF, 🇩🇪, visited on 2018-03-26; by Dirk Bräuer, iRFP Dresden)
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.