Re: [Iotsi] Fwd: Save the date: July 15/16, 2017: Workshop on IoT Semantic/Hypermedia Interoperability (at IETF99 in Prague)
Benoit Claise <bclaise@cisco.com> Fri, 05 May 2017 08:31 UTC
Return-Path: <bclaise@cisco.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 A9BAA12949A for <iotsi@ietfa.amsl.com>; Fri, 5 May 2017 01:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 aStsRX7Oun8C for <iotsi@ietfa.amsl.com>; Fri, 5 May 2017 01:31:20 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BE97129486 for <iotsi@iab.org>; Fri, 5 May 2017 01:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21841; q=dns/txt; s=iport; t=1493973079; x=1495182679; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=gBD5S2bIEFWQMrlHzNmPpPs6MI4CjPiIN+CiQIIcai0=; b=UniEGqqTqSjhGJOGi5n2eBhXmi7jObzG0HLWn53fXPJkQx99+DXD3x+K u5Dt6r4VxbJkf59aw6nxeU4NenplSTVoFZweYTFrlbTR+n5l3t98wXl5j vixorr73ivWUhs7pqqDHORIUrLj39Rf7e1yj8L1mnVcFmwgLNv8CPSu7U 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BMAQDRNwxZ/xbLJq1cGQEBAQEBAQEBAQEBBwEBAQEBhDeBDINoihhzkEMhkRGEX4IPAh8BCoV4AoUFGAECAQEBAQEBAWsohRUBAQEBAgEBARsGSwYFEAkCDgMDAQIkBAMCAicfCQgGAQwGAgEBihQIDpQNnDACgS+CJiuKOwEBAQEBAQEBAQEBAQEBAQEBAQEBAR0yhi2BXisLgmWBPINHFoJQgl8BBJ1vhxuLfIIEhTmDQ4ZojAqDfoQvDxA4gQouIAgZFUaEcwwQGYFMPjaIdQEBAQ
X-IronPort-AV: E=Sophos;i="5.38,291,1491264000"; d="scan'208,217";a="651636252"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 May 2017 08:31:16 +0000
Received: from [10.60.67.90] (ams-bclaise-8919.cisco.com [10.60.67.90]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v458VFTp032040; Fri, 5 May 2017 08:31:16 GMT
To: Carsten Bormann <cabo@tzi.org>, iotsi@iab.org
Cc: t2trg-chairs@irtf.org
References: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> <D94C28D9-C868-46EC-8806-FF9173CFDD8C@tzi.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <b0b49dc3-c034-9158-3f07-df56e983f642@cisco.com>
Date: Fri, 05 May 2017 10:31:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <D94C28D9-C868-46EC-8806-FF9173CFDD8C@tzi.org>
Content-Type: multipart/alternative; boundary="------------F05676AD4340A1397892EF2B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotsi/tipdTnolfgy5bcMkpirunCVuDCY>
Subject: Re: [Iotsi] Fwd: Save the date: July 15/16, 2017: Workshop on IoT Semantic/Hypermedia Interoperability (at IETF99 in Prague)
X-BeenThere: iotsi@iab.org
X-Mailman-Version: 2.1.22
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, 05 May 2017 08:31:24 -0000
Carsten, I would love to participate to discuss the data modeling aspects. However, the IETF hackathon and its code take precedence. Regards, Benoit > The workshop announced below is somewhat of a logical continuation of > what we did in Santa Clara in March 2016. > So you may be interested to contribute and to participate. > We haven’t sent out the formal call for contributions yet, but the > below should give the direction of what we need. > Please register at the address given, and send the T2TRG chairs (in > CC) ideas of what you want to contribute. > > Grüße, Carsten > > >> Begin forwarded message: >> >> *From: *Ari Keränen <ari.keranen@ericsson.com >> <mailto:ari.keranen@ericsson.com>> >> *Subject: **Save the date: July 15/16, 2017: Workshop on IoT >> Semantic/Hypermedia Interoperability (at IETF99 in Prague)* >> *Date: *May 4, 2017 at 17:45:46 GMT+2 >> *To: *"t2trg@irtf.org <mailto:t2trg@irtf.org>" <t2trg@irtf.org >> <mailto:t2trg@irtf.org>>, "public-wot-ig@w3.org >> <mailto:public-wot-ig@w3.org>" <public-wot-ig@w3.org >> <mailto:public-wot-ig@w3.org>> >> *Cc: *Carsten Bormann <cabo@tzi.org <mailto:cabo@tzi.org>> >> >> Save the date July 15/16, 2017 for Workshop on IoT >> Semantic/Hypermedia Interoperability, in Prague at IETF99. >> >> See the description below and up to date information with >> registration instructions here: https://github.com/t2trg/2017-07-wishi >> >> >> Cheers, >> Ari & Carsten >> >> >> One of the interesting questions in the IoT space is the role of >> hypermedia and/or semantic interoperability for reducing setup >> overhead and thus TCO, and, more generally, enabling interoperation >> in the first place. >> >> For example, OMA and IPSO smart objects use the LWM2M object model, >> which defines a set of pre-structured URI templates and registry of >> object identifiers with semantics attached. This provides machine- >> readable representations of the semantics, but self description is >> not being used much. >> >> OCF has a hypermedia approach with discovery using /oic/res etc., >> which relies on self-description via pointing to predefined resource >> types and interface types, which in turn use a number of >> specification techniques, including JSON schema and RAML. >> >> There is also iot.schema.org <http://iot.schema.org>, which will >> allow us to gather further semantic interoperability information in >> potentially a more granular way. >> >> W3C WoT cares a lot about self-description, with an RDF-based take on >> semantics and describing things. >> >> T2TRG cares about pulling all this together. >> >> On July 15, we will have a workshop that includes people from these >> organizations/groups. The focus will be on building a landscape that >> can benefit from the various approaches, without necessarily papering >> over all the holes or filling in all the rifts. On July 16, we will >> have additional time for follow-on work groups that want to make >> progress on specific issues. >> >> The venue is the Prague Hilton, the same hotel that will host IETF99 >> directly after that. To further minimize travel, we chose the weekend >> directly after the July W3C WoT meeting in close by Düsseldorf. >> >> Elements of the agenda: >> >> State of the union >> >> We will have "state of the union" talks from each of the >> organizations, discussing from a personal perspective where we are on >> interoperability in the organization and what are the next steps. >> >> Research contributions, prototypes >> >> We will issue a call for contributions, with a goal of getting new >> views and new voices into the mix. This will be research on the >> approaches available for building hybrid, overarching systems, as >> well as some practical systems that are already demonstrating how >> this could be made to work in practice, such as systems for >> converting some of the formal notations and/or self descriptions into >> each other. >> >> Specific topics >> >> The below topics (and any other that come up) could be discussed on >> Saturday and/or result in more detailed breakouts on Sunday. >> >> Interops >> >> The "device ecosystem" oriented SDOs are now increasingly using >> common protocols and formats (CBOR, CoAP, IPv6) which is creating one >> narrow waist in the system, and we can look into creating a narrow >> waist also around semantic interoperability and hypermedia design >> patterns. Ultimately, it should not matter which device ecosystem(s) >> you use for your application. The device ecosystems can maintain >> their focus on intra-op and certification while an over arching >> web-like layer of interoperability can add more value to all of them. >> >> Now is a good time to start to organize cross-ecosystem interops, >> where we attempt to orchestrate devices and sources from these >> different device ecosystems. At this point we need to consider >> orchestration across applications as well as device to device >> interoperability. >> >> We have also discussed a lot about conducting more of the actual >> testing over the Internet. This seems like a good concept to build in >> from the beginning. What are the tools we need to conduct an online >> hyper-semantic interop series? Is it staged, from basic to more >> sophisticated? >> >> This seems to represent the canonical use case for both W3C WoT and >> iot.schema.org <http://iot.schema.org>, as well as the various >> translators and bridges being created. >> >> Hypermedia forms >> >> HTML has a form element that can be used to construct POST request >> bodies (and other request payloads, such as for PATCH). An M2M >> equivalent has been lacking for quite some time, although there are >> proposals. Now that we have FETCH and PATCH (RFC 8132), the need is >> even more pronounced. What are the next steps towards common >> Hypermedia "forms", which would help at least T2TRG, OCF, and WoT? >> >> Hypermedia-driven applications in general >> >> T2TRG has a number of drafts documenting how application developers >> use hypermedia to aid in building thing-to-thing (and thing-to-cloud) >> systems. Are these complete? What else do we know about that? What >> about documents from, say, W3C or IPSO? >> >> Model translation >> >> We now have multiple proposals for data modeling (YANG, CDDL, JSON >> Schema, JSON Content Rules) as well as ad-hoc metamodels. What are >> the semantic powers of these modeling approaches? Can we >> automatically translate between them so we can make models of one >> ecosystem available for the other ones? How do we tap hidden Gems >> such as the ZigBee Cluster Library or the Bluetooth GATT specs? What >> about interaction modeling (also YANG, RAML, Swagger, ...)? >> >> > > > > _______________________________________________ > Iotsi mailing list > Iotsi@iab.org > https://www.iab.org/mailman/listinfo/iotsi
- [Iotsi] Fwd: Save the date: July 15/16, 2017: Wor… Carsten Bormann
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Benoit Claise
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Carsten Bormann
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Michael Richardson
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Joaquin Prado
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Carsten Bormann
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Joaquin Prado
- Re: [Iotsi] Fwd: Save the date: July 15/16, 2017:… Joaquin Prado