> <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.
the attributes "type" ('missing', 'overlapping') and "absPosIn" will
become optional with the next major release since this change is not
compatible with railML 2.x.
Regards
--
Christian Rahmig
railML.infrastructure coordinator