| Train category for speed changes/speed profiles (was: last open points for speedProfiles in railML 2.2) [message #514 is a reply to message #368] |
Mon, 11 March 2013 11:21   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dear railML users,
as written in Christians posting some times ago, the aspect of train
categories for speed changes / speed profiles is not satisfactory
discussed.
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
> the release of the new version railML 2.2 is approaching...
> One big issue of the new schema is the implementation of speed
> profiles that will be referenced by the <speedChange> elements. Since
> speed instructions depend on a lot of parameters resulting directly
> from the train (e.g. braking configuration, load), from the track's
> geography (e.g. slope) or from operation (e.g. route of the train),
> the <speedProfile> element includes a lot of attributes. The details
> can be found in trac ticket [1].
>
> At the end of this trac ticket few open points are listed and I want
> to put these open points here into the forum and ask for your
> comments:
>
> 1. What to do with the current "trainCategory" attribute in <speedChange>?
>
> Marking as "deprecated" is an easy way, but there are nevertheless
> international train categories for lines, e.g. "NC_Train" of the ETCS
> domain. Therefore I suggest to introduce a new attribute
> "etcsTrainCategory" and mark the other one as deprecated.
>
> [1] https://trac.assembla.com/railML/ticket/41
There was no response here!
We met in Berlin last week and had small discussion at the round table
about this issue. But these discussions did also not lead to a clear
change request. I summarized the open points in a new Trac ticket and
hope that this thread collects some statements about the wished and
needed implementation for the upcoming railML 2.2.
See Trac ticket #225 [2]:
At the railML conference in Berlin (2013-03-06) a bit confusion
raised around the train category for speed profiles and speed
changes. See also #41 for the speed profile implementations.
Current implementation:
* Attribute etcsTrainCategory in speedChange element.
* no general train category attribute in speedProfile element, use
other special characterization instead
Questions/requests:
* general train category attribute for the speedProfile element
* special train category attribute for the speedProfile element in
order to define "passenger" and "goods" trains
* special train category attribute for the speedProfile element in
order to define special vehicle family types, e.g. "Flirt"
Any comments* in short-term appreciated.
[2] http://trac.assembla.com/railML/ticket/225
* +1, -1, questions, hints, use cases...
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
