Home » railML newsgroups » railml.timetable » RailML semantics, nextdeparture, recurringschedule
Re: RailML semantics, nextdeparture, recurringschedule [message #733 is a reply to message #732] Fri, 20 May 2011 10:08 Go to previous messageGo to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Hi Tuomas,

> Heureka! Sorry for misleading you. I think that is closest so far. That
> the _train_ not the driver is asking "where shall we go on?" And the
> driver then answers, by either inputting trainnumber, or choose from given
> _list of possibilities_ or search. After the train gets its answer
> (Departure), it will use that information to display e.g. route correctly
> in the displays.

OK, let us assume there is a railML timetable (on the system in the train)
and the train knows where it is (station xy). The train needs to know
where to gon for displaying (->commercial perspective).
- the train driver types in the trainNumber (train searches the related
commercial "train" acoording to the trainNumber)
- train lists all "trainParts" starting at xy and train driver chooses one
then the train searches the related commercial train according to the
trainPart references)

The timetable gives a full overview over all trains. There is no special
list sorted by stations. So it is necessary to search the list of trains
or trainParts.

Kind regards,
Joachim

Tuomas Tiihonen wrote:
>
> Hi Joachim,
>
> Joachim Rubröder wrote:
>> Your train drivers question sounds like a taxi driver asking about
>> possible further rides. Maybe it is the train asking "where shall we go
>> on?" by providing a list of possibilities (-> operational trains) with a
>> filter function. Then the train driver would choose the correct one,
>> because he knows it. But I would assume that a train driver would type in
>> the train number and the train searches in a given in a timetable where to
>> go next.
>
> Heureka! Sorry for misleading you. I think that is closest so far. That
> the _train_ not the driver is asking "where shall we go on?" And the
> driver then answers, by either inputting trainnumber, or choose from given
> _list of possibilities_ or search. After the train gets its answer
> (Departure), it will use that information to display e.g. route correctly
> in the displays.
>
> This matches our concept, except this is thought in commercial perspective
> rather than operational.
>
> So how the commercial train would know the next commercial train that
> leaves the end station? Is that only by crawling through list of trains or
> is there ordered list (under rostering, circulation?)..
>
> 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: Fri May 17 05:58:36 CEST 2024