From nobody Thu May 4 11:03:14 2017 Return-Path: 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 2526A12EAA8; Thu, 4 May 2017 11:03:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] 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 RnNAXZ782JCN; Thu, 4 May 2017 11:03:09 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55BB112EAB0; Thu, 4 May 2017 11:02:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v44I2hE7004091; Thu, 4 May 2017 20:02:44 +0200 (CEST) Received: from client-0124.vpn.uni-bremen.de (client-0124.vpn.uni-bremen.de [134.102.107.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wJjYH43jtzDHFP; Thu, 4 May 2017 20:02:43 +0200 (CEST) Content-Type: multipart/alternative; boundary="Apple-Mail=_E4E3CFBA-E033-400C-B73C-AD6FC0FD5E08" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Carsten Bormann Date: Thu, 4 May 2017 20:02:42 +0200 Cc: t2trg-chairs@irtf.org X-Mao-Original-Outgoing-Id: 515613762.792282-f102d08445d494d7db18ec12fc49a44f Message-Id: References: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> To: iotsi@iab.org X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2017 18:03:13 -0000 --Apple-Mail=_E4E3CFBA-E033-400C-B73C-AD6FC0FD5E08 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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=E2=80=99t 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=C3=BC=C3=9Fe, Carsten > Begin forwarded message: >=20 > From: Ari Ker=C3=A4nen > > 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 " >, "public-wot-ig@w3.org = " > > Cc: Carsten Bormann > >=20 > Save the date July 15/16, 2017 for Workshop on IoT Semantic/Hypermedia = Interoperability, in Prague at IETF99. >=20 > See the description below and up to date information with registration = instructions here: https://github.com/t2trg/2017-07-wishi = >=20 >=20 > Cheers, > Ari & Carsten >=20 >=20 > 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. >=20 > 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. >=20 > 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. >=20 > There is also iot.schema.org , which will = allow us to gather further semantic interoperability information in = potentially a more granular way. >=20 > W3C WoT cares a lot about self-description, with an RDF-based take on = semantics and describing things. >=20 > T2TRG cares about pulling all this together. >=20 > 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. >=20 > 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=C3=BCsseldorf. >=20 > Elements of the agenda: >=20 > State of the union >=20 > 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. >=20 > Research contributions, prototypes >=20 > 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. >=20 > Specific topics >=20 > The below topics (and any other that come up) could be discussed on = Saturday and/or result in more detailed breakouts on Sunday. >=20 > Interops >=20 > 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. >=20 > 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. >=20 > 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? >=20 > This seems to represent the canonical use case for both W3C WoT and = iot.schema.org , as well as the various = translators and bridges being created. >=20 > Hypermedia forms >=20 > 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? >=20 > Hypermedia-driven applications in general >=20 > 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? >=20 > Model translation >=20 > 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, ...)? >=20 >=20 --Apple-Mail=_E4E3CFBA-E033-400C-B73C-AD6FC0FD5E08 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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=E2=80=99t 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=C3=BC=C3=9Fe, Carsten


Begin forwarded message:

From: = Ari Ker=C3=A4nen <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" <t2trg@irtf.org>, "public-wot-ig@w3.org" = <public-wot-ig@w3.org>
Cc: Carsten Bormann <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, 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=C3=BCsseldorf.

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, 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, ...)?



= --Apple-Mail=_E4E3CFBA-E033-400C-B73C-AD6FC0FD5E08-- From nobody Fri May 5 01:31:37 2017 Return-Path: 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 ; 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 ; 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 ; 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: =?us-ascii?q?A0BMAQDRNwxZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhDeBDINoihhzkEMhkRGEX4IPAh8BCoV4AoUFGAECAQEBAQEBAWs?= =?us-ascii?q?ohRUBAQEBAgEBARsGSwYFEAkCDgMDAQIkBAMCAicfCQgGAQwGAgEBihQIDpQNn?= =?us-ascii?q?DACgS+CJiuKOwEBAQEBAQEBAQEBAQEBAQEBAQEBAR0yhi2BXisLgmWBPINHFoJ?= =?us-ascii?q?Qgl8BBJ1vhxuLfIIEhTmDQ4ZojAqDfoQvDxA4gQouIAgZFUaEcwwQGYFMPjaId?= =?us-ascii?q?QEBAQ?= 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 , iotsi@iab.org Cc: t2trg-chairs@irtf.org References: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> From: Benoit Claise Message-ID: Date: Fri, 5 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: Content-Type: multipart/alternative; boundary="------------F05676AD4340A1397892EF2B" Content-Language: en-US Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2017 08:31:24 -0000 This is a multi-part message in MIME format. --------------F05676AD4340A1397892EF2B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 > > >> *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 " > >, "public-wot-ig@w3.org >> " > > >> *Cc: *Carsten Bormann > >> >> 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 , 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 , 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 --------------F05676AD4340A1397892EF2B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
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>
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
Cc: Carsten Bormann <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, 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, 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

--------------F05676AD4340A1397892EF2B-- From nobody Fri May 5 04:26:53 2017 Return-Path: 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 26A6212960D; Fri, 5 May 2017 04:26:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 sTulqQIV6BKj; Fri, 5 May 2017 04:26:51 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E945212946D; Fri, 5 May 2017 04:26:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v45BQh0i021689; Fri, 5 May 2017 13:26:43 +0200 (CEST) Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wK8jv3GG5zDHWQ; Fri, 5 May 2017 13:26:43 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Carsten Bormann In-Reply-To: Date: Fri, 5 May 2017 13:26:42 +0200 Cc: iotsi@iab.org, t2trg-chairs@irtf.org X-Mao-Original-Outgoing-Id: 515676402.254548-de7821f00d32a93426eb602b7e5a94e4 Content-Transfer-Encoding: quoted-printable Message-Id: References: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> To: Benoit Claise X-Mailer: Apple Mail (2.3273) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2017 11:26:52 -0000 On May 5, 2017, at 10:31, Benoit Claise wrote: >=20 > However, the IETF hackathon and its code take precedence. Hi Benoit, the overload factor of the pre-IETF weekend is indeed becoming = ridiculous. I have approximately four events I have to be at this weekend at the = same time. Which makes it very important to prepare for it ahead of time, so we can = make good progress in the shorter f2f contact times that remain. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon May 8 05:47:10 2017 Return-Path: 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 33448127077 for ; Mon, 8 May 2017 05:47:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 KnM5cnyzDdiZ for ; Mon, 8 May 2017 05:47:03 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E498129462 for ; Mon, 8 May 2017 05:47:02 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 7AD80E033; Mon, 8 May 2017 09:13:13 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1D72D636E0; Mon, 8 May 2017 08:47:01 -0400 (EDT) From: Michael Richardson To: t2trg-chairs@irtf.org, iot-dir@ietf.org, iotsi@iab.org In-Reply-To: References: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Date: Mon, 08 May 2017 08:47:01 -0400 Message-ID: <10389.1494247621@obiwan.sandelman.ca> Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 12:47:04 -0000 Carsten Bormann wrote: > the overload factor of the pre-IETF weekend is indeed becoming > ridiculous. I agree. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ From nobody Thu May 18 08:08:06 2017 Return-Path: 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 B920E129C31; Thu, 18 May 2017 08:07:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.3 X-Spam-Level: X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] 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 9ICiCHGCUvYN; Thu, 18 May 2017 08:07:52 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD2DC12950B; Thu, 18 May 2017 08:01:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v4IF12Zr014751; Thu, 18 May 2017 17:01:02 +0200 (CEST) Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wTDs95m1zzDJJG; Thu, 18 May 2017 17:01:01 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Carsten Bormann In-Reply-To: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> Date: Thu, 18 May 2017 17:01:00 +0200 Cc: t2trg-chairs@irtf.org X-Mao-Original-Outgoing-Id: 516812460.379046-fadc14e2f7236acf57af90c973af5307 Content-Transfer-Encoding: quoted-printable Message-Id: <8A81FF20-B3CB-4AD7-B872-ADF0BF239542@tzi.org> References: <04441040-B2D6-47F3-8224-20ED52F731A1@ericsson.com> To: "t2trg@irtf.org" , "public-wot-ig@w3.org" , iotsi@iab.org X-Mailer: Apple Mail (2.3273) Archived-At: Subject: [Iotsi] Call for Contributions: Workshop on IoT Semantic/Hypermedia Interoperability (Prague, July 15/16) X-BeenThere: iotsi@iab.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Internet of Things Semantic Interoperability Workshop List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2017 15:07:55 -0000 We have now produced the call for contributions for WISHI, as reproduced = below. See = https://github.com/t2trg/2017-07-wishi/blob/master/CALL-FOR-CONTRIBUTIONS.= md for a version with links. Please forward this message to groups that might find it useful. Please also don=E2=80=99t forget to register: = https://goo.gl/forms/yUTebqK9C84Ef01i2 Gr=C3=BC=C3=9Fe, Carsten # Workshop on IoT Semantic/Hypermedia Interoperability: Call for = Contributions When: July 15/16, 2017 (weekend before IETF99) Where: Hilton Prague (IETF meeting hotel). Pob=C5=99e=C5=BEn=C3=AD 1, = Prague, Czech Republic. Registration: https://goo.gl/forms/yUTebqK9C84Ef01i2 # Workshop overview Please have a look at: https://github.com/t2trg/2017-07-wishi # Call for contributions We are soliciting contributions that are on topic for the workshop in = one of four forms (or any mixture thereof): 1. State-of-the-union speeches: Where is your favorite IoT standards-settings organization on the road to semantic/hypermedia interoperability, and what are its next steps? What role could it play in the emerging IoT semantic interoperability ecosystem? 2. Research contributions: What did you try? What did you learn about the self-description properties of the devices and the modeling languages in use? How can you translate between different approaches? What are the semantic limitations that you encountered? What can you say about what properties modeling languages and self-description formats should have? 3. Prototypes: What did you build? What did you learn from it? 4. Work proposals: What should be done? Can you give a roadmap of what analyses, experiments, prototypical artifacts should the community try next? Some slots for #1 are already allocated, so please check with to avoid duplication. For all contributions, a short position paper is the preferred form of input. For a selected subset of these contributions, we will allocate presentation and discussion time. Don't let our request for a paper discourage you from proposing other interesting forms of contributions. If you have a great demo, or an existing paper a discussion of which would help us forward, please do suggest it. (You can always write a few additional paragraphs for the workshop so people can come prepared and understand how your work fits in.) # Important dates For the state-of-the-union speeches (type #1 above), please discuss your request with the chairs by May 31. For the other types, please register your intent to submit a contribution with [the chairs][] as soon as you can do. [the chairs]: mailto:t2trg-chairs@irtf.org The position paper form of the contribution will be made available to the participants on July 1, 2017. Please send in your contribution by **June 25, 2017**.