> ---------- 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:
Setting up messages as wrappers for formatted data like this sounds plausible, if potentially problematic, to me. I do have some questions. www.aprs.org/aprs12.html is timing out for me right now, so many of these may be answered there. 1) Can any message contain one or more ITEM-in-MESSAGE lines (do we need to parse each line of each message to check for items), or is there a way to identify that a particular message contains items. 2) Can a message contain more than one ITEM-in-MESSAGE? (A response to a where are the nearest ten repeaters sort of query). If so, what is the limit to the number of items in a message? 3) Can a message contain both message text and ITEM-in-MESSAGE? 4) Is the query for an ITEM also a message (is ITEM-in-MESSAGE an adhoc extension of messaging, or are messages being used as a wrapper for another protocol (and how well defined is that protocol)? In either case, can a message wrap more than one thing (with implications for parsing)? 5) Object names, at least in Xastir's db (DataRow.call_sign), are treated as unique identifiers for objects/items. What potential exists for confusion between different objects of the same name? 6) The comment field in the current spec is currently defined as able to contain any printable ACSII characters except | and ~ (pipe and tilde), so how do we tell the difference between comment content containing a } followed by a number from the }LN line number terminator? >Where }LN... Is the Message Line Number (if used) Merry Snailing, -Paul -- Paul J. Morris Biodiversity Informatics Manager Harvard University Herbaria/Museum of Comparative Zoölogy [EMAIL PROTECTED] AA3SD PGP public key available _______________________________________________ Xastir-dev mailing list Xastir-dev@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
