Home » railML newsgroups » railML.infrastructure » Include track length information in topology
Re: Include track length information in topology [message #2107 is a reply to message #2081] Fri, 18 January 2019 15:28 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 463
Registered: January 2016
Senior Member
Hello,

Am 08.01.2019 um 22:37 schrieb Thomas Nygreen:
> [...]
> One concern I have is how to interpret spotLocation/@pos if
> the optional netElement/@length is missing.

one possible solution is to define the rule, that if the optional
attribute <spotLocation>@pos is being used, the other optional attribute
<netElement>@length has to be given.

Alternatively, the attribute <netElement>@length could be declared as
being mandatory.

What do you prefer?

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org

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
Previous Topic: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir
Next Topic: switchType IS vs. IL
Goto Forum:
  

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

Current Time: Mon Sep 16 15:21:26 CEST 2024