That would require the re-working of every database and logging system
that's out there, now... and, in the case of LOTW, that could bring the
main database down for DAYS, as anyone who's ever had to migrate/modify
datastructures in SQL can tell you... the amount of data that would have to
be converted would mean that nobody would be able to upload logs to QRZ,
LOTW, or eQSL for, potentially, a week or longer while the migration and
restructure takes place, and for software such as HRD or ClubLogger, even
longer....
This isn't a simple DROP TABLE.... this is ALREADY a major data migration
if such a change were to be forced.
...and, for what? So a new operating mode can be its own mode, instead of a
submode of MFSK (which, in actuality, it is just that)?  Technically, FT8
should have been added as a submode of MFSK way back when it was added to
the ADIF spec, but it wasn't.
It's not a fight worth dying over... It is what it is...

de AI8W, Chris


On Wed, Jul 31, 2019 at 2:16 PM Serge Smirnoff R6YY via wsjt-devel <
[email protected]> wrote:

> Dear Dave,
>
> thanks for the comment. Now I will try to guess who is the author of
> this brilliant idea.
> Essentially, this is probably good for the many experimental modulation
> types that periodically appear and immediately die as unclaimed.
> But for the type of FT4, which is preparing to become a major in amateur
> radio communications, this is absolutely unacceptable. It will be
> correct to re-vote back while there is still time. This will be a wise
> decision.
>
> 73, Serge R6YY
>
>
> 31.07.2019 20:10, Dave AA6YQ пишет:
> > + AA6YQ comments below
> >
> > The ADIF committee apparently thinks all software is easy to change and
> should do so to match their intentions.
> >
> > + An interchange specification is by definition dynamic. New digital
> modes are a common occurrence - a trend we should welcome and encourage.
> SUBMODE was added to the ADIF specification 6 years ago. If an application
> can't "keep up" with simple extensions like SUBMODE, either it's poorly
> structured, or its developer is incompetent.
> >
> > We unsuccessfully fought this idea so you'll just have to live with what
> they've done.
> >
> > + The vote on 2019-05-21 to approve ADIF 3.1.0 -- which defines FT4 as
> <MODE:4>MFSK SUBMODE:3>FT4 -- was unanimous, as shown in this announcement:
> >
> > <
> https://groups.yahoo.com/neo/groups/adifvoting/conversations/messages/168>
> >
> > --------------------------------------------------------
> > Do you approve of the ADIF 3.1.0 specification and agree that it is
> ready for publication?
> >
> > Yes 100.00% (14)
> > No    0.00% (0)
> >
> > 14 people voted for "Yes"
> >
> > Nizar Ben Rejeb    3V8MN
> > Dave Bernstein    AA6YQ
> > James Reisert    AD1C
> > Bernd Koch    DF3CB
> > Jordi Quintero    EA3GCV
> > Graham Smith    G3ZOD
> > Terry Genes    G4POP
> > Richard Murphy    K1MU
> > Rick Ellison    N2AMG
> > Scott Davis    N3FJP
> > Dave Morris    N5UP
> > Don Agro    VE3VRW
> > Jim Hargrave    W5IFP
> > Michael Carper    WA9PIE
> > --------------------------------------------------------
> >
> > If you don't recognize the names, the list includes representatives of
> DXLab, eQSL, FLE, HRD, Logger32, Log4OM, LoTW, MacLoggerDX, N3FJP, Sim31,
> and SwissLog.
> >
> >         73,
> >
> >                 Dave, AA6YQ
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to