What about the SIG tag? Wouldn't it to the job? Which "State" description do you take "first" if there are two descriptions possible? I think it is in SP or OK...
... Hash: SHA1 ... Well, i am new in the list and i don't know all the discussions you have had in previous dates... i like the reason to keep "state" and...
The reason to keep STATE and change its value with DXCC is that the alternative -- a unique field for each country's political subdivisions -- would result in...
... No unique fields for all countries. Where would this end? ... Why can't we keep STATE and CNTY for the US and VE_PROV for VE and use SIG/SIG_INFO for any...
Why is it important to preserve the STATE, CNTY, and PROVINCE fields? No matter how we name the SUBDIVISION fields, the transition can easily be made...
Sig and SigInfo were meant to cover the cases where things like Lighthouses, Ships, Islands, Castles and other collectable things were to be saved. The Sig...
Right Mik. Wasn't this even your proposal? I like the idea since it's all purpose. Yes, we can get rid of VE_PROV: Put "WACP" into SIG and "xx" into SIGINFO...
Rich, Actually, the "Required Fields" in the spec show "Max Width", and do NOT say "Suggested Max Width". The "Optional Fields" DO say "Suggested Max Width"...
... content ... ADIF ... I finally had to weigh in on this aspect. Without ADIF being BOTH a format and a content specification it is on a slippery slope to...
Going back to ADIF Ver. 1.0, there were 4 parts to the specification. Among these were Part 1, "Physical specifications--a specification of how fields and...
I recall no proposal to change that part of the spec. It should be copied verbatim into the 2.X spec; any objections? 73, Dave, AA6YQ ... specification. ... of...
Hi, To reduce the noise a bit, I must say that I do not favor the core record, and explicit data length proposals currently in discussion. BUT I would...
Mike, I agree with you on everything said except the explicit data length proposal. I too would go along with it, but there are some parties involved that...
Perhaps it would be helpful to look at this from a user's perspective. We all know that eQSL.cc accepts up to 240 characters in the QSLMsg field. Our user is...
Tom, I thought your proposal was a good way to cover the situation very well. IRL, In the Real Life, each developer probably will choose to truncate, or ...
Along the lines of Mike's earlier post, let me be clear about my position on this matter. Consider a "value to end-users" scale of 1 to 10. As reference ...
Dave, I appreciate your passion and conviction on the subject! I even agree with your intentions. My concerns are if we raise the bar too high, we'll have a...
... Hash: SHA1 El Miércoles, 5 de Febrero de 2003 05:36, Thomas Dandrea ... IMHO i DO NOT like the "fixed-length" proposal for ADIF2... yes, i have just ...
... Hash: SHA1 El Miércoles, 5 de Febrero de 2003 04:42, Dave Bernstein <dhb@...> ... Why OPERATOR is a required field???? I don't understand why... it...
... Hash: SHA1 Hello all! I have a question about the Entities references in ADIF... How and why are sorted the entities in the table? We have 372 in the adif...
... IF, that is, the "market" dictates that this is really necessary.< Well said Tom. The market dictating this requirement is a very big IF. I am not in...
SNKDavis@...
Feb 5, 2003 12:52 pm
643
Tom, The point here is that if we remove the maximum length nonsense, you won't have to rewrite your application (and more specifically, your database schema)....
Yes, there is a tradeoff. In order to provide more reliable and easier to use functionality for users so that more of them are attracted to our products and...
The intent, I believe, is for ADIF to stay in sync with ARRL DXCC country codes. Around the time we started on ADIF2, there was some confusion from the DXCC...
Wait for markets to dictate requirements is a rather passive strategy, particularly in a technology business. It doesn't always fail, but its not well known...
Dave, 1. I have been using the codes listed on dennis's site; codes assigned by the ARRL came later and are different. 2. The ARRL is too slow assigning these...
Hi, 1. Not sure were the requirement comes from to have OPERATOR as a required field; I do not see the need. 2. Some, maybe most, award issuing organizations...
Are you suggesting that the 10000-series codes that "we" would assign would be temporary until the ARRL assigns a code, at which point users must modify their...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
