IoT Mashup - webinos APIs - Nilsson
Download as PPTX, PDF1 like1,256 views
This document outlines the Webinos API specifications presented at an Oxford meeting in July 2013. It discusses the goals of reusing existing W3C API specifications where possible and standardizing any new APIs within W3C. An overview is given of the Webinos and W3C APIs that have been reused, modified, or are being provided as input for standardization. Key features of Webinos include finding and accessing remote services using the Webinos Service Discovery API along with relevant Webinos or W3C access APIs. Twenty-four new Webinos APIs and eight reused W3C APIs are specified across areas such as sensors/actuators, media, data storage, communication, and security.
IoT Mashup - webinos APIs - Nilsson
- 1. 1 WEBINOS API SPECIFICATIONS - OXFORD MEETING JULY 2013 Claes Nilsson, Sony Mobile Presented by Christian Fuhrhop, Fraunhofer FOKUS
- 2. 3 Goals Easy to use APIs for web developers that support webinos use cases Don’t re-invent the wheel, re-use existing API specifications, preferable from W3C, as much as possible When needed modify existing API or specify new APIs but align our with W3C style as much as possible New APIs are subject for standardization within W3C
- 3. 4 API landscape WACDAP WebApps WebRTC Geolocation What WG Provide standardization input to W3C Just referred or Reused and modified Reused and modified SysApps Firefox OS NFC extension APIs Reused and modified
- 4. 5 Webinos Personal Zone Connections between People Users devices Webinos Personal Zone Hub (PZH) Connections between devices Webinos Personal Zone Users devices Webinos Personal Zone Hub (PZH) Connections between devices Webinos enables access to remote services
- 5. 6 webinos key feature is the ability to find and use a service in a remote device
- 6. 7 Webinos key feature! 1. The webinos Service Discovery API is used to find and bind to a service 2. A webinos or W3C API is used to access the service
- 7. 8 Webinos Service Discovery API • High level API. All low level protocol details hided to web developer. • Discoverable service must reside on devices registered in a webinos personal zone. • The ”Service Type” to search for relates to the Webinos or W3C API used to access the service. Example: • http://webinos.org/api/sensors/temperature (Search for temperature sensors. The webinos sensor API is used to access the sensor data)
- 8. 9 Service discovery example PZH Security Policy MediaContent API ... ..... MediaContent API ServiceDiscovery API 1. window.webinos.discovery.findServices( {api:' http://webinos.org/api/mediacontent '}, {onFound:serviceFoundCB}); 3. User selects media content service Mobile application binds to selected media content service. 4. Mobile application uses webinos MediaContent API to access the remote media content service. Precondition: User registers devices/services as members of the Personal Zone, alt using MDNS to find services dynamically MediaContent API 2. Mobile application lists discovered media content services for user selection.
- 9. 10 webinos APIs - Sensors and Actuators webinos Vehicle API: Provides access to specific vehicle data including trip computer data and vehicle sensors. webinos Generic Sensor API: Access data from different types of sensors, e.g. proximity, temp, light and noise sensors. webinos Generic Actuator API: Control actuators, e.g. switches, motors and thermostates.
- 10. 11 webinos APIs - Sensors and actuators W3C Geolocation API: Access to geograhical location information. W3C Device Orientation API: Access to physical Orientation and motion of a device. webinos Navigation API: Provides mechanisms to interact with on- board navigation software. POI
- 11. 12 webinos APIs - Sensors and actuators webinos NFC API: Near Field Communication support.
- 12. 13 webinos APIs - Media W3C Media Capture and Streams: Access to multimedia streams (video, audio, or both) from local devices (video cameras, microphones, Web cams). webinos TV Control API: Provides means to acquire a list of TV sources, channels and their streams. webinos Media Content API: Access to multimedia contents (images, music, videos). Based on Tizen MediaContent API.
- 13. 14 webinos APIs – Data Storage W3C File API: Allows web applications to read files on a device. W3C File API: Writer: Allows web applications to write to files. W3C File API: Directories and System: Allows web applications to navigate file system hierarchies.
- 14. 15 webinos APIs – Communication/Messaging webinos Messaging API Sending, receiving and searching SMS, MMS, E-mail and IM. webinos App2App Messaging API Messaging between webinos applications. W3C PeerConnection API: Allows media to be sent and received over the network to another browser.
- 15. 16 webinos APIs – Personal Information webinos Contacts API: Provides access to a user unified address book. Based on old W3C DAP Contacts API and WAC Contacts API. W3C Calendar API: Provides access to a user calendaring service. (old shelved W3C DAP version, to be replaced with W3C SysApps Calendar API when that is done.)
- 16. 17 webinos APIs – User Interaction webinos Web Notifications API: Display notifications outside the context of a web page. Based on the W3C Web Notifications API. webinos Remote UI API: Create and access a UI on a remote device and manipulate DOM objects.
- 17. 18 webinos APIs – Security webinos Authentication API Provides information to applications about the current authentication status of users. webinos Secure Elements API: Access to application on a smart card or any other secure element.
- 18. 19 webinos APIs – Misc webinos Core interface: Defines the webinos namespace and provides information about the personal zone. webinos AppLauncher API: Activation of webinos applications on the device. webinos Widget API: W3C Widget API with webinos extensions. Webinos Personal Zone
- 19. 20 webinos APIs – Misc webinos Context API: Enables access to a user's context data. webinos Payment API: Provides in-app payment. webinos AppState Synchronization API: Enable and manage application synchronisation.
- 20. 21 Working with W3C webinos is active in the W3C System Applications WG – Runtime and Security model – Raw Socket API – webinos has valuable input to next phase SysApps APIs, e.g. Media Storage, Secure Elements W3C NFC WG – Feeding back experiences from webinos NFC API specification and implementation
- 21. 22 Summary webinos API key feature is the ability to find and bind to a remote service and use a webinos or W3C API to access the service 24 new webinos API specified 8 W3C APIs referred
- 22. 23 Links Webinos: – Latest webinos API specifications W3C: – Device APIs – System Applications – Web Applications – Geolocation – WEB RTC – NFC
Editor's Notes
- #5: System Applications WGThe mission of the System Applications Working Group is to define a runtime environment, security model, and associated APIs for building Web applications with comparable capabilities to native applications. This requires stronger integration with the host platform than is the case for traditional web pages. Browsers are designed to cope with the user visiting untrusted web sites, necessitating a cautious approach to security that narrowly limits what a particular website can do. The contrast between the two contexts can be illustrated by comparing a) an application with limited access to specific fields in the user's contacts, and b) an application that implements a contacts manager, where the application is entrusted with the ability to access, create, delete and update entries.What is the WHATWG?The Web Hypertext Application Technology Working Group (WHATWG) is a growing community of people interested in evolving the Web. It focuses primarily on the development of HTML and APIs needed for Web applications.The WHATWG was founded by individuals of Apple, the Mozilla Foundation, and Opera Software in 2004, after a W3C workshop. Apple, Mozilla and Opera were becoming increasingly concerned about the W3C’s direction with XHTML, lack of interest in HTML and apparent disregard for the needs of real-world authors. So, in response, these organisations set out with a mission to address these concerns and the Web Hypertext Application Technology Working Group was born.WACI am not sure on the implications (or non-implications) of WAC beingbought up by GSMA but my view is that today otherinitiates are moreimportant for webinosthan WAC. I mighthave missed somethingbutcurrently I don'tseeany activity around WAC. Yes, that was the point that I thinkwould be worthmaking - that WAC (for variousreasons) is stagnating so wereacted to that and went from just referencing WAC APIs towardsadaptingthem for webinos. Basicallyshowing the reviewers that we are awarewhathappenselsewhere and are makingdecisionsbased on this.Adobe acquiredPhoneGap: http://m.techcrunch.com/2011/10/03/adobe-acquires-developer-of-html5-mobile-app-framework-phonegap-nitobi/
- #22: Continuousalignment with API implementations, examples:Privacy aware location and proximity added to Context API New sensor types in Sensor API based on M2M use cases.