Other information sources
This site is intended to collect the schema changes by topics, that influence the XML output. As it starts as a stub please refer to railML forum and SVN too.
railML schema changes since version 2
Between railML 2.0 and railML 2.1
Unfortunately no information available.
Between railML 2.1 and railML 2.2
Timetable subschema
To be filled.
Infrastructure subschema
ocp/@abbrevation
Fact:
|
The abbrevation attribute in the <ocp> element is declared deprecated.
|
Reason:
|
There are multiple different abbreviations for single operation or control points. They can't be defined with one attribute.
|
Recommendation:
|
Use the new <tsi> and/or <designator> elements instead.
|
Related Trac Tickets:
|
#112
|
Related SVN Commits:
|
[335], [439]
|
Old sample (railML 2.1):
|
<ocp ... name="Passau Hbf." abbrevation="NPA"/>
|
New sample (railML 2.2):
|
<ocp ... name='Passau Hbf.' ...>
<tsi country="80"/>
<designator register='RL100' entry='NPA'/>
<designator register='ENEE' entry='80-26506-6'/>
<designator register='IBNR' entry='8000298'/>
<designator register='DB640' entry='Pa'/>
</ocp>
|
Rollingstock subschema
Common subschema
Between railML 2.2 and railML 2.3
Timetable subschema
Infrastructure subschema
Fact:
|
The <trainRadio> element and <trainRadioChange> element have been introduced.
|
Recommendation:
|
Use the new <trainRadio> and <trainRadioChange> elements for defining conditions describing the train radio conditions along the track.
|
Related Trac Tickets:
|
#43
|
Related SVN Commits:
|
[630]
|
ocs element sample:
|
<ocsElements>
<trainRadioChanges>
<trainRadioChange id="trc01" pos="57.46" dir="up" radioSystem="GSM-R" broadcastCalls="true">
</trainRadioChange>
</trainRadioChanges>
</ocsElements>
|
infra attributes sample:
|
<infraAttrGroups>
<infraAttributes id="ia01">
<trainRadio radioSystem="GSM-R" broadcastCalls="true" />
</infraAttributes>
</infraAttrGroups>
|
Fact:
|
The parameter vMax in the <speedChange> element has been modified so that it can also handle the value "end".
|
Recommendation:
|
Use the new value "end" in order to mark the end of a temporary speed restriction.
|
Related Trac Tickets:
|
#97
|
Related SVN Commits:
|
[609]
|
sample:
|
<speedChange id="sc7" pos="256.7" vMax="end" dir="up" />
|
radiusChange/@geometryElementDescription
Fact:
|
A new attribute named geometryElementDescription has been added to the <radiusChange> element. It is an enumeration parameter, which provides the following entries that enable a more detailed description of transition curves:
- TS_cubicParabola
- TS_parabola4
- TS_clothoide; the usually used transition curve in modern railways, see English Wikipedia and German Wikipedia description
- TS_WienerBogen; a special transition curve used in Austria and Germany, see German Wikipedia description
- TS_BlossBogen; a special transition curve widely in Germany, see German Wikipedia description
- TS_Sinusoide
- TS_Cosinusoide
- SC
- (any other)
|
Reason:
|
So far, it was not possible to model transition curves in railML although they represent a basic track alignment feature.
|
Recommendation:
|
Use the new geometryElementDescription attribute in the <radiusChange> element for modelling the begin and end points of transition curves.
|
Related Trac Tickets:
|
#251
|
Related SVN Commits:
|
[616]
|
sample for transition curve begin:
|
<radiusChange ... geometryElementDescription='TS_clothoide' />
|
sample for transition curve end:
|
<radiusChange ... geometryElementDescription='SC' />
|
Fact:
|
The element <tsi> has been marked deprecated.
|
Reason:
|
Elements dedicated for the usage in conjunction with TAP TSI shall be replaced by a more generic approach.
|
Recommendation:
|
Instead of the element <tsi>, please use the <designator> element with the new register entry "PLC" (Primary Location Code) for referencing a TAF TSI relevant name of an operational control point.
|
Related Trac Tickets:
|
#252
|
Related SVN Commits:
|
[611]
|
old sample (railML 2.2):
|
...
|
new sample (railML 2.3):
|
...
|
line/@lineCategory
Fact:
|
The optional attribut lineCategory has been added to the parameters of the element <line>.
|
Reason:
|
The European standard EN 15528 defines several line categories for classification of railway lines depending on allowed maximum axle load and meterload paramters.
|
Recommendation:
|
Use the new paramter lineCategory within the element <line> to define a line category according to EN 15528. The following values are possible:
- A
- B1, B2
- C2, C3, C4
- D2, D3, D4, D4xL
- E4, E5
- (any other)
|
Related Trac Tickets:
|
#259
|
Related SVN Commits:
|
[620], [621], [622]
|
sample:
|
<line ... lineCategory='E4' />
|
Fact:
|
Although being optional, the attribut xml:lang should always be given in the <additionalName> element.
|
Reason:
|
In order to being able to correctly read the given additional name e.g. for an OCP, it is necessary to know in which language the additional name has been written.
|
Recommendation:
|
Always use the optional paramter xml:lang when using the element <additionalName>.
|
Related Trac Tickets:
|
#263
|
Related SVN Commits:
|
[629]
|
sample:
|
...
|
Fact:
|
New optional element crossedElement has been added for the elements levelCrossing, bridge and tunnel.
|
Reason:
|
This implementation allows to model more specific information about natural and infrastructure landmarks that are crossed by a river, a railway line or a street.
|
Recommendation:
|
If you want to define information about a natural or infrastructure landmark that you are going to cross with your track, please use the new element <crossedElement>.
|
Related Trac Tickets:
|
#271
|
Related SVN Commits:
|
[629]
|
sample for bridge:
|
<bridge id="br01" name="Marienbrücke" pos="2050">
<crossedElements>
<crossedElement type="highway:cycleway" id="cw01" name="Elberadweg" pos="2200" />
<crossedElement type="highway:road" id="rd01" name="B6" pos="2150" />
<crossedElement type="natural:river" id="ri01" name="Elbe" pos="2100" />
</crossedElements>
</bridge>
|
Rollingstock subschema
Common subschema