[aprssig] New MSG-OBJ format

[Lynn W. Deffenbaugh (Mr)]

Almost, but if the symbol is optional, then it must be delimited.   
Consider the following (I don't know if they're valid symbols, but 
hopefully you'll get the gist of my concern).  These are the message 
body sent to OBJECT (yes, I'm caving in on POI).

FOOTSORE My Feet Hurt - Is this a symbol of y with M overlay?
FOOTSORE [My] My Feed Hurt - No ambiguity.

ACCIDENT On Route 75 Exit 23 - Is this a symbol of n with O overlay?
ACCIDENT [/.] On Route 75 Exit 23 - Explicit X marks the spot

You get the idea hopefully.  If it's optional, then it needs to be 
unambiguous, but unfortunately also less simple.

Also, obvious to you and me, but worth stating in a specification is 
that there cannot be spaces in the object name!

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

On 2/21/2012 4:06 PM, Bob Bruninga wrote:
> Forget my last email.
>
> I think you are right.  Since only the OBJECT engine needs to understand it,
> lets simplify it down to what you suggest.
>
> SERVER NAME is simply "OBJECT".  MESSAGE OBJECTS are addressed to it.
>
> MESSAGE-OBJECT format is:
>
> NAME /$ TEXT
>
> Where NAME is variable 3 to 9 byte object name
>
> /$ is optional symbol (must be 2 bytes with fore and aft spaces)
>
> And TEXT is any existing APRS subformat or text
>
> Done.
> The message contains a line number (since it is sent by an existing radio)
>
> I have posted this in http://aprs.org/aprs12/msg-obj.txt
>
> Bob, WB4APR
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>