W3C Web of Things Interest Group

Transcription

1 W3C Web of Things Interest Group Joerg Heuer Unrestricted Page 1

2 Welcome to Sapporo March 15 Start of WoT IG April 15 1 st F2F Munich July 15 2 nd F2F Sunnyvale (Prague) October 15 3 rd F2F Sapporo Version rev1 IEEE P802.3 Maintenance report July 2008 Plenary Page 2

3 Welcome to Sapporo March 15 Start of WoT IG April 15 1 st F2F Munich July 15 2 nd F2F Sunnyvale (Prague) October 15 3 rd F2F Sapporo Version rev1 IEEE P802.3 Maintenance report July 2008 Plenary Page 3

4 Welcome to Sapporo March 15 Start of WoT IG April 15 1 st F2F Munich July 15 2 nd F2F Sunnyvale (Prague) October 15 3 rd F2F Sapporo Version rev1 IEEE P802.3 Maintenance report July 2008 Plenary Page 4

5 Unrestricted Web of Things IG Joerg Heuer

6 Objective And concretely Source: Postscapes / Harbor Research 6

7 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: 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? Individual Approaches Standardized IoT Building Blocks Application Layers 7

8 Atomic Use Cases Domain Scenarios Atomic Use Cases Proceeding Map domain applications to atomic use cases and requirements Identify best practices Assemble a stack of tech recommendations 8

9 Work on technical Landscape Discuss Domains Set of atomic UCs Model of Building Blocks Identify Tech Candidates Landscape and White Gaps March 15 Start of WoT IG April 15 1 st F2F Munich July 15 2 nd F2F Sunnyvale (Prague) Script API Prot. Mapping Discussion of UCs Atomic Use Cases to Bridge Application Domains Concluded on initial set of use cases Agreed on top three Building Blocks Thing Discovery Thing Description Security & Privacy Conclude on Model of Building Blocks Agree on setup for Tech Landscape Finalize Tech Landscape, proceed plug fest eval. and Agree on WG October 15 3 rd F2F Sapporo Agree on Principle Types of API Agree on Tech Landscape Evaluation Tech verification with Plug Fests 9

10 How does it relate to IOT WoT Framework Building Blocks are intended to map to existing IoT platforms and protocols Adoption of WoT Technologies allows for Integration of things in today s Web Web applications integrating things WoT Building Blocks IoT Platform Application Layers Integration of application domains by means of semantic web Version rev1 IEEE P802.3 Maintenance report July 2008 Plenary Page 10

11 WoT Building Blocks Thing Description 11

12 WoT BB Scripting API & Mapping WoT Servient WoT Servient Adap ter Script Server Script-API Ressource Script-API s Mapping Mapping Mapping Web Web Web Web Web Web Server Legacy Script Server Script-API Ressource Script-API s Mapping Mapping Mapping Web Web Web Web Web Web Server WoTServient Script Server Script-API Ressources Script-API Mapping Mapping Mapping Web Web Web Web Web Web Server Legacy Comm Legacy Dev www TF work Web technology Legacy / IoT WoT Application 12

13 WoT BB Things Discovery Wiki - Landscape Six Categories with examples and brief descriptions Finding things around me (NFC, UriBeacon) 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) 13

14 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 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: Requirements For each criteria you find a definition linked to it and in y%26privacy_means 14

15 1st Plugfest Focus on Thing Description and Mapping Lighting Scenario 8 Independent Implementations Cortex M3 ES9288 ARM 9 15

16 Upcoming Work Items for a WG Thing Description (data models, server metadata, security-enabling) Script API & Mapping (API, Discovery, Mapping, security enablement) Working on advanced notice Strengthen / initiate Liaisons and exchange with IoT organisations (e.g. IIC, OIC, ) Increase participation TF on communication is under discussion 16

17 Agenda (1/2) Thursday, 29th of October, Status / Contribs / Plugfest :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:30 Lunch 13:30 Contributions Generic Sensor API - Tobi Lange WebGPIO, WebI2C kotakagi Generic discovery/communication API Youenn Fablet, Canon Research France Things Web - Internet Service Script and Bindings KiChul Park, Samsung Discovery, configuration and working of Lemonbeat-Devices - Frank Reusch, Daniel Lux, RWE 15:30 Plugfest Implementor's pitches 16:00 Coffee Break 16:30 Plugfest 18:30 EoD 19:30 WoT Dinner Version rev1 IEEE P802.3 Maintenance report July 2008 Plenary Page 17

18 Agenda (2/2) Friday, 30th of October - working meetings in break outs / logistics / wrap up :30 Plan for the day (Plenary) Plugfest Report Plans for the next Plugfest 9: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 Version rev1 IEEE P802.3 Maintenance report July 2008 Plenary Page 18