On Wed, Sep 03, 2008 at 11:38:28AM -0500, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > Curt, > > Er, I'm confused. Was there any discussion or did this arise from > someone giving Bob too much time again? You passed it along without > comment: Do I interpret this as a favorable passage, unfavorable, or > simply informational and without comment?
IMHO this is another randomly generated spec modification by Bob without adequate discussion. It is an attempt to work around the fact that it is currently not possible to push objects through an Igate back to RF. This was in response to some good ideas for APRS applications where queries to certain call signs could generate responses of nearby objects. Since IGates won't pass objects through to RF unless specially configured, but will pass messages for a station heard on RF by that Igate, some means of getting positional data back in response to the query is needed. I'm generally in favor of finding a way to satisfy this, but just going with the first idea that popped into Bob's head doesn't seem like the best approach. APRS is already enough of an inconsistent collection of random good ideas as it is. Perhaps those with enough interest will converge on a well-designed plan on APRSSIG. I suggest we wait until a real consensus is reached. > Curt, WE7U wrote: > > > > ---------- Forwarded message ---------- > > Date: Tue, 2 Sep 2008 11:12:29 -0400 > > From: Robert Bruninga <[EMAIL PROTECTED]> > > Subject: ITEM-in-Message for XASTIR > > > > Please consider adding this to XASTIR: > > > > ITEM-in-Message format: > > > > Over the years, we have identified a capability that is missing > > in APRS, and that is the ability to send an OBJECT to a specific > > person via the global APRS network. Currently we can use APRS > > messages anywhere in the world to anywhere in the world, but > > Igates will only pass messages and not OBJECTS. SO we need to > > add a ITEM-in-MESSAGE capability. > > > > This will be an exciting all-new capability. The format is very > > easy. It is the existing ITEM format, but it is just put inside > > a message instead. It is Human readable so that it can be used > > now and then new firmware and software can parse it. I suggest > > simply what we have now, the ITEM format... > > > > :USER :)OBJNAME!DDMM.mmN/DDDMM.mmW$comments....}LN... > > > > Where :USER______: is the message format > > Where )OBJNA........ Is the ITEM format > > Where }LN... Is the Message Line Number (if used) > > > > ON RECEIPT: The "ITEM-in-MESSAGE" is ACKED and then the "ITEM" > > format is parsed like any other object for display on the > > STATION LIST and on any attached GPS. > > > > I am adding this idea into the new APRS1.2 spec: > > www.aprs.org/aprs12.html > > > > This is very powerful, because with it, we can have SERVERS send > > POSITION info to mobiles who request information. Where is the > > nearest XXXXXX? Then one server anhwere in the world can > > respond with a position-in-message object to that station... > > > > We can also use this with the eventual APRS-VOIP system to FORCE > > the location of the CALLED person to show up on the radio/map of > > the CALLING person. This APRS<==>VOIP is where we have been > > heading for the past many years. See www.aprs.org/avrs.html > > > > > > Thanks > > _______________________________________________ > > Xastir-dev mailing list > > [email protected] > > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev > > -- > Gerry Creager -- [EMAIL PROTECTED] > Texas Mesonet -- AATLT, Texas A&M University > Cell: 979.229.5301 Office: 979.862.3982 FAX: 979.862.3983 > Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843 > > _______________________________________________ > Xastir-dev mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "Argue for your limitations and sure enough, they're yours." -- R. Bach _______________________________________________ Xastir-dev mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
