Dev:Changes: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
(→‎Between railML 2.2 and railML 2.3: adding changelog 2.3: tsi)
m (Ferri Leberl moved page Dev:changes to Dev:Changes)
 
(39 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Other information sources =
{{mirror}}
 
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 ===
 
==== {{IS:Doc|ocp}}/{{Attr|@abbrevation}} ====
{|
|Fact:
| The {{Attr|abbrevation}} attribute in the {{IS:Tag|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 {{IS:Tag|tsi}} and/or {{IS:Tag|designator}} elements instead.
|-
| Related Trac Tickets:
| [http://trac.assembla.com/railML/ticket/112 #112]
|-
| Related SVN Commits:
| [http://trac.assembla.com/railML/changeset/335 [335]], [http://trac.assembla.com/railML/changeset/439 [439]]
|-
| Old sample (railML 2.1):
|
<syntaxhighlight lang="xml">
<ocp ... name="Passau Hbf." abbrevation="NPA"/>
</syntaxhighlight>
|-
| New sample (railML 2.2):
|
<syntaxhighlight lang="xml">
<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>
</syntaxhighlight>
|}
 
=== Rollingstock subschema ===
 
=== Common subschema ===
 
== Between railML 2.2 and railML 2.3 ==
 
=== Timetable subschema ===
 
=== Infrastructure subschema ===
 
==== {{IS:Doc|trainRadio}}, {{IS:Doc|trainRadioChange}} ====
{|
|Fact:
| The {{IS:Tag|trainRadio}} element and {{IS:Tag|trainRadioChange}} element have been introduced.
|-
| Recommendation:
| Use the new {{IS:Tag|trainRadio}} and {{IS:Tag|trainRadioChange}} elements for defining conditions describing the train radio conditions along the track.
|-
| Related Trac Tickets:
| [http://trac.railml.org/ticket/43 #43]
|-
| Related SVN Commits:
| [http://trac.railml.org/changeset/630/railML [630]]
|-
| ocs element sample:
|
<syntaxhighlight lang="xml">
<ocsElements>
  <trainRadioChanges>
    <trainRadioChange id="trc01" pos="57.46" dir="up" radioSystem="GSM-R" broadcastCalls="true">
    </trainRadioChange>
  </trainRadioChanges>
</ocsElements>
</syntaxhighlight>
|-
| infra attributes sample:
|
<syntaxhighlight lang="xml">
<infraAttrGroups>
  <infraAttributes id="ia01">
    <trainRadio radioSystem="GSM-R" broadcastCalls="true" />
  </infraAttributes>
</infraAttrGroups>
</syntaxhighlight>
|}
 
==== {{IS:Doc|speedChange}}/{{Attr|@vMax}} ====
{|
|Fact:
| The parameter {{Attr|vMax}} in the {{IS:Tag|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:
| [http://trac.railml.org/ticket/97 #97]
|-
| Related SVN Commits:
| [http://trac.railml.org/changeset/609/railML [609]]
|-
| sample:
|
<syntaxhighlight lang="xml">
<speedChange id="sc7" pos="256.7" vMax="end" dir="up" />
</syntaxhighlight>
|}
 
==== {{IS:Doc|radiusChange}}/{{Attr|@geometryElementDescription}} ====
{|
|Fact:
| A new attribute named {{Attr|geometryElementDescription}} has been added to the {{IS:Tag|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
* TS_WienerBogen
* TS_BlossBogen
* 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 {{Attr|geometryElementDescription}} attribute in the {{IS:Tag|radiusChange}} element for modelling the begin and end points of transition curves.
|-
| Related Trac Tickets:
| [http://trac.railml.org/ticket/251 #251]
|-
| Related SVN Commits:
| [http://trac.railml.org/changeset/616/railML [616]]
|-
| sample for transition curve begin:
|
<syntaxhighlight lang="xml">
<radiusChange ... geometryElementDescription='TS_clothoide' />
</syntaxhighlight>
|-
| sample for transition curve end:
|
<syntaxhighlight lang="xml">
<radiusChange ... geometryElementDescription='SC' />
</syntaxhighlight>
|}
 
==== {{IS:Doc|tsi}} ====
{|
|Fact:
| The element {{IS:Tag|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 {{IS:Tag|tsi}}, please use the {{IS:Tag|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:
| [http://trac.railml.org/ticket/252 #252]
|-
| Related SVN Commits:
| [http://trac.railml.org/changeset/611/railML [611]]
|-
| old sample (railML 2.2):
|
<syntaxhighlight lang="xml">
...
</syntaxhighlight>
|-
| new sample (railML 2.3):
|
<syntaxhighlight lang="xml">
...
</syntaxhighlight>
|}
 
 
=== Rollingstock subschema ===
 
=== Common subschema ===
[[Category:GeneralDescription]]

Latest revision as of 16:31, 18 May 2020

🗒️ This page is mirrored from page Dev:Changes in The railML® 3 wiki.
RailML Trademark RGB V2.png
XML Railway exchange format
https://railML.org
Latest release: 2.5
(September 1st, 2021)
 
Main Menu
 
Subschemas
XML tree
UML diagrams
Use cases
Versions & Changes

This page is intended to inform about the schema changes by topics, that influence the XML output. As it starts as a stub please refer to the railML forum (link to the railML® website) and the ticket systems for railML® 2 and for railML® 3, too.

Versions & Licences

→Main Article: Dev:Versions

The development of the early alpha versions started in 2001. Version 1.0, the first version allotted for productive use, was published in 2005. In 2019, the development was forked into the established railML® 2 family and the new railML® 3 family. railML® 3 differs from railML® 2 in many features and therefore is not designed backward compatible. The most fundamental difference is difficult to recognize at the surface: It is based on RailTopoModel®, thus incorporating a sophisticated topology model in the background. The current railML® 2 version is 2.5. The current railML® 3 version is 3.2.

A detailed version list can be found on https://www.railml.org/en/developer/version-timeline.html (link to the railML® website).

All currently supported railML® versions are licensed dually under a restricted form of the Creative Commons licence (external link) CC-BY-NC-ND and (for certified programmes) in a commercial licence. To learn more about the licence terms see https://www.railml.org/en/user/licence.html (link to the railML® website).

Schema changes in older railML versions / Other information sources

It is not intended to describe changes between minor versions in railML® 1 as there are no records from the pre-repository time. Also changes between the major releases (railML® 1 > railML® 2 or railML® 2 > railML® 3) could not be described here, as there are too many structural and major changes in railML®.

railML schema changes within version 2

The changes between the railML® 2 minor versions are available in the following descriptions:

Please, employ template:change to add entries.

railML schema changes within version 3

The changes between the railML® 3 minor versions are available in the following descriptions:

Please, employ template:change to add entries.

Retrieved from "https://wiki2.railml.org/index.php?title=Dev:Changes&oldid=10826"