| Re: stopDescription [message #667 is a reply to message #661] |
Thu, 25 January 2007 15:06  |
Daniel Huerlimann
Messages: 17
Registered: September 2004
|
Junior Member |
|
|
jrubroeder(at)sma-partnerch wrote:
> Problem: The type-attribute of the entry-element is overloaded with three
> different kinds of information: "begin/end", "stop/pass",
> "operational/conditional".
> The RhB (Rhätische Bahn) uses railML to distribute timetable information
> between their systems and need a more detailed distinction for the
> different kinds of stop.
>
> As further development of the timetable schema I therefore suggest to
> delete the two enumerations "operational" and "conditional" of the
> attribute "type" and use a new (optional) element "stopDescription"
> instead, with the following attributes (all optional):
>
> - commercial boolean Indicates, whether the stop is for
> commercial purpose (announced to customer) or operational only.
> - stopOnRequest boolean Indicates, whether the train stops always
> or on request only. Typically in combination with minStopTime = 0.
> - onOff on/off/both Indicates, whether passengers are
> allowed to get on or off the train and goods may be loaded or unloaded.
> - purpose string Describes the purpose of the stop.
> (e.g. crew change, customs)
> - serviceID string Train stops on spezified days
> only. (Seasonal Stop)
>
> I think this covers most of the different kinds of stops.
>
> Joachim
>
As an addition I recommend to add an information (boolean) whether the
defined times (arrival and departure) are used as restrictions (e.g. to
define an earliest departure time) or if they are used for information only.
- isTimingStation boolean
Best regards
Dani
|
|
|
|
Members
Search
Help
Login
Home
