Home » railML newsgroups » railML.infrastructure » Redefine the use of signal@ocpStationRef (railML2.4) (signal@ocpStationRef)
Redefine the use of signal@ocpStationRef (railML2.4) [message #2039] Tue, 18 December 2018 15:03 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 165
Registered: March 2016
Senior Member
I suggest to delete the sentence "it refers to an ocp whose operationalType equal 'station' in the wiki (https://wiki.railml.org/index.php?title=IS:signal).

This as also other ocp types can have a signal. Here just two of several examples: An ocp propOperational@type=blockSignal has signals of type=blocking. Note that panels/boards are signals with @switchable="false". So that an ocp propOperational@type=stoppingPoint has signals (boards) that belong to the ocp.

I suggest to ignore the semantic in the attribute name for now and rename the attribute to @ocpRef in railML2.5 (if developed). I asume this does not apply to railML3.

[Updated on: Tue, 18 December 2018 15:04]

Report message to a moderator

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


Current Time: Thu Oct 31 23:48:55 CET 2024