Hello Eelco

Would it be sufficient to map tag names to corresponding predefined semantic URLs? So that tags defined in XEP-0347 §5.2 also had a column with predefined semantic URLs, one for each tag (if available)?

Searching using SPARQL should be possible anyhow, if you have a SPARQL endpoint on your server. Tags could be identified by URLs of the following type. ROOM could correspond to URI urn:xmpp:iot:discovery:tags:room, for instance. If you want a HTTP-based URL, you could prefix the tag with the URL pointing to the server, like http://thingk.me/tags/room (and then provide some simple RDF when performing a GET to the corresponding URL).

Would that be sufficient?

Or do you want the sensor to register and update semantic URLs from the beginning? Perhaps as an optional parameter to the <str> and <num> tags? As follows:

(Not to say that the NAME tag should correspond to rdfs:label, it’s just an example.)

Best regards,

Peter Waher

From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl]
Sent: den 13 januari 2015 09:32
To: XMPP in the Internet of Things
Subject: [IOT] Semantic searches in registry

Hi,

I was wondering if anyone has considered of adding semantics to the IoT XMPP specs?

I’m particularly interested in ways to add semantics to the IoT discovery XEP.

Paragraph 5.2 of the XEP (https://xmpp.org/extensions/xep-0347.html#tags) describes a set of meta tags that can be used to describe things as it does put some limits on the values you can set. But I would like to link the meta-data to some sort of semantic ontologies (RDF). I then want to use that data to enable ’smarter’ queries to the registry (ie. sparql like queries).

Is there any known work in this area?

If I have any results of myself in this field I will share it on this list.

Thanks,

Eelco

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4794 / Virus Database: 4257/8886 - Release Date: 01/07/15