TT:operatingDay

From wiki.railML.org
Jump to: navigation, search

operatingDay
 


Scheme description / Schemenbeschreibung / Description du schéma

Position of operatingDay in the XML-Tree / Position von operatingDay im XML-Baum / position de operatingDay dans l’aborescence XML

Multiplicity / Anzahl / Multiplicité

[0..∞]

Semantics / Bedeutung / Sémantique

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 / Attributs de 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 / Contraintes syntactiques

  • 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 / Contraintes semantiques

Private-cloud-icon.png Semantic Constraint "TT:001":
 
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. Must not overlap with other validity periods.
 
Proposed on November 12th 2018
Approved on March 21st 2019
Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples

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:

Notes / Anmerkungen / Notes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.

Open issues / Offene Punkte/Pedenzen / Questions ouvertes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.