Main Page/CollectionOfApis

From Automotive and Web Platform Business Group
Jump to: navigation, search


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:

W3C maintains a complete list of all specifications and Working Group Notes relating to JavaScript interfaces, excluding submissions or editor's drafts:

There are many W3C Working Groups working on APIs of relevance to the web run-time, e.g. (and in no particular order):

Work on browser testing and performance:

Application to Application IPC

  • The Push API by the WebApps working group defines a generic mechanism for Server-sent notifications regardless of the delivery mechanism

The (for now) parked (at the W3C) Web Intents / Web Activities work provides amongst other things a mechanism for Interprocess communication between Web applications.

Offline Applications

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.



Device Services Discovery

File System




  • The Geolocation API provides access to the device coordinates, and allows keeping continuous track of its location.


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.


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 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)

System Information

Installable Applications

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.


Web Application Security

Synchronization and Flow Control


Web and Devices in general