Home » railML newsgroups » railml.timetable » Operator information
Operator information [message #642] Thu, 21 April 2005 11:41 Go to next message
jesper.hansen is currently offline  jesper.hansen
Messages: 1
Registered: April 2005
Junior Member
We're foreseeing the need for specifying the operator in the timetable.

Has anyone else had this need? Is it correct that this is not part of the
current version and if not could this be added?

Are there plans for developing a format for reading passenger data
statistics?

Jesper

Report message to a moderator

Re: Operator information [message #643 is a reply to message #642] Thu, 28 April 2005 11:36 Go to previous messageGo to next message
tobias is currently offline  tobias
Messages: 8
Registered: April 2005
Junior Member
Jesper Hansen wrote:

> We're foreseeing the need for specifying the operator in the timetable.

> Has anyone else had this need? Is it correct that this is not part of the
> current version and if not could this be added?


Does anyone have an answer to this? Since the operator could differ
between different trains, it seems like this would be an attribute on the
train element. I suppose that either depitcode, remarks or description
could be used but that would be forcing data into the format and it seems
like a bad idea.

Tobias Bende

Report message to a moderator

Re: Operator information [message #644 is a reply to message #643] Wed, 04 May 2005 08:49 Go to previous messageGo to next message
coord.timetable is currently offline  coord.timetable
Messages: 1
Registered: May 2005
Junior Member
<br><font size=2 face="sans-serif">I agree that the easiest thing would
be to add a new optional attribute &quot;operator&quot; to the trainType
since none of the other attributes is meant for this information.</font>
<br>
<br><font size=1 color=blue face="Arial">&lt;</font><font size=1 color=#800000 face="Arial">xsd:attribute</font><font size=1 color=red face="Arial">
name</font><font size=1 color=blue face="Arial">=&quot;operator&quot;</font><font size=1 color=red face="Arial">
type</font><font size=1 color=blue face="Arial">=&quot;</font><font size=1 face="Arial">xsd:string</font><font size=1 color=blue face="Arial">&quot;</font><font size=1 color=red face="Arial">
use</font><font size=1 color=blue face="Arial">=&quot;</font><font size=1 face="Arial">optional</font><font size=1 color=blue face="Arial">&quot;/&gt;</font>
<br>
<br><font size=2 face="sans-serif">Is there any need to change the operater
during the course of the train? This would mean to place him on the same
level with the trainData like it was suggested for the &quot;kind&quot;
of train by Sergey Vkthel.</font>
<br><font size=2 face="sans-serif">Are there other missing attributes like
that, we could integrate in a version 1.01? </font>
<br>
<br><font size=2 face="sans-serif">Joachim Rubröder</font>

Report message to a moderator

Re: Operator information [message #645 is a reply to message #643] Wed, 04 May 2005 08:58 Go to previous messageGo to next message
Joachim.Rubröder is currently offline  Joachim.Rubröder
Messages: 33
Registered: September 2004
Member
sorry, I had some technical problems posting my first response.

I agree that the easiest way is to add an optional attribute "operator" to
the trainType for the Version 1.01.

Is anyone in the need to change the operator during the course of the
train, like it was suggested for the attribute "kind" by Sergey Vakthel?
This would mean to place the operator on a deeper level like the train
data.

And are there more attributes like that to be thought of?

Joachim Rubröder

Report message to a moderator

Re: Operator information [message #646 is a reply to message #645] Sun, 08 May 2005 00:21 Go to previous message
tobias is currently offline  tobias
Messages: 8
Registered: April 2005
Junior Member
jrubroeder(at)sma-partnerch wrote:

> I agree that the easiest way is to add an optional attribute "operator" to
> the trainType for the Version 1.01.
>
> Is anyone in the need to change the operator during the course of the
> train, like it was suggested for the attribute "kind" by Sergey Vakthel?
> This would mean to place the operator on a deeper level like the train
> data.

I think it makes sense to have the operator on the trainType level.

Report message to a moderator

Previous Topic: new attributes in entry
Next Topic: intervalGroup
Goto Forum:
  

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

Current Time: Sat Apr 20 08:48:14 CEST 2024