(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:isCommercial of railML ® version 3.3 |
| Documentation
|
Indicated that the stop is of a commercial nature
|
| Subschema
|
timetable
|
| Parents*
|
stop
|
| Children
|
None
|
Attributes:
- onOff: Used to specify if passengers can board or unboard the train or both. When used in context of cargo trains it indicates if goods are being loaded, unloaded or both.
If not specified it is assumed that 'both' applies. (optional; xs:string)
- Possible values:
- both: Allows entering and exiting the train
- off: Allows exiting the train
- on: Allows entering the train,
- onRequest: Indicated that this stop is planned as stop on request. If not specified the stop is assumed to not be on request. (optional;
xs:boolean)
|
*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:isCommercial of railML ® version 3.2 |
| Documentation
|
Indicated that the stop is of a commercial nature
|
| Subschema
|
timetable
|
| Parents*
|
stop
|
| Children
|
None
|
Attributes:
- onOff: Used to specify if passengers can board or unboard the train or both. When used in context of cargo trains it indicates if goods are being loaded, unloaded or both. (optional;
xs:string)
- Possible values:
- both: Allows entering and exiting the train
- off: Allows exiting the train
- on: Allows entering the train,
- onRequest: Indicated that this stop is planned as stop on request. (optional;
xs:boolean)
|
*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