| Re: TrainpartRefs [message #848 is a reply to message #753] |
Tue, 06 November 2012 14:00  |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hi Joachim, Carsten, Andreas and others,
Sorry for the late re-activating of this "quite closed thread".
coord(at)timetablerailmlorg (Joachim Rubröder) writes:
> you are totally right.
>
> The multiple use of the same trainPart in different trainPartSequences
> provides problems together with the use of rosterings or resevations.
>
> I therefore corrected the exaple to:
> <trainPartRef position="1" ref="tp2109a" />
> <trainPartRef position="2" ref="tp2109b" />
If found some more occurences in another example. :-(
"TT_Rostering.xml"
<trainPartRef position="1" ref="tp_651_RB_36301_4" />
<trainPartRef position="2" ref="tp_651_RB_36301_4" />
<trainPartRef position="1" ref="tp_651_RB_36301_5a" />
<trainPartRef position="2" ref="tp_651_RB_36301_5a" />
The possible double reference of one trainPart in either a "commercial"
train and/or a "operational" train for enabling both views should be
documented at the wiki-Documentation-Page. [1]
Kind regards...
Susanne
[1] http://www.wiki.railml.org/index.php?title=TT:trainPartRef
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
