As a follow-up to my recent note about the ARRL policy
on real-time posting of DXpedition log information, I would like to make it
clear that I recognize the authority of the ARRL and the appropriate officials
to make and enforce policy for the DXCC program. As the developer of DXA for
posting real-time log information from a DXpedition, I am committed to
making DXA operate within the guidelines set by the ARRL.
Of course, I have also said that I believe the basis on
which the recent policy on real-time posting was created is not technically
sound--that there is a negligible amount of cheating that could be enabled by
real-time applications, and that what cheating does occur happens because
the QSL manager has a fairly wide latitude for issuing QSL confirmations.
Furthermore, I am of the strong opinion that a tiny number of cheaters should
not rob the vast majority of DXers from the enhancements that accrue from
real-time operations. On this issue, see http://www.cordell.org/DXA/DXA_survey_2005/responses.html.
However, ARRL is on the right track on one issue: the
QSL manager. For DXA on K7C, the ARRL required us to "make no changes in the log
[during QSLing] in response to requests from DXers." This turned out to be
a very healthy policy, and I believe it should be required of all DXCC
DXpeditions. What is actually meant by "no changes" should be clarified, but I
believe it puts the emphasis and effort for safeguarding the DXCC program where
it belongs--at the QSL manager. The quality of the logs is the responsibility of
the DXpeditioners; the quality of the QSLing is the responsibility of the QSL
manager.
Bob KK6EK
3YØPI, XRØY/Z, VKØIR, XRØX,
K7C
Dr. Robert Schmieder
4295 Walnut
Blvd.
Walnut Creek, CA 94596
(925)
934-3735
[EMAIL PROTECTED]
www.cordell.org
