W3C home > Mailing lists > Public > public-wot-ig@w3.org > January 2016

Re: [T2TRG] 3. WoT Thing needs to have meta Band

From: David Janes <davidjanes@davidjanes.com>
Date: Wed, 27 Jan 2016 11:11:16 -0500
Message-ID: <CACp1KyMwR_vr=S06f20Kpq1ydU6uUQpORGMF6yR2EYzkYe+sVg@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Carsten Bormann <cabo@tzi.org>, public-wot-ig@w3.org, "t2trg@irtf.org" <t2TRG@irtf.org>
But the beautiful thing is all that information is there to reason upon.
And now that you mention it, if people start adding energy consumption
profiles to their Models, you can start making clever decisions like you

This is one the reasons I'm big on Linked Data / qnames. If the vocabulary
is not there now, it can be added later. On the other hand if you start
doing things like…

enum ProximitySensorDirection {

…it may never be used, it may be incomplete, and so forth. But when the
time comes to create it (because it's needed), it's easy to drop it in :
it's just URLs.


On Wed, Jan 27, 2016 at 9:39 AM, Michael Richardson <mcr+ietf@sandelman.ca>

> David Janes <davidjanes@davidjanes.com> wrote:
>     > So if you have an old Pentium in the basement that you'd like to
> heat the
>     > room (or the student's computer pool room at Karlsruhe), you can add
>     > "iot-facet:climate.heating" to the metadata facets. When some client
> wants to
>     > heat up the room, they introspect the environment, find that there's
> a device
>     > that (says its) a heater and turn it on.
> But if my goal is to have more computation, and I turn on more computers, I
> might also want to turn off some heating.  Or in the summer, I might want
> to
> use the computers in some place that needs heat, rather than running my
> cooling costs up.
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
Received on Wednesday, 27 January 2016 16:12:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:26:54 UTC