Forum: railML.infrastructure » Redefine the use of signal@ocpStationRef (railML2.4)

Home » railML newsgroups » railML.infrastructure » Redefine the use of signal@ocpStationRef (railML2.4) (signal@ocpStationRef)

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

Re: Redefine the use of signal@ocpStationRef (railML2.4) [message #2040 is a reply to message #2039]

Tue, 18 December 2018 15:28

Torben Brand
Messages: 158
Registered: March 2016

Senior Member

I see that the same wiki definition is inherited towards the elements: switch, crossing, levelCrossing, trainDetector, trackCircuitBorder and locallyControlledArea.

I suggest to delete the sentence in the generic parent. As the same restriction does also NOT apply to all the other elements listed here.

Report message to a moderator

[Message index]

		Redefine the use of signal@ocpStationRef (railML2.4) By: Torben Brand on Tue, 18 December 2018 15:03
		Re: Redefine the use of signal@ocpStationRef (railML2.4) By: Torben Brand on Tue, 18 December 2018 15:28
		Re: Redefine the use of signal@ocpStationRef (railML2.4) By: Ferri Leberl on Fri, 11 January 2019 12:21

Previous Topic:	Question towards use of @passable attribute (2.4)
Next Topic:	Multiple train protection systems

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon May 06 13:56:35 CEST 2024