Home » railML newsgroups » railml.timetable » Feature requests for timetable schema
Feature requests for timetable schema [message #672] Tue, 04 March 2008 23:24 Go to previous message
susi is currently offline  susi
Messages: 4
Registered: January 2006
Junior Member
Hello,

in current projects there occured amongst others the following feature
requests for timetable sub schema:

* a "trainPart" structure parallel to "trains" with quite all
attributes from "train", only the "formation" with its data should
be fix for "trainPart"; references from "train" to "trainPart"s and
back should be optional

* operating-period-depended formation data for "train", e.g. other
formation at weekend, but same train

* an in-between element between "train" and "entry" for section
information along some track (e. g. between major stations), some of
current "section" data could be transferred into

* attributes for reservation data: booking number of actual wagons

* actual brake usage data about "formation" used in timetable,
independent from brake possibilities in rollingstock

* actual passenger data about seat capacity in 1st and 2nd class and
catering in timetable, independent from possibilities in
rollingstock

* ...

On 13th meeting in Bern, I will present some ideas for integrating it
in current railML 1.1

Feel free to comment, discuss or expand.

See you at meeting.

Best regards,
Susanne Wunsch.
 
Read Message
Read Message
Previous Topic: Timetable scheme as presented on 12th RailML meeting
Next Topic: Timetable schema
Goto Forum:
  


Current Time: Mon Apr 29 15:26:25 CEST 2024