- 1 General
- 2 Application to Application IPC
- 3 Offline Applications
- 4 Authentication
- 5 Contacts
- 6 Device Services Discovery
- 7 File System
- 8 Messaging
- 9 Multimedia
- 10 Navigation
- 11 Notifications
- 12 Sensors
- 13 Speech
- 14 System Information
- 15 Installable Applications
- 16 Telephony
- 17 Web Application Security
- 18 Synchronization and Flow Control
The goal of this page is to document ongoing work at W3C that is of relevance to the Web and Automotive Platform business group and to the automotive industry. A similar effort has been done by Vodafone - this work has already been briefly integrated here where relevant - for details on the Vodafone work, see:
- Workshop paper "HTML5 and Device APIs for Automotive: Is it time to power Infotainment and Car Portal Applications with Web Technologies?"
- Slides of talk "W3C Web and Automotive Workshop"
There are many W3C Working Groups working on APIs of relevance to the web run-time, e.g. (and in no particular order):
- System Applications
- Device APIs
- Web Applications
- HTML Working Group
- Web Real Time Communications
- Web Notifications
- Web Events
- Independent User Interface (Indie UI)
- Pointer Events
- Web Application Security
- Web Cryptography
Work on browser testing and performance:
Application to Application IPC
- http://dev.webinos.org/specifications/draft/app2app.html This is a Webinos spec, so not necessarily W3C work
- The Push API by the WebApps working group defines a generic mechanism for Server-sent notifications regardless of the delivery mechanism
Given that connectivity in the car will likely be provided by cellular networks of variable coverage according to the location (possible bad signal in the countryside, going through tunnels, etc.) and also the high speed at which cars move, offline becomes a requirement. Offline capabilities could allow IVIs and car applications to locally store assets such as maps, pages, and navigation and application data to reduce as much as possible unnecessary traffic, (Web) application loading time or to offer functionality when no connectivity is available.
- App Cache: Allows Web applications to have their "shells" of main resources available without a connection.
- Web Storage: Key/Value pairs storage.
- IndexedDB: Storage of binary assets.
- http://dev.webinos.org/specifications/draft/authentication.html This is a Webinos spec, so not necessarily W3C work
- http://dev.webinos.org/specifications/draft/contacts.html This is a Webinos spec, so not necessarily W3C work
Device Services Discovery
- http://dev.webinos.org/specifications/draft/servicediscovery.html This is a Webinos spec, so not necessarily W3C work - there is more recent work in the W3C DAP group
- http://dev.webinos.org/specifications/draft/messaging.html This is a Webinos spec, so not necessarily W3C work
- http://www.w3.org/TR/DOM-Level-3-Events/ DOM Events
- http://www.w3.org/TR/mmi-arch/ Multimodal Architecture and Interfaces (Application Life-Cycle Event messages)
- http://dev.webinos.org/specifications/draft/MediaContent.html This is a Webinos spec, so not necessarily W3C work
- The Geolocation API provides access to the device coordinates, and allows keeping continuous track of its location.
- Device Orientation: events for physical orientation and movement of a device.
- http://dev.webinos.org/specifications/draft/navigation.html This is a Webinos spec, so not necessarily W3C work.
Automotive applications may want to notify the user directly of specific events related to his vehicle, or provide alerts.
- The Web Notifications spec allows to alert the user outside of the “web page” or browser context, similar to the "native notifications" displayed in the status bar of or home screen of a mobile phone. Currently the only available implementation of this spec is on Chrome Desktop and (apparently) Firefox Desktop.
- http://dev.webinos.org/specifications/draft/notifications.html. This is a Webinos spec, so not necessarily W3C work.
- http://dev.webinos.org/specifications/draft/sensors.html This is a Webinos spec, so not necessarily W3C work.
DAP has a few specs related to device sensors:
Other sensor specs might be added to an extension of the DAP charter, such as: Temperature Sensor, Ambient Humidity and Atmospheric Pressure.
Voice is the main interface for a driver to interact with an IVI system, as it provides minimal distraction. At the minimum, basic speech recognition capabilities should be available offline while the majority and the most advanced features could still rely on Internet connectivity.
- W3C Speech Synthesis
- W3C Speech Input. (Currently the only available implementation is in the Chrome browser which accesses a Google backend server, i.e. the captured audio is uploaded and a usable transcribed string is returned)
- Offline/Online state of a browser: http://www.w3.org/TR/2011/WD-html5-20110113/offline.html?path=1_5_2_4_5#browser-state
- The DAP WG has moved from the original NetInfo Spec to a reworked specification for Network Information which considers the measure of available bandwidth (See: https://dvcs.w3.org/hg/dap/raw-file/84a2fb7b753b/network-api/index.html). Nonetheless, there is no consensus in the WG on the benefits and implementability of the latest spec version, so it should not be relied upon.
- W3C Widgets specifications (unfortunately has very little industry support and implementations besides from Opera browser.
See also the following work from the SysApps WG:
- Runtime Model System-level apps definition, lifetime and manifest.
- App-URI: addressing packaged applications and resources inside them.
- SysApps Web Telephony API
- W3C Call Control
Web Application Security
Synchronization and Flow Control
- http://www.w3.org/TR/smil/ Synchronized Multimedia Integration
- http://www.w3.org/TR/scxml/ State Transition Notation