| Marking @frontier and @chargeFrontier as DEPRECATED? [message #1940] |
Fri, 31 August 2018 09:13  |
christian.rahmig
Messages: 460
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
|
|
|
|
| Re: Marking @frontier and @chargeFrontier as DEPRECATED? [message #1943 is a reply to message #1940] |
Fri, 31 August 2018 11:34  |
christian.rahmig
Messages: 460
Registered: January 2016
|
Senior Member |
|
|
Dear all,
Am 31.08.2018 um 09:13 schrieb Christian Rahmig:
> [...]
> 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.
I filed a Trac ticket for this issue [1].
[1] https://trac.railml.org/ticket/341
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
|
|
|
|
| Re: Marking @frontier and @chargeFrontier as DEPRECATED? [message #1977 is a reply to message #1943] |
Tue, 02 October 2018 11:07 |
christian.rahmig
Messages: 460
Registered: January 2016
|
Senior Member |
|
|
Dear all,
Am 31.08.2018 um 11:34 schrieb Christian Rahmig:
>> [...]
>> 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.
>
> I filed a Trac ticket for this issue [1].
>
> [1] https://trac.railml.org/ticket/341
based on received feedback the modification described in [1] has been
implemented with 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
|
|
|
|
Members
Search
Help
Login
Home
