TT:operatingPeriodRef trainPart: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
(link to Midnight_overrun added)
No edit summary
 
(18 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{ElementDocu|
{{ElementDocu|
elementName = operatingPeriodRef
elementName = operatingPeriodRef
Line 9: Line 10:
|parent = {{TT:Tag|trainPart}}
|parent = {{TT:Tag|trainPart}}


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


|ownAttributes =
|ownAttributes =
* {{Attr|startDate}}: 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.{{StartEndDoc}}
* {{Attr|endDate}}: This describes optional further restrictions of the operating period.
 
|constraints =
|constraints =
* {{Attr|ref}} {{RailMLType|tGenericRef}}, mandatory
* {{Attr|ref}} {{RailMLType|tGenericRef}}, mandatory
 
* {{Attr|startDate}} {{XsdType|date}}, optional {{depr|2.2}}; shall be lower or equal {{Attr|endDate}} if both are used.
* {{Attr|startDate}} {{XsdType|date}}, optional <br/> If not empty it has to be equal or later than the {{Attr|startDate}} of the referenced {{TT:Doc|timetablePeriod}}.
* {{Attr|endDate}} {{XsdType|date}}, optional {{depr|2.2}}; shall be higher or equal {{Attr|startDate}} if both are used.
 
|semcon={{startEndConNoOverlap}}
* {{Attr|endDate}} {{XsdType|date}}, optional <br/> If not empty it has to be equal or earlier than the {{Attr|endDate}} of the referenced {{TT:Doc|timetablePeriod}}.
|notes =
Child element {{TT:Doc|specialService|operatingPeriodRef}} is deprecated from {{rml|2.2}} on. An individual {{TT:Doc|operatingPeriod}} for each {{TT:Doc|trainPart}} should be referenced instead. See ticket {{ticket|158}}.


|example =  
|example =  
Line 37: Line 37:
  <rail:operatingPeriodRef ref="TGL"/>
  <rail:operatingPeriodRef ref="TGL"/>


Same reference but restricted to certain period:
* See also
 
:# [[TT:Midnight_overrun | How to indicate midnight overruns in {{rml|link=no}}]]
<rail:operatingPeriodRef ref="TGL" startDate="2009-10-05" endDate="2009-10-16"/>


see also
* '''iRFP Dresden''': selection of examples for operationg periods in German
* [[TT:Midnight_overrun | How to indicate midnight overruns in RailML]]
:# {{external|https://www.irfp.de/download/railml_beispiel_verkehrstage.pdf|iRFP-Informationen und -Beispiel zu Verkehrstagen in {{rml|link=no}}|lang=DE|comment=by Dirk Bräuer, iRFP Dresden|date=May 2012}}
* [http://www.irfp.de/download/railml_beispiel_verkehrstage.pdf Weitere Informationen und RailML-Beispiel zu Verkehrstagen, PDF, 185 kByte]
* [http://www.irfp.de/download/railml_beispiel_mueg.pdf RailML-Beispiel zu Mitternachtsübergängen, PDF, 269 kByte]


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

Latest revision as of 12:47, 14 May 2024


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 "CO:002":
 
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.
 
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 ticket #158.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.

Retrieved from "https://wiki2.railml.org/index.php?title=TT:operatingPeriodRef_trainPart&oldid=15570"