Forum: railml.timetable » @categoryPriority of <category> to be declared deprecated in version 2.5

Home » railML newsgroups » railml.timetable » @categoryPriority of <category> to be declared deprecated in version 2.5

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

@categoryPriority of <category> to be declared deprecated in version 2.5 [message #2277]

Tue, 26 November 2019 18:03

Milan Wölke
Messages: 146
Registered: April 2007

Senior Member

Hi,

bei einem Review der Dokumentation für das Element <category> im Wiki im Rahmen der TT-Developer Telcos sind wir auf das Attribut @categoryPriority gestoßen. Dieses Attribut ist als String definiert und erlaubt beliebigen Freitext, der dann durch das lesende Programm interpretiert werden muss. Da der Standard keinerlei Vorgaben bzgl. des Inhalts macht, muss es eine Abstimmung zwischen Produzent und Konsument geben, was ja eigentlich durch den Standard vermieden werden soll. In der Developer Group ist keine aktive Verwendung des Attributs bekannt. Entsprechend hat sich die Gruppe dafür ausgesprochen dieses Attribut mit railML 2.5 für deprecated zu erklären. Sollte es Verwendungen des Attributs in der Community geben, die einem solchen Schritt entgegenstehen würden, bitte ich darum diese hier vorzustellen. Vielen Dank schon mal im Voraus.

-------------------------------------------------

during a review of the documentation for the element <category> in the Wiki within the TT-Developer Telco we came across the attribute @categoryPriority. This attribute is defined as string and allows any free text, which has to be interpreted by the reading program. Since the standard does not make any specifications concerning the content, there must be a coordination between producer and consumer, which should actually be avoided by the standard. No active use of the attribute is known in the Developer Group. Accordingly, the group has decided to declare this attribute deprecated with railML 2.5. If there are uses of the attribute in the community that would stand in the way of such a step, please introduce them here. Many thanks in advance.

Best regards, Milan

Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]

		@categoryPriority of <category> to be declared deprecated in version 2.5 By: Milan Wölke on Tue, 26 November 2019 18:03
		Re: @categoryPriority of <category> to be declared deprecated in version 2.5 By: Janne Möller on Wed, 04 December 2019 16:32
		Re: @categoryPriority of <category> to be declared deprecated in version 2.5 By: Milan Wölke on Mon, 09 December 2019 13:56
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: Vasco Paul Kolmorgen on Wed, 11 December 2019 21:21
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: Milan Wölke on Mon, 10 February 2020 14:00
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: Janne Möller on Wed, 19 February 2020 08:39
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: Milan Wölke on Wed, 26 February 2020 11:58
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: huerlimann(at)opentrackch on Mon, 06 April 2020 11:44
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: Milan Wölke on Fri, 26 June 2020 13:38
		Re: @categoryPriority of <category> in version 2.5 / Extension of train part By: Dirk Bräuer on Wed, 01 July 2020 10:34

Previous Topic:	Continuation: different stop types / Mehrere Betriebshalt-HaltegruÌnde usw.
Next Topic:	[railML2] Usage of //ocpTT/times/@scope

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Oct 07 13:32:51 CEST 2024