The mission of the Automotive and Web Platform Business Group is to influence the Open Web Platform on the unique needs of the automotive industry, and to help stakeholders within the automotive industry to build a good and practical understanding on the standardization processes within the W3C. The initial scope of this business group will be to determine what vehicle data should be exposed through a Web API(s). The goal or deliverable will be to draft a specification and then hand it off to a W3C working group that can take the spec and finalize it through the W3C specification and community process. If the business group is successful in this initial effort, there are many other technical challenges such as reducing driver distraction and improving safety that this group could address while influencing the Open Web Platform for Automotive.
The proposed charter for the group is http://www.w3.org/community/autowebplatform/automotive-and-web-platform-business-group-charter/
Thanks to all who came to the W3C Automotive Business Group’s third face to face in Santa Clara on March 17th and 18th. It was a well attended, productive meeting with over 20 participants from Access, Continental, Daimler, Elektrobit, GM, Google, Intel, JARI, KDDI, LG, OBIGO, OpenCar, Openstream, Pandora, PSA, QNX and W3C. There was very good discussion (and action items) around the maturing vehicle information specification and group direction as well as some excellent presentations by W3C staff, KDDI, OBIGO, Elektrobit, and Continental.
Split spec into two docs: one for interfaces that will not change (durable) such as the VehicleInterface (getting/setting data) and one for data interfaces that are likely to come, go and/or change
Add better handling, at a global level, for units of measure/localization
Add better facility for extensibility of data interfaces
Add facility for availability/capability
Address interface grouping/categories
Address location – which specs to reference?
Address get history
Fill out supported use cases
Address relationship to visual data if appropriate – What to reference?
Address additional specs to be referenced as appropriate
Move sections from guidelines to specs
Security section reference. see KDDI presentation too
Continuation/formalization of Vehicle Information Task Force (small group that has been working on spec)
Vehicle Information Task Force to complete spec by May 23
Timeline laid out to potentially create an automotive working group by October 2014
Potential Task Force Groups
Multimedia in vehicle
Speech and Multi-modal
Containerization and off-line storage – managing in a secure way
Next face to face will be on May 23 in conjunction with the GENIVI All Member Meeting
Immediate action items for the group are as follows:
Create timeline, actions and assignments for Vehicle Information Spec completion. ***Please let us know if you are interested in participating. We will start moving forward starting early next week.***
Form task forces. ***Please let us know if you would like to form and lead a task force.***
Set up next face to face at GENIVI AMM on May 23. ***Please let us know if you can attend.***
“For more than a decade, the World Wide Web Consortium (W3C) has been at work on a set of coding standards intended to enable a single piece of code – be it for an app or a website – to display across a broad range of connected devices. And the automotive industry has been paying close attention, hoping this new set of standards, known as HTML5, would increase the number of apps available for the connected vehicle, or, at the very least, bring down development costs.
By the look of it, the W3C, which acts as the main international standards organization for the World Wide Web, is getting close. In December 2012, it published the complete definition of HTML5 specifications – an actual set of standards is expected before the end of this year. And the connected car industry is now part of the official process. The W3C’s Automotive and Web Platform Business Group launched in February 2013, and the first draft of an HTML5 automotive standard is expected in April.”
Happy new year
The Automotive business group has been very active in the last weeks with a lot discussions about the vehicle API and the next Face to Face meeting.
Some discussions in progress to finalize the date for this meeting.
Let’s keep in touch for more news
Even during this summer period of vacations, the Automotive and Web Platform Business Group is moving:
Now that QNX has contributed its API proposal as well (joining proposals from Genivi, Tizen and Webinos), the group has started to look into merging and harmonizing these individual proposals into a common specification, targetted for December 2013
The group is also discussing the next Face to Face meeting date and location.