+ AA6YQ comments below
But the original intent as was discussed on the ADIF list was that the SUBMODE
field was to allow new modes to be added there before the committee needed to
approve them.
+ The original intent was to enable the Secretary of ADIF to add support for a
new mode to ADIF without requiring a discussion and vote.
SUBMODE was to have a "suggested" enumeration.
They changed the meaning of it...because they named it incorrectly and somebody
started interpreting it as a propagation mode label.
+ No one ever misinterpreted SUBMODE to mean "propagation mode".
+ The primary issue was that some ADIF participants wanted to ensure that each
new mode's MODE-SUBMODE representation was technically precise. "Should FT4's
parent MODE be MFSK or GFSK?", for example. The resulting controversies led the
Secretary of ADIF to require a discussion and vote for each new mode
representation.
+ The secondary issue is that some mode developers felt that having their new
mode represented with a MODE-SUBMODE combination was somehow less derogatory
compared with modes represented by MODE alone.
+ The bottom line is the MODE-SUBMODE combination is simply a string of
characters that unique identify a mode when information about a QSO is moved
from one amateur radio application or another. Since users occasionally view or
edit this information, we choose recognizable representations like <MODE:4>RTTY
or <MODE:4>MFSK <SUBMODE:3>FT4 rather than <MODENUMBER:3>345. These
representations are only used for conveying information among applications;
they have no impact on an application's user interface or functionality.
73,
Dave, AA6YQ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
