“Open” Web AppFramework manifests etc) but These elements are standardised, Each of these elements can be improved (e.g.JSON Apps testable agreed and can be deployed now W3C Widgets Packager Chromium Embedded Web Renderer OR Android - WebView XACML = WAC + Policy Subject = person APIs GeoLocation Orientation Calendar Contacts Others W3C + WAC + Webinos CRX
Decoupled Browser (Warning disruptive!!) Also remote http (normal Apps website)+ Decouple Appstore Widget URI OR HTTP URI OR FILE URI Packager Standard Browser (Firefox, Chrome, Safari ec..) Supporting web sockets Policy Websocket – with APIs domain origin test GeoLocation Orientation Calendar Contacts Others User grants access of domain to feature (ala geo-location)
Webinos as a Server Server Client/Browser Apps Packager Policy Widget Renderer APIs GeoLocation Orientation Calendar Contacts Others
webinos for M2M/webinos for server apps Server Background Apps Packager NO UI Policy Web Services and Embedded APIs Servers very GeoLocation similar Orientation Calendar Contacts Others
Operating System vs Webinos Underlying OSApplication Technology
Cross Device RequirementsWhat do we need? Interoperable web application packaging Device and User Identity + Addressability Cross device synchronisation Peer2Peer Connectivity Device and Service Discovery Distributed Policy Framework Remoting mechanisms Defined Interoperable APIs A data sharing model 20
Me and My Devices Mutually authenticated TLS sessions bind all devices to a Peter: PZP (Personal Zone Proxy) cloud agent Peter: PZH (Personal Zone Hub) Peter: PZP Security Policy (Personal Zone Proxy) PZH Server (Logical Entity) Peter PZH Peter: PZP Peter: PZP Peter: PZP (Personal Zone Proxy)(Personal Zone Proxy) (Personal Zone Proxy)
Me and your devices PZH - Personal Zone Hub PZP - Personal Zone Proxy – Resides on Server – Resides locally on the – TLS – Transport Layer – Logical Entity: 1 PZH per device Security user – Present on every webinos Secure/Certified – Each PZH server can host device connection between multiple PZH’s webinos components Peter: PZH Helen: PZH (Personal Zone Hub) TLS (Personal Zone Hub) Security Policy Security Policy Server / PZH Server / PZH (Logical Entity) (Logical Entity) TLS TLS Internet/Cloud LocalPeter’s Personal Zone John’s Personal Zone Peter: PZP Direct P2P (e.g. Bluetooth, WiFi Direct) Peter: PZP Peter: PZP Peter: PZP Peter: PZP Helen: PZP (Personal Zone Proxy) (Personal Zone Proxy) Security Policy Security Policy Devices Devices 23
Data Ownership Micro PZP DOCTOR 1 PZH ? DOCTOR 2 Micro PZP TRAINER 2 Same scenario for In car telematics and swapping insurers. Same scenario for Smart Meters.
All fully integratedOpen Source Community Drupal: Developer Education Github: Source Code and Forums repository Jira: Issue tracking/ Bugs GreenHopper: Agile Scrum Development 25
Final Takeaways Convergence is a trend – Which platform for developing for apps across devices – How will they work together? Web is the “universal” platform Webinos is OPEN – Not led by any SINGLE company Webinos is compatible (needed?) by many other Oss (including web based OS) Webinos is a consumer centric view of privacy and security Free to join… Free to use...