Dev:changes/2.5: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
No edit summary |
(+TT:category@trainusage) |
||
Line 15: | Line 15: | ||
[[File:Anpassungen railML 2 -Bedarfszüge.pdf|thumb]] | [[File:Anpassungen railML 2 -Bedarfszüge.pdf|thumb]] | ||
|trac={{ticket|372}}|nattr={{@|onRequest}}|uelem={{tag|TT|trainPart}}}} | |trac={{ticket|372}}|nattr={{@|onRequest}}|uelem={{tag|TT|trainPart}}}} | ||
===New value {{enum|other:anything}} for {{Tag|TT|category|@=trainUsage}}=== | |||
{{change | |||
|fact={{Tag|TT|category|@=trainUsage}} has been extended to allow for custom values | |||
|reason=The demand for more distinguished categories appeared in {{site|https://www.railml.org/forum/index.php?t=msg&goto=2271&#msg_2271|this discussion}} | |||
|recomendation= | |||
|trac={{ticket|375}} | |||
|svn={{SVN|1039}} | |||
|example= | |||
|xsd=railwayBaseTypes.xsd | |||
|nattr= | |||
|uattr={{Tag|TT|category|@=trainUsage}} | |||
|nelem= | |||
|uelem={{Tag|TT|category|attr=trainUsage}} | |||
}} | |||
==Interlocking Subschema== | ==Interlocking Subschema== | ||
==Infrastructure Subschema== | ==Infrastructure Subschema== |
Revision as of 17:48, 14 August 2020
| ||||||||
| ||||||||
railML® 3 Wiki – RailTopoModel® Wiki |
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
New @onRequest for <trainPart>
Fact: | new attribute @onRequest (bool) has been added in element <trainPart> in order to allow for standardized modelling of onRequest journeys. |
Reason: | Required by railML partner. Also this should help avoiding modelling of onRequest journeys using special train categories. |
Related Development Tickets: | #372 |
New attribute(s): | @onRequest |
Updated element(s): | <trainPart> |
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
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 |
Related Commits: | [1039] (Note on legacy SVN commits) |
New attribute(s): | @trainProtectionSystem |
Updated element(s): |