Dirk Bräuer Messages: 311 Registered: August 2008
Senior Member
Dear Christian,
since we have agreed in the meantime that the assumptions and examples on
mileageChanges are generally right, there are some small changes still to
do for RailML 2.2:
<mileageChange>.type should become optional (not applicable in all cases,
not at the beginning of a track)
<mileageChange>.absPosIn should become optional (not applicable at the
beginning of a track, redundant in all other cases)
Please close this issue by providing track ticket for these changes for
RailML 2.2.