This version corrects two typographical errors in the Mode Enumeration: ATB => ATV PAK125 => PSK125 http://groups.yahoo.com/group/adifdev/files/ADIF%20207.htm ...
This may have been asked before, but in the Mode Enumeration, we have "SSB" and do not allow "USB" or "LSB". I would like to include them if possible. 73, Tom...
I have several points to discuss as well -- e.g. why is MTTY a mode? -- but suggest that we first clarify the decision process. To get the ball rolling, I...
- That proposed process sounds OK to me, as long as there is some feedback and follow-up opportunity. - As far as LOTW goes, the latest ARRL bulletin says it's...
Note that in this definition of a MultiLine String: "MultilineString a sequence of Characters and line-breaks, where a line break is an ASCII CR (code 13)...
Dave, Thanks for your work! I agree with your proposal. Make a closure. A week should be sufficient for review of the current proposal, as months have passed...
To be clear, the proposal is that any issue raised by a participant gets one week of air time for discussion and debate; Dave N5UP then makes a decision, which...
Just to expand on my question about adding "LSB" and "USB" to the mode enumeration... I wondered if it had been discussed before, to know if these modes were...
One of the problems with allowing SSB, USB, and LSB is that it leads to inconsistencies in matching. If 2 people have a QSO and one person logs "SSB" and the...
I have set Dave, N5UP, as a group moderator. His continued participation, and involvement are well known to all. This duties are to check on applications, and...
That's correct Dave, SSB, USB, LSB is not the only place were there is problem with alternate mode names. In fact there are quite a few of them. If you are...
This is for YOU if you have not been very active in participating in the ADIFDev group, but you produce any software that relies on the ADIF standard. We got...
Please start re-reading old posts (you can use the "Search Archives" function on the Yahoo web site to narrow you reading) concerning the following issues that...
Dave, We logbook authors can obviously handle conversion from SSB to/from USB and LSB as needed... I propose we let it stand as "SSB" in the ADIF MODE...
Aside from the choice of whether STATE should be backward compatible, and whether to provide a SUBMODE, I think we all agree that the fundamental conflict...
For reasons I've previously articulated, I believe that we should establish a standard length for each field. If increasing the proposed standard lengths makes...
Rather than have separate fields to represent each country's political subdivisions -- states, counties, cantons, provinces, prefectures, guns, oblasts, etc....
Unless someone can provide a good rationale for their existence, I propose that we eliminate FSK and MTTY from the Mode enumeration in ADIF 2.0.7 -- they seem...
ADIF 2.0.7 adds seven fields to characterize the location of the logging station: MY_CNTY MY_COUNTRY MY_GRIDSQUARE MY_IOTA MY_LAT MY_LON MY_STATE To be...
I bowed out of this discussion many months ago, however I feel I must weigh in again. Imposing maximum (and apparently) arbitrary lengths on fields does...
I question whether "camp 1" and "camp 2" do have a disagreement with the Required Fields now in proposed ADIF 2.0.7? I thought the two camps disagreed on the...
To ensure that data can be moved from one app to another without loss, we need to know that both apps conform to a standard representation of each data item; I...
Hello Thomas, Friday, January 31, 2003, 2:34:47 AM, you wrote: I agree TDnesc> We logbook authors can obviously handle conversion from SSB to/from TDnesc> USB...
Friday, January 31, 2003, 4:23:40 AM, you wrote: I agree DA> While I'd personally prefer two new, appropriately-named fields, I'm ok with DA> repurposing STATE...
Hi All, Here are my responses to the request for a vote: - Should State Fields be used only for US States? - Yes - Should ADIF be backward compatible? -...
SNKDavis@...
Jan 31, 2003 11:56 am
608
There is no way that my logging software can accommodate a 32 character callsign or operator field, for example. So there is no way I can support an ADIF 2...
I am not in favor of multiple ADIF formats. You all know how much time we spend explaining the differences to our users between ADIF, Cabrillo, and any other...