Generic:vehicleBrakes/3.2

Automatic Schemaexport for Element vehicleBrakes

Autoexport from the XML-Schema for element generic:vehicleBrakes of railML® version 3.2 UML-visualization of generic
Documentation	Description of the type of vehicle brakes and their application as brake effort or deceleration. There is a distinction between normal brake operation and emergency brake application.
Subschema	generic
Parents*	brakes
Children	auxiliaryBrakes (0..*)
Attributes: airBrakeApplicationPosition: base brake switch, one of G, P or R (optional; xs:string) Possible values: N/A P: Passenger R: Rapid G: Goods, brakeType: technical type of brake system: vacuum or compressed air brake, hand brake, parking brake, cable brake etc. (optional; xs:string; patterns: other:\w{2,}) Possible values: none compressedAirBrake: de: Druckluftbremse vacuumAirBrake: de: Saugluftbremse cableBrake: de: Seilzugbremse parkingBrake handBrake, emergencyBrakeMass: brake mass for emergency brake operations, differs from regular brake mass depending on auxiliary brakes in metric tons (optional; xs:decimal), emergencyBrakePercentage: brake percentage for emergency brake operations, differs from regular brake percentage depending on auxiliary brakes (optional; xs:integer; minInclusive: 6; maxInclusive: 225), maxDeceleration: specification of maximum possible momentary deceleration in meter per square second (optional; xs:decimal), meanDeceleration: specification of effective mean deceleration of a whole brake operation in meter per square second (optional; xs:decimal), regularBrakeMass: brake mass for normal brake operations of none-automatic brakes in metric tons (optional; xs:decimal), regularBrakePercentage: brake percentage for normal brake operations of none-automatic brakes (optional; xs:integer; minInclusive: 6; maxInclusive: 225)
*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.