CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Public Logs

To: "'Ward Silver'" <hwardsil@gmail.com>,"'CQ-Contest Reflector'" <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] Public Logs
From: "Joe Subich, W4TV" <w4tv@subich.com>
Date: Thu, 13 Dec 2007 19:04:24 -0500
List-post: <mailto:cq-contest@contesting.com>
Ward, 

DXCC rules prohibit publishing complete logs. In the end, the 
publishing of complete logs could result in disallowance of 
DXCC credit for "contest DXpedition" QSOs and ultimately the 
disqualification from DXCC for anyone who regularly participates 
in contests which make logs public.   

see: http://www.arrl.org/blog/DXCC%20Dialog?ofst=25
and: http://www.arrl.org/blog/DXCC%20Dialog?ofst=30 

Of particular interest: 
  
  > The presentation in any public forum of logs or other 
  > representations of station operation showing details of 
  > station activity or other information from which all 
  > essential QSO elements (time, date, band, mode and callsign) 
  > for individual contacts can be derived creates a question 
  > as to the integrity of the claimed QSOs with that station 
  > during the period encompassed by the log. Presentation of 
  > such information in any public forum by the station operator, 
  > operators or associated parties is not allowed and may be 
  > considered sufficient reason to deny ARRL award credit for 
  > contacts with any station for which such presentations have 
  > been made. Persistent violation of this provision may result 
  > in disqualification from the DXCC program.
   
Please note the prohibition of disclosing the complete log info 
by even "associated parties."  I would certainly include contest 
sponsors as "associated parties."  It's up to those sponsors to 
properly analyze their logs for potential rules violations but that 
analysis process MUST NOT include requiring the participants to 
violate the rules of the DXCC program (or any other program) by 
making the entire log public.  

Any contest sponsor who makes complete logs public should be 
censured by the entire amateur community.  

73, 

   ... Joe, W4TV 
 


> -----Original Message-----
> From: cq-contest-bounces@contesting.com 
> [mailto:cq-contest-bounces@contesting.com] On Behalf Of Ward Silver
> Sent: Thursday, December 13, 2007 4:44 PM
> To: CQ-Contest Reflector
> Subject: [CQ-Contest] Public Logs
> 
> 
> > Not on your life!  My log is my log - I make it available to the
> > contest sponsor for checking as a condition of entry but it is NOT
> > public and should never be made public.  There is no reason for it
> > to be made public.
> 
> You may choose not to share the details of your station or 
> your methods of 
> operation that can not be deduced from a public record of 
> your QSO's. But 
> all of the contacts were completely public. When it comes to 
> activities 
> conducted over the airwaves of Amateur Radio, the concept of 
> "private" ends 
> at the antenna.  This is by definition - both of physics and 
> of regulation - 
> and has nothing to do with what is in your submitted log.
> 
> The day is rapidly approaching when any station's activities 
> on the air will 
> be trackable in real-time and recorded for posterity.  All it 
> takes is a few 
> receivers sprinkled around the globe with software to decode 
> the various 
> transmissions.  Admittedly, unraveling a pileup may take a 
> little longer, 
> but technology is moving quickly.  With enough submitted QSO's, I can 
> reconstruct your log whether you submit one or not. This is 
> not a good hobby 
> for anyone that isn't comfortable being visible.
> 
> The very concept of a "private log" of anything involving a radio 
> transmission is on its last legs.
> 
> 73, Ward N0AX 
> 
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
> 
> 

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>