|End date||June 2016|
|Confidentiality||Proceedings are Public|
|Initial Chairs|| Paul Boyes, OpenCar
Adam Abramski, Intel
| Initial Team Contacts
(FTE %: 20)
| Kazuyuki Ashimura (10%), Ted Guild
|Usual Meeting Schedule|| Teleconferences: topic-specific calls
can/may be held
Face-to-face: we will meet during the W3C's annual Technical Plenary week with other additional F2F meetings may be scheduled on an as needed basis
The group will develop APIs to expose vehicle data and information from an automotive network bus(es) (e.g. MOST (Media Oriented Systems Transport) or CAN (Controller Area Network)) to a Web application. The APIs will expose information like the vehicle brand, model, year, fuel type, transmission type, steering wheel position, tire pressure, oil level, wiper position, lights, doors, windows and seat settings as well as navigation, trip computer data, climate control data, speed, rpms, acceleration, gears and other vehicle sensors.
As the variety and types of information that are generated from vehicles varies from OEM (car manufacturer) to OEM it is expected that this specification will be broken into two parts: a Vehicle Information Specification containing durable, unchanging access methods for obtaining vehicle information; and a Vehicle Data Specification to specify agreed upon standardized data elements as well as the method for extending data elements to OEM specific elements. Initially these specifications will be limited to passenger vehicles. How an implementation obtains this data is not in the scope of the group.
The specification(s) produced by this Working Group will include security and privacy considerations. The APIs developed by this group may use a different security model than the traditional browser security model.
Members of the Working Group should review other working groups' deliverables that are identified as being relevant to the Working Group's mission.
To advance to Proposed Recommendation, each specification is expected to have two independent implementations of each feature defined in the specification(s). The implementation(s) should demonstrate the interoperability between them such that the web application running on either implementation should render the same data and data values with the same functionality.
This Working Group will not define or mandate implementation details including vehicle, network or sensor protocols for sharing data between the vehicle data network and sensors. The vehicle data bus network and protocols are OEM specific and vary from vehicle to vehicle.
However, to facilitate interoperability among vehicle OEMs and encourage adoption of the API, the group may informatively reference existing suites of protocols, either directly in the Vehicle API deliverable(s) or in a non-normative companion Note.
The working group will deliver at least the following specification:
The working group may decide to group the API functions in one or more specifications as they see fit.
|Note: The group will document significant changes from this initial schedule on the group home page (link to be added once group approved).|
||Q1 2015||Q3 2015||Q1 2016||Q3 2016||Q3 2016|
The Working Group expects to maintain contacts with at least the following groups and Activities within W3C (in alphabetical order) and ask for reviews of deliverables where appropriate:
The following is a tentative list of external bodies the Working Group should collaborate with:
To be successful, the Automotive Vehicle API Working Group is expected to have 10 or more active participants for its duration, and to have the participation of industry leaders in fields relevant to the specifications it produces.
Effective participation to Automotive Vehicle API Working Group is expected to consume one fifth of a full-time employee for each participant and two fifths of a full-time employee for editors. Chairing the group is expected to take two fifth of a full-time employee. This Working Group will also allocate the necessary resources for building Test Suites for each specification.
Teleconferences will be conducted on an as-needed basis.
This group primarily conducts its work on the public mailing list email@example.com. Administrative tasks may be conducted in Member-only communications.
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the Automotive Working Group home page.
As explained in the W3C Process Document (section 3.3), this group will seek to make decisions when there is consensus and with due process. The expectation is that typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs should put a question out for voting within the group (allowing for remote asynchronous participation -- using, for example, email and/or web-based survey techniques) and record a decision, along with any objections. The matter should then be considered resolved unless and until new information becomes available.
Any resolution taken in a face-to-face meeting or teleconference is to be considered provisional until 10 working days after the publication of the resolution in draft minutes sent to the working groups mailing list. If no objections are raised on the mailing list within that time, the resolution will be considered to have consensus as a resolution of the Working Group.
This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This charter for the Automotive Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.