Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:minimalTime of railML ® version 3.3 |
| Documentation
|
Allows to provide a minimum runtime that applies from the enclosing base itinerary point to the next.
Between two base itinerary points several runtime reserves can be specified independently from each other. The actual runtime of the train in a section is calculated by adding the minimum runtime to the sum of all supplements.
|
| Subschema
|
timetable
|
| Parents*
|
followupSection
|
| Children
|
None
|
Attributes:
- runTime: The duration that it takes at least to travel the described section. (obligatory;
xs:duration)
|
*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:minimalTime of railML ® version 3.2 |
| Documentation
|
Allows to provide a minimum runtime that applies from the enclosing base itinerary point to the next.
Between two base itinerary points several runtime reserves can be specified independently from each other. The actual runtime of the train in a section is calculated by adding the minimum runtime to the sum of all supplements.
|
| Subschema
|
timetable
|
| Parents*
|
followupSection
|
| Children
|
None
|
Attributes:
- runTime: The duration that it takes at least to travel the described section. (obligatory;
xs:duration)
|
*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
Open Issues