Position Paper for W3C Web and Automotive Workshop 
Participant
Ludovic Alidra -- Renault -- ludovic.alidra@renault.com

-> Participant's perspective on the topic Workshop 
-------------------------------------------------- 
For years, car manufacturers have been observing the gap between Consumer Electronics devices and in-car systems regarding product renewal pace, lifecycle length and prices. 

From an end-user point of view, it becomes obvious that automotive and consumer electronics worlds will merge in the near future. A car could be considered alternatively as a device in the home network, as a machine in an M2M network or as a node in a personal network. This approach opens a wide horizon for new services. 

Renault already started to provide new services for its customers thanks to networking facilities via M2M services and downloadable applications. 

Driver distraction and safety topics do not seem to be specific to web usage in a car environment, they are already addressed by usual embedded HMI and systems engineering approaches. 

-> Viewpoint 
------------ 
We believe that standards and common approaches insure a better quality for the end-user (Mobile interoperability and Security), improve platform neutrality and code reuse, and reduce development and deployment costs for carmakers and other actors of the value chain. 

From a more technical point of view, we consider that the main topics to focus on in the medium term are: 
- HMI Performance (provide a high quality user experience for graphics and voice) 
- Functional API definition (for both M2M and user-centric applications) 
- Capability of monetizing vehicle data collection, distribution and rendering, which includes the ability to build application Stores as an important special case. 
- Handling of Security / Privacy issues 
- Compatibility and Interoperability with customer devices 

-> Concrete examples and suggestions 
------------------------------------- 
- Renault can provide use-cases to illustrate needs. 
- Renault is actively supporting Genivi, and could in the medium term provide feedback on practical matching of Web API implementations with Genivi lower-level API's