IETF Logo Mail Archive

Re: [Iotsi] interactive vs. programmatic IoT

Michel Kohanim <michel@universal-devices.com> Fri, 25 March 2016 18:10 UTC

Return-Path: <michel@universal-devices.com>
X-Original-To: iotsi@ietfa.amsl.com
Delivered-To: iotsi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A997D12D5A5 for <iotsi@ietfa.amsl.com>; Fri, 25 Mar 2016 11:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=universaldevices.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YAreQfG-U8mF for <iotsi@ietfa.amsl.com>; Fri, 25 Mar 2016 11:10:41 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0702.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::702]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2C2F12D5C1 for <iotsi@iab.org>; Fri, 25 Mar 2016 11:10:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=universaldevices.onmicrosoft.com; s=selector1-universaldevices-com02c; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=M9WmIbmxfDJmrPd0W1oYfocIU0X/oKL3mQ09UiFaLt0=; b=Mkofh4dGH8BZ5tvrxHM3xhz3fe2526UG49adLJh3KsNFvDvLN038EmkLYq+N89a5lDQh92ByYLexswe4y5CjPwwDS/k7NdgkTdHf0g7lxShg3ZUpwOqd+OMmpJQ4xMWPZimUiFzbwddxaXthGX1FTjDEBaFmK+ntfXgPveAduVI=
Received: from SN1PR0201MB1534.namprd02.prod.outlook.com (10.163.129.21) by SN1PR0201MB1535.namprd02.prod.outlook.com (10.163.129.22) with Microsoft SMTP Server (TLS) id 15.1.434.16; Fri, 25 Mar 2016 18:10:24 +0000
Received: from SN1PR0201MB1534.namprd02.prod.outlook.com ([10.163.129.21]) by SN1PR0201MB1534.namprd02.prod.outlook.com ([10.163.129.21]) with mapi id 15.01.0434.023; Fri, 25 Mar 2016 18:10:24 +0000
From: Michel Kohanim <michel@universal-devices.com>
To: "iotsi@iab.org" <iotsi@iab.org>
Thread-Topic: [Iotsi] interactive vs. programmatic IoT
Thread-Index: AQHRhGBdNJkBbWOcLEWXS+VUoQ40oJ9lrL0AgAMNr4CAAAgGgIAAEeYAgAADCLCAAC6WgIAACaLwgADxAT6AAFL1YIAAJnAAgAAAMEA=
Date: Fri, 25 Mar 2016 18:10:23 +0000
Message-ID: <SN1PR0201MB1534F3473C2783A963325BC498830@SN1PR0201MB1534.namprd02.prod.outlook.com>
References: <CABCOCHQpj2wMObJUUAFMAQ1xAtdw08ZRQqtaqwMWre_63RQhpQ@mail.gmail.com> <D40BA8183A12B448ACB9448546032E089C935B71@ORSMSX116.amr.corp.intel.com> <9ef1d2dac4a347c19f989d9dee5efbd9@QEO00410.de.t-online.corp> <SN1PR0201MB15344A90DBBAACA135F0E61398820@SN1PR0201MB1534.namprd02.prod.outlook.com> <CABCOCHRN43QZDVMYeEbLEHetfTEio-Y=MiHkAFEga9cZ59ksMA@mail.gmail.com> <SN1PR0201MB1534EB82A99FAC915D0876D298820@SN1PR0201MB1534.namprd02.prod.outlook.com> <CABCOCHTm0kGqU+MjnA4J0OK-tKmVZAPxjmy7i8cQcKax21hDkg@mail.gmail.com> <SN1PR0201MB1534F8F86D1ED7916176833E98820@SN1PR0201MB1534.namprd02.prod.outlook.com> <2218A00E-2A48-4498-A667-A6F9DF6AA1BB@yahoo.com> <CD7461FB-FC3C-4341-8B28-467FDA444C1F@w3.org> <SN1PR0201MB153477B83FBCBD065B64A32598830@SN1PR0201MB1534.namprd02.prod.outlook.com> <3CB5AB31-FCFD-4D5C-9A30-F2CE26EB6BB5@w3.org>
In-Reply-To: <3CB5AB31-FCFD-4D5C-9A30-F2CE26EB6BB5@w3.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: iab.org; dkim=none (message not signed) header.d=none;iab.org; dmarc=none action=none header.from=universal-devices.com;
x-originating-ip: [75.83.36.12]
x-ms-office365-filtering-correlation-id: 846f3f0e-9577-4674-8ca0-08d354d8bc75
x-microsoft-exchange-diagnostics: 1; SN1PR0201MB1535; 5:G7I1QSmfaJmUYbEAXyS8lOGE4LBDKtZo9jkoeh0MQ8rBYp4oPpEfbWdzyn9aMLXt3+1g/Kbb+zUHjzEmJGDEvKrf+CjhiFch1gud/xSZiCx4v1MQ46wHM8vO90c8H8Z5V5Tkeo7QvEXh9gbL7n8khQ==; 24:ruLgXBz4uZbcgbgHbJY0xif0eCP3Son/Hfwj5eTrM41+ZClMjxHgZbOJBhruak80obwjTtu05+sSct6Zvb1Wp0UJE06oVhnsufuoDrPd44Q=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0201MB1535;
x-microsoft-antispam-prvs: <SN1PR0201MB153587FF052DF05041661AFC98830@SN1PR0201MB1535.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041046)(6043046); SRVR:SN1PR0201MB1535; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0201MB1535;
x-forefront-prvs: 0892FA9A88
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(24454002)(71364002)(54356999)(16236675004)(5004730100002)(81166005)(5640700001)(5002640100001)(5630700001)(11100500001)(50986999)(99286002)(76176999)(15975445007)(2950100001)(2501003)(19609705001)(74316001)(106116001)(19580395003)(2351001)(5003600100002)(3280700002)(122556002)(19300405004)(10400500002)(86362001)(2900100001)(790700001)(77096005)(1220700001)(1096002)(3660700001)(3846002)(586003)(6116002)(5008740100001)(1730700002)(102836003)(19625215002)(2906002)(93886004)(66066001)(450100001)(16601075003)(561944003)(189998001)(33656002)(107886002)(19580405001)(92566002)(19617315012)(87936001)(76576001)(110136002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0201MB1535; H:SN1PR0201MB1534.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR0201MB1534F3473C2783A963325BC498830SN1PR0201MB1534_"
MIME-Version: 1.0
X-OriginatorOrg: universal-devices.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2016 18:10:23.9455 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d628f750-5cc1-4a42-9d4c-463ac737d54f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0201MB1535
Archived-At: <http://mailarchive.ietf.org/arch/msg/iotsi/33bQiH6k_ymH_fJaalRTDe1O6Vo>
Subject: Re: [Iotsi] interactive vs. programmatic IoT
X-BeenThere: iotsi@iab.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Internet of Things Semantic Interoperability Workshop <iotsi.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/iotsi>, <mailto:iotsi-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotsi/>
List-Post: <mailto:iotsi@iab.org>
List-Help: <mailto:iotsi-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/iotsi>, <mailto:iotsi-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2016 18:10:47 -0000

Hi Dave,

Our market is smart building/energy management and I totally agree with you.

With kind regards,

******************************
  Michel Kohanim
  CEO

  (p) 818.631.0333
  (f)  818.436.0702
  http://www.universal-devices.com<http://www.universal-devices.com/>
******************************

From: Dave Raggett [mailto:dsr@w3.org]
Sent: Friday, March 25, 2016 11:09 AM
To: Michel Kohanim <michel@universal-devices.com>
Subject: Re: [Iotsi] interactive vs. programmatic IoT


On 25 Mar 2016, at 15:53, Michel Kohanim <michel@universal-devices.com<mailto:michel@universal-devices.com>> wrote:

I think our proposal, HATEOAS, and IOTDB all address the last part in one form or another. This said, does the consumer really need to know that it’s dealing with a “light” rather than a generic device that supports on/off/dim/brighten/on level/ramp rate/color, etc.?

What kind of consumer are you talking about?  If it is someone living in a smart home, then they will for the most part not be interested in the technical details, and would be much more interested in what a particular company’s products can offer them for controlling their home.  The user interface offered to the end user would adapt to the devices discovered in the home.   On the other hand an application developer would indeed be interested in the capabilities of particular devices and how these could be exploited to provide an innovative service.

—
   Dave Raggett <dsr@w3.org<mailto:dsr@w3.org>>

v2.23.0 | Report a Bug | By Email