Subject: Position Ambiguity [was] Re: [aprssig] findu.com Location off...
Robert Bruninga bruninga at usna.eduMon Jun 12 12:46:13 UTC 2006
- Previous message: [aprssig] APRS & IRLP / Echolink
- Next message: [aprssig] Programming cable for THD700
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yes, the intent of trademarking the APRS name was exactly for that purpose. To discourage short-cut applications that undermine the integrity of the original APRS network from dragging down the network to only the simplest-lowest common denomminator of code. Which is exactly what is happening. Too much code just treats "APRS" as if it is a map plot of ICONS. This overlooks a lot of the complexity of the networking and channel sharing code, hides the RF network from the users, and ignores a lot of the human interface... This makes messaging, instant DFing and other fundamentals of APRS either inefficient or non-existant. de Wb4APR, Bob >>> kc2mmi at verizon.net 06/08/06 2:34 PM >>> Thank you, Bob. I stand corrected then, the APRS spec already provides for this and (as you've said so many times about so many things) it is just so much of the software and hardware out there that is not supporting what you've provided for in the APRS specs. Maybe it is time for you to adopt a new spec, or register a trademark (or is APRS a registered mark?) and simply not allow the use of it to any company not fully meeting a compliancy spec for it. It would be way less confusing if "APRS" meant "fully APRS compliant" rather than "well, some of this stuff is something like what APRS might be".<G> _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
- Previous message: [aprssig] APRS & IRLP / Echolink
- Next message: [aprssig] Programming cable for THD700
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
