--part1_b7.d8765a4.2818e1b7_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Once again, there seems to be questions raised about the cabrillo output from
TR Log. I purchased a computerized logging program so I wouldn't have to
worry about things like this! Users shouldn't have to run every cabrillo
output through a text editor to see if it conforms to the cabrillo spec, but
I'm getting worried that this is, in fact, the case.
In fairness to the software developer, there are many contests and it may be
hard to accommodate all. I would suggest a rigorous verification for each
cabrillo format offered in TR and making the cabrillo output unavailable for
contests that have not yet been verified.
Finally, I don't buy the logic that the output doesn't have to meet the
cabrillo format because the log checking software that checks the logs
overlooks particular format errors. We either have a standard or we do not.
If a log is called a cabrillo log, it should meet the cabrillo specification,
without exceptions. It's as simple as that.
--part1_b7.d8765a4.2818e1b7_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT SIZE=2>Once again, there seems to be
questions raised about the cabrillo output from
<BR>TR Log. I purchased a computerized logging program so I wouldn't have
to
<BR>worry about things like this! Users shouldn't have to run every
cabrillo
<BR>output through a text editor to see if it conforms to the cabrillo spec,
but
<BR>I'm getting worried that this is, in fact, the case.
<BR>
<BR>In fairness to the software developer, there are many contests and it may
be
<BR>hard to accommodate all. I would suggest a rigorous verification for
each
<BR>cabrillo format offered in TR and making the cabrillo output unavailable
for
<BR>contests that have not yet been verified.
<BR>
<BR>Finally, I don't buy the logic that the output doesn't have to meet the
<BR>cabrillo format because the log checking software that checks the logs
<BR>overlooks particular format errors. We either have a standard or we
do not.
<BR>If a log is called a cabrillo log, it should meet the cabrillo
specification,
<BR>without exceptions. It's as simple as that.</FONT></HTML>
--part1_b7.d8765a4.2818e1b7_boundary--
--
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|