The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Introduction
Documentation
Syntax
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
Introduced with version 3.2.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues