Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element RS:vehiclePart of railML ® version 3.3 |
| Documentation
|
A physical part of the vehicle which has its own body. The parts of a vehicle are connected with some kind of coupling and/or articulation. A vehiclePart can be a segment of an articulated vehicle or a car of multiple unit.
|
| Subschema
|
rollingstock
|
| Parents*
|
vehicle
|
| Children
|
designator (0..*), elementState (0..*), freightFacilities (0..*), isSupportingTilting (0..1), passengerFacilities (0..*)
|
Attributes:
- airTightness: The flag, whether this part provides air tightness for the passengers. (optional;
xs:boolean),
- category: Helps the reading software to “branch” between general vehicle types and to read/expect certain attributes depending on the vehicle type (for instance, rotationMassFactor at <propulsion> or <wagon>) (optional;
xs:string; patterns: other:w{2,}; consider Dev:UsingAny too.)
- Possible values:
- booster: locomotive without cab
- cabCoach: driving trailer
- freightWagon: non-driven wagon used for transport of any goods
- locomotive: vehicle with traction engine, not for passenger use
- motorCoach: passenger coach with motors for traction
- passengerCoach: non-driven coach for passenger use,
- emergencyBrakeOverride: The flag, whether this part provides a mean of override the emergency brake trigger. (optional;
xs:boolean),
- maximumCantDeficiency: The maximum value of permissible cant deficiency for this vehicle part measured in millimetres. (optional;
xs:decimal),
- partOrder: The order number of the vehicle part within the entire vehicle starting with 1 from A-end (front) of the vehicle. (obligatory;
xs:positiveInteger),
- 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.
|
Autoexport from the XML-Schema for element RS:vehiclePart of railML ® version 3.2 |
| Documentation
|
A physical part of the vehicle which has its own body. The parts of a vehicle are connected with some kind of coupling and/or articulation. A vehiclePart can be a segment of an articulated vehicle or a car of multiple unit.
|
| Subschema
|
rollingstock
|
| Parents*
|
vehicle
|
| Children
|
designator (1..*), freightFacilities (0..*), passengerFacilities (0..*)
|
Attributes:
- airTightness: The flag, whether this part provides air tightness for the passengers. (optional;
xs:boolean),
- emergencyBrakeOverride: The flag, whether this part provides a mean of override the emergency brake trigger. (optional;
xs:boolean),
- maximumCantDeficiency: The maximum value of permissible cant deficiency for this vehicle part measured in millimetres. (optional;
xs:decimal),
- partOrder: The order number of the vehicle part within the entire vehicle starting with 1 from A-end (front) of the vehicle. (obligatory;
xs:positiveInteger),
- id: unique identifier (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}}); 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.1 within the RS 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 parents have been changed.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues