From railML 3 Wiki
Jump to navigation Jump to search




Autoexport from the XML-Schema for element IL:radioBlockCentre of railML® version 3.2
Documentation Container with the characteristics of an individual radioBlockCenter element
Subschema interlocking
Parents* radioBlockCentres
Children belongsToInfrastructureManager (0..1), belongsToOperationalPoint (0..*), connectedSignalBox (0..*), containedTrackAssets (0..*), designator (0..*), etcsGeneralData (0..1), hasCommand (0..*), hasCommunicationSettings (0..*), hasIndication (0..*), hasName (0..1), isLimitedByRadioBlockCentreBorder (0..*)
  • elementNumber: element number of the asset for internal reference in engineering data (optional; xs:nonNegativeInteger),

  • model: The model name of the asset from the supplier. (optional; xs:string),

  • softwareVersion: The specific software version of the asset itself. (optional; xs:string),

  • 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
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 IL subschema. It is available only in railML® 3.2. Do not hesitate to contact for further questions.

Changes 3.1→3.2

Introduced with version 3.2.


Best Practice / Examples

Additional Information


Open Issues