hey openguides,
now i'm static again for a bit, thinking about the openguides for consume.net project again. we have a dedicated box for consume.openguides, and any manner of mapping and wireless stuff. it's a quad xeon SGI that lives at deckspace. all it has now is an IP - 81.3.72.69
i'm wondering if it would be poss to set up an A record for it, so it can be consume.openguides.org ? then, it can be openguides.consume.net too, when the time comes. matt's sysadmining it, ask him for accounts...
what we actually doing with it for consume? partly replacing the twiki, partly making a comments+better mapping interface for the nodedb. wondering about best way to differentiate wireless node wiki nodes, from documentation wiki nodes - hex had some ideas at one point...
i'm planning to make a very simple RDF/XML interface, a POE or mod_perl job, to the current nodedb once we get a copy of the data - the usual mysql-based triplestore with Squish.pm - just as an intermediate interface, and because i have that code already.
i'm also thinking about patching the RSS bit of CGI::Wiki, to look at the category bit of the node - i wrote a tt-based simple RDF serialiser the other week - mmm sudden dreams of autogen an ontology from the category hierarchy again - anyway. i could do with some advice on packaging multiple modules in one package for CPAN, and figuring out where and how to install templates... for an RDF::Simple package with parser and serialiser
elsewhere, i'm tweaking people about SVG mapservers and extrapolating shapes from GPS traces and annotating them, etc. i hope i'm actually making sense in front of the geowankers.
bounce bounce,
zx -- "Common sense won't tell you. We have to tell each other." -DNA