[aprssig] Deprication/abandonment of the X1J exception

[Lynn W. Deffenbaugh (Mr)]

I read that exception and decided to implement it if I ever saw it in a 
packet.  In  my 3 years of inspecting non-parsed APRS packets, I've 
never seen a single instance of this exception from the APRS-IS nor from 
any of the APRSISCE/32 RF monitor stations.  Therefore it is not 
currently implemented in my client application and I would actually be 
relieved it were to go away.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/3/2012 10:08 AM, Steve Dimse wrote:
> On Jan 3, 2012, at 9:54 AM, Bob Bruninga wrote:
>
>> Would anyone object to abandonment/deprication of the X1J exception?
> The many oddball exceptions in the spec have only been implemented on request in findU. If no one ever complained that their X1J was not getting parsed correctly it would not have been implemented. It is not implemented on findU. If anyone has used it in the last decade they did not check their posit on findU.
>
> Steve K4HG
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>