----- Original Message ----
May I make a small suggestion?
Why not put an RST of "00(0)" in the submitted log instead?
---------------------------
In this case, the Cabrillo-spec doesn't view RST as a placeholder. A
placeholder, by Cabrillo-spec inference, is <space>.
Thinking strategically (not tactically)... if an event claims to allow
Cabrillo-formatted submissions, then the thought flow goes something like
this...
A. A sponsor should require participants to submit logs that accurately
reflect their activity. This is the only way to accurately adjudicate an event
and provide historical accuracy. Follow the Cabrillo spec when determining how
to apply it to their event. Do not stray from the spec.
B. Software authors should generate Cabrillo-formatted submissions that comply
with both the Cabrillo-formatting spec and the sponsor's Cabrillo-compliant
"data-to-include" spec. Data is placed by column and placeholders are spaces.
C. Robot authors should parse in accordance with the spec. QSO data is to be
found in fixed locations within a fixed-length QSO field.
D. Sponsors and their Robots should reject files (both from authors and
submitters who use authors products) that fail to comply. "Dumbing down" the
spec because some folks can't follow specs injects unnecessary turmoil on many
levels.
E. If the Cabrillo-format spec or the sponsor's "data-to-include" spec are
ambiguous, then there should be a safe mechanism to offer meaningful
well-intended input and eventual resolution (without individuals taking things
personally).
Again, this is strategic (planning that avoids later problems) thought, not
tactical (executing an idea) thought.
Sincere kind regards to all,
Ev, W2EV
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|