|
Forum: railml.common
|
|
Topic: [railML3] Overview of how to deal with schema changes
|
| [railML3] Overview of how to deal with schema changes [message #3228] |
Mon, 22 April 2024 14:51 |
Christian Rößiger
Messages: 60
Registered: March 2015
|
Member |
|
|
Is there a general overview of how to deal with changes between minor versions in railML3.x? I am interested in both the schema development perspective as well as the implementation of the interface as import/export software. There was already a discussion in this forum and also a news article ( https://www.railml.org/en/public-relations/news/reader/handl ing-minor-changes-within-versions.html) that also contains a conclusion which approach was chosen for railML3.x, but I did not find a general description, especially not concerning the software implementation part.
According to the mentioned news article, the (planned) removal of attributes / elements must first be marked as "deprecated" in a minor version. Unfortunately, the article does not explicitly describe what to do when making changes to elements/attributes. I assume that a minor version with both representations (deprecated and current) must also be published in this case.
It is also not clear to me what this means for the implementation (and certification) of export/import interfaces. Does an export or import interface for a version 3.x have to support all regular elements of this version as well as all elements marked as "deprecated"?
I would find it very useful if this inforation could be summarised in a general document as a help for railML schema developers and software implementers.
Best Regards
Christian
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
|
|
|
|
Members
Search
Help
Login
Home
