From railML 3 Wiki
Revision as of 21:53, 25 April 2022 by RailML Coord Documentation (talk | contribs) (Created page IL:routeSequence using XSD2MediaWiki Converter 1.0.6)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search




Autoexport from the XML-Schema for element IL:routeSequence of railML® version 3.2
Documentation RouteSequence is a combination of single routes defining the path from A to B independent of involved signalBoxes (interlockings).
Subschema interlocking
Parents* routeSequences
Children belongsToOperationalPoint (0..*), comboEntry (1..1), comboExit (1..1), containsRoute (1..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), objectName (0..*)
  • priorityRank: Gives the priority of the path in case there are several possible paths between entry and exit. The highest priority is 0. (optional; xs:nonNegativeInteger),

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

  • 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