Clarify balise attribute 'staticTelegram'
The usage of the attribute @staticTelegram need to be revised.
As Volker Knollmann suggested on a wiki page, the balise attribute staticTelegram has to be further clarified: "Coded? Uncoded? Binary? Plaintext?"
- Forum discussion
- Trac ticket
- Wiki documentation
- Balise: [http://wiki.railml.org/index.php?title=IS:balise&stable=0]
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).