[Web and Automotive - W3C Workshop]

--------------------------------------------------------------------------
Name:		Mikko Ylinen
Organization:	Intel Open Source Technology Center
E-mail:		mikko.ylinen@intel.com
--------------------------------------------------------------------------

		Author's Interest in Web and Automotive

1. Intro

Web is emerging in automotive. Car manufacturers and Tier-1s have very
recently started to study the possibilities of Web and HTML5 to be used
in application development and even to create flexible user interfaces
(UI) in in-vehicle infotainment (IVI) systems.

In order to be able to provide automotive rich UI and applications, an
access to IVI system provided data is needed. Ideally, this is done
through standardized automotive Web APIs.

2. Challenges

To date, there's no standardized Web API for IVI to access automotive 
data. Furthermore, different car manufacturers (or even different car
models) can provide very different data items.

Different parties, e.g. GENIVI or Webinos, have started to specify
their own specifications for automotive Web APIs. They aim to be all-
inclusive which not always a good match for everybody's needs.

3. Proposal

To overcome the challenges, the Authors would like to propose the
following to be discussed in the Web and Automotive W3C Workshop:

a) Definition of basic design guidelines for the automotive Web API design

- The API is lightweight and provides getting and setting data items
- The API implements an extremely minimal set of data items that are
  the base set required for compliance
- The API has mechanisms for event based updates to requested data items.
- The API implements a method for a Web application to query for
  supported data items, so graceful functionality degradation is possible

b) Tizen IVI implementation and demo

- Architecture overview covering challenges listed in [2. Challenges]
- A demo showing data retriewal from hardware upto a Web application

c) Kick-off standardization work around automotive Web APIs.