13 Jan
2015
13 Jan
'15
3:48 p.m.
Thanks Joachim and Peter for your quick replies.
My initial thoughts were similar to what Peter is suggesting but I'm currently
rethinking this and have the idea that this can be done in a more elegant way.
I'm still very much in brain storm mode for this so maybe the ideas seem a bit wild or
not well thought through but I would like to share some of my initial thoughts because
some of this ideas might have been discussed before.
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)?
That was my initial idea but what I do not like about this solution is that it is a rather
arbitrary list and is left open to developers and users of the XEP on what to implement /
use. I rather would use a solution were users can 'discover' the semantics that a
registry is supporting. For example, add something to the discovery message of the
registry that has information about the supported ontology.
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:
<str name=’NAME’ url=’ http://www.w3.org/2000/01/rdf-schema#label’
value=’Ohlsson’/>
I'm thinking about having something like:
<property name='man' value='www.ktc.se'/>
or
<property name='man'
resource='http://www.manufacters.com/sweden/ktc'/>
In RDF terms the 'Thing' would be the subject of the RDF triple, 'man'
would be the property that would either have a property value or would link to another
resource. Datatypes would be irrelevant IMO.
(Not to say that the NAME tag should correspond to
rdfs:label, it’s just an example.)
As for SPARQL I would really like to have a way to send these queries inline XMPP so as a
add-on or replacement for the current 'query language'.
Thanks,
Eelco
This message may contain information that is not intended for you. If you are not the
addressee or if this message was sent to you by mistake, you are requested to inform the
sender and delete the message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind resulting from the risks
inherent to the electronic transmission of messages.