Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:combinedRoute of railML ® version 3.2
|
Documentation
|
a concatenation of single routes providing a continuous path for traffic movement
|
Subschema
|
interlocking
|
Parents*
|
combinedRoutes
|
Children
|
belongsToOperationalPoint (0..*), comboEntry (1..1), comboExit (1..1), containsRoute (1..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), objectName (0..*)
|
Attributes:
- 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
|
*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.
|
Autoexport from the XML-Schema for element IL:combinedRoute of railML ® version 3.1
|
Documentation
|
a concatenation of single routes providing a continuous path for traffic movement
|
Subschema
|
interlocking
|
Parents*
|
combinedRoutes
|
Children
|
any (0..*), comboEntry (1..1), comboExit (1..1), containsRoute (1..*), designator (0..1)
|
Attributes:
- id: unique identifier (optional;
xs:ID ; 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.
|
Changes 3.1→3.2
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues