Home » railML newsgroups » railml.interlocking » [railML3]: Proposed semantic constrain for TvdSection
Re: [railML3]: Proposed semantic constrain for TvdSection [message #3478 is a reply to message #3476] Fri, 21 February 2025 09:55 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 100
Registered: March 2016
Senior Member
Dear Thomas,

it is purely sematic.
There are two possible child elements "hasDemarcatingBufferstop" or
"hasDemarcatingTraindetector" each with [0..*].
However, it shall be ensured, that at least two childs out of these two
possibilities are used. And at least one of these childs is
"hasDemarcatingTraindetector".

The XSD cannot ensure by syntax that these rules are followed.
--
Best regards,
Joerg v. Lingen - Interlocking Coordinator
 
Read Message
Read Message
Read Message
Previous Topic: [railML3] Request for feedback on changes of our deprecation policy
Next Topic: [railML3]: SignalBox and RadioBlockCentre without reference to infrastructure
Goto Forum:
  


Current Time: Wed May 07 02:06:21 CEST 2025