railML® schema changes between railML® 2.4 and railML® 2.5
|
This instance of Template:Future seems to be obsolete. Please check, if this article contains information that is only valid for future railML® versions. If this is not the case, feel free to remove this template. Don't forget to check Category:Future if there are more obsolete instances.
|
|
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
New value other:anything for <category>@trainUsage
Fact:
|
<category>@trainUsage has been extended to allow for custom values
|
Reason:
|
The demand for more distinguished categories appeared in [this discussion this discussion] (link to the railML® website)
|
Related Development Tickets:
|
#375
|
Related Commits:
|
[1039] (Note on legacy SVN commits)
|
Updated XSD file(s):
|
railwayBaseTypes.xsd
|
Updated attribute(s):
|
<category>@trainUsage
|
Updated element(s):
|
<category>
|
Interlocking Subschema
Infrastructure Subschema
Rollingstock Subschema