[aprssig] APRS device identifiers (tocalls) in YAML, XML and JSON

Georg Lukas georg at op-co.de
Thu Oct 24 08:20:05 CDT 2013


Lynn, both of your points are correct. What I was thinking about are two
things:

a) a strict RegEx subset that is semantically equivalent to the *?n
proposal, maybe just turning "APWM??" into "APWM.." which provides the
same data and is not less readable, while being a regex still.

b) a way to extract the version number, like done by aprs.fi.
Example: APDR12 becomes APRSdroid, version 12 (which is still not quite
correct, because it is in fact version 1.2, but having that indicaiton
helps nevertheless). This was achieved by capture groups in the regex,
which make it less readable but are a very flexible mechanism.

The version extraction is probably not easily possible with *?n, unless
we define the "version" to be whatever we obtain by only extracting the
wildcard matched characters from the to-call - and here we are
reinventing regular expressions again, at the same time making it hard
for people with regex libraries at their hands to extract the version.

73 de Georg DO1GL
-- 
|| http://op-co.de ++  GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N  ++
|| gpg: 0x962FD2DE ||  o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+  ||
|| Ge0rG: euIRCnet ||  X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y?   ||
++ IRCnet OFTC OPN ||_________________________________________________||
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20131024/9425e996/attachment.pgp>


More information about the aprssig mailing list