Home » railML newsgroups » railML.infrastructure » [railML3] Restricting IS:line and RTM:linearPositioningSystem (New semantic constraints suggested)
Re: [railML3] Restricting IS:line and RTM:linearPositioningSystem [message #3254 is a reply to message #3251] Fri, 21 June 2024 12:22 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 508
Registered: January 2016
Senior Member
Dear David and Michael,

thank you for sharing your thoughts/feedback on the proposed semantic constraints.

Looking from a standpoint of unambiguous identification and location, I support the proposal by Larissa. Making the attributes @startMeasure and @endMeasure of a linearPositioningSystem optional is weakening the standard. It is also infecting the RTM where the positioning concept is derived from. So, I would vote for keeping these linearPositioningSystem parameters mandatory, but I am looking forward to receiving more feedback from the community...

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] New semantic constraint to ensure unambiguous infrastructure states
Next Topic: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation
Goto Forum:
  

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

Current Time: Thu Jun 19 03:08:19 CEST 2025