## Description The double-defined attributes <baliseGroup>@mileageDirection and <functionalType>@mileageDirection seem to be not clearly defined, proposal to delete and replace with a different attribute <functionalType>@validityDirection. The value of the attribute @applicationDirection "both" is not used, so needs to be removed. ## Background Discussion about orientation of baliseGroup and validity direction of balise telegrams in the forum (see [https://www.railml.org/forum/index.php?t=msg&th=1068&start=0&]). ## Links * Forum discussion * Silvan Gruber, 06.06.2025 : https://www.railml.org/forum/index.php?t=msg&th=1068&start=0& * Wiki documentation * IS:baliseGroup: https://wiki3.railml.org/wiki/IS:baliseGroup ## Proposed solution railML 3.4 It is suggested to: 1. Delete `<baliseGroup>@mileageDirection` and `<functionalType>@mileageDirection` 2. Create `<functionalType>@validityDirection` with the values `"nominal"` or `"normal"`, `"reverse"` and `"both"` (according to UNISIG SUBSET-026, section 7.5.1.103) 3. Update documentation for attribute `@applicationDirection` to only allow two values: `"reverse"` and `"normal"`