Home » railML newsgroups » railml.timetable » values 'earliest' and 'latest' of <ocpTT>.<times>.@scope
Re: values 'earliest' and 'latest' of <ocpTT>.<times>.@scope [message #1928 is a reply to message #1848] Mon, 27 August 2018 15:28 Go to previous message
Heribert Neu is currently offline  Heribert Neu
Messages: 7
Registered: January 2018
Junior Member
Hello Dirk,

I agree with your assumptions. Earliest and latest are data from the order process.

The times should still be kept in one place <times>, even if they are not expected or present at all ocpTT in some use cases. Therefore earliest and latest should not be declared as deprecated.

As a consequence, however, only an example of the use of earliest and latest in the wiki needs to be added. I do not believe that anything needs to be legalized.

Best Regards
Heribert
 
Read Message
Read Message
Previous Topic: stopDescription: New enumeration value 'none' for attribute onOff in railML 2.4
Next Topic: train stablings
Goto Forum:
  


Current Time: Mon Oct 14 14:26:35 CEST 2024