Autoexport from the XML-Schema for element IL:routeReleaseGroupRear of railML® version 3.2 | |
| Documentation | One or more TVD sections as part of the route which can be released in a group in rear of passing train. |
| Subschema | interlocking |
| Parents* | routeReleaseGroupsRear |
| Children | belongsToOperationalPoint (0..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), hasTvdSection (0..*), objectName (0..*) |
Attributes:
If the route has only one route release group then the set of TVD sections in the route is released en bloc with the delay given here. (optional;
| |
| *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. | |
IL:routeReleaseGroupRear
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:routeReleaseGroupRear of railML® version 3.1 | |
| Documentation | One or more TVD sections as part of the route which can be released in a group in rear of passing train. |
| Subschema | interlocking |
| Parents* | routeReleaseGroupsRear |
| Children | any (0..*), designator (0..1), hasTvdSection (0..*) |
Attributes:
If the route has only one route release group then the set of TVD sections in the route is released en bloc with the delay given here. (optional;
| |
| *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
|
Release groups are typically a list of TVD sections to be released as a unit in rear of the passing train. The TVD sections of one group may cover only a part of a route. These release groups are necessary if several elements within the route are to be released together, i.e. each one is cleared by the passing train. A good example is a pair of coupled switches. They are kept in the route until both of them are cleared.
The route lists each of its release groups in <hasReleaseGroup>. However, this is only a reference to the instantiations of partialRoute for a particular routeReleaseGroup as defined in <knowsPartialRoute>. The release groups are only referenced in the route definition as shown here.
<hasReleaseGroup ref="prt02"/> <hasReleaseGroup ref="prt03"/>
The related details of the release groups are defined in the known assets.
<routeReleaseGroupRear delay="PT1S" id="prt02" typicalDelay="PT2S">
<designator register="_SimpleRegister" entry="tm_A02T"/>
<hasTvdSection ref="A02T"/>
</routeReleaseGroupRear>
<routeReleaseGroupRear delay="PT10S" id="prt03" typicalDelay="PT7S" >
<designator register="_SimpleRegister" entry="tm_A68W02T"/>
<hasTvdSection ref="A68W02T"/>
</routeReleaseGroupRear>
This extract show the combination of two sections within one release group.
<hasReleaseGroup ref="prt02-03"/>
…
<routeReleaseGroupRear delay="PT1S" id="prt02-03" typicalDelay="PT2S">
<designator register="_SimpleRegister" entry="tm_A02T+A68W02T"/>
<hasTvdSection ref="A02T"/>
<hasTvdSection ref="A68W02T"/>
</routeReleaseGroupRear>