Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:arrival of railML ® version 3.3 |
| Documentation
|
Allows to specify the arrival time of a train within the given timescope, i.e. the time has come to a full stop.
|
| Subschema
|
timetable
|
| Parents*
|
times
|
| Children
|
None
|
Attributes:
- dayOffset: Specifies a day offset. This can be useful for trains that start before midnight but finish after or trains that run for more than one day. If no day offset is specified it is assumed to be zero. (optional;
xs:int; minInclusive: -7; maxInclusive: 7),
- time: Specifies the actual time encoded by this element. (obligatory;
xs:time)
|
*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:arrival of railML ® version 3.2 |
| Documentation
|
Allows to specify the arrival time of a train within the given timescope, i.e. the time has come to a full stop.
|
| Subschema
|
timetable
|
| Parents*
|
times
|
| Children
|
None
|
Attributes:
- dayOffset: Specifies a dayoffset. This can be useful for trains that start before midnight but finish after or trains that run for more than one day. (optional;
xs:int; minInclusive: -7; maxInclusive: 7),
- time: Specifies the actual time encoded by this element. (obligatory;
xs:time)
|
*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, 3.3. 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.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The parents have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues