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 previous message
Martin Zien is currently offline  Martin Zien
Messages: 12
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

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: [railML3] Extension methods
Next Topic: Issue with unique tID in commons3
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Apr 20 15:14:13 CEST 2024