Home » railML newsgroups » railml.timetable » railML 3.x TT: Times vs. Durations in itineraries
railML 3.x TT: Times vs. Durations in itineraries [message #1534] Fri, 24 March 2017 10:34
Leopold Kühschelm is currently offline  Leopold Kühschelm
Messages: 8
Registered: September 2015
Junior Member

After our discussion yesterday in the developer conference about
ocpTT.stopDescription I have reviewed the elements there and how the
might map onto information in railML 3.x timetable approach.

So I came accross the definitions of absolute times and durations and
have seen that the use-cases:
http://wiki.railml.org/index.php?title=TT:UC:TimetableInform ation
http://wiki.railml.org/index.php?title=TT:UC:PassengerInform ationAtStations
http://wiki.railml.org/index.php?title=TT:UC:ATimetableForAC ompetition

use as well ocpTT.times (xs:time) elements and the elements
ocpTT.stopDescription.stopTimes, ocpTT.sectionTT.runTimes with durations
(xs:duration). In my opinion it is then not quite clear how durations
and times interact with each other. Therefore please specify why the
use-cases needs both - absolute times and durations -
and which is the main reference for the usecase or how they interact in
other ways.

Thanks in advance,
Previous Topic: Request for feedback for railML 2.4
Next Topic: Topologie-Stichtag / Topology reference date
Goto Forum:

Current Time: Sun Jan 21 23:17:53 CET 2018