Introduction
Documentation
Syntax
|
Documentation
|
Allows referencing a platform edge defined in infrastructure.
|
Subschema
|
timetable
|
Parents*
|
platformEdgeRefs
|
Children
|
None
|
Attributes:
- onOff: Indicates if the referenced platform edge is used for boarding/unboarding/loading/unloading at the stop. The info provided here should not contradict the information specified at isCommercial/@onOff.
if no value is given the default value 'both' applies. (optional; xs:string )
- Possible values:
- both: Allows entering and exiting the train
- off: Allows exiting the train
- on: Allows entering the train,
- ref: Reference to a platform edge defined in infrastructure (obligatory;
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.
|
|
Documentation
|
Allows referencing a platform edge defined in infrastructure.
|
Subschema
|
timetable
|
Parents*
|
platformEdgeRefs
|
Children
|
None
|
Attributes:
- onOff: Indicates if the referenced platform edge is used for boarding/unboarding/loading/unloading at the stop. The info provided here should not contradict the information specified at isCommercial/@onOff (optional;
xs:string )
- Possible values:
- both: Allows entering and exiting the train
- off: Allows exiting the train
- on: Allows entering the train,
- ref: Reference to a platform edge defined in infrastructure (obligatory;
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