| Re: train parts [message #678 is a reply to message #677] |
Tue, 15 July 2008 22:04   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
coord(at)timetablerailmlorg wrote:
> * You are creating a new sub structure called "trainParts" but I'm not
> sure that this is the atomic part of a train. Maybe there will be the
> need for trainPartParts next time.
So let's define a "train" as something that is unique with its train
number on a day and that goes as on "thing" on rails. That means that
people, who handle the train doesn't know about its parts.
In order to avoid redundancy, the "train" knows about its sections and
all according stopping (and passing) times and positions. That can be
stations, signals, reference points or anything else.
Instead of full defining times and positions inside "trainParts", the
"train" defines its "parts". That means, along a defined section the
"train" runs without changing its formation. Data about "current
formation" should be saved along the whole route, maybe only in points,
where formation changes (for avoiding redundancy).
Example:
Some Train 18345 runs from A via B to C.
From A to B we've two cars, in B one car is decoupled, from B to C only
one car runs.
A -->-- B ->- C
21---21 1---1 (1 and 2 are cars)
<train number="18345">
<parts>
<part id="1" from="A" to="C" posInTrain="1"/>
<part id="2" from="A" to="B" posInTrain="2"/>
</parts>
<!--...timesAndPositions...-->
</train>
If somebody wants to describe the whole run of some part, he can define
a "composition". In order to get detailed timetable for such a part, you
have to follow the references.
Example:
Some destination coach ("Kurswagen" in German) t1 runs in train 18345 as
part "2" (unique id in train) and in train 12345 as part "b".
<compositions>
<composition id="t1">
<trainRef="18345" partRef="2"/>
<trainRef="12345" partRef="b"/>
</composition>
</compositions>
> * The "train" can by now be further grouped to a trainGroup or an
> intervalGroup. For some users the "intervalGroup" is what he calls a
> train, for others it is the "trainPart"
Interval trains means, that there is a "master train" and some "offset
trains". That has to be clarified in documentation.
> * A simple railML user (without operatingPeriods and formations) knows
> about its "trains" but doesn't want to have to deal with "trainParts"
> because there is no reason for him.
The above mentioned version helps simple users, which doesn't handle
with train parts. They can use trains as they are by now.
Thanks for your comments.
Feel free to discuss this approach.
Kind regards,
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
