From railML 3 Wiki
Jump to: navigation, search




Autoexport from the XML-Schema for element IL:basculeBridge of railML® version 3.2
Documentation The contained basculeBridge element
Subschema interlocking
Parents* basculeBridges
Children any (0..*), assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), hasCommand (0..*), hasIndication (0..*), hasInterface (0..1), refersTo (0..1), takesControlOf (0..*)
  • technicalOpenTime: The time needed for the opening process of the bridge. (optional; xs:duration),

  • technicalClosingTime: The time for the technical closing process of the bridge. (optional; xs:duration),

  • typicalNonPassableTime: The typical time period the bridge is not passable during traversal of a vessel. (optional; xs:duration),

  • description: Description of the logic. (optional; xs:string),

  • elementNumber: element number for internal referencing in the engineering data (optional; xs:nonNegativeInteger),

  • id: unique identifier (optional; 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}\})
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. It is available only in railML® 3.2. Do not hesitate to contact for further questions.


Best Practice / Examples

Additional Information


Open Issues