| Re: deprecated attribute "trainLine" for element "trainPart" [message #849 is a reply to message #752] |
Tue, 06 November 2012 14:45  |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hi Carsten, Christoph and others,
Sorry for the late re-activating of this "quite closed thread".
"Carsten Weber" <weber(at)irfpde> writes:
> "Christoph Jobmann" <christophjobmann(at)deutschebahncom> schrieb im
> Newsbeitrag news:j47pnc$89i$1(at)sifaivifhgde...
>> Greetings,
>>
>> lately I noticed that the attribute "trainLine" for the element
>> "trainPart" was declared deprecated since v2.1 since the new attribute
>> "line" was introduced in order to define deviations from the train's line.
>> Now I looked at the definition of the element "train" and was unable to
>> locate a "line" attribute. Did I miss something? Or was this a once
>> planned but after all forgotten extension?
>> Additionally I noticed that the examples still use the (now deprecated)
>> trainLine attribute.
>
> Well it is not really useful to bring a "line" name to a train.
> Normally all the trains parts of a train are from the same line but in
> some cases it does not work. This will bring a lot of trouble in a
> case of a train which combines several lines. A good example are
> trains which do coupling and sharing. These trains consist of several
> lines by there train parts so that you can not really use a "line"
> attribute at a train.
If that's the last statement all agree with, the "deprecation text"
should be adjusted and not try to point to the non-existing 'line'
attribute in <train>.
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
