Home » railML newsgroups » railml.timetable » [railML 3] Clarification regarding unused DistanceBasedCalculationRule element
[railML 3] Clarification regarding unused DistanceBasedCalculationRule element [message #4084] Mon, 20 July 2026 15:21 Go to previous message
Ricardo Subtil is currently offline  Ricardo Subtil
Messages: 1
Registered: July 2026
Junior Member
Good afternoon!

While working on import functionality of railML 3.2 timetable schema for our software, I noticed the existence of a DistanceBasedCalculationRule element in the railML 3.2 schema. It looks to be entirely unused, but judging by its semantics, it appears to be a specialization of another rule element for followup sections and calculated reserve times, akin to the existing timeBasedRule.

We would like to use this element as is currently in the schema, since it fits our use-case nicely, without modifications necessary. When communicating calculated reserve times, we need to document the original distance based property for our software to reconstruct the information at import time. Here's an example of how we would use this element in an actual railML export:

<!-- 5 minutes -->
<reserve reserve="PT5M">
  <rule>
    <!-- 10 minutes every 100 kilometres (100000 metres) -->
    <distanceBasedRule referenceDistanceMeters="100000" supplement="PT10M" />
  </rule>
</reserve>

The only extension we would require in our software would be to allow this element to be present in the rule element. However we need some clarification if this element should be used as I described. While I believe we have a legitimate use-case for it, it was also subsequently deleted from the upcoming 3.4 version, suggesting a deprecation path.

Kind regards,
Ricardo Subtil
 
Read Message
Read Message
Read Message
Previous Topic: [railML 3] LTP and STP Variants
Next Topic: [railML3] identifierRange in PatternTrain
Goto Forum:
  


Current Time: Tue Sep 15 11:42:47 CEST 2026