Home » railML newsgroups » railML.infrastructure » [railML3 wiki] opEquipment
[railML3 wiki] opEquipment [message #3677] Mon, 28 July 2025 09:53 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 72
Registered: February 2025
Location: Brussels
Member
Hello,

The wiki documentation on this website: https://wiki3.railml.org/wiki/IS:opEquipment#3.3-0
lists the child elements of opEquipment in this order: ownsInfrastructureElement (0..*), ownsPlatform (0..*), ownsServiceSection (0..*), ownsSignal (0..*), ownsStoppingPlace (0..*), ownsTrack (0..*)

However, the xsd lists it in this order: ownsPlatform, ownsTrack, ownsSignal, ownsStoppingPlace, ownsServiceSection, ownsInfrastructureElement

Since the xsd defines lists of child elements always as a xs:sequence, it's important to respect the correct order, else there are validation issues against the XSD.

I'm not sure if it's a requirement but it's so aligned that I suspect the wiki is meant to also publish the order of children. And it seems to be always in alphabetic order.

Or I could be wrong? :)

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: [railML3] Restricting aggregation of RailTopoModel
Next Topic: [railML 2] Semantic Constraint at trackBegin and trackEnd
Goto Forum:
  

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

Current Time: Sat Nov 15 18:45:18 CET 2025