Home » railML newsgroups » railml.interlocking » [railML3]: Proposed semantic constrain for TvdSection
Re: [railML3]: Proposed semantic constrain for TvdSection [message #3476 is a reply to message #3453] Thu, 20 February 2025 14:27 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 89
Registered: March 2008
Member
Dear Jörg,

These are syntactic, not semantic, constraints. Also, it does not guarantee that the TVD section has a well-defined closed area. For instance, if there is a switch inside the TVD section, it would need (at least) three demarcating elements. (At least) four if it has a crossing. The demarcating elements still also have to be placed in a certain manner. We could instead add a constraint that there should be no path out of the TVD section that does not lead to a demarcating element, but it would be quite complex to validate.

Best regards,
Thomas


Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
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 00:51:07 CEST 2025