- From: David Janes <davidjanes@davidjanes.com>
- Date: Wed, 27 Jan 2016 11:17:25 -0500
- To: Carsten Bormann <cabo@tzi.org>
- Cc: "t2trg@irtf.org" <t2TRG@irtf.org>, public-wot-ig@w3.org
- Message-ID: <CACp1KyM1t2TpQViDUb3qcBOhKMAaaCNOWuRZuFZTbkQU3MkgYA@mail.gmail.com>
In particular, I'll refer you to the WeMo case in the document at the start of this email thread. _Somehow_ you're going to have to be associate the fact that "this wemo is controlling a light" and "this other wemo is connect to a space heater". This is a real problem that exists today if you want to be able to say "turn on all the lights in the living room" or "turn off all the heaters in the basement". I'm hoping I'm not confusing things when I say that the metadata band doesn't have to live on the device. It can be a URL "out there" somewhere. I'm trying to keep the ideas flexible enough that evolve based on how people will actually use stuff in the future. D. On Wed, Jan 27, 2016 at 10:12 AM, Carsten Bormann <cabo@tzi.org> wrote: > David Janes 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. > > That assumes that (1) I have control over the metadata and (2) I think > about doing that. Generally, the discovery/metadata component will work > best if it can do its work while unattended. So I'm not sure I want to > be adding facets to things continuously. (But maybe there is no way > around that fusing metadata from multiple sources, and one of those may > be the user that is trying to achieve some effect.) > > Grüße, Carsten >
Received on Wednesday, 27 January 2016 16:18:13 UTC