TT:reserve: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Created page TT:reserve using XSD2MediaWiki Converter 1.0.6)
 
No edit summary
Line 13: Line 13:
=={{Additional Information}}==
=={{Additional Information}}==
==={{Notes}}===
==={{Notes}}===
Any reserve given with {{@|reserve}} is expected to be the absolute value of the reserve. Negative values are not expected nor valid here.
==={{Open issues}}===
==={{Open issues}}===

Revision as of 15:07, 7 March 2024

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element TT:reserve of railML® version 3.3
    
Documentation Describes one of the runtime reserves that have been applied for calculating the arrival time at the following stop.
Subschema timetable
Parents*

reserves

Children

name (0..*), rule (0..1)

Attributes:
  • reserve: The time allotted for as a runtime reserve for the reason given by type.
    The rule element can be used to further explain the value of this attribute, the field value however is the leading data here. (obligatory; xs:duration),

  • type: Optional field that can be used to describe the reasoning for a supplement. (optional; xs:string; patterns: other:w{2,})
Possible values:
  • general: General as defined by UIC 451-1:2000
  • qualityByInfrastructureManager: supplement added by infrastructure manager to improve timetable stability
  • qualityByRailwayUndertaking: supplement added by railway undertaking to improve timetable stability
  • synchronization: Used for synchronizing regular schedules (i.e. trains that run repeatedly during the day - once per hour)
  • trackworkByInfrastructureManager: supplement added by infrastructure manager due to scheduled trackwork
  • unspecified: Can be used if no information about the type of supplement can be provided.
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.


 

Autoexport from the XML-Schema for element TT:reserve of railML® version 3.2
    
Documentation Describes one of the runtime reserves that have been applied for calculating the arrival time at the following stop.
Subschema timetable
Parents*

reserves

Children

name (0..*), rule (0..1)

Attributes:
  • reserve: The time allotted for as a runtime reserve for the reason given by type.
    The rule element can be used to further explain the value of this attribute, the field value however is the leading data here. (obligatory; xs:duration),

  • type: Optional field that can be used to describe the reasoning for a supplement. (optional; xs:string; patterns: other:w{2,})
Possible values:
  • general: General as defined by UIC 451-1:2000
  • qualityByInfrastructureManager: supplement added by infrastructure manager to improve timetable stability
  • qualityByRailwayUndertaking: supplement added by railway undertaking to improve timetable stability
  • synchronization: Used for synchronizing regular schedules (i.e. trains that run repeatedly during the day - once per hour)
  • trackworkByInfrastructureManager: supplement added by infrastructure manager due to scheduled trackwork
  • unspecified: Can be used if no information about the type of supplement can be provided.
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.


 

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


Changes 3.1→3.2

There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Any reserve given with @reserve is expected to be the absolute value of the reserve. Negative values are not expected nor valid here.

Open Issues