Home » railML newsgroups » railml.timetable » RailML semantics, nextdeparture, recurringschedule
Re: RailML semantics, nextdeparture, recurringschedule [message #730 is a reply to message #728] Wed, 11 May 2011 14:01 Go to previous message
tuomas.tiihonen is currently offline  tuomas.tiihonen
Messages: 15
Registered: May 2011
Junior Member
Joachim Rubröder wrote:
>
> Hi Tuomas,
>
>> Our Next departure is used by the driver of the train. So after driver
>> finishes one departure the driver can choose next departure for the train
>> he/she is currently driving. If I understand correctly it is perhaps the
>> vehicle->block closer to this.
>
> now we're getting closer. If the train driver chooses the next departure
> its probably kind of a service plan for train drivers. This is not yet
> implemented in railML but very similar to the rostering structure, wich is
> a service plan for vehicles. The problem with the train drivers is that
> they are much more complex (different skills, payment, pause times, ...)
> to deal with.
>

Hi Joachim,

actually the next departure is not related to the driver in our system.
Driver is just the user who selects the next departure from the system. So
in this context there is no need to know any information about the driver,
or even who is the driver or even if there is the driver :)

As driver is the user of the information he/she needs to know the next
departures for the train he/she is sitting in not for driver itself.

You can imagine that the train intelligently answers driver's question:
"Dear train, please tell me all possible next departures where you, train,
can depart from this exact station we are currently at"

After this question train would generate this information, hopefully from
railml by searching next departures from last driven departure. Or in
railml next block from last driven block?

Br,
Tuomas

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

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: These: Das Aufteilen eines großen RailML-Netzes auf mehrere kleinere RailML-Netze darf zu keinem Verlust an Informationen führen.
Next Topic: timetable.trainParts.trainPart.ocpsTT.ocpTT.times scope value
Goto Forum:
  

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

Current Time: Sat May 18 01:12:17 CEST 2024