Home » railML newsgroups » railml.common » [railML3] Binding position of Meta-Data in railML-Scheme (Request to make the position of "metadata" in railML more binding at top position)
[railML3] Binding position of Meta-Data in railML-Scheme [message #3034] Tue, 09 August 2022 15:29 Go to next message
Martin Zien is currently offline  Martin Zien
Messages: 10
Registered: December 2021
Junior Member
The current XSD-Defintion of railML 3.2 shows the node of "metadata" behind "common", "infrastructure" and "interlocking".
This is driven by the idea to have the nodes sorted alphabetically.
And theortically, the XSD allows to place the main nodes at any order inside the railML.
And of course, it is desirable to have "metadata" in a top position of the railML.

But when typical "onboard"-routines of programming languages create the railML by using the XSD, "metadata" is placed in the order that is applied in the XSD-Definition (means: behind "interlocking").

For this reason it should be considered to re-locate the node "metadata" in front or behind "common" in the XSD - exeptionall to the principle of the aplhabetical order.

Best regards
Martin Zien
Re: [railML3] Binding position of Meta-Data in railML-Scheme [message #3039 is a reply to message #3034] Tue, 27 September 2022 20:00 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 53
Registered: March 2008
Hi Martin,

My apologies for the late reply!

As you write, the domain elements (common, infrastructure, interlocking, metadata, rollingstock, timetable and visualizations) can be placed in any order in a railML 3.2 file. Can you elaborate why metadata should appear first?

I have created an issue in Gitlab and we will discuss this in the coordinators' group. What does the community think?

Thomas Nygreen - Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Extension methods
Goto Forum:

Current Time: Thu Oct 06 15:41:02 CEST 2022