W3C home > Mailing lists > Public > public-wot-ig@w3.org > April 2018

[TF-LD] From compact representations to semantic lifting

From: Kjetil Kjernsmo <kjetil@kjernsmo.net>
Date: Tue, 24 Apr 2018 00:25:06 +0200
To: public-wot-ig@w3.org
Message-ID: <8041058.A4sKm7Jggf@owl>
Hello again!

I've been working a bit again on the energy system in my house, also as an 
exercise for IoT. I have working an Arduino Uno with some temperature 
sensors, mostly around a heat exchanger, and I'd like to monitor the 
efficiency of heat exchanger. There exists a formula for that. :-)

I have a minimal HTTP server on it, and the response is simply a JSON with 
the sensor ID as a key and the temperature as the value. Compact enough, I 
think. But being a semwebber, I'd like to have applications use RDF, so at 
some point, I would like to perform some semantic lifting. 

Obviously, it is pointless for an RDF template to reside on the Arduino, a 
key challenge is to attach knowledge about the data to them. In some cases, 
like mine, the semantics shouldn't be very far from the microcontroller, 
since those who implemented that also has immediate knowledge about the 
data. So, I would like to see a mechanism where I can connect both the TD 
and the semantic lifting from the Arduino.

I was thinking about this in terms of protocol bindings, primarily. For 
HTTP, a Link header seems to come naturally, whereever the knowledge sits, 
a Link header is inserted pointing to the TD and the semantic lifting, and 
so a processor could create RDF data. In my case, I would have the Link 
header in the flash of my Arduino. I'm not too familiar with other 
protocols, though I have realized there is a whole zoo out there. 

I'm not sure how far the LD task force has gotten in their work, but I 
figured I'd share these thoughts now, perhaps they be the beginning of a use 

Code is here, BTW:


Received on Monday, 23 April 2018 22:25:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 April 2018 22:25:47 UTC