| stopDescription [message #661] |
Wed, 30 August 2006 18:44  |
Joachim.Rubröder
Messages: 33
Registered: September 2004
|
Member |
|
|
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
|
|
|
|
Members
Search
Help
Login
Home
