Home » railML newsgroups » railml.timetable » Wiki documentation for border <ocpTT> between two chained <trainPart>
Re: Wiki documentation for border <ocpTT> between two chained <trainPart> [message #1288 is a reply to message #1286] Thu, 23 July 2015 14:01 Go to previous messageGo to previous message
Burkhard Franke is currently offline  Burkhard Franke
Messages: 5
Registered: October 2014
Junior Member
Hello Christian

thanks for this input. I agree on your point but would not call it a
"recommendation" or "best practice": is there any reason why the border
properties should differ? I cannot think of any.
And how should importing programs deal with contradicting properties
(different station tracks, arrival later than departure, ...) in border
ocps?

So I´d like to raise your point: Exporting programs MUST ensure that
border <ocpTT> do not contain contradictionary information. Otherwise
the railML-file is not (semantically) valid.

Or is this too harsh?

Best regards
Burkhard

--
Burkhard Franke

trafIT solutions gmbh
Heinrichstrasse 48
8005 Zürich

T: (+41)44/271 16 06
F: (+41)44/271 16 08
E: franke(at)trafitch
W: www.trafit.ch

Timetable Stability Analysis: www.OnTime-rail.com
Validation and Visualization of railML data: www.railoscope.com

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Different wiki documentation for rs:places and tt:places
Next Topic: Unclear wiki description of attribute operationalStopOrdered
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Apr 30 02:29:43 CEST 2024