Home » railML newsgroups » railML.infrastructure » [railML3] Proposal of a semantic constraint for mileageChange
Re: [railML3] Proposal of a semantic constraint for mileageChange [message #3090 is a reply to message #3085] Thu, 25 May 2023 21:01 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 486
Registered: January 2016
Senior Member
Dear Thomas,

interesting thoughts, thank you.

For the first question regarding the location of a mileage change on more than one netElement, I would ask the community for their opinion: Do you want to model mileage changes on two netElements?

Concerning the second point: Yes, the attribute <mileageChange>@type already tells you what to expect: a gap or an overlap. Therefore, the attributes seem to be indeed redundant.

As usual I appreciate any kind of further opinion 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
Previous Topic: [railML3] Transporting dangerous goods
Next Topic: [railML3] Proposal of a semantic constraint for <baliseGroup>
Goto Forum:
  

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

Current Time: Tue Feb 11 09:55:12 CET 2025