Timetable scheme V1.04 released [message #669] |
Wed, 18 April 2007 21:12 |
Joachim Rubröder railML
Messages: 0 Registered: November 2019
|
|
|
|
The latest version of the timetable scheme is available on the
RailML-Server.
There were some changes presented and discussed on the last meeting.
1. Element "special" was renamed to "specialService". Its attributes were
renamed to be alike in "service" or "timetablePeriod"
* date -> singleDate
* from -> startDate
* until -> endDate
2. Element "entry" got two new optional attributes to specify the correct
position and alignment of the train at this entry.
* alignment, enum (head, center, rear)
* offset, distance
This is useful to describe that the head (alignment) of the train stops
100 m (offset) after the station building (entry). Or the rear (alignment)
of the train passes a signal (entry).
3. Element "operatingPeriod" as new subelement of "operatingPeriods"
containing the known elements "service" and "holidays".
This change was made to get the same structure as in
timetablePeriods/timetablePeriod, compositions/composition and
categories/category.
4. Element "operatingDay" could now be used more than 5 times. Its
attributes are changed as well:
* operatingCode as before
* dayType now deleted
* holidayOffset optional integer, new (0=holiday,
-1=beforeHoliday, empty=regularday, ...)
* priority optional integer, new attibute describing if
25.December is treated as holiday or as beforeHoliday
Information of versions < V1.04 could be translated in the new attributes,
but the new structure is more flexible.
5. Elements "xs:any" are included for "train", "entry" and "composition"!
The example shows a way to use them with some additional customer
information. Please verify if this is the proper way to use "xs:any" as it
was proposed in our meeting.
Any feedback would be very useful for the new version 1.1 !!
Regards,
Joachim Rubröder
|
|
|