Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:stop:times of railML ® version 3.3
|
Documentation
|
Used to describe when the train arrives and/or departs from an OP.
|
Subschema
|
timetable
|
Parents*
|
externalTrainReference,
stop
|
Children
|
arrival (0..1), departure (0..1)
|
Attributes:
- scope: The timescope of the provided times. If the scope is unknown other:unknown should be provided. (obligatory;
xs:string ; patterns: other:w{2,})
- Possible values:
- commercial: Commercial time (german: verkehrliche Zeit) - If changed the change needs to be communicated as such. This information is intended and relevant for transportation customers/passengers.
- operational: Operational time (german: betriebliche Zeit) - This information is intended and relevant for RU/IM operations.
|
*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.2 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
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.
Introduced with version 3.3.
Semantics
Best Practice / Examples
Semantic constraint TT:008
The semantic constraint TT:008 ensures that no contradictory information can be provided. For example, it ensures that only a single 'scheduled' departure time is provided.
Mit der semantischen Beschränkung TT:008 wird sichergestellt, keine sich widersprechenden Informationen angegeben werden können. Beispielsweise wird sichergestellt, dass nur eine geplante also 'scheduled' Abfahrtszeit angegeben wird.
Valid:
<stop>
<times scope="operational">
<arrival time="10:05:15"/>
<departure time="10:07:00"/>
</times>
<times scope="published">
<arrival time="10:05:00"/>
<departure time="10:08:00"/>
</times>
</stop>
Invalid:
<stop>
<times scope="operational">
<arrival time="10:05:15"/>
<departure time="10:07:00"/>
</times>
<times scope="operational">
<arrival time="10:05:30"/>
<departure time="10:06:45"/>
</times>
<times scope="published">
<arrival time="10:05:00"/>
<departure time="10:08:00"/>
</times>
</stop>
Also invalid:
<stop>
<times scope="operational">
<arrival time="10:05:15"/>
</times>
<times scope="operational">
<departure time="10:07:00"/>
</times>
<times scope="published">
<arrival time="10:05:00"/>
<departure time="10:08:00"/>
</times>
</stop>
Additional Information
Notes
Open Issues