Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:transferPoint of railML ® version 3.3 |
| Documentation
|
Each entry encodes the transfer duration to a transfertarget, that can be specified in varying detail.
It is expected that at least one of the optional attributes @platformEdgeRef, @platformRef, @trackRef and transferOP is specified.
|
| Subschema
|
timetable
|
| Parents*
|
transferRelation
|
| Children
|
None
|
Attributes:
- duration: The transferduration encoded by this entry. (obligatory;
xs:duration),
- transferOPRef: Allows specifying a target OP. This can be used to describe transfer times to an OP that is close by. (optional;
xs:IDREF),
- platformEdgeRef: Reference to a platformEdge definied in infrastructure. (optional;
xs:IDREF),
- platformRef: Reference to a platform defined in infrastructure. The option to reference a platform was added as transfer times of the two edges of a platform usually do not differ. Referring to the platform thus can be used to reduce the number of transfertime entries. (optional;
xs:IDREF),
- trackRef: Reference to a track defined in infrastructure (optional;
xs:IDREF)
|
*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:transferPoint of railML ® version 3.2 |
| Documentation
|
Each entry encodes the transfer duration to a transfertarget, that can be specified in varying detail.
It is expected that at least one of the optional attributes @platformEdgeRef, @platformRef, @trackRef and transferOP is specified.
|
| Subschema
|
timetable
|
| Parents*
|
transferRelation
|
| Children
|
None
|
Attributes:
- duration: The transferduration encoded by this entry. (obligatory;
xs:duration),
- transferOPRef: Allows specifying a target OP. This can be used to describe transfer times to an OP that is close by. (optional;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- platformEdgeRef: Reference to a platformEdge definied in infrastructure. (optional;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- platformRef: Reference to a platform defined in infrastructure. The option to reference a platform was added as transfer times of the two edges of a platform usually do not differ. Referring to the platform thus can be used to reduce the number of transfertime entries. (optional;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- trackRef: Reference to a track defined in infrastructure (optional;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}})
|
*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.
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 attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues