Home » railML newsgroups » railML.infrastructure » Marking @frontier and @chargeFrontier as DEPRECATED?
Marking @frontier and @chargeFrontier as DEPRECATED? [message #1940] Fri, 31 August 2018 09:13 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear all,

the OCP contains the following two boolean attributes whose meaning (and
therefore usage) seems to be unknown:
* <ocp><propOther>@frontier
* <ocp><propOther>@chargeFrontier

Who uses these attributes and for what?

If nobody shows their interest in these attributes, I am going to mark
these attributes as DEPRECATED for railML version 2.4.

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
 
Read Message
Read Message
Read Message
Previous Topic: [railML3.1|Simple Example] Errors
Next Topic: Representation of operational stations
Goto Forum:
  


Current Time: Fri May 03 06:20:18 CEST 2024