Home » railML newsgroups » railml.interlocking » [railML3]: Proposed semantic constrain for TvdSection
[railML3]: Proposed semantic constrain for TvdSection [message #3453] Wed, 05 February 2025 05:48 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 100
Registered: March 2016
Senior Member
Dear all,

A semantic constrain will support checking of correct use of railML
data. Within "TvdSection" there shall be a semantic constrain considered.

One element "TvdSection" shall have minimum of two childs
"hasDemarcatingBufferstop" or "hasDemarcatingTraindetector".

Each element "TvdSection" shall have minimum of one child
"hasDemarcatingTraindetector".

This constrain applies for physical reasons and is independent of any
use case.
--
Best regards,
Joerg v. Lingen - Interlocking Coordinator

Report message to a moderator

[Message index]
 
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:
  

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

Current Time: Tue May 06 21:29:17 CEST 2025