[aprssig] Proper DIGI Path

[Ron McCoy]

Perhaps, since the community here "discusses, argues and debates" the 
spec, the community should start an open spec of APRS so that all of the 
developers will be working form a known starting point.

This would certainly help interoperability and provide a forum to hash 
out the current ambiguities in the various standards documents.

Stephen H. Smith wrote:
> Robert Bruninga wrote:
>   
>> Yes, everything that goes into the addendums is proposed,
>> discussed, argued, debated ad nauseum and finalized here on the
>> APRSSIG.  Then it is documented in the addendums.  The 1.1
>> addendum was solidified in 2004.  The 1.2 contains additional
>> items since then.
>>
>> Bob, WB4APR
>>
>>
>>   
>>     
>
> There are dozens of copies of the base 1.0 spec on websites all over the 
> world. 
>
> These are not accompanied by the addendums, let alone the awareness that 
> the addendum itself is fragmented into two separate partial documents.   
>
> When is this this stuff going to be merged into a single Ver 1.2 main 
> document?
>
>
>
>
> --
>
> Stephen H. Smith    wa8lmf (at) aol.com
> EchoLink Node:      14400    [Think bottom of the 2M band]
> Home Page:          http://wa8lmf.com  --OR--   http://wa8lmf.net
>
> World Digipeater Map
>   http://wa8lmf.net/APRSmaps
>
> JavAPRS Filter Port 14580 Guide
>   http://wa8lmf.net/aprs/JAVaprsFilters.htm
>
> "APRS 101"  Explanation of APRS Path Selection & Digipeating
>   http://wa8lmf.net/DigiPaths
>
> Updated "Rev H" APRS            http://wa8lmf.net/aprs
> Symbols Set for UI-View,
> UIpoint and APRSplus:
>
>
>
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>