Dev:changes/2.5: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(→Versions: Version set to 2.5) |
|||
Line 1: | Line 1: | ||
{{navi}} | {{navi}} | ||
{{head|{{rml}} schema changes between {{rml}} 2.4 and {{rml}} 2.5}} | {{head|{{rml}} schema changes between {{rml}} 2.4 and {{rml}} 2.5}} | ||
{{future|version=2. | {{future|version=2.5}} | ||
This site is intended to collect the schema changes between {{rml}} 2.4 and {{rml}} 2.5. | This site is intended to collect the schema changes between {{rml}} 2.4 and {{rml}} 2.5. |
Revision as of 14:16, 20 June 2020
| ||||||||
|
railML® schema changes between railML® 2.4 and railML® 2.5
|
This site is intended to collect the schema changes between railML® 2.4 and railML® 2.5.
A complete diff comparison will soon be available under Dev:changes/2.5/diff.
Changes are also marked on the element pages with (introduced with version 2.5) for introduced components and (deprecated with version 2.5) for components that became obsolete. All occurances of these tags are listed in Category:Intro/2.5 respectively Category:Depr/2.5.
For changes with other version upgrades see Dev:changes.
Timetable Subschema
Interlocking Subschema
Infrastructure Subschema
New @trainProtectionSystem for <trainProtectionChange> and <trainProtection>
Fact: | new attribute @trainProtectionSystem (string) has been added in elements <trainProtectionChange> and <trainProtection>.
@trainProtectionSystem shall reference values from codelist TrainProtectionSystems.xml. |
Reason: | <trainProtectionChange> and <trainProtection> were missing a parameter to reference the train protection system – compare the forum discussion (link to the railML® website). |
Related Development Tickets: | #356 |
New attribute(s): | @trainProtectionSystem |
Updated element(s): |