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.
The REST Services Interface (RSI – formerly VIWI) Task Force has been meeting regularly. We would like to see more participation especially in implementing the specification to prove it out. Please check out the RSI Task Force Wiki. We are in the process of scheduling regular meetings.
Here is quick summary of RSI:
Volkswagen submitted RSI to the W3C, in December of 2016, as it is in-line with the HTML5 and “services” direction the Automotive Working Group and Automotive and Web Platform is pursuing. The following domains were part of the initial submission:
The RSI work is focused on guidelines and rules for designing REST APIs that are extended with a WebSocket subscribe mechanism for delivering high frequency data, avoiding polling. The Protocol specification describes the main REST/WebSocket model with the Domain specifications defining domain specific information models.
An open reference server implementation and framework can be found here and may be used for implementations. Ideally code will be committed back to this repository.
The Task Force plans on focusing on Media and Location Based Services (LBS) domains to start with academic papers for LBS in the works.
Please join us by reaching out to the group, following the group, following the GitHub repositories, and following us on Twitter #w3cauto.
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.***