TT:operatingPeriodRef trainPart: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(8 intermediate revisions by 2 users not shown)
Line 10: Line 10:


|childs = {{TT:Tag|specialService|operatingPeriodRef}} {{depr|2.2}}
|childs = {{TT:Tag|specialService|operatingPeriodRef}} {{depr|2.2}}
 
|minocc=0
|inheritedAttributes =
|inheritedAttributes =
{{InheritRefAny
{{InheritRefAny
Line 21: Line 21:


|ownAttributes =
|ownAttributes =
* {{Attr|startDate}} {{depr|2.2}}: This describes optional further restrictions of the operating period.
* {{Attr|startDate}} {{depr|2.2}}: This describes optional further restrictions of the operating period.{{StartEndDoc}}
* {{Attr|endDate}} {{depr|2.2}}: This describes optional further restrictions of the operating period.
* {{Attr|endDate}} {{depr|2.2}}: This describes optional further restrictions of the operating period.{{StartEndDoc}}
 
|constraints =
|constraints =
* {{Attr|ref}} {{RailMLType|tGenericRef}}, mandatory
* {{Attr|ref}} {{RailMLType|tGenericRef}}, mandatory
* {{Attr|startDate}} {{XsdType|date}}, optional {{depr|2.2}}
* {{Attr|startDate}} {{XsdType|date}}, optional {{depr|2.2}}; shall be lower or equal {{Attr|endDate}} if both are used.
* {{Attr|endDate}} {{XsdType|date}}, optional {{depr|2.2}}
* {{Attr|endDate}} {{XsdType|date}}, optional {{depr|2.2}}; shall be higher or equal {{Attr|startDate}} if both are used.
 
|semcon={{startEndCon}}
|notes =  
|notes =  
Child element {{TT:Doc|specialService|operatingPeriodRef}} is deprecated from railML 2.2 on. An individual {{TT:Doc|operatingPeriod}} for each {{TT:Doc|trainPart}} should be referenced instead. See TRAC ticket #158.
Child element {{TT:Doc|specialService|operatingPeriodRef}} is deprecated from railML 2.2 on. An individual {{TT:Doc|operatingPeriod}} for each {{TT:Doc|trainPart}} should be referenced instead. See TRAC ticket {{ticket|158}}.


|example =  
|example =  
Line 36: Line 35:


  <rail:operatingPeriodRef ref="TGL"/>
  <rail:operatingPeriodRef ref="TGL"/>
Same reference but restricted to certain period {{depr|2.2}}:
<rail:operatingPeriodRef ref="TGL" startDate="2009-10-05" endDate="2009-10-16"/>


* See also  
* See also  
:# [[TT:Midnight_overrun | How to indicate midnight overruns in railML]]
:# [[TT:Midnight_overrun | How to indicate midnight overruns in railML]]


* '''iRFP Dresden''': selection of examples for operationg periods and midnight overruns in German
* '''iRFP Dresden''': selection of examples for operationg periods in German
:# [http://www.irfp.de/download/railml_beispiel_verkehrstage.pdf iRFP-Informationen und -Beispiel zu Verkehrstagen in railML] (DE, Dirk Bräuer, iRFP Dresden, 74 kByte, May 2012)
:# {{external|http://www.irfp.de/download/railml_beispiel_verkehrstage.pdf|iRFP-Informationen und -Beispiel zu Verkehrstagen in railML|lang=DE|comment=by Dirk Bräuer, iRFP Dresden|date=May 2012}}
:# [http://www.irfp.de/download/railml_beispiel_mueg.pdf iRFP-Beispiel zur Abbildung von Mitternachtsübergängen in railML] (DE, Dirk Bräuer, iRFP Dresden, 165 kByte, May 2012)


|backHome = TT:elements
|backHome = TT:elements
}}
}}

Revision as of 12:52, 19 June 2020


operatingPeriodRef
 


Scheme description / Schemenbeschreibung

Position of operatingPeriodRef in the XML-Tree / Position von operatingPeriodRef im XML-Baum

Multiplicity / Anzahl

[0..1]

Semantics / Bedeutung

The Element <operatingPeriodRef> is used for referencing the operatingPeriod for the trainPart.

Das Element <operatingPeriodRef> referenziert die zum trainPart gehörige Verkehrsperiode.
 
Please, be aware of the semantic constraint(s)!

Attributes of operatingPeriodRef / Attribute von operatingPeriodRef

  • ref: This refers to the id attribute of the associated <operatingPeriod> element.

Syntactic Constraints / Syntaktische Beschränkungen

  • ref xs:IDREF, mandatory
  • startDate xs:date, optional (deprecated with version 2.2); shall be lower or equal endDate if both are used.
  • endDate xs:date, optional (deprecated with version 2.2); shall be higher or equal startDate if both are used.

Semantic Constraints / Semantische Beschränkungen

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
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele

Normal reference to the operatingPeriod for 'daily':

<rail:operatingPeriodRef ref="TGL"/>
  • See also
  1. How to indicate midnight overruns in railML
  • iRFP Dresden: selection of examples for operationg periods in German
  1. iRFP-Informationen und -Beispiel zu Verkehrstagen in railML (external link, May 2012, 🇩🇪; by Dirk Bräuer, iRFP Dresden)

Notes / Anmerkungen

Child element specialService is deprecated from railML 2.2 on. An individual operatingPeriod for each trainPart should be referenced instead. See TRAC ticket #158.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.