IETF Logo Mail Archive

Re: [Iotsi] interactive vs. programmatic IoT

"Kreuzer, Kai" <k.kreuzer@telekom.de> Thu, 24 March 2016 15:50 UTC

Return-Path: <k.kreuzer@telekom.de>
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 3205312DDBC for <iotsi@ietfa.amsl.com>; Thu, 24 Mar 2016 08:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.229
X-Spam-Level:
X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 CW1ujbQjIcl9 for <iotsi@ietfa.amsl.com>; Thu, 24 Mar 2016 08:50:41 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94B6E12DC22 for <iotsi@iab.org>; Thu, 24 Mar 2016 08:37:32 -0700 (PDT)
Received: from q4de8ssaz61.gppng.telekom.de ([10.206.166.200]) by tcmail21.telekom.de with ESMTP/TLS/DHE-RSA-AES128-SHA; 24 Mar 2016 16:37:30 +0100
X-IronPort-AV: E=Sophos;i="5.24,385,1454972400"; d="scan'208,217";a="910968239"
Received: from unknown (HELO qeo40064.de.t-online.corp) ([10.224.209.65]) by q4de8ssaz61.gppng.telekom.de with ESMTP/TLS/AES128-SHA; 24 Mar 2016 16:37:29 +0100
Received: from QEO00411.de.t-online.corp (10.224.209.111) by QEO40065.de.t-online.corp (10.224.209.65) with Microsoft SMTP Server (TLS) id 8.3.406.0; Thu, 24 Mar 2016 16:37:27 +0100
Received: from QEO00410.de.t-online.corp (10.224.209.110) by QEO00411.de.t-online.corp (10.224.209.111) with Microsoft SMTP Server (TLS) id 15.0.995.29; Thu, 24 Mar 2016 16:37:26 +0100
Received: from QEO00410.de.t-online.corp ([fe80::b0a0:1946:1239:7a98]) by QEO00410.de.t-online.corp ([fe80::b0a0:1946:1239:7a98%12]) with mapi id 15.00.0995.031; Thu, 24 Mar 2016 16:37:27 +0100
From: "Kreuzer, Kai" <k.kreuzer@telekom.de>
To: "Subramaniam, Ravi" <ravi.subramaniam@intel.com>, Andy Bierman <andy@yumaworks.com>, "iotsi@iab.org" <iotsi@iab.org>
Thread-Topic: [Iotsi] interactive vs. programmatic IoT
Thread-Index: AQHRhGBdNJkBbWOcLEWXS+VUoQ40oJ9lrL0AgAMNr4A=
Date: Thu, 24 Mar 2016 15:37:26 +0000
Message-ID: <9ef1d2dac4a347c19f989d9dee5efbd9@QEO00410.de.t-online.corp>
References: <CABCOCHQpj2wMObJUUAFMAQ1xAtdw08ZRQqtaqwMWre_63RQhpQ@mail.gmail.com> <D40BA8183A12B448ACB9448546032E089C935B71@ORSMSX116.amr.corp.intel.com>
In-Reply-To: <D40BA8183A12B448ACB9448546032E089C935B71@ORSMSX116.amr.corp.intel.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.224.192.134]
x-esetresult: clean, is OK
x-esetid: 16A13A3EA95BF6E543E764
Content-Type: multipart/alternative; boundary="_000_9ef1d2dac4a347c19f989d9dee5efbd9QEO00410detonlinecorp_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/iotsi/-uSDTk3pQJYzZC5wknj_i_9SDGI>
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: Thu, 24 Mar 2016 15:50:55 -0000

Hi,

I fully second Ravi on this – the ultimate goal is that algorithms can make “sense” out of the services that they find. Being able to only operate through UIs pushes the semantic knowledge” onto the user, so I would not even talk about semantic interoperability, but rather “only” about technical interoperability (see also the second half of my blog post here<http://kaikreuzer.blogspot.de/2016/03/semantic-interoperability-in-internet.html>).

> HATEOAS doesn't really help here

I do not agree on this. The idea of having the links on the resources is to make them self-descriptive and navigatable. So algorithms should be able to dynamically “discover” what the service is about and use it adequately without any prior knowledge. But Matthias is probably the best person to comment on this.

Best regards,
Kai

Von: Iotsi [mailto:iotsi-bounces@iab.org] Im Auftrag von Subramaniam, Ravi
Gesendet: Dienstag, 22. März 2016 18:49
An: Andy Bierman; iotsi@iab.org
Betreff: Re: [Iotsi] interactive vs. programmatic IoT

Hi Andy,

IMHO, for IOT to be successful it would be primarily (what you are calling) “programmatic clients” – most *useful* IOT systems would tend to be relatively or fully autonomous with human interactions at the “periphery” of such systems.

OCF has called out that it is “declarative and late binding” because the expectation is that a “human” would declare “what” they wanted the system to be and its objectives and the rest is done by autonomous interactions of “programmatic participants” (well… at this stage, OCF spec is in the “crawl” stage so this ‘vision’ is hard to see but the basic concepts support this direction ☺ )

Ravi

From: Iotsi [mailto:iotsi-bounces@iab.org] On Behalf Of Andy Bierman
Sent: Tuesday, March 22, 2016 10:29 AM
To: iotsi@iab.org<mailto:iotsi@iab.org>
Subject: [Iotsi] interactive vs. programmatic IoT

Hi,

It seems to me that the use-cases discussed at the meeting
assume there is a human with access to UI driving the client.

Does this mean use-cases which do not assume any human interrupts
are possible are not IoT, but something else? In this environment
everything is usually programmed in advance. HATEOAS doesn't
really help here.  It is not likely the client can make decisions
about code-points it has never seen before.

Are there any expectations that IoT includes programmatic clients
or is it just for interactive clients?


Andy

v2.23.0 | Report a Bug | By Email