| new draft V1.1-R1 [message #681] |
Mon, 18 August 2008 14:35  |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hello,
there are some new developments around the timetable schema. As Susanne
showed in the last meetings, there are still unsolved issues around
"operational trains" versus "commercial trains" and "splitting / joining".
So I started a greater restructuring of the timetable schema. A first
draft (Version 1.1-R1) could be seen on the developer side. There is also
a handmade example included in order to get an impression.
Main changes are:
- "trains" as basic train parts with fix "formation" and "operatingPeriod"
- "trainGroups" for commercial/operational trains
- "routeOcps" instead of "timetableentries" and "entry" elements
- "routeSections" instead of "section" elements
- several discarded elements and attributes ("operation", "section",
"intervalTrainID", ...)
- several renamings in "id" and "RefId" to use the common
"tElementWithIDAndName", ...)
- some grouping of the attributes ("trainKind", "arrivalDepartureTimes",
...)
- new attributes "emptyRunning" and "shuntingTime" for rollingstock
circulation purposes
Please have a look at all these changes and let's start a discussion about
them. Or at least give me some feedback.
Kind regards,
Joachim
--
Joachim Rubröder
Schema Coordinator: railML.timetable
|
|
|
|
Members
Search
Help
Login
Home
