Home » railML newsgroups » railml.timetable » deprecated attribute "trainLine" for element "trainPart"
deprecated attribute "trainLine" for element "trainPart" [message #747] Wed, 07 September 2011 14:57 Go to next message
Christoph.Jobmann is currently offline  Christoph.Jobmann
Messages: 12
Registered: October 2010
Junior Member
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.

Best regards
Christoph Jobmann

--
----== posted via PHP Headliner ==----

Report message to a moderator

Re: deprecated attribute "trainLine" for element "trainPart" [message #752 is a reply to message #747] Fri, 09 September 2011 10:45 Go to previous messageGo to next message
Carsten Weber is currently offline  Carsten Weber
Messages: 27
Registered: November 2011
Junior Member
Dear RailML-Users,

"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.

Just for a better view to the problem (this is not RailML-code ;) ):
<train>
<line: "?">
<trainPart>
<line: "RE 1">
</trainPart>
<trainPart>
<line: "RE 2">
</trainPart>
</train>

What will you wright at the position of the question mark if your
(operational) train consists of two train parts which belong to different
lines?

Most of the informations could be given much more easier (and smaller) than
it is defined in several schemas. But a simple form will bring a lot of
trouble in a complex use case. So you have to define a schema for complex
use case and this way you also have to fill in simple cases in the complex
way.

Best regards.

Carsten Weber

Report message to a moderator

Re: deprecated attribute "trainLine" for element "trainPart" [message #849 is a reply to message #752] Tue, 06 November 2012 14:45 Go to previous message
Susanne Wunsch railML is currently offline  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

Report message to a moderator

Previous Topic: TrainpartRefs
Next Topic: Difference between 'Train coupling & sharing' and 'scope'
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Sep 09 15:37:17 CEST 2026