W3C “Web of Things” Interest Group · Welcome to Sapporo March ‘15 Start of WoT IG April...

W3C “Web of Things” Interest Group

Interest Group

Joerg Heuer

Unrestricted

Welcome to Sapporo

March ‘15Start of WoT IG

April ‘151st F2F Munich

IEEE P802.3 Maintenance report – July 2008 PlenaryVersion 1.0Version 0.2 rev1 Page 2

Munich

July ‘152nd F2F Sunnyvale(Prague)

October ‘153rd F2F Sapporo

Welcome to Sapporo




Munich



Web of Things IG – Joerg HeuerUnrestrictedUnrestricted

Objective

6

And concretely …Source: Postscapes / Harbor

Research

Approach

Goal: overcome domain silos and enable cross domain IoT applications

Observation:Upper OSI layers are often proprietary implementations in IoT platforms and protocols due to lack of standards

Investigation:

ApplicationLayers

Standardized

IndividualApproaches

7

Investigation:• What web technologies are applied in IoT

scenarios today?• How can web technologies in the upper layers be

used complementing IoT?• What can be seen as good practice?• Where do we see white gaps?

StandardizedIoT BuildingBlocks

Atomic Use Cases

• Map domain applications to

ProceedingAtomic Use CasesDomain Scenarios

8

• Map domain applications to “atomic use cases” and requirements

• Identify best practices• Assemble a stack of tech

recommendations

Work on technical Landscape


Atomic Use Cases to Bridge Application Domains


• Concluded on initial set of use cases• Agreed on top three Building Blocks

Script APIProt. Mapping

ThingDiscovery

ThingDescription

Security &Privacy

Discussion of UCs

July ‘15

Discuss DomainsSet of atomic UCs

Model of Building BlocksIdentify

Tech Candidates• Conclude on Model of Building Blocks

9



• Agree on Principle Types of API• Agree on Tech Landscape Evaluation• Tech verification with Plug Fests

Landscape and White Gaps

• Conclude on Model of Building Blocks• Agree on setup for Tech Landscape

Finalize Tech Landscape,

proceed plug fest eval. and Agree

on WG

How does it relate to IOT …

WoT Framework Building Blocks are intended to map to existing IoTplatforms and protocols

Adoption of WoT Technologiesallows for

ApplicationLayersWoT

Building Blocks


allows for

• Integration of things in today‘s Web

• Web applications integrating things

• Integration of application domains by means of semantic web

IoT Platform

• Thing Description

WoT Building Blocks

11

WoT BB – Scripting API & Protocol Mapping

WoT Servient

Script

Protocol

MappingProtocol

MappingProtocol

Client

Script-API

Server

Script-API

Ressource

s

WoT Servient

Script

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Server

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Protocol

MappingProtocol

MappingProtocol

Mapping

Client

Script-API

Server

Script-API

Ressources

WoT Servient

Script

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Server

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Protocol

MappingProtocol

MappingProtocol

Mapping

Client

Script-API

Server

Script-API

Ressource

s

Adap

ter

12

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Server

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

Web

Protocol

Client

MappingProtocol

Mapping

wwwLegacy Dev

Legacy

Comm

Legacy Protocol

Web technologyTF work WoT ApplicationLegacy / IoT

WoT BB – Things Discovery

• Wiki -https://www.w3.org/WoT/IG/wiki/Discovery_Categories_and_Tech_Landscape

• Six Categories with examples and brief descriptions

• Finding things around me (NFC, UriBeacon)

• Finding things on my network (mDNS, Multicast CoAP)

13

• Finding things on my network (mDNS, Multicast CoAP)

• Searching in directories (CoRE Resource Directory, XMPP IoT Discovery)

• Searching via peers (P2P based approaches)

• Accessing thing metadata (CoRE Link Format, HATEOAS)

• Semantic based discovery (Mostly research articles)

WoT BB – Security & Privacy

• Security&Privacy Requirements: an identification of security and privacy requirements in the use cases that are considered by the WoT IG.

• Landscape of Security&Privacy Means: surveys the landscape of security&privacy means for WoT.

• Security&Privacy Advanced Concepts: complements the atomic view of the requirements catalogue and mechanism candidates with a composite view. This addresses notions such as S&P in discovery of things or thing lifecycle

• Security&Privacy Challenges: traditional Web and office IT

14

• Security&Privacy Challenges: traditional Web and office IT established practices in security and privacy but it is not sufficient to just translate them to to WoT. This deliverable identifies challenges that drive security and privacy in WoT

• Entry points for Ucs:

https://www.w3.org/WoT/IG/wiki/Security%26Privacy_RequirementsFor each criteria you find a definition linked to it and inhttps://www.w3.org/WoT/IG/wiki/Landscape_of_Security%26Privacy_Means

• Focus on Thing Description and Protocol Mapping

• Lighting Scenario

• 8 Independent Implementations

1st Plugfest

15

Cortex M3ES9288 ARM 9

• Work Items for a WG

• Thing Description (data models, server metadata, security-enabling)

• Script API & Protocol Mapping (API, Discovery, Protocol Mapping, security enablement)

• Working on advanced notice

• Strengthen / initiate Liaisons and exchange with IoT organisations

Upcoming

• Strengthen / initiate Liaisons and exchange with IoT organisations(e.g. IIC, OIC, …)

• Increase participation

• TF on communication is under discussion

16

Agenda (1/2)

Thursday, 29th of October, Status / Contribs / Plugf est---------------9:00 W3C WoT IG Objective & Goals of the meeting 9:30 TF AP Report 10:00 TF DI Report 10:30 TF TD Report 11:00 Coffee Break 11:30 Security & Privacy Report (Slides) 12:00 Finalizing first version of Tech Landscape


12:00 Finalizing first version of Tech Landscape

12:30 Lunch

13:30 ContributionsGeneric Sensor API - Tobi LangeWebGPIO, WebI2C kotakagiGeneric discovery/communication API Youenn Fablet, Canon Research FranceThings Web - Internet Service Script and Protocol Bindings KiChul Park, SamsungDiscovery, configuration and working of Lemonbeat-Devices - Frank Reusch, Daniel Lux, RWE15:30 Plugfest Implementor's pitches16:00 Coffee Break 16:30 Plugfest18:30 EoD19:30 WoT Dinner

Agenda (2/2)

Friday, 30th of October - working meetings in break outs / logistics / wrap up------------------------8:30 Plan for the day (Plenary) Plugfest Report Plans for the next Plugfest9:00 Breakout in TFs

12:30 Lunch


13:30 Reports from Break Outs 14:30 Work organization and time plan, outreach upcoming F2Fs Preparation of WoT WG work items work in TFs, Outreach joint meeting IRTF T2T 15:30 EoM

W3C “Web of Things” Interest Group · Welcome to Sapporo March ‘15 Start of WoT IG April...

Documents

Transcript of W3C “Web of Things” Interest Group · Welcome to Sapporo March ‘15 Start of WoT IG April...