TT:times ocpTT ocpsTT patternTrainPart: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(railML→{{rml}})
 
Line 28: Line 28:
{{note|Not to be confused with {{TT:Tag|train|attr=processStatus}}@processStatus, that describes the scope in relation to a process of train path ordering.}}
{{note|Not to be confused with {{TT:Tag|train|attr=processStatus}}@processStatus, that describes the scope in relation to a process of train path ordering.}}
* {{Attr|arrival}}: Moment at which the train ends its movement and gets to a halt at the parent <ocpTT>; usually called ''arrival time''.
* {{Attr|arrival}}: Moment at which the train ends its movement and gets to a halt at the parent <ocpTT>; usually called ''arrival time''.
** If this attribute is set at the first {{TT:Tag|ocpTT}} of a {{TT:Tag|trainPart}} that is also the first of the {{TT:Tag|trainPartSequence}} of all {{TT:Tag|train}}s it belongs to, it shall describe an "arrival from outside of the scope of the railML file": It expresses that the train arrives at that first {{TT:Tag|ocpTT}} at the given time, but the railML file does not express from where the train arrives nor whether it arrives as a train movement at all or rather as a shunting movement.
** If this attribute is set at the first {{TT:Tag|ocpTT}} of a {{TT:Tag|trainPart}} that is also the first of the {{TT:Tag|trainPartSequence}} of all {{TT:Tag|train}}s it belongs to, it shall describe an "arrival from outside of the scope of the {{rml}} file": It expresses that the train arrives at that first {{TT:Tag|ocpTT}} at the given time, but the {{rml}} file does not express from where the train arrives nor whether it arrives as a train movement at all or rather as a shunting movement.


* {{Attr|arrivalDay}}: arrival on the n-th day, with {{TT:Doc|train}} (but not necessarily the parent {{TT:Doc|trainPart}}) starting on day 0 at its first {{Attr|departure}}. To learn, how to handle values ≠0, see [[TT:Midnight_overrun | How to indicate midnight overruns in railML]].
* {{Attr|arrivalDay}}: arrival on the n-th day, with {{TT:Doc|train}} (but not necessarily the parent {{TT:Doc|trainPart}}) starting on day 0 at its first {{Attr|departure}}. To learn, how to handle values ≠0, see [[TT:Midnight_overrun | How to indicate midnight overruns in {{rml}}]].


* {{Attr|departure}}: departure or run-through (passing) time;  
* {{Attr|departure}}: departure or run-through (passing) time;  
** normally specified at all except the very last station of the last {{TT:Doc|trainPart}} (section) of a {{TT:Doc|train}}:
** normally specified at all except the very last station of the last {{TT:Doc|trainPart}} (section) of a {{TT:Doc|train}}:
** If this attribute is set at the last {{TT:Tag|ocpTT}} of a {{TT:Tag|trainPart}} that is also the last of the {{TT:Tag|trainPartSequence}} of all {{TT:Tag|train}}s it belongs to, it shall describe "departure to outside of the scope of the railML file": It expresses that the train departs at that last {{TT:Tag|ocpTT}} at the given time, but the railML file does not express to where the train departs nor whether it departs as a train movement at all or rather as a shunting movement.
** If this attribute is set at the last {{TT:Tag|ocpTT}} of a {{TT:Tag|trainPart}} that is also the last of the {{TT:Tag|trainPartSequence}} of all {{TT:Tag|train}}s it belongs to, it shall describe "departure to outside of the scope of the {{rml}} file": It expresses that the train departs at that last {{TT:Tag|ocpTT}} at the given time, but the {{rml}} file does not express to where the train departs nor whether it departs as a train movement at all or rather as a shunting movement.


* {{Attr|departureDay}}: departure on the n-th day, with {{TT:Tag|train}} (but not necessarily the parent {{TT:Tag|trainPart}}) starting on day 0 at its first {{Attr|departure}}. To learn, how to handle values ≠0, see [[TT:Midnight_overrun | How to indicate midnight overruns in railML]].
* {{Attr|departureDay}}: departure on the n-th day, with {{TT:Tag|train}} (but not necessarily the parent {{TT:Tag|trainPart}}) starting on day 0 at its first {{Attr|departure}}. To learn, how to handle values ≠0, see [[TT:Midnight_overrun | How to indicate midnight overruns in railML]].

Latest revision as of 20:48, 22 January 2024


times
 


Scheme description / Schemenbeschreibung

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

  • Parent: <ocpTT>
  • Children: None

Multiplicity / Anzahl

[0..∞]

Semantics / Bedeutung

The Element <times> describes arrival and departure times of a train with their scope.

Das Element <times> beschreibt Ankunfts- und Abfahrtszeiten eines Zuges und ihre Interpretation.
 
Please, be aware of the semantic constraint(s)!

Attributes of times / Attribute von times

Possible values are:
  • actual recorded arrival and/or departure times of a currently running or already driven train
  • calculated arrival and/or departure times from a simulation tool
  • published arrival and/or departure times that the passengers get on written sheets or online
  • scheduled arrival and/or departure times for operational purposes
  • earliest acceptable arrival and/or departure time (used to express a wish of a customer at a very early planning stage of a new timetable)
  • latest acceptable arrival and/or departure time (used to express a wish of a customer at a very early planning stage of a new timetable)
  • expected (introduced with version 2.5) forecasted arrival and/or departure times based on realtime data
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
🗒️ Not to be confused with <train>@scope, that distinguishes different paths / alternative slots of a train.
🗒️ Not to be confused with <train>@processStatus, that describes the scope in relation to a process of train path ordering.
  • arrival: Moment at which the train ends its movement and gets to a halt at the parent <ocpTT>; usually called arrival time.
    • If this attribute is set at the first <ocpTT> of a <trainPart> that is also the first of the <trainPartSequence> of all <train>s it belongs to, it shall describe an "arrival from outside of the scope of the railML® file": It expresses that the train arrives at that first <ocpTT> at the given time, but the railML® file does not express from where the train arrives nor whether it arrives as a train movement at all or rather as a shunting movement.
  • departure: departure or run-through (passing) time;
    • normally specified at all except the very last station of the last trainPart (section) of a train:
    • If this attribute is set at the last <ocpTT> of a <trainPart> that is also the last of the <trainPartSequence> of all <train>s it belongs to, it shall describe "departure to outside of the scope of the railML® file": It expresses that the train departs at that last <ocpTT> at the given time, but the railML® file does not express to where the train departs nor whether it departs as a train movement at all or rather as a shunting movement.
  • xs:anyAttribute: This provides an extension point for non-railML® attributes in a foreign namespace. How to use it?
    (introduced with version 2.2)

Syntactic Constraints / Syntaktische Beschränkungen

Not yet described. / Noch nicht beschrieben.

Semantic Constraints / Semantische Beschränkungen

Private-cloud-icon.png Semantic Constraint "TT:010":
 

@scope='earliest' and 'latest' are not intended to encode supplement times, as this is redundant to <ocpTT>.<sectionTT>.<runTimes>@operationalReserve, @additionalReserve, @minimalTime.
@scope='earliest' und 'latest' sind nicht zur Abbildung von Fahrzeitzuschlägen zu verwenden, da dies redundant zu <ocpTT>.<sectionTT>.<runTimes>@operationalReserve, @additionalReserve, @minimalTime ist.


 
Proposed on June 19th 2019
Approved on October 15th 2020
Discuss this semantic constraint
Please, recognize our guidelines on semantic constraints

Private-cloud-icon.png Semantic Constraint "TT:012":
 

When @scope='actual' is used, then the operating period and/or timetable period specified at the trainpart level shall refer to only one operating day. Like this the operating day to which the actual times refer is defined.
Wenn @scope= 'actual' verwendet wird, bezieht sich die operating period und/oder timetable period des train(part) auf nur einen einzelnen Betriebstag. Es muss so festgelegt werden, auf welchen Betriebstag sich die erfassten Ist-Zeiten beziehen.


 
Proposed on June 19th 2019
Approved on June 2nd 2022
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Private-cloud-icon.png Semantic Constraint "TT:014":
 

@arrival is not to be specified if the attribute ocpType of the parent <ocpTT> has the value pass - use departure for run-through (passing) times; This is in line with the definition of @arrival as the moment at which the train ends its movement and gets to a halt at the parent <ocpTT>.


 
Proposed on June 19th 2019
Approved on June 2nd 2022
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Private-cloud-icon.png Semantic Constraint "TT:015":
 

At the first <ocpTT> of a <trainPart> that is not the first one of the <trainPartSequence>, the attribute @arrival is optional. If it is set anyway, then, for consistency reasons, the value of @arrival of the regarding <ocpTT> must be identical for both this <trainPart> and the preceding one.


 
Proposed on June 19th 2019
Approved on June 2nd 2022
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Private-cloud-icon.png Semantic Constraint "TT:016":
 

At the last <ocpTT> of a <trainPart> that is not the last one of the <trainPartSequence>, the attribute @departure is optional. If it is set anyway, then, for consistency reasons, the value of @departure of the regarding <ocpTT> must be identical for both this <trainPart> and the subsequent one.


 
Proposed on October 09th 2020
Approved on June 2nd 2022
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.

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