Clarify balise attribute 'staticTelegram'

Description

The usage of the attribute @staticTelegram need to be revised.

Background

As Volker Knollmann suggested on a wiki page, the balise attribute staticTelegram has to be further clarified: "Coded? Uncoded? Binary? Plaintext?"

Links

• Forum discussion
  • Christian Rahmig, 07.10.2024: https://www.railml.org/forum/index.php?t=msg&goto=3332&#msg_3332
• Trac ticket
  • #163 (closed)
• Wiki documentation
  • IS:baliseGroup: https://wiki3.railml.org/wiki/IS:baliseGroup

Proposed solution in railML 2.4

The attribute @staticTelegram shall be used for storing the binary data telegram in a HEX string. Thus, it is proposed to restrict the string data type to a HEX pattern: [0-9a-fA-F]*

Proposed solution in railML 3.x

For railML 3.x the whole topic of balise telegrams need to be re-evaluated and aligned with the user needs formulated in the railML use cases (e.g. in interlocking domain).