(continued from part III)
Over the last year I had hardly time to advance my Perl client to the AllegroGraph tuple server. Which is a shame, as it is fun to take the existing REST interface and to offer it in a perlish mindset.
So when the Perl hackathon (report) was in Vienna these days, and coincidentally also the RDF Perl hackathon Geilo next week, I thought I should use the opportunity to a rub shoulders with the Perl illuminaries, at least for half a day. But when I arrived, everyone was already in deep hacking mode, so I had no excuse but to do programming myself.
The Python client shipped with the distribution is using it, so I wondered how this would pan out in Perl. Pan out on CPAN, so to say. Last weekend I did some tinkering and concocted a first, naive Perl client.
At the moment I'm spec'ing out semantic extensions for an algebraic language for an environment monitoring system. Sensor endpoints send raw measurement data into a concentrator. There these values are value-added, i.e. checked for plausibility and flagged appropriately, maybe re-measured after a new calibration cycle. At a central server the raw data is then aggregated into more abstract concepts, such as a "sliding mean value over the last 6 hours", or "ozon strain on plants". This is where the algebraic language kicks in. It operates on time series.