Forum: railML.infrastructure » [railML2] Enhancing the <lock> element

Home » railML newsgroups » railML.infrastructure » [railML2] Enhancing the <lock> element

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: [railML2] Enhancing the <lock> element [message #2700 is a reply to message #2687]

Sun, 11 April 2021 06:08

Jörg von Lingen
Messages: 87
Registered: March 2016

Member

Thanks for your feedback. We will the attribute @lockRef as suggested.

Best regards,
Joerg v. Lingen - Interlocking Coordinator
Am 25.03.2021 um 13:52 schrieb Michael Gruschwitz:
> Dear all!
>
> Am 25.02.2021 um 08:57 schrieb Torben Brand:
>> Reference to what the lock actually locks can be done either
>> from the lock or to the lock. In railML2.4nor extensions we
>> have the attribute @lockRef on the element <switch>,
>> <crossing> and the <derailer>. But you could also have a
>> subelement <takesControlOf> with an @ref attribute like in
>> railML3. What does the community prefer?
>
> We prefer the solution to have the attribute @lockRef on the element <switch>,
> <crossing> and the <derailer> as it is implemented in the same manner on the
> <controllerRef>.
>
> Best regards,

Report message to a moderator

[Message index]

		[railML2] Enhancing the <lock> element By: christian.rahmig on Mon, 16 November 2020 14:32
		Re: [railML2] Enhancing the <lock> element By: Torben Brand on Thu, 25 February 2021 08:57
		Re: [railML2] Enhancing the <lock> element By: Michael Gruschwitz on Thu, 25 March 2021 13:52
		Re: [railML2] Enhancing the <lock> element By: Jörg von Lingen on Sun, 11 April 2021 06:08

Previous Topic:	[railML2/3] <trainDetector> for manually operated stations
Next Topic:	[railML2] adding an attribute for clearance on switches and crossings.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed May 08 05:26:46 CEST 2024