| Re: [railML3] Proposal of a semantic constraint for mileageChange [message #3090 is a reply to message #3085] |
Thu, 25 May 2023 21:01   |
christian.rahmig
Messages: 436
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
|
|
|
|
Members
Search
Help
Login
Home
