Introduction
Documentation
Syntax
|
|
| Documentation
|
Specifies the vehicle rostering for one formation.
|
| Subschema
|
timetable
|
| Parents*
|
vehicleRosterings
|
| Children
|
blockConnections (0..1), blocks (1..1), name (0..*)
|
Attributes:
- depotRef: Allows referencing the associated depot of the enclosing vehicle rostering. The reference endpoint is expected to be an infrastructure OP (optional;
xs:IDREF),
- formationRef: Allows referencing a formation of rollingstock in order to associate the enclosing vehicle rostering with the vehicles assigned to the referenced formation (optional;
xs:IDREF),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); compare: Dev:Identities
|
*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
Additional Information
Notes
Open Issues