Skip to toolbar

Community & Business Groups

Automotive and Web Platform Business Group

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/

Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.

final reports / licensing info

date name commitments
Vehicle Information API Licensing commitments
Vehicle Data Interfaces Licensing commitments

Chairs, when logged in, may publish draft and final reports. Please see report requirements.

Publish Reports

Meeting summary from W3C Automotive Business Group, Tokyo face to face

The W3C Automotive Business Group has just completed his second face-to-face meeting in Tokyo on Wednesday, May 29 2013. This meeting was a great success, with active discussion from over 30 participants related to the automotive industry in one way or another—automakers, tier one suppliers, hardware and software suppliers, telecom carriers, academia, government and the W3C organization itself. We all gathered to discuss how to move forward standardization of automotive-specific uses of HTML5. Much helpful guidance was provided from the co-chair of the W3C’s Web & TV Interest Group, by discussing how sometime similar issues that our automotive team raised were resolved in the TV group.

The day was jam packed with presentations. KDDI, Access, Obigo, and Intel presented on various use cases in the automotive space that used HTML5. There are currently four proposals for standardizing HTML5-based vehicle APIs: from Tizen, Webinos, GENIVI and QNX (as yet unpublished). There were presentations made by GENIVI (represented by LGE), Tizen (represented by Intel), and QNX on the findings on how those various proposals differed and how they could be made to work together.

KDDI spoke about how head unit capabilities could be augmented with mobile phone APIs through HTML5. Access described the work they’re doing integrating HTML5 as a tool in the process for creating automotive engine tone generation systems. Obigo showed a short video on how navigation systems can be enabled by mobile phones with web servers. Intel discussed the types of advanced features that can be enabled by navigation systems that are web server savvy.

At the last face to face meeting in Barcelona, it had been discussed to start with OBD-II being the least common denominator of vehicle functions, as every vehicle supported it. LGE showed that the intersection of OBD-II data and what was supported through GENIVI, Tizen, and Webinos APIs was very small; the functionality represented in the existing APIs is not captured in OBD-II. However there was still support for integrating OBD-II APIs so that diagnostic applications could be supported. QNX described findings that lead to ensuring HTML5 specifications would be able to support mobile developers not just automotive, and that they should support applications and not just built-in HMIs. Part of this was ensuring synchronization with Apache Cordova.

It was generally agreed by the presenters that although the four proposals cover much of the same ground, there are a lot of specific differences that would need to be rectified. It was discussed that the best strategy would be to create a superset of the four proposals, taking the best from all, to which there did not seem to be any objection. LGE and QNX took the action to begin the process of merging the four contributions for approval by the group. Intel has volunteered as the specification editor, and has creating the initial skeleton for the specification.

A presentation from ISO about how synchronization of ISO and W3C Automotive Business Group standardization efforts would be beneficial for both parties was the last of the day’s presentations.

There were suggestions from a number of parties about areas beyond vehicle data APIS (the group’s original charter) that will also need addressing, like navigation, speech, multimedia, and even ADAS APIs. It seems there is a high degree of interest in broadening support for HTML5 applications in many aspects of the vehicle, and collection of the related use cases is encouraged through a mailing list discussion. Overall, it was a productive day full of constructive dialog and collaborative efforts to ensure a rich future for HTML5 in the car.  For future efforts, the group will be hosting a monthly conference call. And we’re looking to schedule another face to face—possibly at ITS in Tokyo or at the W3C Technical Plenary session in November in Shenzhen, China (near Hong Kong).

The W3C Automotive Business Group would like to thank the Linux Foundation and Intel for picking up the tab for the meeting room, audio/visual equipment and lunch.

Filed by Andy Gryc on June 13, 2013 4:58 PM in

W3C Automotive and Web Platform Business Group on the road, get behind the wheel

The W3C Automotive and Web Platform Business Group held its first face to face meeting in Barcelona on the 22 April.

A lot of ideas were discussed during this meeting between BMW, VW, PSA, Visteon, Continental, Intel, KDDI, LG, Magneti Marelli, QNX, Ford, Strategy Analytics, Genivi and W3C with agreement on next steps to prepare the next face to face meeting in Tokyo (29 May).

In particular:

  • A first round of proposals for a Web Vehicle API was discussed, with proposals from Intel, QNX, Genivi (LG) and Webinos.
  • The group decided to first focus on an API that would provide read access.

Decision on next steps include:

  • Creating an overview of the superset of the proposed Vehicle APIs to look for overlaps and gaps.
  • Considering whether the mandatory dataset provided in OBDII could serve as a starting point for a common dataset to be shared by different OEMs via a Vehicle API.
  • Creating a document that maps current W3C work onto the requirements of the automotive sector (e.g. geolocation, packaging, …).

Don’t miss the opportunity to drive the automotive technology evolution, join the W3C Automotive and Web Platform Business Group.

Join First AutoWeb Face to Face Meeting in Barcelona (April 22)

Following the first conference call organized, the next step is a Face to Face meeting to move on the Business group activities.

F2F meeting in Barcelona:
Monday April 22
This is the same venue as the GENIVI All Members Meeting
GENIVI is sponsoring this F2F meeting. Thank you to GENIVI!
Time: 12 noon until 9 or 10pm

See also the Proposed Agenda

For full and final details please check the relevant wiki page 

These Face to Face meetings will be restricted to Business Group participants with the Business Group Agreement finalized or in process to be finalized.
Any question, support, contact Alan Bird (abird@w3.org) or Bernard Gidon (bgidon@w3.org)

To register, please use this registration form

This next step is the starting point of this Automotive Business Group activities, DON’T MISS IT

A second face-to-face meeting is planned for May 29 in Tokyo at the same venue as the Automotive Linux Summit and LinuxCon – more details on the relevant wiki page

1st Conf Call – Tues/Wed 3/26 & 3/27

Hi all,

I wanted to quickly schedule a couple of conf calls. Both will be scheduled for next week (one to cover Europe and one to cover APAC). Details are on our wiki under the current events page on the left hand side. If you would like me to send you the calendar appointment, please send me an email (address below).

Also, please notice I’m also suggesting that we add a F2F meeting in Tokyo during the Automotive Linux Summit and LinuxCon. My rationale for this is to cover both Europe and APAC since we have participants from both geos.

Conf Call #1: Tuesday, March 26, 2013 9:00 AM US Pacific Time
Conf Call #2: Tuesday, March 26, 2013 9:00 PM US Pacific Time

If you have additional topics please send me an email at adam . m . abramski at intel . com

Talk to you all next week,
Adam

Welcome to the W3C Automotive and Web Platform Business Group from Adam Abramski

Since a lot of new participants have joined since Adam sent this mail, and some folks have reported difficulties finding it, I am reposting the following as a blog entry.
It is also archived in the archive of the public mailing list.