Home » railML newsgroups » railml.timetable » @categoryPriority of <category> to be declared deprecated in version 2.5
Re: @categoryPriority of <category> in version 2.5 / Extension of train part [message #2291 is a reply to message #2284] Wed, 11 December 2019 21:21 Go to previous messageGo to previous message
Vasco Paul Kolmorgen
Messages: 63
Registered: November 2004
Member
Dear Janne,

thank you for the feedback. railML.org welcomes the work on the uniform
use of the railML-TT schema in Norway.

Can you describe an usement/example for the use of
<railml><timetable><categories><category>@categoryPriority in Norway for
the wiki page and maybe also specify the using programme and use case?
Maybe we could contact this railML partner and ask for in-depth
documentation to publish in the wiki after discussion in the TT
developers group. This would help the community to use the element in a
proper manner.

Regarding the extension of the attributes of the train part, a modelling
suggestion here in the forum and an introduction in one of the upcoming
TT developer phone calls would certainly make sense. Ideally, the
extension in railML2.4nor would be identical to the new modelling in
railML 2.5, which would reduce the later conversion effort for all
participants.

A question: How should the priority be processed, if it is indicated at
the same time at the train part and at the category? Can you make the
corresponding railML2.4nor documentation (also about higher priority
ascending/descending) available to the railML community and the Wiki?

Thank you and kind regards,

Vasco
--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Am 04.12.2019 um 16:32 schrieb Janne Möller:
> For simulation purposes we want to use the abovementioned
> @categoryPriority, so we would very much like to keep this
> attribut. Though we will be using the free string to set in
> values that correspond integer values, with a higher value
> meaning a lower priority.
>
> Additionally we have the requirement to specify the priority
> of a trainPart, in case it differs from the referenced
> category priority. We are planning to add an extension to a
> Norwegian version of railML2.4 (railML2.4nor), and would
> like to propose a category-attribute for train parts in
> future railML-versions. In railML2.4nor we will use this
> attribute with type integer.
>
> Best regards,
> Janne Möller
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Continuation: different stop types / Mehrere Betriebshalt-Haltegründe usw.
Next Topic: [railML2] Usage of //ocpTT/times/@scope
Goto Forum:
  


Current Time: Thu Nov 14 06:39:16 CET 2024