View source for IL:interlocking

<!--Element '''{{{element}}}'''-->
=={{introduction}}==
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
{{ImportComment}}
=={{documentation}}==
==={{syntax}}===
<!-- NEVER expand this template!!! -->
{{robot|subschema=IL|element=interlocking|parent=}}
==={{semantics}}===
{{importComment}}
=={{examples}}==
<!--<tabber>
 3.1=Example, valid only for {{rml|3.1}}
|-|
 3.2=Example, valid only for {{rml|3.2}}
</tabber>
-->

=={{Additional Information}}==
==={{Notes}}===
The railML interlocking subschema contains definitions of data describing railway signalling and the use of interlocking systems. There are lot of different objects which will appear in infrastructure '''and''' interlocking. As a rule all physical characteristics, which can be "touched" are in infrastructure. All things about function and usage from train control point of view are in interlocking. Interlockings in strict sense are control systems using movable elements, signals, detectors, and other components in combinations and sequences that hinder collision and derailment of trains. Although the entire subschema is called “interlocking” the term “interlocking” is mainly used in this document for the equipment of the interlocking logic.

An interlocking description consists mainly of:
*Track and trackside signalling components,
*Route control logic,
*Interfaces,
*Control system, and
*Controllers.

Each of these categories are described in more detail in sections below.

[[File:OverviewIL.png]]

The base type for interlocking entities in {{rml}} includes the {{attr|id}} attribute (see [[Dev:identities]] about its use) and the {{tag|Generic|designator}} element, as well as the [[Dev:UsingAny#New_attributes_(Use_of_xs:anyAttribute)|the possibility to add custom attributes through the xs:anyAttribute mechanism]].

==={{Open issues}}===