AW: [TF-LD] From compact representations to semantic lifting

Hello Kjetil,

since you already use http and JSON, perhaps you could try just to create a Thing Description for your thing (temperature sensors) and store it in Thing Directory (based on a triple store):
http://plugfest.thingweb.io:8081/ 
Discovery and further semantic integration for your thing can go from there on, i.e., one can discover your TD and from there access your temperature sensor (depending on your implementation, maybe you don't need a protocol binding). Further on, you can enrich the TD with semantics from iotschema.org in order to describe your Thing and thus enhance semantic interoperability. For example, you may say my Thing has TemperatureSensing Capability:
https://github.com/iot-schema-collab/iotschema/blob/master/capability.jsonld 
as well as following Interaction Pattern and Data:
Temperature and TemperatureData
https://github.com/iot-schema-collab/iotschema/blob/master/interaction-patterns.jsonld 
For examples of TDs enriched with iotschema, from latest PlugFest in Prague, please see:
https://github.com/w3c/wot/tree/master/plugfest/2018-prague/TDs 

Please also join our bi-weekly web meetings, for example today:
https://lists.w3.org/Archives/Public/public-wot-ig/2018May/0007.html 

Cheers,
Darko Anicic


-----Ursprüngliche Nachricht-----
Von: Kjetil Kjernsmo [mailto:kjetil@kjernsmo.net] 
Gesendet: Dienstag, 24. April 2018 00:25
An: public-wot-ig@w3.org
Betreff: [TF-LD] From compact representations to semantic lifting

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 case?


Code is here, BTW:
https://github.com/kjetilk/arduino_tempmonitor

Cheers,

Kjetil

Received on Friday, 11 May 2018 12:42:34 UTC