SCRIPTING APIS FOR THE WEB OF THINGS

Transcription

1 SCRIPTING S FOR THE WEB OF THINGS Louay Bassbouss Fraunhofer FOKUS louay.bassbouss@fokus.fraunhofer.de WWW W3C Track: Building and Designing the Web of Things, Montréal, Canada

2 MOTIVATION Script (expose) MQTT + App (consume) BLE COAP MQTT COAP Script (expose) COAP HTTP + BLE 2

3 FEATURES WoT Client Discover Things Local Remote Access Things Read/Write properties Call actions Observe events Consider Thing Descriptions Physical BLE BLE App WoT Client COAP MQTT MQTT Script WoT Server COAP Physical Provides access to physical objects (sensors/actuators) Knows how to control these objects (also using proprietary protocols) Physical XXX XXX WoT Server Advertise Things Local Remote Serve Clients Handle read/ write requests Handle action calls Trigger events Consider Thing Descriptions 3

4 WOT CLIENT : REQUIREMENTS SHOULD expose interfaces to client applications that abstract from the underlying protocols (BLE, COAP, MQTT, ) SHOULD offer control interfaces that consider the semantic of Thing Descriptions (name of properties, actions, events, data types, ) SHOULD offer discovery interfaces with capability of filtering Things based on parameters like thing types, capabilities, SHOULD consider Security and Privacy by design Physical BLE App Client COAP MQTT Providers of the WoT Client implement bindings to one or more protocols. The could directly talk to physical objects using corresponding protocols (e.g. BLE) BLE 4

5 SIMILAR W3C S W3C already offers an that follow the same principles à W3C Presentation The Presentation allows web applications to:... request display of web content on secondary screens (e.g. TVs, )... communicate with and control the web content... identify whether at least one secondary screen is available or not The web content may comprise HTML documents, web media types such as images, audio, video, or application-specific media Presentation abstracts from underlying protocols for discovery and communication: Chrome implementation uses Google Cast () Firefox implementation uses mdns + WebRTC The specification includes security and privacy considerations 5

6 W3C PRESENTATION Control Device Web Page/App Web Page/App Presentation mdns WebRTC Presentation Devices Presentation Miracast G. Cast mdns WebRTC Google Cast Web Page/App Presentation G. Cast Miracast 6

7 W3C PRESENTATION Goal is to define an that enables web pages to use secondary screens to display web content Control Page session.send session. onmessage PresentationRequest(url).start().then(function(session){ }) session.onmessage session.send Presentation Page Primary Screen Second Screen 7

8 W3C SECOND SCREEN PRESENTATION WG The work of the Second Screen Presentation is continued in a Working Group The Working Group was created in October 2014 à End date: 31 October 2016 The WG took the final report of the CG as initial working draft for the Presentation Working Draft: 8

9 WOT CLIENT PROPOSAL 9

10 WOT CLIENT PROPOSAL 10

11 WOT CLIENT EXAMPLE 11

12 IMPLEMENTATION AS CORDOVA PLUGIN The Cordova plugin provides the WoT Client The Cordova plugin implements BLE protocol binding Implemented for ios (Android work in progress) Cordova App Implementation as Node.js module is planned Cordova Plugin Underlying Implementation Thing Thing Thing 12

13 DEMO 13

14 THANK YOU 14

15 Contact Louay Bassbouss Senior Project Manager R&D Future Applications and Media Tel. +49 (30) Fraunhofer Institute for Open Communication Systems FOKUS Kaiserin-Augusta-Allee Berlin, Germany Tel: +49 (30) Fax: +49 (30) Fraunhofer Institute for Open Communication Systems Kaiserin-Augusta-Allee Berlin, Germany