Forum: railml.timetable » RailML semantics, nextdeparture, recurringschedule

Home » railML newsgroups » railml.timetable » RailML semantics, nextdeparture, recurringschedule

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: RailML semantics, nextdeparture, recurringschedule [message #732 is a reply to message #731]

Thu, 12 May 2011 15:22

tuomas.tiihonen
Messages: 15
Registered: May 2011

Junior Member

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]

		RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Fri, 06 May 2011 09:02
		Re: RailML semantics, nextdeparture, recurringschedule By: Joachim Rubröder railML on Tue, 10 May 2011 10:28
		Re: RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Tue, 10 May 2011 13:52
		Re: RailML semantics, nextdeparture, recurringschedule By: Joachim Rubröder railML on Tue, 10 May 2011 14:51
		Re: RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Wed, 11 May 2011 08:47
		Re: RailML semantics, nextdeparture, recurringschedule By: Joachim Rubröder railML on Wed, 11 May 2011 10:09
		Re: RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Wed, 11 May 2011 14:01
		Re: RailML semantics, nextdeparture, recurringschedule By: Joachim Rubröder railML on Wed, 11 May 2011 16:58
		Re: RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Thu, 12 May 2011 15:22
		Re: RailML semantics, nextdeparture, recurringschedule By: Joachim Rubröder railML on Fri, 20 May 2011 10:08
		Re: RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Mon, 23 May 2011 07:46
		Re: RailML semantics, nextdeparture, recurringschedule By: tuomas.tiihonen on Wed, 11 May 2011 14:01

Previous Topic:	These: Das Aufteilen eines großen RailML-Netzes auf mehrere kleinere RailML-Netze darf zu keinem Verlust an Informationen führen.
Next Topic:	timetable.trainParts.trainPart.ocpsTT.ocpTT.times scope value

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat May 18 00:21:38 CEST 2024