| timetable-Schema 0.96 ? [message #560] |
Thu, 02 October 2003 18:26 |
Joachim.Rubröder
Messages: 33
Registered: September 2004
|
Member |
|
|
Hello,
here are some changes and new fields, I would like to add for a new
Version 0.96:
-> entry\trackID (string)
the type should be changed to string ('3A', '9 3/4') as requested by
Softlab and UNI-Hannover
-> entry\trackInfo (string)
new optional field ('Short train in section B') as requested by Softlab
-> entry\publishedArrival (string)
-> entry\publishedDeparture (string)
new optional fields, requested by SBB. There are differences between the
real departure/arrival and the published departure/arrival. If a train
is arriving in time but too early (which is possible in Switzerland
:-)), it has to wait until the published departure time.
-> train\remarks (string)
-> train\description (string)
new useful otional fields, requested by DB an SBB, containing
information like 'Zurigo - Monaco' or 'RailML-Express'
-> train\seatCapacity (integer)
new optional field requested by DB (VISUM)
-> service\serviceID (string)
the type should be changed to string ('daily', 'Mo-Fr', '17'), as
requested in the forum
-> service\bitMask (string)
-> service\description (string)
-> service\startDate (date)
-> service\endDate (date)
the optional fields like bitMask ("010110..." for every day of the
period) were already discussed in the Zurich-meeting and is used by SBB,
DB (RUTK) and in the Pathfinder-Project. The startDate is needed to fix
the beginning of the bitMask sequence. Maybe we could also create a new
element <timetablePeriod> ('2003', '12.12.04-10.12.05', 'Summer of 69')
with startDate end endDate and use this as reference for all <service>
elements.
Any comments about these fields or other ideas not yet mentioned in the
forum??
Greetings from Zurich,
J.Rubröder
|
|
|
|
Members
Search
Help
Login
Home
