Difference between revisions of "Dev:changes/2.5"

From wiki.railML.org
Jump to: navigation, search
[checked revision][checked revision]
(Versions: Version set to 2.5)
Line 11: Line 11:
 
For changes with other version upgrades see [[Dev:changes]].
 
For changes with other version upgrades see [[Dev:changes]].
 
==Timetable Subschema==
 
==Timetable Subschema==
 +
===New {{@|onRequest}} for {{tag|TT|trainPart}}===
 +
{{change|fact=new attribute {{@|onRequest}} (bool) has been added in element {{tag|TT|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.|trac={{ticket|372}}|nattr={{@|onRequest}}|uelem={{tag|TT|trainPart}}}}
 
==Interlocking Subschema==
 
==Interlocking Subschema==
 
==Infrastructure Subschema==
 
==Infrastructure Subschema==
Line 33: Line 35:
  
 
==Rollingstock Subschema==
 
==Rollingstock Subschema==
==Timetable Subschema==
 

Revision as of 12:40, 30 June 2020

railML®
XML Railway exchange format
https://railML.org
Latest release: 2.4
(October 7th, 2018)
 
Main Menu
 
Subschemas
XML tree
Use cases
Versions & Changes

railML® schema changes between railML® 2.4 and railML® 2.5
 

Sunrise.png This article contains information that is only valid for a future railML® version. The article refers to version 2.5, whereas the current railML® version is 2.4.

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 Trac Tickets: #372
New attribute(s): @onRequest
Updated element(s): <trainPart>

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 Trac Tickets: #356
New attribute(s): @trainProtectionSystem
Updated element(s):

Rollingstock Subschema