Home » railML newsgroups » railML.infrastructure » [railML2] Adding a new element informationArea to ocp
Re: [railML2] Adding a new element informationArea to ocp [message #2803 is a reply to message #2800] Mon, 02 August 2021 15:49 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Milan,
dear all,

when we want to use <propPassengerInfo> not only with <ocp>, but also with <track> and <platformEdge>, the question arises, if this <propPassengerInfo> shall be generic or specific. In particular:
* using a generic <propPassengerInfo> would allow <informationArea> elements not only for <ocp>, but also for <platformEdge> and <track> elements.
* using a specific <propPassengerInfo> implementation could be used to restrict <informationArea> elements only for <ocp>

What do you think: do we need <informationArea> also for <track> and <platformEdge>?

Best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML2] adding new element <area> for the mapping of track sections
Next Topic: [railML2] extension suggestion for the element <state> for working zones
Goto Forum:
  


Current Time: Thu May 02 13:36:57 CEST 2024